Full System Lockup, no error.

JadeXG · 08 Jan 2012

The problem:
Computer freezes (Screens are frozen in place, no inputs, all processes stop). Recovery is by hard reset.

The System:
Windows 7 Professional x64
MSI p67A-G45 Motherboard
Intel i7-2600k CPU
16 GB Corsair 1066 RAM
1x SDD (Corsair)
1x HDD (500GB)

New OS install (less than 1 week)
New Computer build (less than one week)

So, I did some homework (certain I've missed a step, hence the post) and:
Updated my drivers
Updated my drivers again
Updated my BIOS
Disabled all non-essential start-up programs
Ran a chkdsk on both drives
Checked CPU temperatures under IDLE and stressing loads
Checked case temps ''
Ran Event Viewer, and didn't notice anything around the "Critical Kernel- Power Event ID 41" errors. Nothing remarkable is happening within 10-30 minutes of lockup.

I'm totally at a loss as to how to re-stabilize the system. It's crashing about once every 1 to 2 Hours.

usasma · 09 Jan 2012

The only thing that jumps out (to me) is video testing. Since it's a new install and you've updated the drivers, I'd check the video. Use the free video tests at this link: Hardware Diags
Also check the video card to make sure:
- that it has adequate airflow getting to it
- that the cooling fan is working
- that the cooler isn't clogged with dust/dirt
- that the power plug is firmly plugged into the card (if so equipped)

Only 55 Windows Updates since SP1 - most systems have 60-70 or more. Please visit Windows Update and get all available updates.

MSINFO32 reports one BSOD, a STOP 0x116 (video). Try the troubleshooting steps at this link: STOP 0x116: VIDEO_TDR_ERROR troubleshooting

You have an MSI motherboard. If you have MSI Afterburner installed, please uninstall it immediately. It (and Riva Tuner/EVGA Precision) are known to cause BSOD's in some Win7 systems.

BTW - nice job in updating drivers. There was only 1 2009 driver in the memory dump (audio) - the rest were 2010 and 2011, we don't see that very often!

The BSOD is the same as the one in MSINFO32 that I mentioned above. Try those steps and see what happens.

BSOD BUGCHECK SUMMARY

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010712-16255-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan  7 00:19:03.758 2012 (UTC - 5:00)
System Uptime: 0 days 0:10:14.601
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+78b8 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
Bugcheck code 00000116
Arguments fffffa80`0dbfc010 fffff880`072078b8 00000000`00000000 00000000`0000000d
BiosVersion = V1.10
BiosReleaseDate = 03/31/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

JadeXG · 09 Jan 2012

So I remember the BSOD you're looking at. I was trying to see just how much I could get away with on the new videocard, so I linked 2 monitors into a single display ('Eyefinity') and then told the cards to use CrossfireX on that new display. Needless to say it was a little too much for the system to handle.

Your comment did lead me down a new path, though initial results are not promising: I've removed the 2nd video card, presuming that maybe the power comsumption on my 600W power supply is too much on one part (I only have 2 6-pin PCI-E power connectors, and was using adapters to pull additional power from molex connections. Within 20 minutes of this new single card setup, the system's already locked up once.

I can say, if it helps, that it seems I can set the problem off by starting a file transfer between an onboard drive and an external HDD(USB connection). This won't always crash the system, but is probably somewhere in the 10-25% likelyhood of crash. The internal drive has undergone a chkdsk, and the external was reformatted recently.

I'm also wondering if this might be a problem with pagefile? I had to take the pagefile on my SDD off of 'system managed size' because with 16 GB of RAM, it wanted a 16 GB pagefile on the 60 GB SDD.

I appreciate what help I've already gotten, but if anyone else has any Ideas, I'm all ears.

JadeXG · 10 Jan 2012

So with no new suggestions I am thinking about:
Re-installing Windows 7 in hopes that the problem magically goes away
...and if that fails going to Fedora. Oh joy.

usasma · 10 Jan 2012

Please make a new Windows_NT6_BSOD_jcgriff2.zip report
We'll review the contents to see what's changed since the last time.

JadeXG · 10 Jan 2012

I did some google searching and found some interesting information that may yet abate my (probably apparent) frustration. It looks like the EuP 2013 power states and intel C state settings routinely crash the P67A motherboards. I say this as I'm trying to force it to crash again. If it does, I'll post a report, if not, I'll post the full fix. Thank you, Usasma for the help.

JadeXG · 10 Jan 2012

Problem Solved!
In sum (so that this is easily found by search): MSI P67A motherboard, (G45 in this case, but others have noted it in other GXX systems as well) Intel i3, i5, i7 (i7 in this case) CPU system freezes without a BSOD. THis is caused primarily by the Intel C state setting, which underclocks processors when not needed. Also potentially at fault is the EuP 2013 power setting, particularly if the instability occurs coming out of sleep mode.

To fix the problem: Enter the BIOS, go to Green Power, disable EuP 2013 and Intel C state.

Again, thanks for all the help I received here, it got me away from what the problem wasn't, which led me to what it was. Much appreciated.