Solved Random Freezes, BSOD, error 0x116

[Baasha]

Since yesterday, my computer has been randomly freezing (even ctrl+alt+del didn't do anything) and I've had to hard-reboot several times.

Today, my monitor just turned off (black screen) and I had to hard-reboot. Upon rebooting, I got a message that said it was a BSOD with error 0x116 which is usually related to graphics cards.

I'm running the latest Beta driver from NVIDIA (301.24) on my EVGA GTX-580 Classified 3GB. I have 4 cards in 4-Way SLI and I am NOT OC'ing them. I only OC them during gaming.

Since this issue just started happening, I'm afraid it's something else that's causing this.

I should also mention that on 04/27/12, my OS drive (2 Corsair Force GT SSDs in RAID-0) showed some error and upon running CHKDSK, it fixed some corrupted areas of the SSD but MS Office just started crashing. After spending five days trying to fix it (reinstalling etc.), the issue never went away; MS Office would not let me reinstall (Office 2010 Pro Plus). So I ended up doing a "Repair Install" and then was able to install Office without any issue. Everything seemed to be working normally again but as mentioned, since yesterday, my computer just started freezing up randomly.

I ran ComboFix and Malwarebytes Anti-Malware and neither of them found any problems. I also ran SFC /SCANNOW and there were no integrity violations etc.

Please take a look at the attached DMP files and Perfmon Report and let me know what it says.

 

[zigzag3143]

"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.

As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.

If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating.

Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.

Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.

If so, it might be as simple as dust buildup and subsequently inadequate cooling.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps

http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

 

[Baasha]

Okay I will test the graphics cards to see if there's anything wrong with them.

Can you tell me what the dump file says? I attached it to my previous post.

I also tried running Driver Verifier and got 3 BSODs saying AmUStor.sys was the driver that caused it.

Could that be the cause of the crashes? Those BCC were 0xD5 though, not 0x116.

 

[zigzag3143]

Okay I will test the graphics cards to see if there's anything wrong with them.

Can you tell me what the dump file says? I attached it to my previous post.

I also tried running Driver Verifier and got 3 BSODs saying AmUStor.sys was the driver that caused it.

And you uploaded them where?

Could that be the cause of the crashes? Those BCC were 0xD5 though, not 0x116.

The only DMPS I have seen point to BCC116

 

[Baasha]

Okay I will test the graphics cards to see if there's anything wrong with them.

Can you tell me what the dump file says? I attached it to my previous post.

I also tried running Driver Verifier and got 3 BSODs saying AmUStor.sys was the driver that caused it.

And you uploaded them where?

Could that be the cause of the crashes? Those BCC were 0xD5 though, not 0x116.

The only DMPS I have seen point to BCC116

Hi,

I've attached the new dumps with the AmUStor.sys BSODs with BCC 0xD5.

Please let me know what they point to.

Thanks.

 

[zigzag3143]

Okay I will test the graphics cards to see if there's anything wrong with them.

Can you tell me what the dump file says? I attached it to my previous post.

I also tried running Driver Verifier and got 3 BSODs saying AmUStor.sys was the driver that caused it.

And you uploaded them where?

Could that be the cause of the crashes? Those BCC were 0xD5 though, not 0x116.

The only DMPS I have seen point to BCC116

Hi,

I've attached the new dumps with the AmUStor.sys BSODs with BCC 0xD5.

Please let me know what they point to.

Thanks.

Related to AmUStor.sys USB Mass Storage Driver from Alcor Micro, Corp. Yours is from 2009. I would re-install newest available. Yours is from 2009

ALCOR MICRO - Storage Product > SD Card Controller

 

[Baasha]

The only DMPS I have seen point to BCC116

Hi,

I've attached the new dumps with the AmUStor.sys BSODs with BCC 0xD5.

Please let me know what they point to.

Thanks.

Related to AmUStor.sys USB Mass Storage Driver from Alcor Micro, Corp. Yours is from 2009. I would re-install newest available. Yours is from 2009

ALCOR MICRO - Storage Product > SD Card Controller

Hi,

I cannot find any driver on that site. Also, with that link you provided, there are 6 products. The multi-card dashboard I bought was the Ultra MD2. I don't know what special # that is on that site. Even when I clicked a couple of them, it just takes me to a product description. There are no drivers. Please help!

 

[zigzag3143]

Hi,

I've attached the new dumps with the AmUStor.sys BSODs with BCC 0xD5.

Please let me know what they point to.

Thanks.

Related to AmUStor.sys USB Mass Storage Driver from Alcor Micro, Corp. Yours is from 2009. I would re-install newest available. Yours is from 2009

ALCOR MICRO - Storage Product > SD Card Controller

Hi,

I cannot find any driver on that site. Also, with that link you provided, there are 6 products. The multi-card dashboard I bought was the Ultra MD2. I don't know what special # that is on that site. Even when I clicked a couple of them, it just takes me to a product description. There are no drivers. Please help!

I would love to but this is not a popular card and the link I gave you is the only one I could find. I would try googling the driver and card.

 

[Baasha]

0x116 BSOD AGAIN!

Since I never was able to fix that problem before, I went ahead and did a fresh install of the OS (Win 7 SP1 x64) after secure erasing the SSDs. I set everything up newly and just finished installing a few programs (MS Office, Adobe etc.) and I just had a BSOD!!

It was BCC 0x116 which I think relates to the graphics cards! I am going to test the GPUs one by one (I have four) but this is ridiculous! I just did a brand new "fresh" install of the OS and I have a BSOD already!

Please look at the attached dump file(s) and let me know what it says.

Thanks.

*EDIT*
To make matters worse, I cannot even log on to my desktop now! I got to the password screen and once I entered it and hit "Enter", the screen flashed and then the PC just restarted! I got a BCC of 0x7e this time!

I've attached those Dump files as well.

HELP!

 

[zigzag3143]

First since you re-installed you are back to the 2005 asacpi.sys and needs to be updated. These two crashes were related to video subsystem.

Asacpi.sys

The pre 2009 version of this driver is a known BSOD cause.

Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).

