Windows 7 Troubleshooting Frequent BSOD Errors on Windows 7

F

Frits87

New Member
Joined
Aug 16, 2010
Messages
12
Hi,

every day I have a few BSOD's... I've tried a MemTest and there was no problem.


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 2067

Additional information about the problem:
BCCode: 124
BCP1: 00000000
BCP2: 85D288FC
BCP3: 00000000
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\081610-19718-01.dmp
C:\Users\Joris\AppData\Local\Temp\WER-27019-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

View attachment Minidump.rar

Hope someone can help me...
 
Solution
Hello,

Basically 0x124 issues are Hardware that makes things very complicated to troubleshoot. Follow this article Stop 0x124 - what it means and what to try - Windows 7 Forums

Update the following Driver

ASACPI.sys Mon Mar 28 08:00:36 2005

Run a Hardware Diagnostic (Memory and Hard Drive) follow this link for instructions Link Removed - Invalid URL

Try this free stress test: Free Software - GIMPS

Sort by date Sort by votes
3xHybrid.sys belongs to the software Philips Semiconductors 3xHybrid or ASUS Hybrid TV Tuner by Philips Semiconductors GmbH or ASUSTeK. Update this driver.




081210-24476-01.dmp

WHEA_UNCORRECTABLE_ERROR (124)
0x124_GenuineIntel_PROCESSOR_BUS_PRV
Code: 
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: 00000000, Machine Check Exception
Arg2: 857b64dc, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, 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:  System

CURRENT_IRQL:  0

STACK_TEXT:  
80e55cc4 828da1c5 857b64c0 82974f88 82974f80 nt!WheapCreateTriageDumpFromPreviousSession+0x32
80e55ce4 828dafe1 82974f80 857b64c0 82974fb0 nt!WheapProcessWorkQueueItem+0x56
80e55d00 82872043 82974f80 00000000 848d44c0 nt!WheapWorkQueueWorkerRoutine+0x1f
80e55d50 829fed16 00000001 a7eca15a 00000000 nt!ExpWorkerThread+0x10d
80e55d90 828a0159 82871f36 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: hardware
IMAGE_NAME:  hardware
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV
BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV
081310-16629-01.dmp

3xHybrid.sys

Code: 
BugCheck D1, {0, 2, 0, 938964c7}

Unable to load image \SystemRoot\system32\DRIVERS\3xHybrid.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for 3xHybrid.sys
*** ERROR: Module load completed but symbols could not be loaded for 3xHybrid.sys
Probably caused by : 3xHybrid.sys ( 3xHybrid+574c7 )


DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 938964c7, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82d9f700
Unable to read MiSystemVaType memory at 82d7f0c0
 00000000 

CURRENT_IRQL:  2

