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

...

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.

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...

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?

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 ;)

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.

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.

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...

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

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.

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

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.

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.

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.

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.

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?

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).

  • 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.

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

    • No registered users viewing this page.
  • Posts

    • PDF-XChange Editor 11.0.1.0 by Razvan Serea PDF-XChange Editor is a comprehensive PDF editor that allows you to create, view, edit, annotate, and digitally sign PDF documents with ease. With advanced features like OCR, document security, and PDF optimization, PDF-XChange Editor is a powerful tool for both personal and professional use. Whether you need to edit text, images, or links, or add comments, stamps, or watermarks, PDF-XChange Editor provides all the necessary tools to make your PDFs look perfect. Additionally, it supports a wide range of file formats, including PDF, XPS, and DOCX, making it easy to convert and share your documents. PDF-XChange Editor key features: Edit text and images in PDF documents Add and remove pages from PDF files Annotate and markup PDFs with comments, highlights, and stamps Use OCR to convert scanned documents into searchable text Create and fill out PDF forms Sign and certify PDF documents digitally Add and edit hyperlinks within PDFs Extract text and images from PDF files Batch process multiple PDF files at once Customize the interface to your preferences Work with multiple documents in tabs Convert PDFs to other formats such as Word, Excel, and HTML Use advanced redaction tools to permanently remove sensitive information Add customizable headers and footers to PDFs Merge multiple PDF documents into a single file Split PDF documents into multiple files Add watermarks to PDF documents Use the measurement tools to calculate distances and areas in PDFs ....and much more PDF-XChange Editor 11.0.1.0 changelog: Fixed a crash in the new Open/Save dialog box when creating a new folder in an unavailable network path. (49552) Fixed a rare/infrequent crash on some dynamic XFA forms after changing their field values. [installer] Fixed an issue where shortcuts were lost during an upgrade from the previous version. [installer] Fixed an issue preventing migration of serial keys during updates from version 10. Fixed the issues with the shell context menu after installation of version 11. Fixed the issue with filtering comments. (49478) Fixed the issue that caused "Error [IO subsystem]: Invalid access mode." when converting PDFs to MS Office formats. Fixed an issue with the context menu position on some multi-monitor systems. (48467) Fixed an issue with handling complex custom file filters, displayed by JS, in the new Open/Save Files dialog box. (49486) Fixed several issues with the new 'Select Folder' dialog box. (49505) Fixed an issue with the new custom 'Open File' dialog box when using double-click to open it. (49498) Fixed an 'infinite' loop/proliferation in the 'Open Files' and 'Manage Places' dialog boxes. (49526) Fixed an issue with handling the mouse wheel inside the document "Find" box. (49539) Fixed an incorrect behaviour in the 'Go back (Alt+Left)' button in the new Open/Save Files dialog box. (49510) Fixed an issue with the shortcut keys (Alt+Left/Right) after navigating via breadcrumb paths in the new Open/Save Files dialog box. (49554) [installer] Fixed an issue with redrawing the progress text in the EXE installers. Fixed the issue where a mouse click outside of the polyline/polygon context menu during annotation creation would cancel the annotation. (49475) We switched back to using the system Open/Save/SelectFolder dialog box by default, instead of using the new one, because some popular features such as the QuickAccess/Recent items are missing in the new version. These will be added in a future release. Replaced the 'Extension' column in the new Open/Save File dialog box with a more user-friendly 'Type' column. Also fixed some issues when handling the 'Show file extension' option. (49497) Added the ability to authenticate local network shares in the new Open/Save Files dialog box. (49557) Improved the handling of dates after 01.01.2030 in XFA files - now such dates are stored properly when set via the dropdown widget. Flags NoZoom and NoRotate are now respected for only a limited subset of annotations. Download: PDF-XChange Editor (64-bit) | Portable ~300.0 MB (Shareware) Download: PDF-XChange Editor (32-bit) | Portable ~200.0 MB Download: PDF-XChange ARM64 | 276.0 MB Download: PDF-XChange Portable @PortableApps.com | 97.0 MB View: PDF-XChange Editor Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Still 3x what it should cost. So, it seems the trick is to increase price by 6x so that a reduction in price back to 4x looks like a steal. "You savvy shoppers win again!" I'm glad I'm not in a desperate spot to actually even need this overpriced crap. Hopefully, it comes back down by the time for when (or if) I ever do.
    • Although AI is great and has it's use cases they likely have massively overhyped it and it has not delivered as per their expectations. I fully expect them to start saying the same things again when it does get to a certain level of intelligence!
    • Microsoft wants to end printer driver headaches with Windows Ready Print by Usama Jawad A few days ago, Microsoft released Windows 11 Experimental build 26300.8553, bringing a ton of enhancements such as Start menu customization, search improvements, Taskbar polish, and other minor UI tweaks. Another relatively major enhancement snuck deep within the change log was related to upgrades to the Windows printing experience. Now, Microsoft has shared more details about these benefits. For starters, Microsoft has renamed its Modern Print Platform to Windows Ready Print. The company believes that this name highlights its shift in strategy, which now focuses on modernizing, securing, and streamlining the printing experience for Windows devices. Some of the upgrades present in Windows Ready Print have already been seeded to customers and partners. This includes ending support for third-party printer drivers via Windows Update and transitioning towards the Internet Printing Protocol (IPP) and the native Windows IPP printer driver. In line with these changes, new printer installations will default to Windows Ready Print on eligible devices starting from July 2026. However, Microsoft recognizes that not all environments will be able to migrate to this platform immediately, so it will allow users to choose between installing the printer via Windows Ready Print or the traditional OEM process. Users will be able to toggle this configuration through Settings > Bluetooth & Devices > Printers & Scanners > Printer preferences. This control applies only to new printer installations, and its functionality can also be modified via Group Policy as follows: Launch Group Policy Editor Navigate to Local Computer Policy -> Administrative Templates -> Printers Find and select 'Configure Windows Ready Print driver ranking' -> double click to open it Select 'Enabled' (if you wish to enable Windows Ready Print driver selection) or 'Disabled' (if you wish to explicitly disable Windows Ready Print driver selection). Select Apply Select OK Similarly, if you set up Windows protected print mode through the same setting in Windows 11, it will also default to using Windows Ready Print exclusively. Microsoft hopes that these improvements will help eradicate dependency on OEM-specific driver installation processes and simplify printer installations. We'll likely find out more about other tangible benefits in the coming months.
  • Recent Achievements

    • One Month Later
      johnjacobb40 earned a badge
      One Month Later
    • One Year In
      Primer1st earned a badge
      One Year In
    • Experienced
      JayZJay went up a rank
      Experienced
    • Reacting Well
      Sir_Timbit earned a badge
      Reacting Well
    • Week One Done
      rubentuben8 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      513
    2. 2
      PsYcHoKiLLa
      231
    3. 3
      +Edouard
      138
    4. 4
      ATLien_0
      87
    5. 5
      Steven P.
      81
  • Tell a friend

    Love Neowin? Tell a friend!