Download and install it.

Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (not before).

 

[Baasha]

I updated those drivers and all other ones that seemed to be out of date.

The problem still persists and has actually gotten worse!

I am now getting very frequent BSODs with BCC 0x50. I am going to run MemTest 86 for a few hours to see if the RAM is faulty but I highly doubt that that's the issue.

Also, I ran Prime95 just to check the CPU and my OC again and within a couple of minutes, one of the cores, (Core # 3), said "FATAL ERROR" and it stopped running. So turned everything back to default settings and booted back into Windows. Guess what? I still got the 0x50 BSODs and random freezes/lock ups which forced hard reboots.

I ran Prime95 again for a few minutes and there were no errors so I thought there was something wrong with my OC. It has worked perfectly since last March (2011) when I got my CPU brand new (i7 990X). The CPU never reached above 76C during 100% load in Prime95. During gaming, rendering, and other CPU intensive processes, it never goes above 70C.

I already tested all four of my GPUs (EVGA GTX-580 Classified 3GB in 4-Way SLI) and they had NO problems at all! I ran several benchmarks and played several games that used the cards fully (99% usage in EVGA Precision). I even ran the GPUs overclocked to 950MHz and they had NO issues at all!

The dump files are attached so could you please look at them and let me know what's wrong?

I have a feeling it's a hardware issue because these lockups and BSODs are happening even at stock/default settings (NO OC). Do you think the CPU is FUBAR?

Please let me know at your earliest convenience.

Thanks!

 

[zigzag3143]

These crashes were caused by memory corruption probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html






Driver Verifier

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation"IRP Logging and Force Pending I/O Requests. and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table (DRT)

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[Baasha]

Thanks for the quick reply!

Memory corruption? Ugh..

Regarding the RAID driver, which driver should I update? I've updated pretty much all the drivers I can (by searching on ASUS' website and also running Driver Genius Pro 11.0). Do you mean the Intel RST drivers? I think those are up to date as well. I downloaded the latest ones and updated it when I did the fresh install of the OS. Either way, please let me know which RAID device/driver you are talking about. I am indeed running a RAID array for my OS drive; I have 2 Corsair Force GTs in RAID-0 as my "C:" drive. That's where I've installed the OS.

Anyway, here's what I've done so far:

I reset EVERYTHING to stock/default (NO OC at all) and tried to load MemTest86 (v4.00) but it never booted up! As soon as the blue screen for MemTest popped up (with the penguins), the PC would just automatically restart.

I didn't know what to do so I went back and put all the settings to the OC settings I had before! Multiplier: 33, BCLK: 133, V-Core: 1.30, QPI/VTT: 1.275V, DRAM Bus: 1.66V, and set the Memory to 1600MHz, UCLK: 3600MHz, and the RAM timings to 8-8-8-24 (2N) and rebooted and guess what? MemTest booted right up!

What worried me was that the CPU shows up as "Intel Core i9 3475 MHz" when I have an i7 990X @ 4.41GHz. I don't care about the speed so much but the CPU number/model is totally off. Also, the L1/L2 Cache show as "Unknown" and L3 Cache shows up as "None". Is that normal?

Perhaps the most important thing that really throws me off is the "Settings: RAM: 2071MHz (DDR3-4143)". 2071MHz? My RAM is only rated for 1600MHz and I've NEVER set it above that. Even in the "OC" settings, the RAM (Corsair Dominator 12GB) was ALWAYS at 1600MHz/8-8-8-24 since that's what it's rated for. I haven't run Memtest for a long time so I don't remember what these settings are supposed to be like.

I've done 3 passes so far and there are NO errors at all.

First, why won't MemTest boot up (or work) when I've set everything to default? That seems really odd. Secondly, it started to work when I put all my settings to my OC settings I've had for more than a year (never changed it after I found the sweet-spot @ 4.41GHz).