FAULTING_IP: 
3xHybrid+574c7
938964c7 8b00            mov     eax,dword ptr [eax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  P7131RemoteApp

TRAP_FRAME:  9ad35a44 -- (.trap 0xffffffff9ad35a44)
ErrCode = 00000000
eax=00000000 ebx=865ef574 ecx=865ef574 edx=871c7b18 esi=865ef574 edi=00000004
eip=938964c7 esp=9ad35ab8 ebp=9ad35ab8 iopl=0         nv up ei pl nz ac pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010217
3xHybrid+0x574c7:
938964c7 8b00            mov     eax,dword ptr [eax]  ds:0023:00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 938964c7 to 82c78b7b

STACK_TEXT:  
9ad35a44 938964c7 badb0d00 871c7b18 86f6d248 nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
9ad35ab8 93882d3a 871c7b18 865ef328 9ad35ae0 3xHybrid+0x574c7
9ad35ac8 938967b0 871c7b18 00000000 86eea618 3xHybrid+0x43d3a
9ad35ae0 93852ca0 871c7b18 86faae28 9ad35b04 3xHybrid+0x577b0
9ad35af0 9383f656 86eea618 87068230 00000004 3xHybrid+0x13ca0
9ad35b04 93af8f01 86eea618 87068230 93b002d0 3xHybrid+0x656
9ad35b1c 93af630d 9ad35b48 85f43c05 00000010 ks!DisableEventSynchronize+0x46
9ad35b30 93b155a6 00000001 86faae30 93af8ebb ks!PerformLockedOperation+0xe7
9ad35b58 93b045ca 85f43c48 86faae28 00000001 ks!KsDisableEvent+0x53
9ad35b80 93b06990 85f43c48 9547c008 86faae28 ks!KspHandleAutomationIoControl+0x14e
9ad35ba8 93b04789 8596a908 85f43c48 9ad35bd0 ks!CKsFilter::DispatchDeviceIoControl+0x51
9ad35bb8 93af40ba 8596a908 85f43c48 85f43c48 ks!KsDispatchIrp+0xb0
9ad35bd0 93845aae 8596a908 85f43c48 8596a908 ks!CKsDevice::PassThroughIrp+0x46
9ad35bfc 82c6ef44 8596a908 85f43c48 85f43c48 3xHybrid+0x6aae
9ad35c14 82e44307 86eea618 85f43c48 85f43cdc nt!IofCallDriver+0x63
9ad35c34 82e466fa 8596a908 86eea618 00000000 nt!IopSynchronousServiceTail+0x1f8
9ad35cd0 82e4d73b 8596a908 85f43c48 00000000 nt!IopXxxControlFile+0x6aa
9ad35d04 82c7579a 00000154 00000250 00000000 nt!NtDeviceIoControlFile+0x2a
9ad35d04 777a64f4 00000154 00000250 00000000 nt!KiFastCallEntry+0x12a
01b4fdb8 00000000 00000000 00000000 00000000 0x777a64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
3xHybrid+574c7
938964c7 8b00            mov     eax,dword ptr [eax]

SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  3xHybrid+574c7
MODULE_NAME: 3xHybrid
IMAGE_NAME:  3xHybrid.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  45b9db24
FAILURE_BUCKET_ID:  0xD1_3xHybrid+574c7
BUCKET_ID:  0xD1_3xHybrid+574c7




081510-16068-01.dmp

3xHybrid.sys

Code: 
BugCheck D1, {8b55ff8b, 2, 0, 90863871}

Unable to load image \SystemRoot\system32\DRIVERS\3xHybrid.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for 3xHybrid.sys
*** ERROR: Module load completed but symbols could not be loaded for 3xHybrid.sys
Probably caused by : 3xHybrid.sys ( 3xHybrid+57871 )

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 8b55ff8b, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 90863871, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82d6c700
Unable to read MiSystemVaType memory at 82d4c0c0
 8b55ff8b 

CURRENT_IRQL:  2

FAULTING_IP: 
3xHybrid+57871
90863871 ff10            call    dword ptr [eax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  P7131RemoteApp

TRAP_FRAME:  80de2ea0 -- (.trap 0xffffffff80de2ea0)
ErrCode = 00000000
eax=8b55ff8b ebx=8535d508 ecx=8962d1da edx=80de2f30 esi=86521430 edi=8652167c
eip=90863871 esp=80de2f14 ebp=80de2f40 iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
3xHybrid+0x57871:
90863871 ff10            call    dword ptr [eax]      ds:0023:8b55ff8b=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 90863871 to 82c45b7b

STACK_TEXT:  
80de2ea0 90863871 badb0d00 80de2f30 00000000 nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
80de2f40 9080c8d7 80de2fa4 82c62835 85f1bd48 3xHybrid+0x57871
80de2f48 82c62835 85f1bd48 85c98f90 86521410 3xHybrid+0x8d7
80de2fa4 82c62698 80dc2120 86eca030 00000000 nt!KiExecuteAllDpcs+0xf9
80de2ff4 82c61e5c 9bc27ce4 00000000 00000000 nt!KiRetireDpcList+0xd5
80de2ff8 9bc27ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
82c61e5c 00000000 0000001a 00d6850f bb830000 0x9bc27ce4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
3xHybrid+57871
90863871 ff10            call    dword ptr [eax]
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  3xHybrid+57871
MODULE_NAME: 3xHybrid
IMAGE_NAME:  3xHybrid.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  45b9db24
FAILURE_BUCKET_ID:  0xD1_3xHybrid+57871
BUCKET_ID:  0xD1_3xHybrid+57871



081610-19718-01.dmp


WHEA_UNCORRECTABLE_ERROR (124)
0x124_GenuineIntel_PROCESSOR_BUS_PRV


Code: 
BugCheck 124, {0, 85d288fc, 0, 0}

Probably caused by : hardware

Followup: MachineOwner


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: 00000000, Machine Check Exception
Arg2: 85d288fc, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, 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:  System

CURRENT_IRQL:  0

STACK_TEXT:  
89649cc4 82d0d1c5 85d288e0 82da7f88 82da7f80 nt!WheapCreateTriageDumpFromPreviousSession+0x32
89649ce4 82d0dfe1 82da7f80 85d288e0 82da7fb0 nt!WheapProcessWorkQueueItem+0x56
89649d00 82ca5083 82da7f80 00000000 84d99798 nt!WheapWorkQueueWorkerRoutine+0x1f
89649d50 82e31d84 00000001 af8e56a3 00000000 nt!ExpWorkerThread+0x10d
89649d90 82cd3159 82ca4f76 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV


081610-23774-01.dmp

Code: 
BugCheck 124, {0, 85dc78fc, 0, 0}

Probably caused by : hardware


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: 00000000, Machine Check Exception
Arg2: 85dc78fc, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, 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:  System

CURRENT_IRQL:  0

STACK_TEXT:  
80e55cc4 82cd91c5 85dc78e0 82d73f88 82d73f80 nt!WheapCreateTriageDumpFromPreviousSession+0x32
80e55ce4 82cd9fe1 82d73f80 85dc78e0 82d73fb0 nt!WheapProcessWorkQueueItem+0x56
80e55d00 82c71083 82d73f80 00000000 84cf04c0 nt!WheapWorkQueueWorkerRoutine+0x1f
80e55d50 82dfdd84 00000001 a6173c12 00000000 nt!ExpWorkerThread+0x10d
80e55d90 82c9f159 82c70f76 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV
 
Upvote 0 Downvote
Hi,

Tnx for analysing the Dump-files.

I installed the latest driver of the TV tuner.

Any idea how to solve this one: WHEA_UNCORRECTABLE_ERROR (124) 0x124_GenuineIntel_PROCESSOR_BUS_PRV
 
Upvote 0 Downvote
Hello,

Basically 0x124 issues are Hardware that makes things very complicated to troubleshoot. Follow this article Stop 0x124 - what it means and what to try - Windows 7 Forums

Update the following Driver

ASACPI.sys Mon Mar 28 08:00:36 2005

Run a Hardware Diagnostic (Memory and Hard Drive) follow this link for instructions Link Removed - Invalid URL

Try this free stress test: Free Software - GIMPS



Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net


Hope this helps,
Captain
 
Upvote 0 Downvote
Solution
Captain Jack said:
Update the following Driver

ASACPI.sys Mon Mar 28 08:00:36 2005
Click to expand...

The only reason I'm adding to the above excellent advice by the guys is because simply, nobody really knows how to update ASACPI.sys besides us. (lol at us but true)

Frits87, please visit ASUS' website for your motherboard. Download tab. Choose correct OS. If no 7 choose correct Vista version instead. Go to Utilities tab. Download and install latest ATK0110 shown.

If for some reason that's not there at all, install latest ProbeII package in utilities, instead.

-----

EDIT - One further thing.
Code: 
Afc      Afc.sys      Wed Feb 23 01:58:55 2005
Get rid of this driver for sure! To do so, uninstall all of your ArcSoft software.

If you still have further problems, remove the video card and attach monitor to motherboard instead. Test like this to see if 0x124 do not happen any longer.

If you don't have onboard video, do whatever to borrow another card to install and test.

Basically, I'm saying to look at the video card first as a source of the hardware errors, first.
 
Last edited:
Upvote 0 Downvote
Now we're getting somewhere.

You're having a hibernation file issue. Turn off hibernation. To do so, open an elevated command prompt. Copy/paste this to it then hit enter:

powercfg -h off

Reboot.

-----------

Remove afc.sys in the manner I described above - very important.
 
Upvote 0 Downvote
I succeeded turning of hibernation.

I also removed all Arcsoft-software, but the driver is still there... How can I remove it safely?
 
Upvote 0 Downvote
Delete it like you would delete any other file.

It's at C:\Windows\System32\drivers

Reboot and then run Ccleaner to clean the registry, for good measure.
 
Upvote 0 Downvote
I hear that, as it's consistent with the 0x124 types of hardware crashes you're having.

Captain Jack explained well about them in his post above: Link Removed

His first link shown is the way to deal with these errors. I might recommend changing out the video card if it all possible, to determine if it might be causing the 0x124 stops.

Edit - I just reviewed the thread further. Before changing out the video card, I'd first try removing the TV card from the system.
 
Last edited:
Upvote 0 Downvote
Both your latest minidumps point to a hardware fault with the same 0x124 error. Please see Captain and Torrent's posts on the first page of this thread. Continue testing your hardware and removing the components 1 by 1 to see what's causing the error. If no luck, do a clean win 7 'vanilla' install - without any drivers or software, to run it and see if the same bsod error pops up.

081810-20295-01.dmp:


WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred.


Code: 
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [G:\081810-20295-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c41000 PsLoadedModuleList = 0x82d80570
Loading Kernel Symbols
.................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list


BugCheck 124, {0, 85d8c8fc, 0, 0}

Probably caused by : hardware



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: 00000000, Machine Check Exception
Arg2: 85d8c8fc, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, 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:  System

CURRENT_IRQL:  0

STACK_TEXT:  
80e41cc4 82d041c5 85d8c8e0 82d9ef88 82d9ef80 nt!WheapCreateTriageDumpFromPreviousSession+0x32
80e41ce4 82d04fe1 82d9ef80 85d8c8e0 82d9efb0 nt!WheapProcessWorkQueueItem+0x56
80e41d00 82c9c083 82d9ef80 00000000 84cfda70 nt!WheapWorkQueueWorkerRoutine+0x1f
80e41d50 82e28d84 00000001 a7ece05e 00000000 nt!ExpWorkerThread+0x10d
80e41d90 82cca159 82c9bf76 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV


081810-23212-01.dmp:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred.

Code: 
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [G:\081810-23212-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c4f000 PsLoadedModuleList = 0x82d8e570

Loading Kernel Symbols
.................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list


BugCheck 124, {0, 85a93024, 0, 0}

Probably caused by : hardware


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: 00000000, Machine Check Exception
Arg2: 85a93024, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, 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:  System

CURRENT_IRQL:  0

STACK_TEXT:  
80e45cc4 82d121c5 85a93008 82dacf88 82dacf80 nt!WheapCreateTriageDumpFromPreviousSession+0x32
80e45ce4 82d12fe1 82dacf80 85a93008 82dacfb0 nt!WheapProcessWorkQueueItem+0x56
80e45d00 82caa083 82dacf80 00000000 84cef020 nt!WheapWorkQueueWorkerRoutine+0x1f
80e45d50 82e36d84 00000001 a6195b0c 00000000 nt!ExpWorkerThread+0x10d
80e45d90 82cd8159 82ca9f76 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV
1. Ensure that none of the hardware components are overclocked nor overheated.

2. Update your sytem and all hardware-related drivers. Your drivers are not so old, 2009-10, but getting them the latest is a good idea.

Code: 
80b97000 80b9f000   kdcom    kdcom.dll    Tue Jul 14 04:08:58 2009 (4A5BDAAA)
82c0a000 82c41000   hal      halmacpi.dll Tue Jul 14 02:11:03 2009 (4A5BBF07)
82c41000 83041000   nt       ntkrnlmp.exe Sat Jun 19 06:55:07 2010 (4C1C3F9B)
89400000 89478000   mcupdate mcupdate.dll Tue Jul 14 04:06:41 2009 (4A5BDA21)
89478000 89489000   PSHED    PSHED.dll    Tue Jul 14 04:09:36 2009 (4A5BDAD0)
89489000 89491000   BOOTVID  BOOTVID.dll  Tue Jul 14 04:04:34 2009 (4A5BD9A2)
89491000 894d3000   CLFS     CLFS.SYS     Tue Jul 14 02:11:10 2009 (4A5BBF0E)
894d3000 8957e000   CI       CI.dll       Tue Jul 14 04:09:28 2009 (4A5BDAC8)
8957e000 895ef000   Wdf01000 Wdf01000.sys Tue Jul 14 02:11:36 2009 (4A5BBF28)
895ef000 895fd000   WDFLDR   WDFLDR.SYS   Tue Jul 14 02:11:25 2009 (4A5BBF1D)
895fd000 89645000   ACPI     ACPI.sys     Tue Jul 14 02:11:11 2009 (4A5BBF0F)
89645000 8964e000   WMILIB   WMILIB.SYS   Tue Jul 14 02:11:22 2009 (4A5BBF1A)
8964e000 89656000   msisadrv msisadrv.sys Tue Jul 14 02:11:09 2009 (4A5BBF0D)
89656000 89680000   pci      pci.sys      Tue Jul 14 02:11:16 2009 (4A5BBF14)
89680000 8968b000   vdrvroot vdrvroot.sys Tue Jul 14 02:46:19 2009 (4A5BC74B)
8968b000 8969c000   partmgr  partmgr.sys  Tue Jul 14 02:11:35 2009 (4A5BBF27)
8969c000 896ac000   volmgr   volmgr.sys   Tue Jul 14 02:11:25 2009 (4A5BBF1D)
896ac000 896f7000   volmgrx  volmgrx.sys  Tue Jul 14 02:11:41 2009 (4A5BBF2D)
896f7000 896fe000   intelide intelide.sys Tue Jul 14 02:11:19 2009 (4A5BBF17)
896fe000 8970c000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 02:11:15 2009 (4A5BBF13)
8970c000 89722000   mountmgr mountmgr.sys Tue Jul 14 02:11:27 2009 (4A5BBF1F)
89722000 8972b000   atapi    atapi.sys    Tue Jul 14 02:11:15 2009 (4A5BBF13)
8972b000 8974e000   ataport  ataport.SYS  Tue Jul 14 02:11:18 2009 (4A5BBF16)
8974e000 89757000   amdxata  amdxata.sys  Tue May 19 20:57:35 2009 (4A12F30F)
89757000 8978b000   fltmgr   fltmgr.sys   Tue Jul 14 02:11:13 2009 (4A5BBF11)
8978b000 8979c000   fileinfo fileinfo.sys Tue Jul 14 02:21:51 2009 (4A5BC18F)
8982d000 8995c000   Ntfs     Ntfs.sys     Tue Jul 14 02:12:05 2009 (4A5BBF45)
8995c000 89987000   msrpc    msrpc.sys    Tue Jul 14 02:11:59 2009 (4A5BBF3F)
89987000 8999a000   ksecdd   ksecdd.sys   Tue Jul 14 02:11:56 2009 (4A5BBF3C)
8999a000 899f7000   cng      cng.sys      Tue Jul 14 02:32:55 2009 (4A5BC427)
899f7000 89a05000   pcw      pcw.sys      Tue Jul 14 02:11:10 2009 (4A5BBF0E)
89a05000 89a0e000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 02:11:14 2009 (4A5BBF12)
89a0e000 89ac5000   ndis     ndis.sys     Tue Jul 14 02:12:24 2009 (4A5BBF58)
89ac5000 89b03000   NETIO    NETIO.SYS    Tue Jul 14 02:12:35 2009 (4A5BBF63)
89b03000 89b28000   ksecpkg  ksecpkg.sys  Fri Dec 11 06:04:22 2009 (4B21C4C6)
89c34000 89d7d000   tcpip    tcpip.sys    Mon Jun 14 06:36:59 2010 (4C15A3DB)
89d7d000 89dae000   fwpkclnt fwpkclnt.sys Tue Jul 14 02:12:03 2009 (4A5BBF43)
89dae000 89db6380   vmstorfl vmstorfl.sys Tue Jul 14 02:28:44 2009 (4A5BC32C)
89db7000 89df6000   volsnap  volsnap.sys  Tue Jul 14 02:11:34 2009 (4A5BBF26)
89df6000 89dfe000   spldr    spldr.sys    Mon May 11 19:13:47 2009 (4A084EBB)
89dfe000 89e2b000   rdyboost rdyboost.sys Tue Jul 14 02:22:02 2009 (4A5BC19A)
89e2b000 89e3b000   mup      mup.sys      Tue Jul 14 02:14:14 2009 (4A5BBFC6)
89e3b000 89e43000   hwpolicy hwpolicy.sys Tue Jul 14 02:11:01 2009 (4A5BBF05)
89e43000 89e75000   fvevol   fvevol.sys   Sat Sep 26 05:24:21 2009 (4ABD7B55)
89e75000 89e86000   disk     disk.sys     Tue Jul 14 02:11:28 2009 (4A5BBF20)
89e86000 89eab000   CLASSPNP CLASSPNP.SYS Tue Jul 14 02:11:20 2009 (4A5BBF18)
89eab000 89eb8000   crashdmp crashdmp.sys Tue Jul 14 02:45:50 2009 (4A5BC72E)
89eb8000 89ec3000   dump_ataport dump_ataport.sys Tue Jul 14 02:11:16 2009 (4A5BBF14)
89ec3000 89ecc000   dump_atapi dump_atapi.sys Tue Jul 14 02:11:15 2009 (4A5BBF13)
89ecc000 89edd000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 02:12:47 2009 (4A5BBF6F)
3. Test your hardware, Start -> MDSCHED, memtest86 and prime95. For the hdd, start -> cmd -> CHKDSK /R.
 
Last edited:
Upvote 0 Downvote
You must log in or register to reply here.