Display driver crashes, BUGCODE_USB_DRIVER, nvmfdx32.dll errors

Glonk

Junior Member
Apr 5, 2001
21
0
0
It's 3:20am here and I'm exhausted, so I apologize if this doesn't make a whole lot of sense:

First my specs:
Intel Core 2 Extreme QX6700 (@ stock speeds/volts)
ASUS Striker Extreme (680i SLI) motherboard
4GB PC8500 RAM @ stock SPD speeds/volts)
eVGA GeForce 8800 Ultra
Windows Vista Ultimate, 32-bit
Corsair 620W PSU

I built this system in early June and I've not had any problems like this before with it. But I left it on last night to download some files. When I came to the computer in the morning, the computer was still powered on but the IDE activity light did not flicker (which is strange for something supposedly downloading), and wiggling the mouse or pressing the keyboard would not shake the computer out of powersaving mode. I manually turned the computer off (pressed the button for 10 seconds), then on again.

It appears as though the display driver crashes every 10 seconds or so. The screen will go black for 3-4 seconds (but the mouse cursor is still visible and moves...), then when Windows restores itself there's a little yellow triangle with a '!' mark in it, but there's no tooltip or any mouseover information for it. Disabling Aero and using Windows Classic did not fix this either.

What follows was a comedy of errors in trying to fix the problem. I updated my Nvidia drivers to the latest WHQL versions from www.nvidia.com (162.xx). This didn't solve anything, and actually at the same time I got a plethora of other errors. Many BSODs with different errors: nvmfdx32.dll crashes (Nvidia MCP networking driver?), BUGCODE_USB_DRIVER BSOD (I presume this is also motherboard related?), and lots of IRQL_NOT_LESS_THAN_EQUAL for unnamed drivers. And total system freezes, also.

I opened up the system and found out the 120mm case fan I have to circulate air to the powersupply was not working (I have an Antec P182 case, the PSU is at the bottom of the unit in its own thermal compartment). I had another 120mm fan, so I swapped it out and the new one works. I booted up the computer and, for 20 minutes, all was well. I thought I found my problem: the PSU overheated which caused system instability.

But that was a red herring. The thing is barely warm to the touch after those 20 minutes and the errors occured again. In fact, the entire system is reporting normal, quite low temperatures...so nothing is overheating.

Within a day, it went from being functional to the constant display driver crashes to perpetual system instability due to BSODs and system freezes. I've tried every combination of driver uninstalls/reinstalls with all kinds of versions from latest versions to older versions, and nothing is solving this. It's progressively getting worse, now not only does the display driver die, but I see some screen corruption as well. Portions of the screen remain black first, while others are not, then the whole thing is black, then it's an extremely zoomed in pixelated version of my desktop.

I've no idea what to do next. How can I find out what's causing the system to die a death of a thousand cuts?

Tomorrow I will try reinstalling Vista, but is there anything else anyone can suggest? I appreciate any and all help...thanks,

Dave
 

Mem

Lifer
Apr 23, 2000
21,476
13
81
Try running with 2GB of ram,does stability improve?..Also run Memtest86+ to test your ram.

Memtest86+ homepage ,you can make a bootable CD or floppy from their site.


Memtest86+ is actually better then Vista's built-in memory tester,one guy in a different forum used Vista's one and it passed clean,when he used Memtest86+ it found 100s of errors,faulty ram in his case.
 

Glonk

Junior Member
Apr 5, 2001
21
0
0
Mem: Thanks for the reply.

I ran memtest86 a couple months ago when I first set it up and all was good. I'll try removing some of the RAM and trying it again tomorrow.

Just an update with perhaps more information: I had left the PC off last night and turned it on again at around 2pm today. The machine worked flawlessly, but not under a lot of stress -- again, just downloading some torrents. About half an hour ago (after ~8 hours of being on without problems), I ran Nero Recode to transcode a video I downloaded from XViD to MPEG-4. It transcoded it just fine in short order, but right afterwards the display-flicker and display driver crashing started occuring again. I checked out the temperatures, and they're all low (CPU: ~44C, GPU: ~65C, case: ~30C, HDD: ~42C.) I checked to ensure all my fans were working (they are). I touched the powersupply and it was barely warm, certainly not hot.

But I did notice that the fan built into my Corsair 620W PSU wasn't doing much at all, but it was spinning. Very low airflow.

I opened up my case and pointed a fan at it, and after 20 minutes it's still erroring up. If I shut down the computer for the night, I bet the same behaviour can happen tomorrow (we'll see).
 

Glonk

Junior Member
Apr 5, 2001
21
0
0
Update:

I turned my computer on when I got home at ~6pm last night. It downloaded torrents until about 10pm without issues. I then made it batch-encode a bunch of videos, which took about an hour (using all cores and all that). I then watched an HD video for about 30 minutes. The computer was still fine, no errors. Thought I was home free.

I left the computer on overnight to keep downloading. When I checked it at ~8am, it had its first "video crash" within a few seconds. It didn't occur overnight because there was no icon in the tray, but as I used it, it did its crash thing (black screen, reload) 3 times within about 45 seconds. The computer itself is not crashing at this time, just the display.
 

