Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD 0x00000124 (happening at random times)

11 Apr 2011   #11
DeanP

Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
 
 

If it goes above 90C, then it's likely your GPU is overheating.


My System SpecsSystem Spec
.
11 Apr 2011   #12
stavee

Windows 7 Ultimate x64
 
 

RAM TEST

7hours 40mins

no errors

and for the GPU TEST
i got to 95 and i stopped it
so should i take my graphics card out and give it a clean?
My System SpecsSystem Spec
11 Apr 2011   #13
stavee

Windows 7 Ultimate x64
 
 

cleaned gpu test has been on for 20mins at 87degrees now
way better than before

how long do i leave it on for?
My System SpecsSystem Spec
.

11 Apr 2011   #14
stavee

Windows 7 Ultimate x64
 
 

30 mins stayed the same so i stopped it there

all components passed tests

so hopefully bsod is solved? ill report back if it happens again
My System SpecsSystem Spec
11 Apr 2011   #15
fimble

windows 7 ultimate
 
 

Yeah, you are (were!!) looking for it to "peak" then stabilise, obviously at a not too hot temp. 87 sounds fine for a maxxed out graphics card. Hope all goes well.
My System SpecsSystem Spec
11 Apr 2011   #16
stavee

Windows 7 Ultimate x64
 
 

cheers mate!

and yeah i hope it works im sick of this bsod randomly occurring especially with pretty decent specs
My System SpecsSystem Spec
11 Apr 2011   #17
DeanP

Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
 
 

Go ahead and run the Memtest.
My System SpecsSystem Spec
12 Apr 2011   #18
stavee

Windows 7 Ultimate x64
 
 

i ran it already my results passed!

crash again

please analyse the new dump to see if anything else shows
Zippyshare.com - 041111-84583-01.dmp
My System SpecsSystem Spec
13 Apr 2011   #19
stavee

Windows 7 Ultimate x64
 
 

bump
My System SpecsSystem Spec
13 Apr 2011   #20
DeanP

Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
 
 

Please do not bump - if your thread has been missed, VM or PM me.

Dump still points to Hardware (STOP 0x124)
Bugcheck 0x124 = Hardware WHEA = Hardware Failure

