Random BSOD while idle.

Yasjalnadie · Jul 19, 2012

Computer Specs

Few weeks ago I created a thread about my constant BSOD I did everything asked now I got a random BSOD I'm not to sure why I'm hoping you guys can answer this.

The reason for my passed BSOD all the time is listed below:

Beforehand my computer somehow manage to do a random OC which was causing my computer to become unstable (It was an under powered overlock) . It did a random blue screen last night and I'm not to sure why attached is the updated files.

Just to make sure you guys know I was unable to take off the Overclock for some odd reason. Here is the current voltages and what my Processor is going at.

-Voltages-
0068f626414bded7f506969fee1d3b98.png

-Processor Speed-
4f2314313032668323f49cbc07277def.png

******SIDE NOTE******

Just in case you guys do windows xp as well (Considering i duel boot)

I'm getting the BSOD sometimes on this os as well.

Computer specs

Yasjalnadie · Jul 21, 2012

Bump?

HonorGamer · Jul 21, 2012

Code:

--------------------------------------------
--------------------1-------------------
--------------------------------------------
--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------2-------------------
--------------------------------------------
--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------3-------------------
--------------------------------------------
mcupdate.dll    [url=http://www.runscanner.net/file/mcupdate.dll.html]File not found[/url]
--------------------------------------------
---------------------END--------------------
--------------------------------------------

This means this file wasn't found in the list, and it seems it could be a McAfee Anti-virus file.

So try this:
Do a full scan of your system using: Microsoft Security Essentials - Free Antivirus for Windows

Afterwards: Malwarebytes : Free anti-malware download

If nothing pops up for both of those,

try: http://www.sevenforums.com/tutorials/166445-windows-defender-offline.html

Code:

--------------------------------------------
--------------------1-------------------
--------------------------------------------
Loading Dump File [C:\Users\Justin\Desktop\Dmp Analysis folder\070512-20592-01.dmp]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64

System Uptime: 0 days 1:45:06.747

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002ac86bc, fffff8800aa6a480, 0}

Probably caused by : [b][color=red]memory_corruption[/color][/b] ( nt!MiGetPreviousNode+3c )

SYSTEM_SERVICE_EXCEPTION (3b)

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  GTAIV.exe

STACK_TEXT:  
fffff880`0aa6ae68 fffff800`02d70805 : fffff880`0aa6b500 00000000`00000000 00000000`fffde000 fffffa80`06a99660 : nt!MiGetPreviousNode+0x3c
fffff880`0aa6ae70 fffff800`02d86e8f : ffffffff`ffffffff fffffa80`07cb7c20 fffffa80`0956fd48 00000000`000007ff : nt!MiFindEmptyAddressRangeDownTree+0xd9
fffff880`0aa6aea0 fffff800`02d85cec : fffffa80`0956fb30 00000000`00000000 00000000`00002fe4 fffff880`0aa6afc0 : nt!MiCreatePebOrTeb+0x2af
fffff880`0aa6af30 fffff800`02d81913 : 00000000`00000000 00000000`00001000 00000000`00000000 00000000`00000000 : nt!MmCreateTeb+0x5c
fffff880`0aa6afc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspAllocateThread+0x35f


FAILURE_BUCKET_ID:  X64_0x3B_nt!MiGetPreviousNode+3c

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------2-------------------
--------------------------------------------
Loading Dump File [C:\Users\Justin\Desktop\Dmp Analysis folder\070512-21013-01.dmp]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64

System Uptime: 0 days 0:00:41.639

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002ccc70a, fffff880031cb558, fffff880031cadb0}

Probably caused by : [b][color=red]memory_corruption[/color][/b] ( nt!MiGetNextNode+2e )

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  LogonUI.exe

STACK_TEXT:  
fffff880`031cb798 fffff800`0302e410 : 000005ac`00000390 fffffa80`06a41b60 fffff880`05540000 00000000`04a30000 : nt!MiGetNextNode+0x2e
fffff880`031cb7a0 fffff800`03072bd1 : fffffa80`08be5b30 00000000`00001403 fffffa80`09201000 fffff800`03029d9f : nt!MmEnumerateAndReferenceImages+0x160
fffff880`031cb820 fffff800`03072e0e : fffffa80`08be5b30 fffff800`03072c01 fffff800`03072c01 fffff880`031cb940 : nt!EtwpEnumerateImages+0x51
fffff880`031cb870 fffff800`03029d16 : fffffa80`08bb5060 fffffa80`08be5b30 fffff800`03072c70 fffff880`031cb940 : nt!EtwpProcessEnumCallback+0x19e
fffff880`031cb8f0 fffff800`03072f91 : fffff880`031cba48 fffffa80`069f3f01 00000000`00000001 00000000`00000001 : nt!PsEnumProcesses+0x26
fffff880`031cb920 fffff800`03072fe7 : 00000000`00000000 00000000`00000000 00000000`00000020 00000000`00000000 : nt!EtwpProcessThreadImageRundown+0x51
fffff880`031cb970 fffff800`030decc8 : 00000000`00401802 fffffa80`069f3f28 00000000`00000000 fffff800`02e354d0 : nt!EtwpKernelTraceRundown+0x47
fffff880`031cb9a0 fffff800`030df17c : 00000000`00000000 fffff8a0`0806d590 00000000`00000080 fffffa80`06a31ae0 : nt!EtwpUpdateLoggerGroupMasks+0x268
fffff880`031cbaa0 fffff800`02eee4a2 : 00000000`00000000 fffffa80`069f3c80 fffff800`02e3f128 00000000`00000000 : nt!EtwpUpdateTrace+0x36c
fffff880`031cbb20 fffff800`03105f76 : 00000000`00000008 00000000`00000001 00000000`000000d8 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x5a21e
fffff880`031cbb90 fffff800`0310617a : fffffa80`00000010 ffffffff`80000878 ffffffff`ffffffff 00000000`00000001 : nt!PerfDiagpUpdateCKCLEnableFlags+0xe6
fffff880`031cbc70 fffff800`02ca3a21 : fffff880`010eae00 fffff800`03105f90 fffff800`02e36658 fffffa80`06a41b60 : nt!PerfDiagpProxyWorker+0x1ea
fffff880`031cbcb0 fffff800`02f36cce : 7affd09d`cc0dacab fffffa80`06a41b60 00000000`00000080 fffffa80`06a31ae0 : nt!ExpWorkerThread+0x111
fffff880`031cbd40 fffff800`02c8afe6 : fffff880`02f64180 fffffa80`06a41b60 fffff880`02f6efc0 3b8ffe1e`b95b11be : nt!PspSystemThreadStartup+0x5a
fffff880`031cbd80 00000000`00000000 : fffff880`031cc000 fffff880`031c6000 fffff880`031cae90 00000000`00000000 : nt!KiStartSystemThread+0x16


