Solved screen freezes randomly without any specific warning.

[JMDurden]

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]

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

• Click on the Start rb:
• 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]

Both your dumps show Bug Check 124

Go through this thread for an insight:
:ar: http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Let us know what you've tried

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.

[COLOR="Red"]BugCheck 124[/COLOR], {0, fffffa80079198f8, 0, 0}

Probably caused by : [COLOR="red"]hardware[/COLOR]

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

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

[COLOR="red"]WHEA_UNCORRECTABLE_ERROR (124)[/COLOR]
[COLOR="red"]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.[/COLOR]
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: [COLOR="red"] X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV[/COLOR]

BUCKET_ID: [COLOR="red"] X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV[/COLOR]

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

 

[JMDurden]

• 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]

Lets enable driver verifier to rule out buggy drivers.

Driver Verifier

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.

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]

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]

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.

:ar: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
:ar: Guide to using Memtest86+ - Geeks to Go Forums

 

[JMDurden]

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

 

[koolkat77]

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

 

[JMDurden]

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.

 

[koolkat77]

Thanks for the update.

What antivirus program are you using? (AVG as I see in the msinfo file). Do you have any 3rd party firewall program installed? If yes, uninstall them. Use the AVG Removal Tool to uninstall everything related to AVG. Make sure nothing of AVG is left on your PC as it does cause BSoDs and various other problems on computers. Uninstall Spybot S&D as well, it finds stuff, but is known to slow down and corrupt the system.

• AVG | Download tools and utilities
• Download AVG Removal Tool
• Removing Spybot - Safer-Networking Forums

After uninstalling the programs listed above, run the System File Checker that scans the integrity of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible. Run Disk Check on your hard disk(s) for file system errors and bad sectors on it.

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
• http://www.sevenforums.com/tutorials/433-disk-check.html

Recommended antivirus for windows and members on our forum:

• Microsoft Security Essentials - Free Antivirus for Windows
• Malwarebytes : Malwarebytes Anti-Malware removes malware including viruses, spyware, worms and trojans, plus it protects your computer
  
  (Download the free version of MBAM)​

Guide you may want to go through:

• http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

Run these programs (precautionary). Keep WDO for last.

• Anti-rootkit utility TDSSKiller
• http://www.sevenforums.com/tutorials/24076-malicious-software-removal-tool.html
  &
• http://www.sevenforums.com/tutorials/166445-windows-defender-offline.html?ltr=W

Get the latest versions of your browser(s) and Flash Player from the link below. (IE & Non IE listed below)

• Browsers and Plugins Downloads - FileHippo.com

Good luck

 

[JMDurden]

So, I did all of the above things mentioned and still had the occasional freeze up.
I recently decided to up my ram from 8 gb to 16 gb, which greeted me with an BSOD involving Memory Management.

 

[TVeblen]

When you completely remove all the graphics software and drivers and restart the computer Windows installs it's own WDDM1.1 driver and you need to restart again. Is this the point in which the system runs perfectly?

You should run the machine on just that generic Windows driver for a while. Make sure all is good.

If the card can't run on the manufacture's driver, but will on the generic one, then the typical reason is that the card is no good.

That new RAM problem may be related, or may be new. If it continues after above then remove the new RAM and work on the video problem. I never like to fight a war on two fronts.

 

[gregrocker]

You are getting great help here. Here's some things I notice in addition:

Since the problem happens under stress you needed to stress your RAM - Test with Memtest86+ with way more than 3 passes, like overnight or at least 6 passes.

I would replace video card to see if the problem goes away for good.

Make sure you are also getting a perfect baseline Clean Reinstall - Factory OEM Windows 7
which best practices are for retail too. This is the only way you can know for sure it's not software related. I would even wipe the HD first with Diskpart Clean Command to clean the boot sector.

 

[Dave76]

As Greg mentioned you are getting good help so far.

Your first two crashes were hardware caused, the CPU is blamed.
You will need to run several hardware tests to find the cause.

You need to give more specific answers, just telling us that something is ok or good is not helping to get to the cause of the problem.
Use Core Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Maximum CPU temp for your AMD FX-6100 is 70°C, for max core temps add 5°C, Max CPU core temps 75°C.
Processor AMD FX 6-Core Black Edition FX 6100
After the CPU temps are known you can do further testing to help find the cause.

Take the new RAM out, you're just complicating the issues by adding it now, you can add it after your system is stable.

You said you ran memtest86+, how many passes?
You need to run a minimum of 7 full passes, when it starts pass 8 you can stop it.
This will take several hours, best to run overnight.
You can stop the test if you get any errors, one is too many.

Blue Screen of Death (BSOD) Posting Instructions
When posting a new crash dump, include all System File Collection and health reports. They contain valuable information that we can use to find the cause of the crashes.
Your files are not complete, the other file information is helpful for us to analyze your system.