When I reinstalled the OS, I also cleared the CMOS by removing the battery. When I booted up again, the BIOS already showed the latest version (v.1001)?! Is that normal? I mean the factory (original) BIOS version is MUCH older than that one. So does that mean that there was/is something wrong with the BIOS? My motherboard is the ASUS P6T7 WS SuperComputer.

Please help!

 

[zigzag3143]

You are booting from the Memtest cd/USB right?

Thats perfectly normal.

BCC116 is a video issue but you want to eliminate as many variables as possible.

Memory corruption more often than not is related to a driver. Memory is possible but is less frequent. Its just a matter of running verifier till it catches the mis behaving driver.

 

[Baasha]

You are booting from the Memtest cd/USB right?

Thats perfectly normal.

BCC116 is a video issue but you want to eliminate as many variables as possible.

Memory corruption more often than not is related to a driver. Memory is possible but is less frequent. Its just a matter of running verifier till it catches the mis behaving driver.

I ran 7 passes of MemTest86 and there were NO errors. I turned Driver Verifier on and booted into Windows and there was no BSOD however after a couple of minutes, the outer two screens went black, the center one became blurry (as usual) and the computer just froze! I had to hard reboot and there was no BSOD code.

This is extremely frustrating.

I also uninstalled the graphics drivers with Revo Uninstaller Pro, tried a Clean Boot (disabled all Startup Items, disabled all non-Microsoft services) and booted into Windows. The weirdest thing is that when I get to the log-on screen (to enter my password), once I enter the password, it takes about 30 seconds to get into the desktop and then the screens are just black (the mouse moves however). After I get the black screens for about 10 - 15 seconds, the desktop loads correctly. This is happening even in Safe Mode! This happens even after uninstalling the GPU drivers AND performing the Clean Boot. This happens with Driver Verifier on as well.

Could this be some sort of Virus infection?

I do have to mention that I am somewhat addicted to using CCleaner. That was one of the first programs I installed after reinstalling the OS. I run it before shutting the computer down and clear all the extraneous things and run the registry cleaner as well. I've read that that could seriously damage the OS if the wrong registry key is removed. However, I always check to make sure I don't remove the wrong keys but sometimes there are hundreds of keys where I just click "Clean" and it deletes them. Could this be causing my woes? I seriously doubt this though because I've been using CCleaner for a couple of years without any issue. And, since you said the last dump(s) point to some memory corruption, it most likely is nothing to do with CCleaner.

What about the errors in Event Viewer? The most common one I keep getting is the MSE related one where the OOBE client has stopped working or something like that. I tried deleting that file (as suggested by Microsoft) and then rebooting but it keeps coming back. Should I uninstall MSE and see if that fixes the issue? Yet, I need an anti-virus program so I'm a bit nervous about removing MSE.

Please help!

 

[Baasha]

bump!

Please help!

 

[zigzag3143]

bump!

Please help!

Good news on the ram. BTW you did try the sticks individually right?

Did you try verifier again.

If you continue to crash upload the DMP files.

 

[Baasha]

bump!

Please help!

Good news on the ram. BTW you did try the sticks individually right?

Did you try verifier again.

If you continue to crash upload the DMP files.

Hi, I did not try verifier again. I did, however, get a bunch of 0x116 errors again. I'm totally boggled as to what the issue is. I've tested all four GPUs individually in all the different PCI-E slots and there were no problems at all! I was not only able to run them smoothly, but was also able to OC them quite a bit and still run the benchmarks without issue. What I've narrowed it down to is this: My motherboard has 4 PCI-E 2.0 x16 slots and 3 PCI-E x8 slots. I have the 4 GPUs in the 4 x16 slots and have 2 EVGA Power-Boost modules in two of the x8 slots for extra power for the PCI-E lanes since my MoBo does not have an extra molex connector. When I tried each GPU individually, they passed all the benchmarks without issue (both default and OC settings). When I tried SLI (2 GPUs), if I used the first and second x16 slots, the benchmark crashed within a couple of minutes. If I moved the second GPU to the 3rd PCI-E slot (so 1st and 3rd PCI-E 2.0 x16 slots taken), the crash did not occur! I then thought the 2nd PCI-E slot is to blame so I positioned one card there and the 2nd one in the 3rd slot and ran the benchmark(s) again, it did NOT crash! The same thing happened when I tried 3-way SLI or 4-Way SLI. So, long story short, it looks like if I have BOTH the first and second PCI-E 2.0 x16 slots occupied, the benchmarks crash and I get the 0x116 BCC (I've attached the dumps). So there seems to be some issue when those two are occupied which means it could be that the EVGA Power-boost is not working properly or there is something wrong with the motherboard(?). Is my logic along the right path? Also, please look at the dumps and let me know what they say. Thanks.

 

[Baasha]

*bump!

please help..

 

[zigzag3143]

*bump!

please help..

Without verifier we would be just speculating. In what way can we help?