Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


DXDIAG Blue Screen

  • Please log in to reply
4 replies to this topic

#1 jrodch


  • Members
  • 1 posts
  • Local time:05:15 PM

Posted 06 October 2010 - 03:21 PM

I just replace a motherboard in a machine, all seemed to be running stable until I tried to run Burn It Test. I would get a BSOD every time I opened the program. The only other time was was able to replicate the problem is when I run DXDiag. I get to the point where it asks if I want to bypass "direct play". If I click "no", instant BSOD (same stop error).

I've tried totally reinstalling my video card (onboard ATI 2100). Any ideas?


BC AdBot (Login to Remove)


#2 GMmasterking


  • Members
  • 15 posts
  • Gender:Male
  • Local time:11:15 PM

Posted 06 October 2010 - 03:54 PM

You have to cheack and update your drivers .
Posted Image

#3 hamluis



  • Moderator
  • 56,556 posts
  • Gender:Male
  • Location:Killeen, TX
  • Local time:03:15 PM

Posted 06 October 2010 - 04:19 PM

I think that's correct...if you are using the same hard drive with a new board...you need to remove all the old drivers (for each function) and replace them with the driverrs for the new board.

If you have already done that...telling us the content of the BSOD would be...informative and helpful.


#4 cryptodan


    Bleepin Madman

  • Members
  • 21,868 posts
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:09:15 PM

Posted 06 October 2010 - 04:36 PM

In conjunction with the drivers also make sure you have the latest DirectX Run Time Files and Updates.

Here is the link to your video card drivers: ATI Display Driver version 10.9

Before you install the latest drivers please run Driver Sweeper to remove all your older drivers from the system. This will ensure that corrupted files do not remain installed.

Also make sure that your case is completely cleaned out overheating can cause this. I know you just replaced the motherboard, but your fans maybe caked with dust and preventing ample air flow from entering and exiting the system.

#5 dc3


    Bleeping Treehugger

  • Members
  • 30,809 posts
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:01:15 PM

Posted 06 October 2010 - 04:40 PM

Did you reinstall the hdd that was used with the previous hdd?

When you take a hdd with a Windows OS installed on it that you have been using on one computer and then install it as a master in another computer you are asking for major problems. The excerpt below is from a Intel article which describes in detail what happens. The article also mentions a reference to an article by Microsoft, it can be seen here .

"Moving a hard drive with Windows* 2000 or Windows XP* already installed to a new motherboard without reinstalling the operating system is not recommended.

If a hard drive is moved to a new computer, the registry entries and drivers for the mass storage controller hardware on the new motherboard are not installed in Windows for the new computer and you may not be able to start Windows. This is documented in Microsoft's knowledge base article. This is true even if you move the hard drive to a motherboard with the same chipset, as different hardware revisions can cause this issue as well.

Additionally, moving a hard drive to a new motherboard may not exhibit any errors until you install new IDE drivers. This is because each chipset uses a different Plug-n-Play (PNP) ID to identify it. If you move your motherboard, your registry will have multiple PNP IDs (for the old hardware as well as the new hardware). If there are multiple entries in the registry, Windows cannot determine which hardware to initialize and therefore fails with a STOP error."

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users