BSOD *Stop 124. Tried everything i could think of

Ryouichi Kiriyami · Feb 25, 2015

Major issue. upon reading multiple threads for hours with many restarts. i just can NOT figure out this blue screen. its telling me error code 124.
ive tried going into my bios and turning cap 6 to disabled from auto. ive checked the temperatures. the CPU and GPU dont get above 30c, ive mem tested the RAM. with 0 problems. ive also stress tested the CPU and GPU with flying colors. ive made sure my GPU had its latest drivers. ive made sure my PSU isnt dieing by using a multimeter to gauge the readings. checked CPUID to see if all voltages are right with that.
i am COMPLETELY stumped on this. Currently trying to gain access to the .dmp file

i should probably state. that when the "BSOD" happens. there is no blue screen. i use 2 monitors. one turns one color. and the other turns another. with odd lines

.DMP file information

crash dump file: C:\Windows\Minidump\022415-18735-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A63CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007AEC8F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

ntoskrnl.exe fffff800`02c1e000 fffff800`031fb000 0x005dd000 0x4a5bc600 7/13/2009 3:40:48 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe
hal.dll fffff800`031fb000 fffff800`03244000 0x00049000 0x4a5bdf08 7/13/2009 5:27:36 PM
kdcom.dll fffff800`00bc9000 fffff800`00bd3000 0x0000a000 0x4a5bdfdb 7/13/2009 5:31:07 PM
mcupdate.dll fffff880`00c52000 fffff880`00c5f000 0x0000d000 0x4a5bdf65 7/13/2009 5:29:09 PM
PSHED.dll fffff880`00c5f000 fffff880`00c73000 0x00014000 0x4a5be027 7/13/2009 5:32:23 PM Microsoft® Windows® Operating System Platform Specific Hardware Error Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\PSHED.dll
CLFS.SYS fffff880`00c73000 fffff880`00cd1000 0x0005e000 0x4a5bc11d 7/13/2009 3:19:57 PM
CI.dll fffff880`00cd1000 fffff880`00d91000 0x000c0000 0x4a5be01d 7/13/2009 5:32:13 PM
Wdf01000.sys fffff880`00e33000 fffff880`00ed7000 0x000a4000 0x4a5bc19f 7/13/2009 3:22:07 PM
WDFLDR.SYS fffff880`00ed7000 fffff880`00ee6000 0x0000f000 0x4a5bc11a 7/13/2009 3:19:54 PM
ACPI.sys fffff880`00ee6000 fffff880`00f3d000 0x00057000 0x4a5bc106 7/13/2009 3:19:34 PM
WMILIB.SYS fffff880`00f3d000 fffff880`00f46000 0x00009000 0x4a5bc117 7/13/2009 3:19:51 PM
msisadrv.sys fffff880`00f46000 fffff880`00f50000 0x0000a000 0x4a5bc0fe 7/13/2009 3:19:26 PM
pci.sys fffff880`00f50000 fffff880`00f83000 0x00033000 0x4a5bc117 7/13/2009 3:19:51 PM
vdrvroot.sys fffff880`00f83000 fffff880`00f90000 0x0000d000 0x4a5bcadb 7/13/2009 4:01:31 PM
partmgr.sys fffff880`00f90000 fffff880`00fa5000 0x00015000 0x4a5bc11e 7/13/2009 3:19:58 PM
volmgr.sys fffff880`00fa5000 fffff880`00fba000 0x00015000 0x4a5bc11d 7/13/2009 3:19:57 PM
volmgrx.sys fffff880`00d91000 fffff880`00ded000 0x0005c000 0x4a5bc141 7/13/2009 3:20:33 PM
pciide.sys fffff880`00fba000 fffff880`00fc1000 0x00007000 0x4a5bc115 7/13/2009 3:19:49 PM
PCIIDEX.SYS fffff880`00fc1000 fffff880`00fd1000 0x00010000 0x4a5bc114 7/13/2009 3:19:48 PM
mountmgr.sys fffff880`00fd1000 fffff880`00feb000 0x0001a000 0x4a5bc11a 7/13/2009 3:19:54 PM
atapi.sys fffff880`00feb000 fffff880`00ff4000 0x00009000 0x4a5bc113 7/13/2009 3:19:47 PM
ataport.SYS fffff880`00e00000 fffff880`00e2a000 0x0002a000 0x4a5bc118 7/13/2009 3:19:52 PM
amdxata.sys fffff880`00ff4000 fffff880`00fff000 0x0000b000 0x4a12f2eb 5/19/2009 9:56:59 AM
fltmgr.sys fffff880`00c00000 fffff880`00c4c000 0x0004c000 0x4a5bc11f 7/13/2009 3:19:59 PM
fileinfo.sys fffff880`010ee000 fffff880`01102000 0x00014000 0x4a5bc481 7/13/2009 3:34:25 PM
Ntfs.sys fffff880`01256000 fffff880`013f9000 0x001a3000 0x4a5bc14f 7/13/2009 3:20:47 PM
msrpc.sys fffff880`01102000 fffff880`01160000 0x0005e000 0x4a5bc17c 7/13/2009 3:21:32 PM
ksecdd.sys fffff880`01200000 fffff880`0121a000 0x0001a000 0x4a5bc156 7/13/2009 3:20:54 PM
cng.sys fffff880`01160000 fffff880`011d3000 0x00073000 0x4a5bc814 7/13/2009 3:49:40 PM
pcw.sys fffff880`0121a000 fffff880`0122b000 0x00011000 0x4a5bc0ff 7/13/2009 3:19:27 PM
Fs_Rec.sys fffff880`0122b000 fffff880`01235000 0x0000a000 0x4a5bc111 7/13/2009 3:19:45 PM
ndis.sys fffff880`01407000 fffff880`014f9000 0x000f2000 0x4a5bc184 7/13/2009 3:21:40 PM
NETIO.SYS fffff880`014f9000 fffff880`01559000 0x00060000 0x4a5bc18a 7/13/2009 3:21:46 PM
ksecpkg.sys fffff880`01559000 fffff880`01584000 0x0002b000 0x4a5bc84a 7/13/2009 3:50:34 PM
tcpip.sys fffff880`01602000 fffff880`017ff000 0x001fd000 0x4a5bc26e 7/13/2009 3:25:34 PM
fwpkclnt.sys fffff880`01584000 fffff880`015ce000 0x0004a000 0x4a5bc164 7/13/2009 3:21:08 PM
vmstorfl.sys fffff880`015ce000 fffff880`015de000 0x00010000 0x4a5bc67e 7/13/2009 3:42:54 PM
volsnap.sys fffff880`01000000 fffff880`0104c000 0x0004c000 0x4a5bc128 7/13/2009 3:20:08 PM
spldr.sys fffff880`015de000 fffff880`015e6000 0x00008000 0x4a0858bb 5/11/2009 8:56:27 AM
rdyboost.sys fffff880`0104c000 fffff880`01086000 0x0003a000 0x4a5bc48a 7/13/2009 3:34:34 PM
mup.sys fffff880`015e6000 fffff880`015f8000 0x00012000 0x4a5bc201 7/13/2009 3:23:45 PM
hwpolicy.sys fffff880`01235000 fffff880`0123e000 0x00009000 0x4a5bc0fa 7/13/2009 3:19:22 PM
fvevol.sys fffff880`01086000 fffff880`010c0000 0x0003a000 0x4a5bc1a7 7/13/2009 3:22:15 PM
disk.sys fffff880`0123e000 fffff880`01254000 0x00016000 0x4a5bc11d 7/13/2009 3:19:57 PM
CLASSPNP.SYS fffff880`018b1000 fffff880`018e1000 0x00030000 0x4a5bc11e 7/13/2009 3:19:58 PM
crashdmp.sys fffff880`018e1000 fffff880`018ef000 0x0000e000 0x4a5bcabd 7/13/2009 4:01:01 PM
dump_ataport.sys fffff880`018ef000 fffff880`018fb000 0x0000c000 0x4a5bc113 7/13/2009 3:19:47 PM
dump_atapi.sys fffff880`018fb000 fffff880`01904000 0x00009000 0x4a5bc113 7/13/2009 3:19:47 PM
dump_dumpfve.sys fffff880`01904000 fffff880`01917000 0x00013000 0x4a5bc18f 7/13/2009 3:21:51 PM