melzar

Junior Member
Oct 16, 2007
3
0
0
Hi,

I was wondering if you had found the cause or a solution to your problem, as I have a very similar rig to yours and am experiencing almost the same thing. It usually runs fins under a low load, however if I try to play a game (eg. LostPlanet, Oblivion), it will either freeze (no response from keyboard/mouse inputs, but with sound still playing in a fragmented loop), or blue screen with the BUGCODE_USB_DRIVER error. I've updated XP, BIOS, graphics & sound drivers to latest versions without any apparent success. Running memtest86 also turned up clean. Any help or insight is greatly appreciated.
My specs:
Case: Antec P182
Mobo: Asus Striker Extreme
CPU: Core2 Duo E6700
GPU: XFX GeForce 8800GTX
Sound: Creative SoundBlaster X-Fi Fatal1ty FPS
RAM: Crucial BALLISTIX DDR2 800 PC6400 2GB(1GBx2)
PSU: PC Power & Cooling Silencer 750 Quad
OS: Win XP Pro
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
Debug the dump; see the URL in my .sig for full details. Post the output of !analyze -v here for all to see.
 

melzar

Junior Member
Oct 16, 2007
3
0
0
I've included the last 2 dumps (crashed twice yesterday) with BUGCODE_USB_DRIVER BSODs, and I've also included a random DRIVER_IRQL_NOT_LESS_OR_EQUAL crash which I also see now and then. I also had another system freeze last night (upon running the MS Debugger!), which didn't result in a BSOD (or a Minidmp), but required a hard reboot.

My system also has a Logitech G15 keyboard and Logitech Revolution MX mouse, both of which have the latest drivers/software installed.


Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini103007-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\debug*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Tue Oct 30 13:21:28.625 2007 (GMT+9)
System Uptime: 0 days 1:17:48.250
Loading Kernel Symbols
............................................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {5, 8a1030e0, 10de036d, 8723e180}



