Computer keeps going to BSOD while playing games. Help!


Recommended Posts

Alright, so I used the Catalyst 11.9 uninstall feature to remove 12.4, then installed. I didn't use driver sweeper because I figured the uninstall feature would have removed them.....

I then played Diablo III for almost 2 hours. Gameplay was choppy to say the least. My framerate was hovering right at about 100fps the whole time, but it was extremely choppy anyway. This eventually ended with a blue screen and of course a mixture of anger/sadness from me =P.

Sooooo. I just used driver sweeper to remove all traces of AMD/ATI drivers, and reinstalled Catalyst 11.9. Stay tuned...

Using an older uninstaller to remove a newer driver :/

Could you post the error dump please? This way you could get real help other than speculations.

https://www.neowin.net/forum/topic/1077823-computer-keeps-going-to-bsod-while-playing-games-help/page__view__findpost__p__594871001

Link to comment
Share on other sites

...

My friend has this same "copy" of windows, and his gets the same errors. Do I have a corrupt version, or a corrupt ntoskrnl.exe? Is there any way to replace just this file? If I boot my windows disc and go to repair will it find and replace this corrupt file? Is this even possible if the file on the disc is corrupt itself?

I gather from that statement that your copy of windows is not legit? You should open an elevated command prompt and run:

sfc/scannow

this process will take a long time, but it will identify and (hopefully) correct any system files that are corrupted.

Link to comment
Share on other sites

Okay, I thought I had it all figured out. The 11.9 drivers weren't perfect, but I didn't get any blue screens for a bit. However, I've had it twice since then, both with different reasons for why the BSOD happened.

I got a key for the Krater closed beta, and installed thru steam. I went to play, and it got to the step where it was installing Direct X, and I got the blue screen with this error:

On Wed 5/23/2012 5:39:52 AM GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)

Bugcheck code: 0xC9 (0x224, 0xFFFFF880060ED710, 0xFFFFF9805B7A08B0, 0xFFFFFFFFC00000BB)

Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION

Bug check description: This is the bug check code for all Driver Verifier

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Then, I left my computer on overnight and went to bed. When I woke up, the computer was turned off. I powered on and checked the error, and it showed this:

On Wed 5/23/2012 5:39:52 AM GMT your computer crashed

crash dump file: C:\Windows\Minidump\052312-29312-01.dmp

This was probably caused by the following module: hidclass.sys (HIDCLASS+0x2710)

Bugcheck code: 0xC9 (0x224, 0xFFFFF880060ED710, 0xFFFFF9805B7A08B0, 0xFFFFFFFFC00000BB)

Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION

file path: C:\Windows\system32\drivers\hidclass.sys

product: Microsoft? Windows? Operating System

company: Microsoft Corporation

description: Hid Class Library

Bug check description: This is the bug check code for all Driver Verifier

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

Both recent times were caused by the Bug Check codes 0xC9 (0x224, 0xFFFFF880060ED710, 0xFFFFF9805B7A08B0, 0xFFFFFFFFC00000BB). Can anyone make sense of these. I tried google, but I don't understand much of what I'm reading.

I'm at a loss here.... anybody got anything?????

@jnelsoninjax, i'll try that. Is an "elevated command prompt" the same as a "command prompt?" Probably a stupid question, but I've never heard of that before...

Link to comment
Share on other sites

It's looking like you might have to start over :/ Reinstall Windows, install the drivers that came with the card and then update?

Link to comment
Share on other sites

Okay........ Haha I figured it might come to that. I'll try someone else's copy of Windows. Maybe my disc was scratched, or had corrupted files or something else unexplainable.

Any suggestions before I bite the bullet and spend all night backing up my files?

Link to comment
Share on other sites

If you have space to "image" your complete c drive do it.. because if the same error comes up you can completely restore your pc

Type backup in the start menu and open Backup and Restore ;)

Link to comment
Share on other sites

It really looks like one or more drivers on your system are foobarred. If you don't want to reinstall yet, delete every driver you can find with driver sweeper and start over.

It might be quicker to just reinstall at this point.

Out of interest, do you use a wireless usb receiver? I've seen those really screw up stability before.

Link to comment
Share on other sites

It really looks like one or more drivers on your system are foobarred. If you don't want to reinstall yet, delete every driver you can find with driver sweeper and start over.

It might be quicker to just reinstall at this point.

Out of interest, do you use a wireless usb receiver? I've seen those really screw up stability before.

He has already used Driver Sweeper.

Link to comment
Share on other sites

