BSOD 0x00000124 - i5 2500k 4.3ghz

[Wellsy95]

Hi,

Spec:
I5 2500k 4.3
4gb Kingston hyper x ram
Msi p67a-c45
Gts 450
Coolermaster 500w psu
Azetek 13cl CPU cooler (Not sure on exact name)

I've had this issue a while now. My PC would BSOD during intensive use, like gaming or rendering. This happened once every few months and then disappeared for a while. More recently I've upgraded to two monitors and an SSD and play games more, and the Bsods have returned. They happen randomly, a few times over the past few weeks.

Could this be because my PSU is lacking? I've suspected it for a while. Any suggestions would be great.

 

[enemy1g]

Have you checked your temperatures when you're gaming or rendering? BCCode 124 is normally hardware related. It can also come down to inadequate power to your components. What are your current voltages at?

 

[johnbl]

Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR This bug check indicates that a fatal hardware error has occurred.

if you post your memory dump (memory.dmp) on the cloud (skydrive would work) I could take a quick look at it in the debugger

- common error if you overclock settings are too agressive or your voltage is too low during overclocking

 

[nikoli707]

0x124= need more vcore.

what voltage is in the bios? what does hwmonitor say your voltage is min/max when under load and when idle?

 

[Wellsy95]

Have you checked your temperatures when you're gaming or rendering? BCCode 124 is normally hardware related. It can also come down to inadequate power to your components. What are your current voltages at?

Current voltages, idle
CPU Core - 1.328v
DRAM - 1.504v

 

[Wellsy95]

0x124= need more vcore.

what voltage is in the bios? what does hwmonitor say your voltage is min/max when under load and when idle?

Could a mod change this so it's not the solution? Clicked the wrong button!

Here are the idle and load screenshots, this was only from playing Chivalry for 10mins as I need to install other games.

 

[Wellsy95]

Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR This bug check indicates that a fatal hardware error has occurred.

if you post your memory dump (memory.dmp) on the cloud (skydrive would work) I could take a quick look at it in the debugger

- common error if you overclock settings are too agressive or your voltage is too low during overclocking

I ran it through the windows debugger, this is what I got, all dumps show same error

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa7fc72ebcab, 2, 1, fffff80002eea602}

Probably caused by : volmgr.sys ( volmgr!VmDeviceControl+18e )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa7fc72ebcab, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002eea602, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310d100
fffffa7fc72ebcab

CURRENT_IRQL: 2

FAULTING_IP:
nt!IopCompleteRequest+692
fffff800`02eea602 0f851b050000 jne nt!IopCompleteRequest+0xbb3 (fffff800`02eeab23)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: rundll32.exe

IRP_ADDRESS: fffffa8005997ad8

TRAP_FRAME: fffff88006f54bf0 -- (.trap 0xfffff88006f54bf0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88006f55298 rbx=0000000000000000 rcx=fffff88006f55298
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002eea602 rsp=fffff88006f54d80 rbp=00000000a000000c
r8=fffffa8005997b50 r9=0000000000000080 r10=0000000000000002
r11=fffffa80056c3930 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
nt!IopCompleteRequest+0x692:
fffff800`02eea602 0f851b050000 jne nt!IopCompleteRequest+0xbb3 (fffff800`02eeab23) [br=1]
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002ed5169 to fffff80002ed5bc0

