BSOD's 0x00000124, 0x0000009f, 0x000000f4 , 0x000001e, 0x000000d1

writhziden · 28 Mar 2012

Windows does not appear to be running as it should:

Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

Antisladd · 28 Mar 2012

Got another crash where the computer started to slowly lagg more and more but this time it ended with a bsod after about 5 minutes, got the 0x00000124 code this time again.
will include the new dump as zip, also got the memorydump if that would be helpfull? but it is 120mb compressed

and as i have mentioned, vcore is auto and memory volt is auto aswell

I also now saw ur last post so i will test that and se what happens.
Thanks!

Antisladd · 29 Mar 2012

First i tried binks option and ran it in windows by starting command promt as administrator and typing the sfc /scannow command, found nothing 3 times in a row with restarts inbetween
then i ran one round using the windows disk and going to repair and then the sfc / scannow /....... w/e it was.
non of them found anything wrong

writhziden · 29 Mar 2012

That's good that there were no obvious problems with Windows. Do you use any optimization tools to clean your registry?

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\Antisladd\032912-17893-01\032912-17893-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02a0e000 PsLoadedModuleList = 0xfffff800`02c52650
Debug session time: Wed Mar 28 21:48:53.418 2012 (UTC - 6:00)
System Uptime: 1 days 14:55:51.932
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8009776028, f2000040, 800}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
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: fffffa8009776028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000800, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  cpuz.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`031dda58 fffff800`03008a3b : 00000000`00000124 00000000`00000000 fffffa80`09776028 00000000`f2000040 : nt!KeBugCheckEx
fffff880`031dda60 fffff800`02b9ac43 : 00000000`00000001 fffffa80`09855660 00000000`00000000 fffffa80`098556b0 : hal!HalBugCheckSystem+0x1e3
fffff880`031ddaa0 fffff800`03008700 : 00000000`00000728 fffffa80`09855660 fffff880`031dde30 fffff880`031dde00 : nt!WheaReportHwError+0x263
fffff880`031ddb00 fffff800`03008052 : fffffa80`09855660 fffff880`031dde30 fffffa80`09855660 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`031ddc50 fffff800`03007f0d : 00000000`00000004 00000000`00000001 fffff880`031ddeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`031ddc90 fffff800`02ffbe88 : fffffa80`0aa57000 fffffa80`06990920 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`031ddcc0 fffff800`02a8962c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`031ddcf0 fffff800`02a89493 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`031dde30 fffff880`0f426dca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`009b0b00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x1eadca


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

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

Something is not happy with your graphics card. Hard to tell if it is software or hardware related. Did you Troubleshoot Application Conflicts by Performing a Clean Startup?

Do some hardware checks:

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). 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 Hardware - Stress Test With Prime95 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 a CPU stress test using IntelBurnTest