Dee Kay · Feb 25, 2015

Several posts reference possible outdated or corrupted drivers that can also give the same bug check code 0x124.
Here are a couple links that may help you try to track down the offender and a outline of what steps to follow.

http://answers.microsoft.com/en-us/windows/forum/windows_7-system/blue-screen-bug-check-0x124-wheauncorrectableerror/f15eab92-1bae-4d7a-af83-6ff4f885f22d <--this is from the microsoft community posts about your error

http://mikemstech.blogspot.com/2010/07/windbgkd-debugging-processor-cache.html <--how to read the bug check and dump file

These links can hopefully help you narrow down and pinpoint what is causing your issue. Good luck.

johnbl · Feb 25, 2015

-bugcheck 0x124 generally will not be caused by a driver unless it is a overclocking driver.
(and it would be a side effect of a bad overclock)

-I guess an exception would be certain hacked versions of windows report bugcheck 0x124 in a effort to avoid detection.

-Most often, you just need to stop any overclock, update the BIOS or reset it to defaults.

-Also, you have windows 7 build 7600 you need to update to service pack 1 +updates after you get your machine stable or you will get bugchecks in windows code if you use current graphics drivers.
be sure to run cmd.exe as an admin then run
sfc.exe /scannow
and confirm the system does repair any corrupt files.