STACK_TEXT:
fffff880`06f54aa8 fffff800`02ed5169 : 00000000`0000000a fffffa7f`c72ebcab 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`06f54ab0 fffff800`02ed3de0 : 00000000`00000000 31fffa80`06422010 fffff8a0`0015fa00 fffffa80`05a38c60 : nt!KiBugCheckDispatch+0x69
fffff880`06f54bf0 fffff800`02eea602 : 00000000`a0000003 fffffa80`05b4c830 fffff880`20206f49 fffff880`06f54d90 : nt!KiPageFault+0x260
fffff880`06f54d80 fffff800`02ed98fa : fffffa80`05997b50 fffff800`02ee69cc fffff880`06f55001 fffff800`00000000 : nt!IopCompleteRequest+0x692
fffff880`06f54e50 fffff880`00db14be : fffffa80`05a38c60 fffff8a0`00000000 fffff880`00db92f0 00000000`00000000 : nt!IopfCompleteRequest+0x66a
fffff880`06f54f40 fffff880`01002808 : 00000000`00000000 fffff800`02ee6b91 fffff880`010313b0 fffffa80`03ced640 : volmgr!VmDeviceControl+0x18e
fffff880`06f55150 fffff880`0118a082 : fffffa80`05a38c60 fffffa80`044d1040 fffffa80`05a38f28 fffffa80`044d1190 : fvevol!FveFilterDeviceControl+0x1d0
fffff880`06f551c0 fffff880`00c80ef0 : 00000000`00000000 00000000`00000000 fffffa80`044d1040 00000000`004d0008 : volsnap!VolSnapDeviceControl+0x72
fffff880`06f55230 fffff880`00c72a6b : 00000000`00000000 fffff8a0`0443dc80 00000000`00000000 00000000`000007ff : mountmgr!MountMgrSendDeviceControl+0x9c
fffff880`06f552c0 fffff880`00c7b86b : fffff880`06f55420 fffffa80`0429d4b0 fffffa80`040ab930 fffffa80`0429d4b0 : mountmgr!QueryDeviceInformation+0x207
fffff880`06f55340 fffff880`00c7bf86 : fffffa80`0597c100 fffffa80`0597c100 00000000`00000000 fffff880`06f55420 : mountmgr!QueryPointsFromMemory+0x57
fffff880`06f55400 fffff880`00c80a71 : 00000000`00000800 fffffa80`0429d4b0 fffffa80`040ab930 fffff880`00c81920 : mountmgr!MountMgrQueryPoints+0x36a
fffff880`06f55450 fffff880`02df3b23 : 00000000`00000800 00000000`00000800 00000000`00000001 00000000`000007ff : mountmgr!MountMgrDeviceControl+0xe9
fffff880`06f55520 fffff880`02df381e : 00000000`00000000 fffff880`06f556f0 fffffa80`0429d360 fffffa80`06253d50 : discache!DispGetVolumeGuid+0x14b
fffff880`06f555f0 fffff880`02df399d : fffff880`06f55780 fffff880`02df27cb fffffa80`0690bf20 fffff880`02df3948 : discache!DispGetVolumeInfo+0xa2
fffff880`06f556c0 fffff880`02df329a : ffffffff`80000774 00000000`00000000 ffffffff`80000774 63696e6f`6e80cbbe : discache!DispGetVolumeInformation+0x41
fffff880`06f55720 fffff880`02deed18 : 00000000`c0000225 00000000`00000002 fffff800`031c9b50 fffff8a0`0d07c130 : discache!DisGetFileObjectAttribute+0xe2
fffff880`06f55810 fffff800`031bc10b : 00000000`0000017c 00000000`001dc260 00000000`0000033c fffff880`06f55b60 : discache!ScQueryAttributeInformation+0x390
fffff880`06f55900 fffff800`031b33dc : 00000000`00000000 fffff800`00000080 fffffa80`03ced640 00000000`00000001 : nt!ExQueryAttributeInformation+0x4b
fffff880`06f55930 fffff800`02ed4e53 : 00000000`0000017c 00000000`001dc248 00000000`001dc260 00000980`0000033c : nt!NtQueryInformationFile+0x847
fffff880`06f55a70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13


STACK_COMMAND: kb

FOLLOWUP_IP:
volmgr!VmDeviceControl+18e
fffff880`00db14be 8bc3 mov eax,ebx

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: volmgr!VmDeviceControl+18e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: volmgr

IMAGE_NAME: volmgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce792a0

FAILURE_BUCKET_ID: X64_0xA_volmgr!VmDeviceControl+18e

BUCKET_ID: X64_0xA_volmgr!VmDeviceControl+18e

 

[Wellsy95]

Also, if anyone could give me some quick info on how to go back to stock cpu speed I'd appreciate it, I don't really use my PC enough now a days to warrant a 24/7 OC, and if it will stop this problem that's even better.

Cheers

 

[johnbl]

-I would check to make sure your volmgr.sys file is not infected with a rootkit
-I would also unplug any slow data sources like thumb drives
- verify that your OS files are not corrupted via "sfc.exe /scannow" command
-might even turn off lazy writes to various drives

 

[Wellsy95]

-I would check to make sure your volmgr.sys file is not infected with a rootkit
-I would also unplug any slow data sources like thumb drives
- verify that your OS files are not corrupted via "sfc.exe /scannow" command
-might even turn off lazy writes to various drives

I did a fresh install 3 weeks ago and have had this issue for a while now, but will do it anyway. No other things plugged in either

 

[johnbl]

-I would check to make sure your volmgr.sys file is not infected with a rootkit
-I would also unplug any slow data sources like thumb drives
- verify that your OS files are not corrupted via "sfc.exe /scannow" command
-might even turn off lazy writes to various drives

I did a fresh install 3 weeks ago and have had this issue for a while now, but will do it anyway. No other things plugged in either

i think discache.sys is involved in search indexing your system. it might have a corrupt search database, or is searching a drive with filesystem corruption or drive errors on it. You might want to turn off the indexing, delete the search database, and do a chkdsk /f /r on each of your drives.

 

[nikoli707]

if you want to return to normal just go into the bios and put 33x into the multiplier as that is the stock speed for the 2500k.

0x124 is for sure related to the cpu vcore. although its very rare for 2500k's to error out at 43x multiplier, it not impossible. most 2500k's will go to 4.4ghz on the multiplier without touching anything. in your case it seems you have a chip that just wants more voltage. it probably just needs an extra 0.005v to 0.010v.