Windows XP x64 crashdump problem

device driver

    Sponsored Links

    Next

  • 1. diskless NT family OS
    hi all i want to implement booting diskess nt family os (nt/2k/xp/2003) just like booting 98 using pxe. assume that i'm familiar with ndis, file system driver and pxe. any idea, document or source is appreciated. thanks for ur attention. Nick
  • 2. Cleanup after IoBuildAsynchronousFsdRequest
    Oney's books has a loop to clean up the MDLs then the IoFreeIrp ... The MS samples have something like: if (Irp->MdlAddress != NULL) { MmUnlockPages(Irp->MdlAddress); IoFreeMdl(Irp->MdlAddress); Irp->MdlAddress = NULL; } So this generates two questions: 1) Is MmUnlockPages required in the completion routine of a IRP created with IoBuildAsynchronousFsdRequest? 2) Does IoFreeMdl take care of freeing all MDL's in the chain? TIA!!
  • 3. Automatic installation for a WDM driver
    Hi! I have a driver + inf for a PCI CARD . I would like install them automatically (Even without the presence of the Card). When I say automatically, I mean bring a disk with the two files (sys + inf), run some batch file or executable, and that's it. How can this be done ? Thanks Maurice

Windows XP x64 crashdump problem

Postby Scott » Sun, 07 Aug 2005 00:55:23 GMT

I have a SCSI HBA serving as the boot controller in a dual processor 
hyper-threaded system running WinXP x64 edition. Upon generating a crash via 
Crash-On-Ctrl-Scroll or the HCT crashdumptest, I have seen proof via WinDbg 
that the runtime (miniport) driver is still running when the crashdump 
driver is being loaded. Specifically, I have seen an interrupt generated 
during crashdump initialization get serviced by the runtime driver. I have 
also seen the one second timer I have continue to run on the runtime driver. 
No need to explain what a driver collision like this can do to the hardware. 
If I disable hyper-threading and one of the processors, the problem goes 
away. Why isn't crashdump processing disabling the other processors?

Thanks

Scott



Re: Windows XP x64 crashdump problem

Postby James Antognini [MSFT] » Fri, 12 Aug 2005 06:04:07 GMT

"Being loaded" isn't the same as having control. Obviously, 2 instances of a 
miniport shouldn't have control concurrently. So please clarify that point.

Second, are you saying that the original miniport instance "saw" the timer 
expiration (eg, in a DPC) after the second instance got control at least 
once? Are you sure that what got control was the first instance, namely, at 
an address in the executable of the first instance?

-- 
James Antognini
Windows DDK and WDK Support


This posting is provided "AS IS" with no warranties, and confers no rights.










Similar Threads:

1.Using Windows XP x64 Drivers with Windows Server 2003 x64

Can anyone out there tell me if the Windows XP x64 dfrivers will work on 
Windows Server 2003 x64? I want to load a x64 windows OS so that it can host 
Virtual Server 2005 R2 . I want to use Windows Server 2003 x64 but my 
motherboard (Intel D955XBKLKR 955XE with Intel 830 dual-core processor) only 
has all the Windows XP x64 drivers. Has anyone installed Windows Server 2003 
on this motherboard? Your assistance is very much appreciated. Thanks...

Orgbrat 


2.Windows XP Pro x64 Edition driver problems...yes I know:)

Well I got x64 on friday the 22nd at about 4:30pm
found drivers for Soundblaster Audigy Gamer....beta till mid august
Nvidia Geforce 5900SE ....Nvidia Website not WHQL ...but soon
no codec for Mp3 ripping...got to wait
no drivers for Logitech Quickcam 4000 pro....and no info on it
no drivers for  LNE100TX linksys pci network card....weird and no info
and biggest suprise......the transfer wizard does not transfer the files for 
my other drive....whats up with that?   says it cannot find the data....any 
help with getting my data off the img files would be helpful
 XXXX@XXXXX.COM 
thanks

3.Windows XP X64 development env

I am using WDK 6000. I dont see anything like Windows XP 64-bit WDK
env. I only see Windows Vista X64 and Windows Server 2003 X64. Can I
compile using Windows Server 2003 X64 for Windows XP X64 driver? What
should I do for getting a driver in Windows XP X64?

Thanks.

4.Driver installation on Windows XP x64

Hello,

I have a driver built for Windows 2003 Server x64 using WDK version 
6001.18001. This driver I have successfully installed in Windows Vista x64. 
For this I had to do the testsigning procedure as described in the selfsign 
chapter of the WDK. Now, for testing reasons, I tried to do the same 
procedure in Windows XP x64 except calling "bcdedit -set TESTSIGNING ON" as 
this feature is not available in Windows XP. But in Windows XP the driver is 
not properly installed. After installation I get an error message from the 
hardware wizard with code 39.
In the setupapi.log I get an entry that the device cannot been started 

