VitoCapo
asked on
BSOD "The Device Driver got stuck in an infinite loop" Little Video help?
Ok, my brain hurts trying to fix this one.
I'll put the hardware info below but here's the summary...
I have an MSI motherboard (ATI RS480M2 chipset). 1 Gig of RAM, AMD Athlon processor, 120gig SATA drive, Windows XP Professional. All drivers including BIOS are completely up to date. Windows updates fully up to date as well.
My problem begins with the video.
Originally I had an ATI Radeon X300 SE 256meg (PCI-Express) installed. Whenever hardware acceleration was used it would eventually end up bluescreening or restarting on me. Referrencing "the device driver got stuck in an infinite loop" if a blue screen was displayed at all.
Like a good little techie I attacked the problem with repeated driver reinstalations, beta drivers, etc.. seat and reseated the card, scoured MS Support, etc. Eventually I decided the card must be conflicting with the onboard ATI card (which I then disabled through bios). Eventually I decided to replace the card with an NVidia GForce 6600 256meg PCI-Express.
So, I formatted my harddrives, did a complete reinstall of Windows XP professional, installed all the patches updates and drivers for the hardware/software. Installed a game to see if the problem was resolved......
"The Device Driver got stuck in an infinite Loop"
"STOP: 0x000000EA (0x8564DA30, 0x865DFE38, 0xF7A43CB4, 0x00000001)"
So even with a brand new video card I am experiencing the same problem. Obviously it's not the Video Cards... any suggested ways to proceed?
500 points to anyone who can figure this one out.
Detailed system info found below.....
System Information:::
Bios Info:::
Name : Phoenix - Award BIOS v6.00PG
Manufacturer : Phoenix Technologies, LTD
Version : RS480 - 42302e31
ReleaseDate : 07 / 21 / 2005
Status : OK
CPU:::
Name : AMD Athlon(tm) 64 Processor 3000+
Description: x86 Family 15 Model 47 Stepping 0
Manufacturer : AuthenticAMD
Version : Model 15, Stepping 0
DataWidth : 32 Bits
Socket Designation : Socket 939
Type : Central Processor
CPU Id : 078BFBFF00020FF0
CPU Family : Unknown
CPU Stepping : 0
Load Percentage : 8 %
Max ClockSpeed : 1790 MHz
Current ClockSpeed : 1790 MHz
Voltage : 1.4 V
External Clock : 199 MHz
Upgrade Method : undefined
L2 Cache Size : 21072 Kb
Display Availability : Running/Full Power
PowerManagement Supported : false
Status : OK
Memory::::
Name : Physical Memory
Memory Capacity : 512MB
Memory BankLabel : Bank0/1
Memory TotalWidth : 64 Bits
DataWidth : 64 Bits
Memory DeviceLocator : A0
Memory Type : Unknown
Name : Physical Memory
Memory Capacity : 512MB
Memory BankLabel : Bank2/3
Memory TotalWidth : 64 Bits
DataWidth : 64 Bits
Memory DeviceLocator : A1
Memory Type : Unknown
Motherboard::::
Name : Base Board
Product Name : MS-7093
Video Card::::
Name : NVIDIA GeForce 6600
Display Availability : Running/Full Power
Video Mode : 1024 x 768 x 4294967296 colors
Adapter DAC Type : Integrated RAMDAC
Current Horizontal Resolution : 1024 Pixels
Current Vertical Resolution : 768 Pixels
Current Number Of Colors : 4294967296
Adapter RAM : 256 MB
Current Refresh Rate : 60 Hertz
Video Processor : GeForce 6600
Inf Filename : oem1.inf
Driver Version : 6.14.10.8198
Monochrome : false
Installed Display Drivers : nv4_disp.dll
Status : OK
I'll put the hardware info below but here's the summary...
I have an MSI motherboard (ATI RS480M2 chipset). 1 Gig of RAM, AMD Athlon processor, 120gig SATA drive, Windows XP Professional. All drivers including BIOS are completely up to date. Windows updates fully up to date as well.
My problem begins with the video.
Originally I had an ATI Radeon X300 SE 256meg (PCI-Express) installed. Whenever hardware acceleration was used it would eventually end up bluescreening or restarting on me. Referrencing "the device driver got stuck in an infinite loop" if a blue screen was displayed at all.
Like a good little techie I attacked the problem with repeated driver reinstalations, beta drivers, etc.. seat and reseated the card, scoured MS Support, etc. Eventually I decided the card must be conflicting with the onboard ATI card (which I then disabled through bios). Eventually I decided to replace the card with an NVidia GForce 6600 256meg PCI-Express.
So, I formatted my harddrives, did a complete reinstall of Windows XP professional, installed all the patches updates and drivers for the hardware/software. Installed a game to see if the problem was resolved......
"The Device Driver got stuck in an infinite Loop"
"STOP: 0x000000EA (0x8564DA30, 0x865DFE38, 0xF7A43CB4, 0x00000001)"
So even with a brand new video card I am experiencing the same problem. Obviously it's not the Video Cards... any suggested ways to proceed?
500 points to anyone who can figure this one out.
Detailed system info found below.....
System Information:::
Bios Info:::
Name : Phoenix - Award BIOS v6.00PG
Manufacturer : Phoenix Technologies, LTD
Version : RS480 - 42302e31
ReleaseDate : 07 / 21 / 2005
Status : OK
CPU:::
Name : AMD Athlon(tm) 64 Processor 3000+
Description: x86 Family 15 Model 47 Stepping 0
Manufacturer : AuthenticAMD
Version : Model 15, Stepping 0
DataWidth : 32 Bits
Socket Designation : Socket 939
Type : Central Processor
CPU Id : 078BFBFF00020FF0
CPU Family : Unknown
CPU Stepping : 0
Load Percentage : 8 %
Max ClockSpeed : 1790 MHz
Current ClockSpeed : 1790 MHz
Voltage : 1.4 V
External Clock : 199 MHz
Upgrade Method : undefined
L2 Cache Size : 21072 Kb
Display Availability : Running/Full Power
PowerManagement Supported : false
Status : OK
Memory::::
Name : Physical Memory
Memory Capacity : 512MB
Memory BankLabel : Bank0/1
Memory TotalWidth : 64 Bits
DataWidth : 64 Bits
Memory DeviceLocator : A0
Memory Type : Unknown
Name : Physical Memory
Memory Capacity : 512MB
Memory BankLabel : Bank2/3
Memory TotalWidth : 64 Bits
DataWidth : 64 Bits
Memory DeviceLocator : A1
Memory Type : Unknown
Motherboard::::
Name : Base Board
Product Name : MS-7093
Video Card::::
Name : NVIDIA GeForce 6600
Display Availability : Running/Full Power
Video Mode : 1024 x 768 x 4294967296 colors
Adapter DAC Type : Integrated RAMDAC
Current Horizontal Resolution : 1024 Pixels
Current Vertical Resolution : 768 Pixels
Current Number Of Colors : 4294967296
Adapter RAM : 256 MB
Current Refresh Rate : 60 Hertz
Video Processor : GeForce 6600
Inf Filename : oem1.inf
Driver Version : 6.14.10.8198
Monochrome : false
Installed Display Drivers : nv4_disp.dll
Status : OK
ASKER
Here's the Minidump file:
http://rapidshare.de/files/12649288/Mini020506-03.dmp.html
Eventlog.... (these errors are not recorded consistently but this is the only info that shows in System log. Application log is clean and squekey.
Source: nv
Event ID: 108
Description:
The driver nv4_disp for the display device \Device\Video0 got stuck in an infinite loop. This usually indicates a problem with the device itself or with the device driver programming the hardware incorrectly. Please check with your hardware device vendor for any driver updates.
Additional Error's:
Source: System Error
Event ID: 1003
Description:
Error code 100000ea, parameter1 858d4548, parameter2 85bc35f8, parameter3 f7a3fcb4, parameter4 00000001.
http://rapidshare.de/files/12649288/Mini020506-03.dmp.html
Eventlog.... (these errors are not recorded consistently but this is the only info that shows in System log. Application log is clean and squekey.
Source: nv
Event ID: 108
Description:
The driver nv4_disp for the display device \Device\Video0 got stuck in an infinite loop. This usually indicates a problem with the device itself or with the device driver programming the hardware incorrectly. Please check with your hardware device vendor for any driver updates.
Additional Error's:
Source: System Error
Event ID: 1003
Description:
Error code 100000ea, parameter1 858d4548, parameter2 85bc35f8, parameter3 f7a3fcb4, parameter4 00000001.
Hi Vito,
The infinite loop error is old news on nVidia cards, but I've never seen it happen on an ATI card (or even heard of it on an ATI card). On nVidia cards, the issue is thought to be related to a combination of the video firmware and the drivers: occasionally (or entirely too frequently) nVidia card makers would ship a huge batch of cards with the engineering firmware still on the card, instead of an end-user revision (remember, nVidia doesnt actually make cards...they make reference boards for other manufacturers). The drivers on the web were never written for this bios, and so we find nv4_disp.dll referenced in an infinite loop error all over the web. Sometimes drivers would fix the issue, sometimes a firmware flash would fix the issue, and sometimes a card replacement fixed the issue.
So first, attack the issue like it was just an nVidia issue...check for firmware updates, try a few different revs of the driver (older verions), and see if you can kill this thing in the normal fashion.
Now then, in recent weeks, I've suddenly seen a huge surge in reported infinite loop errors, in several forums. This really makes me wonder if the issue is with a major update to Windows XP, rather than a problem with video cards and drivers. Aside from a few critical patches however, the only major revision I've seen to WinXP in that time frame is .Net 2.0 framework.
Any chance you recently installed the .Net 2 framework on your PC, even while the ATI card was still in it? Was the .Net 2 download part of your patching process with the reinstall? (this is just a theory of mine...no evidence to back it up, except that the timeline fits).
Did you pull drivers for either card from Windows Update, instead of from the manufacturer's website (or the nVidia/ATI websites?). Did you drivers for any device from Windows Update? Did you install all required chipset drivers (if any)?
Ok, if none of that pans out, do you use any kind of virtual video drivers (such drivers are mostly used in remote access apps, like GoToMyPC, PCAnywhere, and similiar view-remote-desktop-apps).
That's all I can think of that would cause this kind of error.
I hope that helps!
-TechInsider
The infinite loop error is old news on nVidia cards, but I've never seen it happen on an ATI card (or even heard of it on an ATI card). On nVidia cards, the issue is thought to be related to a combination of the video firmware and the drivers: occasionally (or entirely too frequently) nVidia card makers would ship a huge batch of cards with the engineering firmware still on the card, instead of an end-user revision (remember, nVidia doesnt actually make cards...they make reference boards for other manufacturers). The drivers on the web were never written for this bios, and so we find nv4_disp.dll referenced in an infinite loop error all over the web. Sometimes drivers would fix the issue, sometimes a firmware flash would fix the issue, and sometimes a card replacement fixed the issue.
So first, attack the issue like it was just an nVidia issue...check for firmware updates, try a few different revs of the driver (older verions), and see if you can kill this thing in the normal fashion.
Now then, in recent weeks, I've suddenly seen a huge surge in reported infinite loop errors, in several forums. This really makes me wonder if the issue is with a major update to Windows XP, rather than a problem with video cards and drivers. Aside from a few critical patches however, the only major revision I've seen to WinXP in that time frame is .Net 2.0 framework.
Any chance you recently installed the .Net 2 framework on your PC, even while the ATI card was still in it? Was the .Net 2 download part of your patching process with the reinstall? (this is just a theory of mine...no evidence to back it up, except that the timeline fits).
Did you pull drivers for either card from Windows Update, instead of from the manufacturer's website (or the nVidia/ATI websites?). Did you drivers for any device from Windows Update? Did you install all required chipset drivers (if any)?
Ok, if none of that pans out, do you use any kind of virtual video drivers (such drivers are mostly used in remote access apps, like GoToMyPC, PCAnywhere, and similiar view-remote-desktop-apps).
That's all I can think of that would cause this kind of error.
I hope that helps!
-TechInsider
ASKER
.NET 2 Framework is installed (installed during my standard OS build)
All hardware drivers were from manufactor websites or provided discs (then updated from manu)
NVidia Drivers are version 8.1.98 (12/10/2005) from NVidia site.
No PCAnywhere, GoToMyPC or the like.
I agree that the ATI issue was.. well bizarre. Whole reason I went out and bought the new NVidia was due to this problem occuring with my ATI. I found it very strange that an ATI video card would have problems on an ATI motherboard.
I'd say this problem started about 4 months ago. At that time I was using the ATI card. Just replaced that with the NVidia yesterday. Like I said clean install of everything at that point. Brain hurts now.. lol!
For grins and giggles I'll try uninstalling Framework 2. I'd love it if it was that easy!
All hardware drivers were from manufactor websites or provided discs (then updated from manu)
NVidia Drivers are version 8.1.98 (12/10/2005) from NVidia site.
No PCAnywhere, GoToMyPC or the like.
I agree that the ATI issue was.. well bizarre. Whole reason I went out and bought the new NVidia was due to this problem occuring with my ATI. I found it very strange that an ATI video card would have problems on an ATI motherboard.
I'd say this problem started about 4 months ago. At that time I was using the ATI card. Just replaced that with the NVidia yesterday. Like I said clean install of everything at that point. Brain hurts now.. lol!
For grins and giggles I'll try uninstalling Framework 2. I'd love it if it was that easy!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
From the stack trace, I find the footprint of nt!READ_REGISTER_ULONG+0x6
Debug report
BugCheck 100000EA, {8564da30, 865dfe38, f7a43cb4, 1}
Probably caused by : nv4_mini.sys ( nv4_mini+52f14 )
Arguments:
Arg1: 8564da30, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 865dfe38, Pointer to a DEFERRED_WATCHDOG object.
Arg3: f7a43cb4, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).
Debugging Details:
------------------
FAULTING_THREAD: 8564da30
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
LAST_CONTROL_TRANSFER: from 804f8c7c to 8054097f
STACK_TEXT:
b9c5d264 804f8c7c f7a43b40 f7a43b70 00000000 nt!KiUnlockDispatcherDatab
b9c5d278 f79b0a67 f7a43b94 00000000 00000000 nt!KeSetEvent+0x74
b9c5d56c 804fcfbf f7a43b40 b9c5d5b8 b9c5d5ac watchdog!WatchdogKernelApc
b9c5d5bc 806d0c35 00000000 00000000 b9c5d5d4 nt!KiDeliverApc+0xb3
b9c5d5bc 805270b6 00000000 00000000 b9c5d5d4 hal!HalpApcInterrupt+0xc5 <-- hardware error or overhear
b9c5d644 f6ffbf14 f59a8100 86424008 f701987f nt!READ_REGISTER_ULONG+0x6
WARNING: Stack unwind information not available. Following frames may be wrong.
b9c5d64c 86424008 f701987f 864cd380 86424008 nv4_mini+0x52f14
b9c5d650 f701987f 864cd380 86424008 00000100 0x86424008
b9c5d654 864cd380 86424008 00000100 86481550 nv4_mini+0x7087f
b9c5d658 86424008 00000100 86481550 86424008 0x864cd380
b9c5d65c 00000000 86481550 86424008 86522770 0x86424008
Debug report
BugCheck 100000EA, {8564da30, 865dfe38, f7a43cb4, 1}
Probably caused by : nv4_mini.sys ( nv4_mini+52f14 )
Arguments:
Arg1: 8564da30, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 865dfe38, Pointer to a DEFERRED_WATCHDOG object.
Arg3: f7a43cb4, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).
Debugging Details:
------------------
FAULTING_THREAD: 8564da30
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
LAST_CONTROL_TRANSFER: from 804f8c7c to 8054097f
STACK_TEXT:
b9c5d264 804f8c7c f7a43b40 f7a43b70 00000000 nt!KiUnlockDispatcherDatab
b9c5d278 f79b0a67 f7a43b94 00000000 00000000 nt!KeSetEvent+0x74
b9c5d56c 804fcfbf f7a43b40 b9c5d5b8 b9c5d5ac watchdog!WatchdogKernelApc
b9c5d5bc 806d0c35 00000000 00000000 b9c5d5d4 nt!KiDeliverApc+0xb3
b9c5d5bc 805270b6 00000000 00000000 b9c5d5d4 hal!HalpApcInterrupt+0xc5 <-- hardware error or overhear
b9c5d644 f6ffbf14 f59a8100 86424008 f701987f nt!READ_REGISTER_ULONG+0x6
WARNING: Stack unwind information not available. Following frames may be wrong.
b9c5d64c 86424008 f701987f 864cd380 86424008 nv4_mini+0x52f14
b9c5d650 f701987f 864cd380 86424008 00000100 0x86424008
b9c5d654 864cd380 86424008 00000100 86481550 nv4_mini+0x7087f
b9c5d658 86424008 00000100 86481550 86424008 0x864cd380
b9c5d65c 00000000 86481550 86424008 86522770 0x86424008
Refer the following problem and it is also related to hardware problem of nVidia video card.
https://www.experts-exchange.com/questions/21710197/Blue-screen-Stop-error-nv4-disp-the-device-driver-got-stuck-in-an-infinite-loop.html
https://www.experts-exchange.com/questions/21710197/Blue-screen-Stop-error-nv4-disp-the-device-driver-got-stuck-in-an-infinite-loop.html
Your video card maybe overheat. Can you open the case and check the temperature of the video card?
If you overclock the video card, change it back to the factory setting.
ASKER
Well, I wasn't overclocking so I can rule that out. Also temp is ok.
Based on the dump info I figured.. why not, so I returned the NVidia card and got a new one.
Installed the new NVidia 6600 with 7.7.7.7 drivers. Now for the part that brings tears to my eyes (hehehe) Fired it up, system locked up about 5-10 minutes once hardware accelleration was used. So, I am now trying....
"Take your vid driver back to one of the 77s or 78s...they were mega stable." {I'm on 7.7.7.7 will try the 78)
"Turn your sound card acceleration down one 'tick' to the left." {Ready to roll testing this)
"Kill the 'hide icons' function of the task bar. (don't ask...)" {Hmpf... no idea but ya never know with MS}
"Move your dimms from slot 1 and 2, to slot 1 and 3." {done and done}
"Shrink your AGP apeture to 1/2 the memory of the card." {next time I crash and reboot I'll hit the bios and do this}
Also trying crossed fingers, and quiet prayers.. thanks for all the help so far folks!
Based on the dump info I figured.. why not, so I returned the NVidia card and got a new one.
Installed the new NVidia 6600 with 7.7.7.7 drivers. Now for the part that brings tears to my eyes (hehehe) Fired it up, system locked up about 5-10 minutes once hardware accelleration was used. So, I am now trying....
"Take your vid driver back to one of the 77s or 78s...they were mega stable." {I'm on 7.7.7.7 will try the 78)
"Turn your sound card acceleration down one 'tick' to the left." {Ready to roll testing this)
"Kill the 'hide icons' function of the task bar. (don't ask...)" {Hmpf... no idea but ya never know with MS}
"Move your dimms from slot 1 and 2, to slot 1 and 3." {done and done}
"Shrink your AGP apeture to 1/2 the memory of the card." {next time I crash and reboot I'll hit the bios and do this}
Also trying crossed fingers, and quiet prayers.. thanks for all the help so far folks!
ASKER
well... so far so good.
Kept the drivers at 77. Turned down the sound acceleration by 1 tick (I think this did it), Killed the hide icons in taskbar (for good measure), dimms were already slotted to 1 and 3, and shrunk the apeture to 128.
Seems to have resolved it. I'm shocked and awed here people! Thankls so much for your help Experts!!!!
Kept the drivers at 77. Turned down the sound acceleration by 1 tick (I think this did it), Killed the hide icons in taskbar (for good measure), dimms were already slotted to 1 and 3, and shrunk the apeture to 128.
Seems to have resolved it. I'm shocked and awed here people! Thankls so much for your help Experts!!!!
Go to the event log and tell us what errors are there. Also go to c:\windows\minidump and post somewhere in the net (You can use for example http://www.rapidshare.de ) the last dump files you have.
Miguel