Solved BSOD 116 when attempting to play games

[oldhome7]

Well, recently I just got a new power supply as an RMA for my last one that popped a cap and ruined by old motherboards southbridge so it prompted me to upgrade to my current 2500k setup. I did manage to keep everything and not have to wipe with the new hardware which was just cpu, mobo, and ram.

It's been a great setup until recently when I want to play games I would randomly get a black screen and about a minute later a reboot, upon inspection with bluescreenview I noticed it was a 116 error. At first I thought it was a Lucidlogix Virtu driver issue so I disabled that and swapped the cable to my gpu, no dice same problem and same error. Then, I figured it was conflicting drivers left over that I missed so I'm now on a fresh install and I'm getting the same issue. I can even duplicate it running OCCT's power supply test, it takes under 30 seconds.

Additional info that may or may not help/be needed: CPU overclock does not make a difference, GPUs, RAM, and iGPU have never been overclocked.

Thanks for any help, it's getting annoying running games on the Intel HD3000.

 

[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

 

[oldhome7]

I knew I forgot to mention a couple things. Stress testing with FurMark 1.9.2 I had no issues in a 22hr run and my GPUs level off around 70c. Prime95 gives no issues either in a 31hr run don't remember temps exactly but it was around 60c. It only seems to happen when I stress both the CPU and GPUs at the same time. That's why I'm leaning towards a faulty PSU Antec sent me as a replacement?

 

[oldhome7]

Well, I've got an update. I got another BSOD and restart tonight and now it sits at the windows 7 loading screen for quite a while and takes it's sweet time logging on, it's down at about 800x600 resolution, and when I can finally do anything it takes about 5 minutes and it crashes. Any ideas?

 

[writhziden]

http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html up to three times with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to provide us with the sfcdetails.txt file if errors occur.

NOTE: your drive may not be C: and could be D:, E:, F:, or even G:. It will not be X:. To determine your drive, use the following commands in a command prompt to find the Windows directory:

C:
dir
D:
dir
E:
dir
F:
dir
G:
dir
​

etc. until you find the Windows directory.

 

[oldhome7]

I've ran SFC multiple times from in windows and from my HBCD usb drive. Each time it comes back clean.

Another update, it now won't even make it to the logon screen before it reboots. I'm at a toss up between some massively nasty virus/malware that found it's way in even on a clean install, which could be possible from one of my storage drives, or my psu is really on its way out.

 

[James7679]

oldhome7, I see that you are running crossfire. Have you tried removing your #2 GPU? If that does not work, remove #1 and put #2 in it's place and try again.

 

[oldhome7]

No, I have not tried that only because my reasoning is that if it does fix the problem it's only because it's less stress on the psu and eventually I do plan on upgrading to either 6 or 7 series crossfire here soon which are quite a bit more power hungry than those current 4850s.

 

[James7679]

Not necessarily. You have to understand the complexity of the 0x116 error. There are many points of reference to this error. 1 could be that the NB voltage is dropping, 2 could be that one of your GPUs are dying, 3 could be bad memory in one of the GPUs. Test them individually to see if the problem goes away.

Also, your PSU, should be more than sufficient to run your setup.

A few other things you can try;
Load the BIOS to run at "Fail Safe Settings"
Load the BIOS to run at "Optimized Settings"
If you are running the XMP profile on your memory turn it off.
If you are running without the XMP profile, try turning it on.

 

[oldhome7]

There is no "Fail Safe" option, but I did try the "Optimized" equivalent, and no XMP option but I did notice when I first built this one it was overvolting my RAM from the very first power on but I set it down to the spec'd 1.35, well 1.349 was the closest my mobo would get.

I didn't think Sandy Bridge had an NB anymore, thought it was all QPI and such? I have contemplated a dying GPU since one is as old as the original build two mobos before this current one, then I got a new mobo for xfire, now this one.

Also, Antec's warranty replacements are refurb parts that's the only reason I was thinking that it might be going out as well because I did have a TPQ-1000 that was bought brand new for the xfire setup and has lasted me a good 3+ years before it popped a cap.

I also noticed today when I got home from school that "MiniXP" from my HBCD usb drive froze during a chkdsk scan that I started this morning. Alas, no error code though because it all runs in RAM. And, before it's asked the RAM checked fine with a 9 1/2 pass run of memtest86+ overnight already.

 

[writhziden]

   Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!

Strip down your system to run only the bare essentials: one RAM module, the CPU, motherboard, one hard disk, one graphics card (or use onboard graphics if you have it), keyboard, mouse, and one monitor. See if you are then able to start Windows and run stable. If it is stable, add one piece of hardware back at a time until you get crashes again. Take notes of what hardware you add and how the system responds to the hardware changes.

As you add and remove hardware, follow these steps for ESD safety:

1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.

Once these steps have been followed, it is safe to remove and replace components within your computer.

 

[oldhome7]

Well, I did get so far as to pull both GPUs and all my storage drives tonight and test and it made no difference. I cannot get down to one drive as I am running a Raid 0 system drive. It did get far enough in that the device manager popup said it was installing Windows, if that says anything. I also got another BSOD but haven't gotten around to grabbing it, but I'll save that for tomorrow and see if HBCD will last long enough to at least grab the code.

 

[writhziden]

What device did Device Manager install?

I wonder if your RAID configuration is intact. RAID tends to degrade if there is any data corruption on the system. When was the last time you ran a http://www.sevenforums.com/tutorials/433-disk-check.html on your drives?

Windows 7 is rather finicky when it comes to RAID, so we generally do not recommend using it. There is also the general opinion in the technical circles that RAID is not a good idea for the average user: Why RAID is (usually) a Terrible Idea - Puget Custom Computers

 

[oldhome7]

It just said Windows and a reboot was required. I did run chkdsk when it first started intermittently acting up from command prompt with options /f /r /b just for redundancy, i know b>r>f. It never came back with any errors or relocated sectors.

Also, I have never had any problem with Raid0 before with 7 even before this last clean install. I did think that maybe one drive was failing so I switched my BIOS settings back to IDE mode and ran an bunch of different HDD tests from my HBCD drive to check since Raid0 doesn't seem to like S.M.A.R.T. But, none of those tests came back with any errors so I'm assuming the drives are okay.

Edit: So I tried booting my Ubuntu usb drive to shrink the partition on my 2tb drive so I could clone my raid0 partition over to it and I ran into a "Machine check error" after selecting the usb drive to boot from with the boot selection popup.

 

[writhziden]

Did you switch back from IDE after running the hard disk tests?

 

[oldhome7]

Yes I switched back to RAID mode afterwards. Apparently it's a common problem with ASRock motherboards and warm boots trying to load that, a cold boot fixed that problem.

I'm thinking it was a bad driver or some hidden virus/malware as I finally got it to boot fine but as soon as I moved my mouse it would BSOD so I said f*** it and did another clean install and I'm slowly installing things one at a time trying to find out, and waiting for Avira's rescue cd to finish downloading because Avira said I had a hidden something that could only be fixed from the rescue cd.

 

[writhziden]

The security experts sometimes recommend a CLEAN clean install. The additional step before the clean install is to run the clean all command through Diskpart: http://www.sevenforums.com/tutorials/52129-disk-clean-clean-all-diskpart-command.html

 

[oldhome7]

Whenever I do a clean install I always DBAN first set on the DoD 5220.22-M setting. I think that's a little more thorough than the DiskPart command. I could just be paranoid as I Gutmann Wipe before I sell a hard drive.

 

[writhziden]

In that case, any viruses should have been wiped through the clean install, so why is avira complaining?

 

[oldhome7]

I didn't wipe my storage drives, I just wiped the Raid array, so maybe something there...