Your System Event Logs stop at 21 Aug '12.
To check the System Event Log settings.
1. Start Event Viewer.
2. In the console tree, expand Windows Logs and select System.
3. On the Action menu, click Properties.
4. In the General Tab, ensure 'Enable logging' is checked.
Maximum log size should be 20480
Under 'When maximum event log size is reached': select 'Overwrite events as needed (oldest events first)'
Click OK.

*If you are still not getting new System Event Logs, you can 'Clear Log' on the same page.
We need current logs to analyze.

From your System Event Logs, most recent available first:

Event[24960]:
  Log Name: System
  Source: Disk
  Date: [U]2012-08-21[/U]T15:51:38.086
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: JMD-PC
  Description: 
The driver detected a controller error on \Device\Harddisk1\DR1.

Was this before you got the new hard drive(s)?
If not or you still have the old drive installed, Download and run Seatools on both your HDDs.
How to use SeaTools for Windows
Short Drive Self Test and Long Drive Self Test.
If the short test fails, post the results, and wait on the long test.
If the short test passes run the long test. This will also take a few hours to complete, run the full Long Drive Self Test.

From your Apps Event Log,which is more recent:

Event[9284]:
  Log Name: Application
  Source: Microsoft-Windows-WMI
  Date: 2012-09-22T22:55:04.000
  Event ID: 10
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Compy
  Description: 
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

This indicates a CPU problem, after confirming the CPU temps we can run a CPU test.

You are also getting a lot of USB device errors, What USB devices are you using?

Remove Spybot - Search & Destroy, for testing, it is crashing a lot.
Use Malwarebytes while we are testing.
Download and run Malwarebytes, be sure to update it before running.

 

[JMDurden]

Alright, I'll be taking the excess ram out and redoing Memtest to make sure of what could possibly be happening.

Here's a much more recent BSOD log. I've wiped everything clean and everything with the exception of the last two are prior to the new RAM that was purchased.

I ran BlueScreenView to check what would be the cause of my problems, and every single entry came up as ntoskrnl.exe being a key factor. I don't know exactly what that might factor into, but I'm supplying said information anyway.

I finished running SeaTools, both the short and long tests, and both of my hard drives (also my GoFlex external hard drive) all passed.

I'll re-run MemTest tonight to see if there's any sort of errors that pop up.

CoreTemp is showing my PC to be running all cores at 26C, but I'll keep things updated on that the more stuff gets used.

Also, I have already removed SpyBot and have had it removed for quite some time. It is simply that my information had not been updated in a while. The USB error was from a bluetooth that I had put into my system that I had incorporated with another program to use my PS3 controllers in my computer. That problem was resolved and removed with the verifier.

Finally, at one point, I had simply removed all the drivers for my card and ran it with the native graphics. The display, while not nearly as soon, did end up freezing. The only things I can really see that being at this point is the processor, seeing how every single other issue has been removed out of the equation.

 

[TVeblen]

It is extremely rare to see a processor go defective, the only cases typically being physical damage and electrical short. They do not just "go bad".
Most likely cause at this point is your video card. Borrow and try another in the machine or get a new one as Gregrocker suggested.

 

[JMDurden]

The reason I bring it up is because One: with all the drivers removed from the video card, the display still froze.

And two, the PSU I had previously inside of this was an Xtreme Gear 700w PSU. I had purchased this computer from Craigslist so I don't know how long they had it. Seeing as I've heard so much negative about Xtreme Gear PSUs, I replaced it, but it had been in there for about a month after I bought it, not including how long they had owned the computer.

So...

 

[Dave76]

Good feedback.

Your first reason is indicating the graphics card may be bad, as mentioned, borrow a card to test or consider buying one. Try to find a place with a good return policy, in case it doesn't solve the issue.

Your second reason confirms that some components may be damaged from a questionable PSU, it does happen.

I recommend to replace the graphics card and test, first.

Second, run a CPU stress test.
OCCT stability checking tool
Run the CPU:OCCT test for at least 30 minutes, be sure to monitor your CPU and GPU temps.
Set the time before you start.
When its done, pass or fail, it will make some graphs. Post these here as they are useful for analyses.
For posting the information from the OCCT test, enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

Several of these indicating the CPU.

Event[5909]:
  Log Name: Application
  Source: Microsoft-Windows-WMI
  Date: 2012-11-11T08:55:14.000
  Event ID: 10
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Compy386
  Description: 
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.


Event[16598]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2012-11-06T10:51:35.297
  Event ID: 19
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Compy386
  Description: 
A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor ID: 0

The details view of this entry contains further information.

 

[JMDurden]

Bought a new graphics card. (EVGA GeForce 650ti) Installed the drivers for it and it froze in about 15 minutes.

It might be the drivers, I don't know, but that's what happened.

Also, here's what OCCT brought up.