Since you already run hardware tests, I suggest that you go to BIOS, take photos of the settings and upload it on your next post (I'm thinking of incorrect settings in your BIOS). If you are overclocking anything (CPU, GPU, RAM) - stop and return to default values.

Regards. . .
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Dean\Downloads\041111-84583-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03018000 PsLoadedModuleList = 0xfffff800`03255e50
Debug session time: Mon Apr 11 18:45:52.604 2011 (UTC + 12:00)
System Uptime: 0 days 7:18:40.524
Loading Kernel Symbols
.................................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000

Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007dbe028, f2000000, 20008f}

Unable to load image PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
Probably caused by : hardware

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

0: 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: fffffa8007dbe028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000020008f, Low order 32-bits of the MCi_STATUS value.

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************

BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff800`00ba8fd8 fffff880`04213c61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort
fffff800`00b9cc98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`04213c61


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel__UNKNOWN

BUCKET_ID:  X64_0x124_GenuineIntel__UNKNOWN

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

0: kd> lmtsmn
start             end                 module name
fffff880`00e0f000 fffff880`00e66000   ACPI     ACPI.sys     unavailable (00000000)
fffff880`00de7000 fffff880`00df2000   amdxata  amdxata.sys  unavailable (00000000)
fffff880`00c86000 fffff880`00c8f000   atapi    atapi.sys    unavailable (00000000)
fffff880`00db2000 fffff880`00ddc000   ataport  ataport.SYS  unavailable (00000000)
fffff880`00e9a000 fffff880`00f5a000   CI       CI.dll       unavailable (00000000)
fffff880`018c0000 fffff880`018f0000   CLASSPNP CLASSPNP.SYS unavailable (00000000)
fffff880`00cf7000 fffff880`00d55000   CLFS     CLFS.SYS     unavailable (00000000)
fffff880`0112b000 fffff880`0119e000   cng      cng.sys      unavailable (00000000)
fffff880`018aa000 fffff880`018c0000   disk     disk.sys     unavailable (00000000)
fffff880`010b9000 fffff880`010cd000   fileinfo fileinfo.sys unavailable (00000000)
fffff880`0106d000 fffff880`010b9000   fltmgr   fltmgr.sys   unavailable (00000000)
fffff880`0122b000 fffff880`01235000   Fs_Rec   Fs_Rec.sys   unavailable (00000000)
fffff880`01870000 fffff880`018aa000   fvevol   fvevol.sys   unavailable (00000000)
fffff880`0142b000 fffff880`01475000   fwpkclnt fwpkclnt.sys unavailable (00000000)
fffff800`035f5000 fffff800`0363e000   hal      hal.dll      Tue Jul 14 13:27:36 2009 (4A5BDF08)
fffff880`01867000 fffff880`01870000   hwpolicy hwpolicy.sys unavailable (00000000)
fffff800`00bad000 fffff800`00bb7000   kdcom    kdcom.dll    Tue Jul 14 13:31:07 2009 (4A5BDFDB)
fffff880`01200000 fffff880`0121a000   ksecdd   ksecdd.sys   unavailable (00000000)
fffff880`01400000 fffff880`0142b000   ksecpkg  ksecpkg.sys  unavailable (00000000)
fffff880`00c9f000 fffff880`00ce3000   mcupdate mcupdate.dll unavailable (00000000)
fffff880`01811000 fffff880`01867000   MDFSYSNT MDFSYSNT.sys unavailable (00000000)
fffff880`015f3000 fffff880`01600000   MDPMGRNT MDPMGRNT.SYS unavailable (00000000)
fffff880`00c6c000 fffff880`00c86000   mountmgr mountmgr.sys unavailable (00000000)
fffff880`00ddc000 fffff880`00de7000   msahci   msahci.sys   unavailable (00000000)
fffff880`00e6f000 fffff880`00e79000   msisadrv msisadrv.sys unavailable (00000000)
fffff880`010cd000 fffff880`0112b000   msrpc    msrpc.sys    unavailable (00000000)
fffff880`015e1000 fffff880`015f3000   mup      mup.sys      unavailable (00000000)
fffff880`00e8d000 fffff880`00e97000   mv91cons mv91cons.sys unavailable (00000000)
fffff880`0148f000 fffff880`01581000   ndis     ndis.sys     unavailable (00000000)
fffff880`01581000 fffff880`015e1000   NETIO    NETIO.SYS    unavailable (00000000)
fffff800`03018000 fffff800`035f5000   nt       ntkrnlmp.exe Wed Oct 27 15:43:09 2010 (4CC791BD)
fffff880`0125c000 fffff880`013ff000   Ntfs     Ntfs.sys     unavailable (00000000)
fffff880`00d88000 fffff880`00d9d000   partmgr  partmgr.sys  unavailable (00000000)
fffff880`00d55000 fffff880`00d88000   pci      pci.sys      unavailable (00000000)
fffff880`00e86000 fffff880`00e8d000   pciide   pciide.sys   unavailable (00000000)
fffff880`00c5c000 fffff880`00c6c000   PCIIDEX  PCIIDEX.SYS  unavailable (00000000)
fffff880`0121a000 fffff880`0122b000   pcw      pcw.sys      unavailable (00000000)
fffff880`00ce3000 fffff880`00cf7000   PSHED    PSHED.dll    unavailable (00000000)
fffff880`01000000 fffff880`0103a000   rdyboost rdyboost.sys unavailable (00000000)
fffff880`01485000 fffff880`0148d000   spldr    spldr.sys    unavailable (00000000)
fffff880`01603000 fffff880`01800000   tcpip    tcpip.sys    unavailable (00000000)
fffff880`00e79000 fffff880`00e86000   vdrvroot vdrvroot.sys unavailable (00000000)
fffff880`01475000 fffff880`01485000   vmstorfl vmstorfl.sys unavailable (00000000)
fffff880`00d9d000 fffff880`00db2000   volmgr   volmgr.sys   unavailable (00000000)
fffff880`00c00000 fffff880`00c5c000   volmgrx  volmgrx.sys  unavailable (00000000)
fffff880`0119e000 fffff880`011ea000   volsnap  volsnap.sys  unavailable (00000000)
fffff880`00f5a000 fffff880`00ffe000   Wdf01000 Wdf01000.sys unavailable (00000000)
fffff880`00e00000 fffff880`00e0f000   WDFLDR   WDFLDR.SYS   unavailable (00000000)
fffff880`00e66000 fffff880`00e6f000   WMILIB   WMILIB.SYS   unavailable (00000000)
My System SpecsSystem Spec
Reply

 BSOD 0x00000124 (happening at random times)




Thread Tools




Similar help and support threads
Thread Forum
BSOD happening at random times.
The BDOS has been happening for the last few days. I have run anti malware and anti virus and restored windows to an earlier point and reset my overclocked speeds but the BSOD is still happening any help is appreciated. ...
BSOD Help and Support
BSOD in random use every day and many times a day,0x00000124
hi there getting this issue for the last couple mounths, really sick of it already :( tryed to do system restore but it didnt hepl :(
BSOD Help and Support
BSOD @ Random Times error 0x00000124
Ever since I installed my new PSU and GPU into my system, I get blue screens by random it seems. Once was when I was watching a Youtube video, the other was me playing a game. I've included the dmps in the Zip file. Please look at the later ones, for example, the one from Sept. 21, or today in...
BSOD Help and Support
BSOD at random times, happening frequently
I've been getting the BSOD frequently, and when I use Windows to "check for a solution", it does not give me any information. I haven't installed any new drivers that I know of or can remember, and my computer is less than 2 years old. It used to do the BSOD only once a month or so, so I ignored...
BSOD Help and Support
Random BSOD errors happening at random times
Hello , im having random BSOD issues and after a BSOD i can use my PC again but the problem is it keeps happening randomly and i will be able to use again Here are some of the errors i have got: PAGE FAULT IN NON PAGED AREA BAD or CORRUPTED POOL MEMORY MANAGMENT I have the files...
BSOD Help and Support
BSOD happening at random times with different error codes
hi there new to this forum and looking for some help - I have had my acer aspire for about 6 months and for the past 5 months this BSOD keeps happening at random times, and the symtem reboots and then restores. I have tried various methods to stop this happening - and I am now at a loss -...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 10:01.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App