Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)
Course Of The Month
4 days, 1 hour left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
graphics driver causes reboot
Posted on 2004-04-18
Hi guys, just wondering if anyone can help me with a little problem.
I have just reinstalled windows xp on my hard drive.The hard drive was apparently damaged according to my xp installer when I formatted it . I ran chkdsk /r and recovered my drive.
But now I have reinstalled xp and when the desktop opens I get a message saying " my graphics card is causing all the problems.
I cannot get to system to delete the drive as the computer keeps going into reboot mode when the warning is displayed.
please help its driving me nuts
Regards
deklufc
I have just reinstalled windows xp on my hard drive.The hard drive was apparently damaged according to my xp installer when I formatted it . I ran chkdsk /r and recovered my drive.
But now I have reinstalled xp and when the desktop opens I get a message saying " my graphics card is causing all the problems.
I cannot get to system to delete the drive as the computer keeps going into reboot mode when the warning is displayed.
please help its driving me nuts
Regards
deklufc
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
4
-
4
- +5
14 Comments
Enter in vga mode by pressing F8 during startup then remove your display adapter in Device manager.
Try reinstalling an updated driver.
Try reinstalling an updated driver.
Also, when you say you have reinstalled XP on you hard drive, was it a fresh installation or did you install windows over itself?
If you installed XP over itself after the disk corruption, then it is possible that your graphics card display driver has become corrupted.
What graphics card do you have?
P.S. You might want to run chkdsk again, just in case. It sometimes finds more errors on a second pass.
If you installed XP over itself after the disk corruption, then it is possible that your graphics card display driver has become corrupted.
What graphics card do you have?
P.S. You might want to run chkdsk again, just in case. It sometimes finds more errors on a second pass.
Thanks everyone for the replies,
I will try the things mentioned above and let you know what the error actually says. I did a format of the hard drive before I installed a clean version of xp.
The card is a gforce mx400
Regards
Deklufc
I will try the things mentioned above and let you know what the error actually says. I did a format of the hard drive before I installed a clean version of xp.
The card is a gforce mx400
Regards
Deklufc
If it comes up with an error straight after installing a fresh copy of XP (with the standard Microsoft drivers) then I would strongly suggest checking your disk again.
Also, ensure all cables, PCI Cards and memory modules are seated correctly in your computer.
The latest drivers for your graphics card can be downloaded from here:
http://download.nvidia.com/Windows/56.72/56.72_winxp2k_english_whql.exe
They are version 56.72 (if you couldn't guess!).
One more thing, if you're overclocking, reduce the FSB to it's default value while troubleshooting. Ensure your memory is rated for the speed it is running at.
Also, ensure all cables, PCI Cards and memory modules are seated correctly in your computer.
The latest drivers for your graphics card can be downloaded from here:
http://download.nvidia.com/Windows/56.72/56.72_winxp2k_english_whql.exe
They are version 56.72 (if you couldn't guess!).
One more thing, if you're overclocking, reduce the FSB to it's default value while troubleshooting. Ensure your memory is rated for the speed it is running at.
Thanks Nil, if this helps this is what comes up now ......
A problem has been detected and windows has shut down to protect your computer.
Driver_IRQL_NOT_LESS_OR_EQ
And this is at the bottom of the message.......
Tech ***stop:OXOOOOOOD1(OXFA568
A problem has been detected and windows has shut down to protect your computer.
Driver_IRQL_NOT_LESS_OR_EQ
And this is at the bottom of the message.......
Tech ***stop:OXOOOOOOD1(OXFA568
Microsoft has this to say about STOP 0X00000D1:
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prmd_stp_ottj.asp
What file does the blue screen say has caused the error?
Do you by any chance have onboard sound?
You might also want to check out how hot your graphics card heatsink is, as well as the temperature of your CPU (just to rule them out).
For your CPU you can use a program like Motherboard monitor to report the temp:
http://mbm.livewiredev.com/download.html
Alternatively you can restart and look in the BIOS under something like 'PC HEALTH', here you should find the temp of your CPU.
For your graphics card you can simply feel the heatsink while it's in use, it should be warm to the touch, but not so hot that you have to move your hand away. (You can also do this for the CPU heatsink)
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prmd_stp_ottj.asp
What file does the blue screen say has caused the error?
Do you by any chance have onboard sound?
You might also want to check out how hot your graphics card heatsink is, as well as the temperature of your CPU (just to rule them out).
For your CPU you can use a program like Motherboard monitor to report the temp:
http://mbm.livewiredev.com/download.html
Alternatively you can restart and look in the BIOS under something like 'PC HEALTH', here you should find the temp of your CPU.
For your graphics card you can simply feel the heatsink while it's in use, it should be warm to the touch, but not so hot that you have to move your hand away. (You can also do this for the CPU heatsink)
download the INTERNATIONAL language drivers, ( 56.72_winxp2k_internationa
I manually traced it to some language files some files - NVRSxxx and NVWRxxx (xxx being ENG for english) were not updated in the single language driver updates, and were older than the rest of the files - when i used the international language files, the files were updated, and system is much more stable.
regards,
A.
I manually traced it to some language files some files - NVRSxxx and NVWRxxx (xxx being ENG for english) were not updated in the single language driver updates, and were older than the rest of the files - when i used the international language files, the files were updated, and system is much more stable.
regards,
A.
Here's what http://www.aumha.org/win5/kbestop.php#0x24 has to say about that STOP error:
0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQ
(Click to consult the online Win XP Resource Kit article.)
The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile
This sounds like a bad video card driver, so maybe you should try a different version.
0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQ
(Click to consult the online Win XP Resource Kit article.)
The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile
This sounds like a bad video card driver, so maybe you should try a different version.
I once had a problem with Adaptec SCSI 1520 controller, display adapter, and 486dx computer running Win?95?.. It turned out to be a conflict but I forget whether it was dma/irq/mem. Win95 would either jam or reboot at the Windows95 screen so I think it's a conflict but it could be a problem with the hard drive also.. Oop and the above comment seems useful too.
If you can boot in safe mode it might be a driver issue, but most likely a hardware conflict. The trouble began with the HD and now migrates to the video. Try checking the power supply first just to rule out erratic power behavior.
Remove the 20 pin connector from the mobo. Disconnect all other wires from mobo and peripherals except the HD. I like to use a plastic coated twist tie and strip the ends so that I can fold the end over to double the end size and then stick one end into the green wire (pwr on) socket and the nearest black wire ground. With the unit plugged into the AC outlet you should get HD spin. If you do proceed to use a digital multimeter testing each lead exept the gray wire and other black grounds. The meter ground probe should be left in one of the black ground wire sockets as you test each of the colored wires. Reds are 5vdc, oranges are 3.3vdc, white is -5vdc, yellow is 12vdc, blue is -12vdc. if they test within .19 of spec (3.3 = 3.49 or 3.11, 5.0 = 5.19 or 4.81) you are safe to assume the PS unit is good. I would note that if during the test if any of the voltages fluctuate so that you never get a stable reading or any one of the leads is out of spec you need to replace the unit.
Remove the 20 pin connector from the mobo. Disconnect all other wires from mobo and peripherals except the HD. I like to use a plastic coated twist tie and strip the ends so that I can fold the end over to double the end size and then stick one end into the green wire (pwr on) socket and the nearest black wire ground. With the unit plugged into the AC outlet you should get HD spin. If you do proceed to use a digital multimeter testing each lead exept the gray wire and other black grounds. The meter ground probe should be left in one of the black ground wire sockets as you test each of the colored wires. Reds are 5vdc, oranges are 3.3vdc, white is -5vdc, yellow is 12vdc, blue is -12vdc. if they test within .19 of spec (3.3 = 3.49 or 3.11, 5.0 = 5.19 or 4.81) you are safe to assume the PS unit is good. I would note that if during the test if any of the voltages fluctuate so that you never get a stable reading or any one of the leads is out of spec you need to replace the unit.
Featured Post
On-screen guidance at the moment of need enables you & your employees to focus on the core, you can now boost your adoption rates swiftly and simply with one easy tool.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Does your iMac really need a hardware upgrade? Will upgrading RAM speed-up your computer? If yes, then how can you proceed?
Upgrading RAM in your iMac is not as simple as it may seem. This article will help you in getting and installing right RA…
pc, laptop monitor connection configurations
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.
Suggested Courses
Course of the Month4 days, 1 hour left to enroll
690 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.