Here the setupapi.log entry:
#-198 Command line processed: "C:\WINDOWS\system32\mmc.exe" 
C:\WINDOWS\system32\devmgmt.msc
#I060 Set selected driver.
#-019 Searching for hardware ID(s): 
usb\vid_174a&pid_0105&rev_0001,usb\vid_174a&pid_0105
#-018 Searching for compatible ID(s): 
usb\class_ff&subclass_bc&prot_ff,usb\class_ff&subclass_bc,usb\class_ff
#-019 Searching for hardware ID(s): 
usb\vid_174a&pid_0105&rev_0001,usb\vid_174a&pid_0105
#-018 Searching for compatible ID(s): 
usb\class_ff&subclass_bc&prot_ff,usb\class_ff&subclass_bc,usb\class_ff
#-019 Searching for hardware ID(s): 
usb\vid_174a&pid_0105&rev_0001,usb\vid_174a&pid_0105
#-018 Searching for compatible ID(s): 
usb\class_ff&subclass_bc&prot_ff,usb\class_ff&subclass_bc,usb\class_ff
#I022 Found "USB\VID_174A&PID_0105" in e:\treiber64\rxusbd\rxusbd.inf; 
Device: "RXUSBD"; Driver: "RXUSBD"; Provider: "E+H"; Mfg: "E+H"; Section 
name: "RXUSBD_Inst".
#I087 Driver node not trusted, rank changed from 0x00000001 to 0x00008001.
#I023 Actual install section: [RXUSBD_Inst.NT]. Rank: 0x00008001. Driver 
date: 02/06/2009. Version: 1.0.0.1.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [RXUSBD_Inst] in 
"e:\treiber64\rxusbd\rxusbd.inf".
#I320 Class GUID of device remains: {36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "USB\VID_174A&PID_0105\5&1BA8E393&0&2".
#W366 An unsigned, incorrectly signed, or Authenticode(tm) signed file 
"e:\treiber64\rxusbd\rxusbd.cat" for driver "RXUSBD" will be installed 
(Policy=Warn, user said ok). Error 0x800b0109: Eine Zertifikatkette wurde 
zwar verarbeitet, endete jedoch mit einem Stammzertifikat, das beim 
Vertrauensanbieter nicht als vertrauensw眉rdig gilt.
#-024 Copying file "e:\treiber64\rxusbd\amd64\rxusbd.sys" to 
"C:\WINDOWS\system32\DRIVERS\rxusbd.sys".
#W362 An unsigned, incorrectly signed, or Authenticode(tm) signed file 
"e:\treiber64\rxusbd\amd64\rxusbd.sys" for driver "RXUSBD" will be installed 
(Policy=Warn). Error 0x800b0109: Eine Zertifikatkette wurde zwar verarbeitet, 
endete jedoch mit einem Stammzertifikat, das beim Vertrauensanbieter nicht 
als vertrauensw眉rdig gilt.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [RXUSBD_Inst.NT.Interfaces] from 
"e:\treiber64\rxusbd\rxusbd.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\VID_174A&PID_0105\5&1BA8E393&0&2".
#W362 An unsigned, incorrectly signed, or Authenticode(tm) signed file 
"e:\treiber64\rxusbd\rxusbd.cat" for driver "RXUSBD" will be installed 
(Policy=Warn). Error 0x800b0109: Eine Zertifikatkette wurde zwar verarbeitet, 
endete jedoch mit einem Stammzertifikat, das beim Vertrauensanbieter nicht 
als vertrauensw眉rdig gilt.
#I163 Device not started: Device has problem: 0x27: 
CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of "USB\VID_174A&PID_0105\5&1BA8E393&0&2" finished 
successfully.

Any idea what I can do?


5.windows driver for XP x64

Hi folks,

I am developing windows para-virtual drivers for Xen. I meet some problems 
when building windows drivers for XP x64 edition. I know that WDK upper 6000 
has not get a build environment for XP x64 edition. WDK 6000 release note 
tells me that ' Use the Windows Server 2003 x64 build environment icons to 
build free or checked x64 drivers for windows XP'. So I just copy windows 
2003 x64 driver binary to XP x64 folder of my driver installer. But when I 
use windows 2003 x64 driver binary on XP x64, there are lots of bugs which I 
cannot reproduce on windows 2003 x64 system. Is there anything wrong when I 
use windows 2003 x64 driver binary on XP x64 system?

Another problem is that I cannot get any debug output on XP x64 with windbg. 
When I connect a debug mode XP x64 with windbg, windbg cannot get any driver 
debug output from KdPrint and XP x64 cannot boot up. It just hangs at windows 
XP start screen. This won't happen on windows server 2003. Anything I forget?
-- 
Wayne

6. Driver for windows xp x64 professional edition??????

7. drivers for windows xp x64

8. Windows XP x64 and WM_DEVICECHANGE



Return to device driver

 

Who is online

Users browsing this forum: No registered users and 12 guest