BSOD - driver irq no less than blah blah

[dclive]

Originally posted by: Mr Fox
This is a Case of Operator Issues....


1,) the OP Has not provided Enough Hardware O/S and Driver Information to Allow good Troubleshooting and Problem Solving.

2,) It looks like he has put x64 Processor Drivers on a 32 Bit O/S In one of the above posts he Said His O/S Version was NT 5.1.2600 Build... that is 32bit XP...... XP x64 is NT 5.2.3790


This is a Software Issue Caused by the Wrong Drivers being used. Just because the Processor is 64 Bit does not mean that the Operating System is....

Install Drivers One at a Time and test... It will let you isolate issues better, and then rollback the O/S.... [/b]

That's factually incorrect.

You cannot install 64 bit drivers into a 32 bit OS. Windows will refuse to install the driver. It's most likely the OP is a bit confused about the driver he installed, but it's not a 64 bit (Windows) driver.

A BSOD can point to a software or a hardware problem, but software issues are typically where problem resolution starts. In this case, since the BSOD pointed to all kinds of different drivers and causes, it's most likely it is a hardware problem, in which case reinstalling is unlikely to be a long-term fix (unless a driver is _not_ installed on the new build, and that is the hardware that is causing the problem.)

Reinstalling, however, is a great way to troubleshoot the issue - because it will quickly clarify whether this is software or hardware. The key issue, however, is that the OP shouldn't install *ANY* non-Microsoft in-the-XP-CDROM-box drivers. In other words, no motherboard drivers, no vendor drivers, nothing.

 

[Hacka]

well i fixed it and i wasnt installing 64bit drivers.. just amd64 cpu drivers. I got it working somehow.. not sure. i think it was my optimizer because it wouldnt remove. But maybe again it was my memory.. dunno lol..