FAILURE_BUCKET_ID:  X64_0x7E_nt!MiGetNextNode+2e

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------3-------------------
--------------------------------------------
Loading Dump File [C:\Users\Justin\Desktop\Dmp Analysis folder\071412-15787-01.dmp]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64

System Uptime: 0 days 0:00:08.829

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8008439038, 0, 0}

Probably caused by : AuthenticAMD

WHEA_UNCORRECTABLE_ERROR (124)

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff880`01fbc6f0 fffff800`01ec3ca9 : fffffa80`08439010 fffffa80`06a36b50 00000000`0000000c 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`01fbcc10 fffff800`01da4547 : fffffa80`08439010 fffff800`01e1e2d8 fffffa80`06a36b50 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`01fbcc40 fffff800`01d0b945 : fffff800`01e7fae0 00000000`00000001 fffffa80`07a9a010 fffffa80`06a36b50 : nt!WheapProcessWorkQueueItem+0x57
fffff880`01fbcc80 fffff800`01c8a841 : fffff880`010b6e00 fffff800`01d0b920 fffffa80`06a36b00 01cd24be`f67aedd0 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`01fbccb0 fffff800`01f17e6a : 00000000`0271c000 fffffa80`06a36b50 00000000`00000080 fffffa80`06a2d890 : nt!ExpWorkerThread+0x111
fffff880`01fbcd40 fffff800`01c71ec6 : fffff880`01e5d180 fffffa80`06a36b50 fffff880`01e67fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`01fbcd80 00000000`00000000 : fffff880`01fbd000 fffff880`01fb7000 fffff880`01fbc9e0 00000000`00000000 : nt!KiStartSystemThread+0x16


FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

--------------------------------------------
---------------------END--------------------
--------------------------------------------

From what this is showing it could be a possible memory problem, so run a http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

If that shows up nothing then run a hardware test:

BugCheck 0x124

You have a 0x124 hardware bugcheck. If the system is still under warranty, I would recommend sending it in to have diagnostic tests done and any bad hardware replaced.

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!!!

For your hardware stop 0x124 crash, read through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html and use the following hardware checks to supplement that link.

If you are overclocking any hardware, please stop.

If you have an SSD, make sure the following are up to date:

SSD firmware

BIOS Version

Chipset Drivers

Hard disk controller drivers/SATA drivers

If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Run all but the advanced tests with SeaTools for HDDs.
SeaTools for Windows

SeaTools for DOS

Monitor temperatures during the following tests.

Use the following programs to monitor the temperatures.

Real Temp is a good CPU temperature monitor.

Speccy - System Information - Free Download will monitor all hardware temperatures.

HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.

Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.

Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.

Follow the steps for doing CPU stress test using IntelBurnTest

Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:

Shut down and turn off your computer.

Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)

Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.

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. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.

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

Remember to read closely through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html for the crash.

Coutesy of: writhziden

Try these first, and post back results. If the crashes keep continueing we will continue.

Random BSOD while idle.

Yasjalnadie

New member

My Computer

Yasjalnadie

New member

My Computer

HonorGamer

New member

My Computer