I did a clean install of Windows 7 Professional but keep getting a persnicketty STOP: 0x00000124 error after starting normally. The error doesn't occur in any of the safe modes.
I've not slept, shaved, bathed or eaten in 5 days and I miss my wife and kids. Our cats have been eyeing me - like prey!
The dump is attached. Any assistance towards ridding my machine of this most unwanted pestilence would be greatly appreciated.
Webdaddy Hi and welcome
Watch out for your wife first, and the cats second. This DMP was probably caused by hardware. I would guess (most of the dmp file was useless) memory.
I would
Download and run memtestx86 for several hours (preferably over night to see if heat issue presents itself)
Run a system file check to verify and fix your system files. to do that you type cmd in search>right click and run as admin> SFC /SCANNOW
If you are overclocking stop
if you are running a raid upgrade its driver
Since heat might be an issue download cpu-z, and gpu-z (both free to keep an eye on temps.
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\120509-23484-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82812000 PsLoadedModuleList = 0x82951570
Debug session time: Sat Dec 5 17:03:39.203 2009 (GMT-5)
System Uptime: 0 days 0:00:34.609
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
.....
2: kd> !analyze pv
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, 8600c01c, b2000040, 800}
Probably caused by : hardware
Followup: MachineOwner
---------
Hello, Zigzag3143! I would have thanked you for your prompt reply had I not lost consciousness a few hours after watching my Longhorns survive a particularly vicious Cornhusker defense. My machine has been running since my original post (@ 14 hours ago) in Safe w/Networking mode without incident so overheating doesn't appear to be an issue (although I do intend to run memtestx86 just to be certain). I've installed the monitors you've suggested but will have to wait until my machine can run in Normal mode long enough to obtain any useful information from them. In the meantime, I'll be reconnecting with my loved ones (after bathing, of course).
Quote