Random blue screens at idle

Asus M4a78t-e - motherboard - atx - amd...
March 23, 2010 at 14:11:12
Specs: Microsoft Windows 7 Home Premium, 3.382 GHz / 3838 MB
I resovled an issue with cool & quiet because my pc was blue screening often. Found out OCing and cool & quiet does not work. Now at idle while the screen saver is on I get the error. It only happens at idle. here is the bsod.

I'm thinking it has soemthing to do with the vista cache driver.

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

Loading Dump File [C:\Windows\Minidump\032210-22074-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\WinDDK\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c19000 PsLoadedModuleList = 0xfffff800`02e56e50
Debug session time: Mon Mar 22 22:42:29.239 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:08.534
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, fffffa8004e5f038, 0, 0}

Probably caused by : hardware

Followup: MachineOwner

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

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.
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004e5f038, 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





fffff880`02da16f0 fffff800`02ed3a89 : fffffa80`04e5f010 fffffa80`036f1040 00000000`0000000f 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02da1c10 fffff800`02db5547 : fffffa80`04e5f010 fffff800`02e2e5f8 fffffa80`036f1040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02da1c40 fffff800`02d1db95 : fffff800`02e90360 00000000`00000202 fffff880`02da1ca8 00000000`00000018 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02da1c80 fffff800`02c98161 : fffff880`00e88e00 fffff800`02d1db70 fffffa80`036f1040 0000052a`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02da1cb0 fffff800`02f2e166 : 0000052a`00000000 fffffa80`036f1040 00000000`00000080 fffffa80`03670b30 : nt!ExpWorkerThread+0x111
fffff880`02da1d40 fffff800`02c69486 : fffff880`02b63180 fffffa80`036f1040 fffff880`02b6dfc0 0000052a`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02da1d80 00000000`00000000 : fffff880`02da2000 fffff880`02d9c000 fffff880`031f95e0 00000000`00000000 : nt!KxStartSystemThread+0x16



MODULE_NAME: hardware

IMAGE_NAME: hardware




Followup: MachineOwner

1: kd> lmvm hardware
start end module name
Mini Kernel Dump does not contain unloaded driver list

See More: Random blue screens at idle

Report •

March 23, 2010 at 14:25:46
I don`t think this is a driver issue. The error has to do something with the hardware. First of all, download Memtest, burn it to a CD, boot from it and see if it finds errors.

A question for you: Is the processor overclocked?

Google is your friend



Keyboard not present,press F1 to continue...

Report •

March 23, 2010 at 15:38:09
Not only cool 'n' quite, u need to disable other settings like spread spectrum & lock pci-e @ 100mhz. Go to bios & load default settings then save, go to windows and see if u got any bsod. After overclocking cpu, u need to stress the cpu using prime95 or other soft.

Report •

March 23, 2010 at 15:52:29
yes I've ran memtest and no problem. and yes I'm overclocking. thanks for the info on spread spectrum, didn't know.

Report •

Related Solutions

March 23, 2010 at 16:08:46
holy smoke. disabled cpu & pcie spread spectrum and then ran amd overdrive benchmark and incressed 226 pts 8113 t0 8339. seems stabel will run stability test now thanks for the tip. I will try the idle tonight when I go to bed.

Report •

March 23, 2010 at 16:54:51
one thin that I've noticed to is when I open amd overdrive which has a black background int eh light areas sometimes it sparkles with green dots. before I rebooted it was fine but this times it has sparkles.

Report •

March 23, 2010 at 17:23:08
could this be a psu issue? the sparkling dots make me wonder if the load is not enough.

Antec earthwatts EA500 500W

+3.3V@25A,+5V@24A,+12V1@22A,+12V2@22A,-12V@0.8A, +5VSB@2.5A

All i have in my system is a blu-ray drive and sata 1tb hard drive. I use an onboard graphics.

AMD Phenom II X2 550 Black Edition Callisto 3.1GHz Socket AM3 80W Dual-Core Processor


the cores have been unlocked
AMD Phenom(tm) II X4 B50 Processor

Report •

March 23, 2010 at 21:16:37
figured it out. I asked the question why dont they just sell the cpu's as 4 cores. here is why.

It allows them to get some value from defective quad core chips.

The quad core chip would be a relatively large silicon die.
If one or two of the cores had some small problem, the wafer
sort process could identify them as candidates for packaging
as dual core processors.

The AMD test will test all sorts of stuff that never
arises in normal usage. Compilers don't use or emit code
for all possible instructions on the processor. Only a
small subset of all possible instructions is generated
by the average compiler. (An evil person writing assembler
code can do that, if they want.)

The thing that is defective, might be something not normally
used. In other words, it is highly unlikely that the end user
will be able to figure out what is broken in the unlocked cores.
My suggestion to use Prime95 is only a bit of a test - by
no stretch of the imagination is it a complete test.

Or, the thing that is defective, might only be defective at
elevated clock rate. If you're making processors, you likely
test them at a few hundred MHz above the stated operating
frequency. That takes some aging and parameter shifting into
account over time.


Report •

March 23, 2010 at 23:29:34
Err....seems that overclocking has compromised the system stability. It`s the best to restore the system defaults, and to start over (or ask question about overclock on the forum.)

Google is your friend



Keyboard not present,press F1 to continue...

Report •

Ask Question