Ryouichi Kiriyami · Feb 25, 2015

Well Dee Kay Drivers updated to their latest points from what i can tell.

as for john

Updated bios last night. i dont have an overclocks going...that i know of. unless it was out of the box. i havnt tampered with it as im fine with my system.

Updateing windows now....Will return soon with an update.

Although its hard to say if it ever fixes the problem...it happens randomly. on no load or medium load or heavy load of the CPU and/or GPU. but as i said i stress tested them both to max and there we no problem.

but im going to update and see where that gets me. then ill give it 3 days.

Dee Kay · Feb 25, 2015

Does device manager show any hardware that may be a problem? Do the event logs show anything that might point to what is causing the problems?

John is very good so until he gets back here are 2 links discussing the stop 124 issue.

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html#post354696 <--what 124 is

http://www.sevenforums.com/bsod-help-support/323060-random-bsod-while-playing-exiting-games.html#post2722309 <--post 5 by Arc

Ryouichi Kiriyami · Feb 26, 2015

Well see i cant tell if its fixed or not...it hasnt happened again but it always happened at random anyways. so ill keep you guys up todate. everythings updated but no crashes so i literally still have no idea.

but as i said. it hasnt happened yet.

EDIT: and no theres no device problems :I

Ryouichi Kiriyami · Mar 5, 2015

UPDATE: it happened again. so ive taken it upon myself to switch out the RAM sticks just incase. as it really does seem to be the problem ive done 2 separate mem tests both showing 0 errors, but we'll see i guess.

switched out the RAM. happened again. Both times seem to be w hen im recording.
I used Action! to record screen. and Debut to record webcam. ive just started recently using Debut. so my guess is Action could be causing an error with my system... i have no idea

Search

BSOD *Stop 124. Tried everything i could think of

Ryouichi Kiriyami

Reputable

Dee Kay

Reputable

johnbl

Polypheme

Ryouichi Kiriyami

Reputable

Dee Kay

Reputable

Ryouichi Kiriyami

Reputable

Ryouichi Kiriyami

Reputable

TRENDING THREADS

Latest posts

Moderators online

Share this page