Solved BSOD While Streaming/Downloading/Gaming, Mostly DRIVER_IRQL Messages

[Matt87]

So, upon reaching my fifth BSOD in one day, it's driving me a little nuts. Usually I try to hunt the suspect file down with Google but that's not helping me this time. Someone recommended me to this site so I'm hoping I can get some insight about fixing this.

Some info on the system:
All of the hardware, less the DVD-ROM drive and graphics card, are three years and a few months old.

The card and DVD-ROM drive are about 2 months old.

Windows 7 Ultimate x64
The OS is relatively fresh. Reformatted when I got the new card.

In case any of the attached files don't describe my system specs in full, I did add them to my profile. Thanks to any and all that can tell me how to fix this. I've tried downloading the new Guild Wars 2 patch three times already and it's driving me nuts that I have to restart every time!

 

[Tekno Venus]

Hi, please note, I'm new at BSOD debugging but am being watched by writhziden so don't worry!

The BSOD dumps you gave me do not give a definitive cause for your BSOD's. They pointed at different drivers each time and lots system files which are very unlikely to cause a BSOD.

As a result I recommend you check your hardware for issues. Please run Memtest86+ to check your RAM. Let it run for 6-8 passes overnight as described in the tutorial. Pay particular attention to parts 2 and 3.

Also check your HDD for errors using Seatools. Download and create a bootable version of the Seatools for DOS program as described here.

Report back your results please.
Stephen

EDIT - Also just had another look at the dump files. I have noticed you do not have any anti-virus program installed on your computer. Please install Microsoft Security Essentials. Then install and scan your computer with Malwarebytes' Anti-Malware. This will remove any viruses you may have caught. DO THIS FIRST, BEFORE ANY HARDWARE SCANS
http://www.bleepingcomputer.com/virus-removal/how-to-use-malwarebytes-anti-malware-tutorial#tutorial

 

[Matt87]

I ran Memtest when I went to bed and it ran for about 5.5hours and did 4 passes with no errors. I wasn't sure how many I was supposed to run so I checked Google and most people seemed to do between 2 or 3. If you insist on doing 6-8 I'll set it up to do it again tonight and allow for more time.

I'm downloading that Seatools DOS program now. I'll be sure to report back ASAP with the results once GuildWars 2 finishes downloading (it's a 52% with another ~4.5GB left, furthest it's been without a BSOD -knock on wood).

Thanks a ton for the swift reply!