I guess I'm gonna just start over. I don't have THAT much stuff to back up. It's just gonna be a pain to re-download and re-install all of my steam games. Other than that it looks like ive got like 15 gigs of essential drivers/media/software that need to get back up, and that wont take too long. Hopefully this solves the problem...

Link to comment
Share on other sites

Okay so I'm back up and running. I used ninite to install mostly everything I had before. Never used it before and man it IS helpful.

Anyway, all my drivers are installed and updated, and I'm installing D3 now for a test run. Installing windows seemed to go much smoother than I remember from last time, but now I'm getting this error (which I guess is no big deal. as long as everything is running smoothly i'll take a ? in my device manager over a BSOD any day):

device_manager.png

Link to comment
Share on other sites

You'll need to install chipset drivers for your processor. That's most likely what those two are. You can grab them from your motherboard manufacturer's website. I don't know why but they never seem to install through Windows update.

Link to comment
Share on other sites

You'll need to install chipset drivers for your processor. That's most likely what those two are. You can grab them from your motherboard manufacturer's website. I don't know why but they never seem to install through Windows update.

Yea, I've already installed my chipset drivers. Only thing that installed through windows update was bluetooth and sound drivers. Everything else I downloaded and installed from the ASUS website.

Link to comment
Share on other sites

My friend has this same "copy" of windows, and his gets the same errors. Do I have a corrupt version, or a corrupt ntoskrnl.exe? Is there any way to replace just this file? If I boot my windows disc and go to repair will it find and replace this corrupt file? Is this even possible if the file on the disc is corrupt itself?

This sounds a bit dodgy. But what I'd try:

1. Memtest for at least 2 full passes.

2. Furmark for 2ish hours.

3. Prime95 for a day.

4. Re install WIndows

Link to comment
Share on other sites

Yea, I've already installed my chipset drivers. Only thing that installed through windows update was bluetooth and sound drivers. Everything else I downloaded and installed from the ASUS website.

Intel processor? See if there's anything on their downloads page that you need to install.

Link to comment
Share on other sites

First he gets NT Kernel errors, thus its the Windows kernel that keeps crashing.

Secondly, what does Prime and Furmark have to do with anything? Those are for stressing your PC not any good to solutions what he is looking for.

Run a diskcheck for faulty sectors and if it doesn't find any, buy ( :rofl: ) or by other means find a clean windows image and re-install.

Link to comment
Share on other sites

Do you have a raid controller enabled in your BIOS but you're not using it? For example I have a JM Micro controller for RAID but since I don't use it I have disabled it and it doesn't show in device manager, those sorts of controllers aren't always detected and installed by Windows.

Link to comment
Share on other sites

This sounds a bit dodgy. But what I'd try:

1. Memtest for at least 2 full passes.

2. Furmark for 2ish hours.

3. Prime95 for a day.

4. Re install WIndows

I've run memtest a few times and the memory is fine. The others I don't really see doing much. Maybe it would tell me what peice of hardware was causing the Windows kernel to go wonky, but it really seems like its a software/driver issue. I just reinstalled windows and everything seems to be fine now short of those two things in my device manager.

Intel processor? See if there's anything on their downloads page that you need to install.

Intel or ASUS website? Of course I can check both, but just wondering which you meant.

First he gets NT Kernel errors, thus its the Windows kernel that keeps crashing.

Secondly, what does Prime and Furmark have to do with anything? Those are for stressing your PC not any good to solutions what he is looking for.

Run a diskcheck for faulty sectors and if it doesn't find any, buy ( :rofl: ) or by other means find a clean windows image and re-install.

Different copy of Windows just got installed. My fingers are crossed.

Do you have a raid controller enabled in your BIOS but you're not using it? For example I have a JM Micro controller for RAID but since I don't use it I have disabled it and it doesn't show in device manager, those sorts of controllers aren't always detected and installed by Windows.

I don't have RAID set up that I know of. I never actively went in to the BIOS and turned it on, but stranger things have happened. I'll check to make sure.

Link to comment
Share on other sites

http://drp.su/ use this if you can't be bothered to find the correct drivers yourself.

Not sure what tone to read your reply in, but in case you are being helpful and not sarcastic, have you used this before?

Link to comment
Share on other sites

The RAID controller was enabled by default on my board, you should be able to see this on boot, if a device powers up and then doesn't find anything :p (before the Windows logo appears).

Link to comment
Share on other sites

  • 5 weeks later...

Not sure what tone to read your reply in, but in case you are being helpful and not sarcastic, have you used this before?

\

Sorry for the late reply, you've probably already sorted it out by now, but yes i was trying to be helpful and yes, I've used it before, works perfectly 95% of the time, it occasionally downloads a Russian sound driver on pre sp3 xp installs.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.