Unexpected shut down please help me

Golden · 13 Jan 2011

Thats OK, no apology neccessary - he wouldn't ask for that if he didn't think it was required. That information is always useful to get to the root of the problem

Tews · 13 Jan 2011

Three out of four of your .dmp files show a stop error 0x124 general hardware fault. Unfortunately, it does not say what peice of hardware is causing the problem.. Read this thread for further information for more suggestions...

Stop 0x124 - what it means and what to try

The fourth .dmp file blames PCTcore.sys ( PCTools ).. This is a known problem with some Windows 7 systems, and should be uninstalled...

Remove ZoneAlarm, and replace it with Microsoft Security Essentials...

Code:

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

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  set up windows

CURRENT_IRQL:  1f

STACK_TEXT:  
8d33e8cc 82c34f3f 00000124 00000000 85ccb01c nt!KeBugCheckEx+0x1e
8d33e908 828e4f04 86a2c1c1 85ccb01c 8287e4f0 hal!HalBugCheckSystem+0xab
8d33e938 82c351f1 86a38ea8 82c42e40 00000000 nt!WheaReportHwError+0x230
8d33ea4c 82c352e3 86a38ea8 86a38ef8 00000000 hal!HalpMcaReportError+0x3b
8d33ea70 82c3554f 00000000 86a38ef8 8d33eb90 hal!HalpMceHandler+0x8b
8d33ea80 82c2b5f5 00000000 00000000 00000000 hal!HalpHandleMachineCheck+0x3b
8d33eb90 82c28261 00000000 8d339750 00000000 hal!HalpMcaExceptionHandler+0x87
8d33eb90 00000000 00000000 8d339750 00000000 hal!HalpMcaExceptionHandlerWrapper+0x89


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE

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


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


Loading Dump File [D:\Users\Tom\Desktop\011211-32526-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 (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8280e000 PsLoadedModuleList = 0x82956810
Debug session time: Tue Jan 11 22:54:09.273 2011 (GMT-5)
System Uptime: 0 days 4:25:34.161
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
.........
1: 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: 00000000, Machine Check Exception
Arg2: 85ec801c, Address of the WHEA_ERROR_RECORD structure.
Arg3: b6004000, High order 32-bits of the MCi_STATUS value.
Arg4: 98000135, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  WLIDSVC.EXE

CURRENT_IRQL:  1f

STACK_TEXT:  
807ce8cc 82c2cf3f 00000124 00000000 85ec801c nt!KeBugCheckEx+0x1e
807ce908 828dcf04 86bc9549 85ec801c 828764f0 hal!HalBugCheckSystem+0xab
807ce938 82c2d1f1 86bca578 82c3ae40 00000000 nt!WheaReportHwError+0x230
807cea4c 82c2d2e3 86bca578 86bca5c8 00000000 hal!HalpMcaReportError+0x3b
807cea70 82c2d54f 00000000 86bca5c8 807ceb90 hal!HalpMceHandler+0x8b
807cea80 82c235f5 00000000 00000000 00000000 hal!HalpHandleMachineCheck+0x3b
807ceb90 82c20261 00000000 807c9750 00000000 hal!HalpMcaExceptionHandler+0x87
807ceb90 00000000 00000000 807c9750 00000000 hal!HalpMcaExceptionHandlerWrapper+0x89


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE

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


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


Loading Dump File [D:\Users\Tom\Desktop\011311-18626-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 (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82842000 PsLoadedModuleList = 0x8298a810
Debug session time: Wed Jan 12 23:05:24.530 2011 (GMT-5)
System Uptime: 0 days 0:00:11.809
Loading Kernel Symbols
...............................................................
...................................................
Loading User Symbols
Loading unloaded module list
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8082c0ab, 8d187078, 0}

Unable to load image \SystemRoot\system32\drivers\PCTCore.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PCTCore.sys
*** ERROR: Module load completed but symbols could not be loaded for PCTCore.sys
*** WARNING: Unable to verify timestamp for TfFsMon.sys
*** ERROR: Module load completed but symbols could not be loaded for TfFsMon.sys
Probably caused by : PCTCore.sys ( PCTCore+24c01 )

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


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


Loading Dump File [D:\Users\Tom\Desktop\011311-33150-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 (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x81c1f000 PsLoadedModuleList = 0x81d67810
Debug session time: Wed Jan 12 18:34:32.779 2011 (GMT-5)
System Uptime: 0 days 0:00:31.326
Loading Kernel Symbols
...............................................................
.......................
Loading User Symbols
Loading unloaded module list
.....
2: kd> !analyze =v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 84eb201c, b66c2000, 145}

Probably caused by : hardware

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

bobrobert · 13 Jan 2011

Have you up dated your system from Microsoft?

Windows update KB2454826

If so restore your system to an earlier date. There is a problem with the up date and some people including myself had to restore or un install the up date.

ohsocute69 · 13 Jan 2011

bobrobert said:

Have you up dated your system from Microsoft?

Windows update KB2454826

If so restore your system to an earlier date. There is a problem with the up date and some people including myself had to restore or un install the up date.

thanku for this i think you have made the issue clearer for me ..

i was just coming back on to say i did a restore to when i reformated pc and issue has gone ....

now i sat here and thought it must be the windows updates so i dissabeled it anyway,

as i dont ever see any use for me , but maybe cause me issues...

so this now makes me clearer that it was the update that done it ...

thanku to all that made comments and fo such fast responses makes me fell that help is always not far away , as i was gong to go to the pc shop tomoro

thanku bobrobert so much and u deserve a nice award for ur comment on this thread !

Corrine · 13 Jan 2011

Here is the thread at Microsoft Answers about this issue: Windows 7 - KB2454826 fails and doesn't recover after reboot

In particular, note the following from Kevin Hau, MSFT:

Hello Everyone!

I wanted to give a quick summary of the issue as well as the current working solutions.

*Issue Summary*

Some users have reporting an issue when the update KB2454826. After installing the update, you may experience the follow STOP on a blue screen:

STOP: 0x0000007F

*Applies to*

Windows 7 (All editions).

*Recommendations*

First, you will need to roll back to a previous state prior to the update. To do so, you can use system restore via the recovery environment. Here are some details:

What are the system recovery options in Windows 7?

*Method 1: Update Video Card driver*

Support feedbacks suggest that by update the video card driver prior to installing the update resolve the problem. Video card manufacturers often release updates to their drivers to enhance performance or fix compatibility. If you need the latest driver for your video card, visit the support section on your video card manufacturer's website for information on how to download and install the newest driver.

*Method 2: Remove Daemon Tool Driver (SPTD.SYS). *

/Thank you Professor Fate for sharing/

One of the Answers users have suggested that they resolved the issue by removing a daemon tool.

1.Confirm that the driver exists on the system. The file should be located in C:\windows\system32\drivers.

2.If the driver exists, steps to remove the software can be found here: My system won't boot after installation of v4, or problems with SPTD.SYS - THE DAEMON TOOLS FORUM

*Please post your results (even if you are successful at resolving the issue). *

When posting, please include the following details:

·Operating System
·Architecture (32bit or 64bit)
·Video card Hardware
·Current video card driver information

You should be able to capture all of the above details via DirectX Diagnostic Tool:

1.Click*Start*, type *dxdiag* in the Start Search box, and then click*dxdiag* in the Programs list.

The DirectX Diagnostic Tool opens.

2.In the DirectX Diagnostic Tool, click the Display tab.

The video card's name and the video card's manufacturer are listed under Device. The driver version is listed under Drivers.

Thanks!

Kevin

It also appears that the majority of the reports are systems with Symantec installed. Dells also appear to be particularly impacted.