Edit to reply to your edit:
Will do! I thought I had Security Essentials installed, I guess it slipped my mind (it's usually one of the first things I install). I'll do that first per your recommendation.

 

[Matt87]

So I've downloaded Security Essentials and Malwarebytes, neither of them have detected anything on a full scan. When I left the house this morning, I left my computer on while Memtest86+ was running. It had scanned from about 11:45pm and was still going at it by 8am this morning. When I left, it had completed 4 passes without error.

Before I got Memtest86+ running, I tried using the Seatools program but it said it couldn't detect my HDD. It's odd, but my BIOS also does not show there is a drive attached as well (it only shows my DVD-ROM drive under the SATA connections). I know it's there because... well I'm able to log on to it and such. I'm not sure how to approach this.

At any rate, I figured what could possibly be the problem. I have a program called ASUS AIsuite, which can be used to overclock. I know little about overclocking but it seemed to be pretty cut and dry on how to use. Anyway, I had it set to one of the overlock profiles (I think there's only one) about a week ago. Thinking it may be the culprit, I restored the clocking to normal and I'll be testing it tonight with various things running that I've had up before during BSOD attacks. Maybe that was the problem all along?

I'd still like to get that Seatools (as well as my BIOS) to find my HDD regardless, to check for any possible errors related to other BSOD mishaps (before I got that program).

 

[Tekno Venus]

Your overlock is probably the reason for the BSOD's. Restoring all your components to their default clock speed should resolve them. I should have noticed that but I didn't. Something for me to remember in the future as just learning about BSOD debugging.

I'm not sure why your HDD isn't showing in the BIOS. Make sure everything is connected inside the case. Check all the cables and unplug and reconnect them if need be. It is rather odd that the BIOS doesn't show it and you can still boot from it. I'll have a think and see what I come up with.

Sorry I can't be more help
Stephen

 

[Matt87]

I'll try the cables when I get home. I agree, it is odd that the BIOS isn't showing it's there, yet it's able to boot from it. Does it actually say in the minidump files that it's being overclocked? I've never looked in them or anything before so I'm unsure of the information they contain.

Like I said, I've gotten a few BSODs before I got that overclocking program, but they were spread out (one every few days or so). I'll be sure to update later the results of Memtest and if I get Seatools to work. Here's hoping I can game in peace lol.

 

[Tekno Venus]

The dumps didn't say that your system was overclocked but kept blaming it on Microsoft processes. This is an indicator of a hardware problem. That is why I asked you to do the hardware checks. However, as I've learnt, they can be a sign of an overclock issue.

I am new at all this so I'll have too remember this in the future
Stephen

 

[writhziden]

For the HD issue, I would recommend contacting the motherboard manufacturer: ASUSTeK Computer Inc. -Support- Contact us


Stephen: To determine whether an overclock exists, run the command

!sysinfo cpuspeed

in WinDbg.

Prior to the overclock (before June)?

CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q8300  @ 2.50GHz"
MaxSpeed:     2500
CurrentSpeed: 2499

After the overclock (around the start of June)?

CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q8300  @ 2.50GHz"
MaxSpeed:     2500
CurrentSpeed: 2504

I do not see any overclocking going on (maybe a very very minor one), and there were hardware related crashes prior to the overclocking. You could try removing AISuite entirely and seeing if that provides stability. Sometimes, just having it installed allows it to interface with the hardware in ways that can cause instability. It is intended for overclocking, so any interface it has with the hardware will be to that effect. Overclocking in general will decrease system stability.

 

[Matt87]

@Stephen
Ahh, well you can be assured that with the Memtest scans and virus/malware scans, nothing turned up so I have a feeling those can be ruled out. I'll play around with Seatools and my HDD Thursday since I'll be home all day.

@writhziden
I actually downloaded AISuite in reference to something I Googled where someone was saying an associated driver fixes a BSOD issue. Although I don't see the same file popping up in any BSOD messages, I'll take your recommendation and try uninstalling it.

When I came home Memtest had run 8 passes without any errors. If I can't figure out the HDD issue I'll call ASUS per your suggestion. The good thing is that I haven't run into any BSOD issues since Monday. I don't think I've changed anything though except for clicking the "normal" button on AISuite program yesterday. If anything new happens I'll keep you both posted. I'll also note the results of Seatools if I ever get the HDD issue working.

 

[Tekno Venus]

Keep us posted. Let's hope that this trend of no BSOD's carries on.

 

[Matt87]

Unfortunately I ran into another BSOD. I deleted the previous minidump files so the ZIP file is smaller. It has two files in it, one from the 5th happened after I made this original post, so it may be worth looking at. So much for that lucky streak.

I'm wondering if it is indeed the HDD, and the BIOS not showing it is a sign of its issues. I wish I had another HDD laying around to test it... is there any sort of way to check the HDD with something else besides Seatools? Such as chkdsk? I'm personally just weary of calling customer support for computer companies... in most of my past experiences, I've barely been able to understand what they're saying.

 

[Tekno Venus]

I'm not on my PC at the mo so can't check the dumps but here is how to run chkdsk: http://www.sevenforums.com/tutorials/433-disk-check.html. Make sure to scan and automatically attempt to fix errors and recover bad sectors. The disk will obviously be in use so it will reboot.

 

[Tekno Venus]

Right then, down to business.

I've had a look at new dump files and the first one indicates hardware as per the earlier ones. The second one however, blames the crash on your NVidia card drivers. If the chkdsk doesn't solve the issues, I want you to try something:

You mentioned that you installed a graphics card 2 months ago in your original post. Try running Furmark to stress test your GPU. STOP THE TEST IMMEDIATELY IF ARTEFACTS BEGIN TO APPEAR ON THE SCREEN OR THE TEMPERATURE LEVELS OUT OR EXCEEDS 90 DEGREES. If no artefacts or distortion appears on the screen, consider the test passed. If artefacts do appear, make sure the card is properly seated.

Stephen

 

[Matt87]

I'm running the gpu test, it's at 99% load, 22% memory load and the temperature is at a steady 79°C. It's been going for almost ten minutes without a hitch. When is it safe to assume it's a pass?

I'll be running checkdsk per your recommendation after this test. Thanks for being a huge help! I really appreciate it!

 

[Tekno Venus]

That seems pretty stable to me, if there were problems, they would have come along within the first 10 minutes I think. Levelling out at 79 degrees shows that you have good cooling as well.
Report back after check disk, I still have some more ideas!

Stephen

 

[Matt87]

The chkdisk scan finished and everything looks green as far as that goes. I'm open to more suggestions!

 

[Tekno Venus]

Ok, I think the next thing to do is determine if a driver is causing the BSOD's because I have a feeling it is a HDD or other hardware issue. To do this you need to use Driver Verifier. This will stress the drivers and cause BSOD's. Once the PC has crashed a few times, upload the new dumps. If there are no crashes after 12-24 hrs, then a driver is not to blame. Stop driver verifier. Instructions:

• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:
  

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    
    
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset​
  -> Restart your computer.

If you have any issues, tell me. If at the end of this a driver is not to blame, I can start to do some more detailed hardware diagnostics, for example, working out why the BIOS is not showing your HDD.

Stephen

 

[Matt87]

Will do, I'll run that verifier until I go to bed tonight. I'll be sure to post the results immediately after a crash or a pass. Thanks a ton!

 

[Matt87]

When restarting after setting up the verifier, my comp almost immediately crashed upon loading the desktop. It successfully created a dmp file. I'm running it in safe mode now and it's able to idle without any issue.

Should I continue to try and start it in normal mode so I can create dmp files for you? Or should I let it sit in safe mode?

Edit: Tried to restart in safe mode with networking but I guess the computer somehow missed my F12 spam. It got another BSOD with the same file in the description: ASACPI.sys.

I'm running in safe mode with networking now I can still goof around on the net while the verifier is running (I guess that means it probably isn't the network driver). I also noticed that both times when loading on to the Desktop with the verifier running, I see a black rectangle appear on the screen in the upper-left part of the screen, then it crashes. Not sure if this means anything.

 

[writhziden]

Please start Safe Mode with Networking and run through the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html. They should indicate what is causing the immediate crashes.