Windows 7: screen freezes randomly without any specific warning.

JMDurden · 22 Sep 2012

Well, backstory. I had invested in purchasing a computer because the people who had owned it previously had problems with it constantly crashing. I decided to buy it and challenge myself in fixing it. So far, I've fixed it up to the point where the crashing is far less frequent to what it used to be, but it still does crash from time to time.

I had initially purchased a new hard drive because I thought that would be the issue, but it seemed as though that wasn't the case. I replaced the original, and terrible, Xtreme Gear PSU, and that seemed to solve the problem for a good bit, but the computer still does freeze on occasion. I've been told it could be an overheating issue, but since the inclusion of my new PSU (Corsair TX750), the heat hasn't gotten to any sort of high level, and even still, it hadn't gone very high in the past.

Now, I'm just confused and would like to see if anyone else could help me out.

Most of the time, everything just freezes and nothing is responsive. I've really only experienced a BSOD three or four times in the past, and the rest has all been complete freezing.

Thank you in advance,

-JMD!

**koolkat77** · 23 Sep 2012

Please upload your msinfo32.nfo file. To get this:

Click on the Start
Type msinfo32 into the Search programs and files box
When it opens, go to File, Save
Save as msinfo32.nfo and save in a place you will remember
Let it finish the process of gathering and saving the system info
Right click the .nfo file, click send to compressed (zipped) folder
Upload the .zip file here.

**koolkat77** · 23 Sep 2012

Both your dumps show Bug Check 124

Go through this thread for an insight:

Stop 0x124 - what it means and what to try

Let us know what you've tried

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Yusra\Downloads\SF_22-09-2012\092212-23415-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`03213000 PsLoadedModuleList = 0xfffff800`03458e90
Debug session time: Sun Sep 23 08:53:36.348 2012 (UTC + 6:00)
System Uptime: 0 days 0:00:08.550
Loading Kernel Symbols
..................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80079198f8, 0, 0}

Probably caused by : hardware

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80079198f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031865b0 fffff800`034d6d29 : fffffa80`079198d0 fffffa80`06a40040 fffffa80`61656857 00000000`00000609 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03186ad0 fffff800`033b6217 : fffffa80`079198d0 fffff800`03430658 fffffa80`06a40040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03186b00 fffff800`0331d865 : fffff800`034923a0 00000000`00000001 fffffa80`07753920 fffffa80`06a40040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03186b40 fffff800`0329da21 : fffff880`011c9e00 fffff800`0331d840 fffffa80`06a40000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03186b70 fffff800`03530cce : 00000000`00000000 fffffa80`06a40040 00000000`00000080 fffffa80`06a25040 : nt!ExpWorkerThread+0x111
fffff880`03186c00 fffff800`03284fe6 : fffff880`030a5180 fffffa80`06a40040 fffff880`030b0040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03186c40 00000000`00000000 : fffff880`03187000 fffff880`03181000 fffff880`03fec450 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

Followup: MachineOwner
---------

JMDurden · 24 Sep 2012

Nothing is overclocking.
Everything is cooled efficiently.
Everything is up to date with the exception of my graphics card, because the updates nVidia puts out are crap and make the problem worse.
I updated the bios, which initially caused my computer to not be able to boot, but I got that fixed.
I keep Windows updated as much as possible
I ran mdsched and it found no memory problems, I'm going to get memtest86 working probably tonight and see if it does anything.

**koolkat77** · 24 Sep 2012

Lets enable driver verifier to rule out buggy drivers.

Driver Verifier

Quote:

I'd suggest that you first backup your data 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/Windows 7 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 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 and click Next
- 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.

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 (an estimate on my part).

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.
Driver Verifier - Enable and Disable

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Quote: Originally Posted by Capt.Jack Sparrow

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

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.

JMDurden · 29 Sep 2012

Okay, so I ran the verifier and encountered two different things.

The first thing was an issue with one of the controllers I was using. Whenever I plugged in the bluetooth for it, the computer insta-crashed. So, I decided that could be this issue and removed it.

So, I kept the verifier on to see if I could find anything else. While the verifier was running, it froze the system whenever I was on my browser, but it didn't show a blue screen. It simply froze the display and I had to hard reboot.

If it's important, the website I was browsing was 4chan, which I had never had a problem with browsing before. I'm thinking it COULD be an extension issue (since I have two running for that site currently), but I'm not entirely sure considering it froze at different times. I'm more so leaning towards the fact that it's a total browser issue considering that the last time I ran my computer and let it stay on overnight (without 4chan being open or any of the extensions enabled) the computer still froze.

This was pre-verifier.

**koolkat77** · 29 Sep 2012

Did you get any BSoDs with verifier enabled?
Verifier does make the system laggy and makes the bad drivers bring out BSoDs.

Did you do any test with Ram?
If not, do it now.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

RAM - Test with Memtest86+

Guide to using Memtest86+ - Geeks to Go Forums

JMDurden · 30 Sep 2012

I ran Memtest86 and both of my sticks of ram came up with no errors after running several tests in both slots.

**koolkat77** · 30 Sep 2012

ok, did you check if all the hardware is compatible with each other?

JMDurden · 15 Oct 2012

Sorry for such a late reply, things have been somewhat hectic.

I recently purchased a new motherboard and everything together. I still got freezing issues, so I checked my graphics card and completely uninstalled it (driver fusion + ccleaner) and the computer ran perfectly. So, the issue was with the graphics card.

For some reason now, I've gotten the card to be stable via updating every single thing I could find. The only thing that consistently causes my computer to display freeze is when I watch anything Youtube-esque (flash related). It'll tend to run one or two videos and then the next one will cause my entire PC to lock up. It doesn't do it for anything else.

I've disabled hardware acceleration on flash video and I've switched between Adaptive and Use Maximum Performance on the Nvidia control panel with no avail.

I just want to watch my videos again.

Windows 7: screen freezes randomly without any specific warning.

screen freezes randomly without any specific warning. problems?