Probably caused by : usbehci.sys ( usbehci!EHCI_PollActiveAsyncEndpoint+37 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: 8a1030e0, Device extension pointer of the host controller
Arg3: 10de036d, PCI Vendor,Product id for the controller
Arg4: 8723e180, Pointer to Endpoint data structure

Debugging Details:
------------------




CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xFE

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from b9ccecc3 to 804f9deb

STACK_TEXT:
8055026c b9ccecc3 000000fe 00000005 8a1030e0 nt!KeBugCheckEx+0x1b
8055028c b9cdb516 8a103028 00000fd0 88461000 USBPORT!USBPORT_BugCheck+0x2d
805502c8 bac8b3dd 075a65a0 8a1039dc 8723e180 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x126
805502ec bac8b8a6 8a1039dc 8723e180 8723e180 usbehci!EHCI_PollActiveAsyncEndpoint+0x37
80550348 bac8d3d3 8a1039dc 8723e180 80550378 usbehci!EHCI_PollAsyncEndpoint+0x98
80550358 b9cc82ba 8a1039dc 8723e180 80545d0c usbehci!EHCI_PollEndpoint+0x1f
80550378 b9cc9578 026c6f50 8a1030e0 8723e008 USBPORT!USBPORT_PollEndpoint+0xe8
805503a0 b9ccced0 8a103028 50457270 80545d0c USBPORT!USBPORT_CoreEndpointWorker+0x2be
805503d0 b9cdafb0 8a103028 80545d0c 8a103028 USBPORT!USBPORT_DpcWorker+0x18a
8055040c b9cdb128 8a103028 00000001 8055b0a0 USBPORT!USBPORT_IsrDpcWorker+0x37e
80550428 805450bf 8a10364c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
80550440 8055ae40 ffdffc50 00000000 8055ae40 nt!KiRetireDpcList+0x61
80550450 80544fa4 00000000 0000000e 00000000 nt!KiIdleThread0
80550454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


STACK_COMMAND: kb

FOLLOWUP_IP:
usbehci!EHCI_PollActiveAsyncEndpoint+37
bac8b3dd 50 push eax

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: usbehci!EHCI_PollActiveAsyncEndpoint+37

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: usbehci

IMAGE_NAME: usbehci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107d62

FAILURE_BUCKET_ID: 0xFE_usbehci!EHCI_PollActiveAsyncEndpoint+37

BUCKET_ID: 0xFE_usbehci!EHCI_PollActiveAsyncEndpoint+37

Followup: MachineOwner
---------

****************************************************************************************

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini103007-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\debug*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sun Oct 28 08:51:11.390 2007 (GMT+9)
System Uptime: 1 days 11:40:52.012
Loading Kernel Symbols
...........................................................................................................................................
Loading User Symbols
Loading unloaded module list
............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {5, 8a1300e0, 10de036c, 8819e828}



Probably caused by : usbohci.sys ( usbohci!OHCI_PollAsyncEndpoint+41 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: 8a1300e0, Device extension pointer of the host controller
Arg3: 10de036c, PCI Vendor,Product id for the controller
Arg4: 8819e828, Pointer to Endpoint data structure

Debugging Details:
------------------




CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xFE

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from b9ccecc3 to 804f9deb

STACK_TEXT:
805502c0 b9ccecc3 000000fe 00000005 8a1300e0 nt!KeBugCheckEx+0x1b
805502e0 b9cdb516 8a130028 00000fd0 88251000 USBPORT!USBPORT_BugCheck+0x2d
8055031c bac818f3 00000000 8a1309dc 8819e828 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x126
80550348 bac82bc9 8a1309dc 8819e828 80550378 usbohci!OHCI_PollAsyncEndpoint+0x41
80550358 b9cc82ba 8a1309dc 8819e828 80545d0c usbohci!OHCI_PollEndpoint+0x1f
80550378 b9cc9578 026c6f50 8a1300e0 8819e6b0 USBPORT!USBPORT_PollEndpoint+0xe8
805503a0 b9ccced0 8a130028 50457270 80545d0c USBPORT!USBPORT_CoreEndpointWorker+0x2be
805503d0 b9cdafb0 8a130028 80545d0c 8a130028 USBPORT!USBPORT_DpcWorker+0x18a
8055040c b9cdb128 8a130028 00000001 8055b0a0 USBPORT!USBPORT_IsrDpcWorker+0x37e
80550428 805450bf 8a13064c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
80550440 8055ae40 ffdffc50 00000000 8055ae40 nt!KiRetireDpcList+0x61
80550450 80544fa4 00000000 0000000e 00000000 nt!KiIdleThread0
80550454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


STACK_COMMAND: kb

FOLLOWUP_IP:
usbohci!OHCI_PollAsyncEndpoint+41
bac818f3 ff7038 push dword ptr [eax+38h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: usbohci!OHCI_PollAsyncEndpoint+41

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: usbohci

IMAGE_NAME: usbohci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107d62

FAILURE_BUCKET_ID: 0xFE_usbohci!OHCI_PollAsyncEndpoint+41

BUCKET_ID: 0xFE_usbohci!OHCI_PollAsyncEndpoint+41

Followup: MachineOwner
---------

*********************************************************************

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini102207-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\debug*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Oct 22 12:12:07.765 2007 (GMT+9)
System Uptime: 0 days 11:49:14.503
Loading Kernel Symbols
.............................................................................................................................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {60, 2, 0, bac934df}



Probably caused by : usbehci.sys ( usbehci!EHCI_PollActiveAsyncEndpoint+139 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000060, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: bac934df, address which referenced memory

Debugging Details:
------------------




READ_ADDRESS: 00000060

CURRENT_IRQL: 2

FAULTING_IP:
usbehci!EHCI_PollActiveAsyncEndpoint+139
bac934df ff7660 push dword ptr [esi+60h]

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from bac938a6 to bac934df

STACK_TEXT:
805502ec bac938a6 8a1169dc 01c234e0 86c234e0 usbehci!EHCI_PollActiveAsyncEndpoint+0x139
80550348 bac953d3 8a1169dc 86c234e0 80550378 usbehci!EHCI_PollAsyncEndpoint+0x98
80550358 b9cc82ba 8a1169dc 86c234e0 80545d0c usbehci!EHCI_PollEndpoint+0x1f
80550378 b9cc9578 026c6f50 8a1160e0 86c23368 USBPORT!USBPORT_PollEndpoint+0xe8
805503a0 b9ccced0 8a116028 50457270 80545d0c USBPORT!USBPORT_CoreEndpointWorker+0x2be
805503d0 b9cdafb0 8a116028 80545d0c 8a116028 USBPORT!USBPORT_DpcWorker+0x18a
8055040c b9cdb128 8a116028 00000001 8055b0a0 USBPORT!USBPORT_IsrDpcWorker+0x37e
80550428 805450bf 8a11664c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
80550440 8055ae40 ffdffc50 00000000 8055ae40 nt!KiRetireDpcList+0x61
80550450 80544fa4 00000000 0000000e 00000000 nt!KiIdleThread0
80550454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


STACK_COMMAND: kb

FOLLOWUP_IP:
usbehci!EHCI_PollActiveAsyncEndpoint+139
bac934df ff7660 push dword ptr [esi+60h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: usbehci!EHCI_PollActiveAsyncEndpoint+139

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: usbehci

IMAGE_NAME: usbehci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107d62

FAILURE_BUCKET_ID: 0xD1_usbehci!EHCI_PollActiveAsyncEndpoint+139

BUCKET_ID: 0xD1_usbehci!EHCI_PollActiveAsyncEndpoint+139

Followup: MachineOwner
---------

 

melzar

Junior Member
Oct 16, 2007
3
0
0
These blue screens popup somewhat randomly. I've had them occur before the windows welcome screen, on the welcome screen, right after logon, and conversely, sometimes it takes 1 day, sometimes I will leave the computer on overnight, and when I come back in the morning I am greeted by a blue screen (even if I haven't left any programs running).