Hi guys,
First question here and I hope you'll be able to either confirm or dispel my thoughts on what is happening here.
Customer system is a Dell Vostro 200 (xp home sp3) with Intel g33/g31 chipset and on-board graphics. The system hangs before the windows logon screen comes up and BSODs with "Driver [file-name] stuck in infinite loop." Booting into safe mode with the standard VGA driver and we have no issues.
I've tried putting a card in the PCI-e slot (Nvidia 8400gs) and get the same BSOD, but it's the Nvidia driver rather than the Intel driver.
Tried changing out the RAM with known good DDR2 and have the same results with both on-board and add-in card.
Tried resetting the BIOS by yanking the battery with the same results.
Tried changing the power supply to a known good unit. Same results with both on-board and add-in card.
Tried reloading windows to a known good hard drive to see if it is a windows problem. With the standard VGA driver, everything is good. As soon as I load the g33/g31 driver (tried multiple revisions of this driver) I get not a BSOD but messed up graphics and cannot get the desktop to fully load. Unfortunately, I can't ask the customer to go with 640x480.
At this point, I've left the RAM testing on memtest overnight to see if it fails on multiple passes, but I'm pretty sure something is going on with the PCI-e bus not functioning properly with the driver.
I spent the better part of the day Googling the errors but found everyone encountering this problem to be extremely frustrated with both Intel and Microsoft's utter lack of response to this problem. I'm hoping someone has found a good solution to this so I don't have to tell the customer the computer is for all intents and purposes dead. They didn't buy the system from us (and it's not under warranty), but they are a good client and I would much rather have the "It was tough problem, but I fixed it" talk than the "Sorry, nothing I can do but get you a new one to replace this two year old system" talk.
I'll post more details (mb model, etc) tomorrow when I have the system in front of me.
Thanks in advance for any help you can give me.
First question here and I hope you'll be able to either confirm or dispel my thoughts on what is happening here.
Customer system is a Dell Vostro 200 (xp home sp3) with Intel g33/g31 chipset and on-board graphics. The system hangs before the windows logon screen comes up and BSODs with "Driver [file-name] stuck in infinite loop." Booting into safe mode with the standard VGA driver and we have no issues.
I've tried putting a card in the PCI-e slot (Nvidia 8400gs) and get the same BSOD, but it's the Nvidia driver rather than the Intel driver.
Tried changing out the RAM with known good DDR2 and have the same results with both on-board and add-in card.
Tried resetting the BIOS by yanking the battery with the same results.
Tried changing the power supply to a known good unit. Same results with both on-board and add-in card.
Tried reloading windows to a known good hard drive to see if it is a windows problem. With the standard VGA driver, everything is good. As soon as I load the g33/g31 driver (tried multiple revisions of this driver) I get not a BSOD but messed up graphics and cannot get the desktop to fully load. Unfortunately, I can't ask the customer to go with 640x480.
At this point, I've left the RAM testing on memtest overnight to see if it fails on multiple passes, but I'm pretty sure something is going on with the PCI-e bus not functioning properly with the driver.
I spent the better part of the day Googling the errors but found everyone encountering this problem to be extremely frustrated with both Intel and Microsoft's utter lack of response to this problem. I'm hoping someone has found a good solution to this so I don't have to tell the customer the computer is for all intents and purposes dead. They didn't buy the system from us (and it's not under warranty), but they are a good client and I would much rather have the "It was tough problem, but I fixed it" talk than the "Sorry, nothing I can do but get you a new one to replace this two year old system" talk.
I'll post more details (mb model, etc) tomorrow when I have the system in front of me.
Thanks in advance for any help you can give me.
