Windows 7 - Bluescreen

TheCase · 03-10-2010

Hiya,

I had my PC running a stable overclock for a few months but I just felt my PC was running sluggish and I wanted to get the RAM running at 1600mhz again instead of 1200mhz and I didnt really need the extra power, but now within the past week I have started to get blue screens of death so Windows 7 says but the computer just locks up I dont see anything blue like the traditional BSOD. Also my computer is no better it takes a good 30 seconds to boot up, software takes ages etc

i7 920
Nvida 275gtx
Asus 6PT
SB X-FI Xterme Audio

Quote:

A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Internal Timer Error
Processor ID: 0

The details view of this entry contains further information.

Any help will be greatful

Thanks

Tews · 03-10-2010

Your crash reported a stop error of 0x124 which is hardware related.. I suspect this is due to your overclocking.. restore all your settings to stock and see if your BDSO errors stop.... also read this thread....

[2-Int] Stop 0x124 - what it means and what to try

zigzag3143 · 03-10-2010

Quote: Originally Posted by TheCase

Hiya,

I had my PC running a stable overclock for a few months but I just felt my PC was running sluggish and I wanted to get the RAM running at 1600mhz again instead of 1200mhz and I didnt really need the extra power, but now within the past week I have started to get blue screens of death so Windows 7 says but the computer just locks up I dont see anything blue like the traditional BSOD. Also my computer is no better it takes a good 30 seconds to boot up, software takes ages etc

i7 920
Nvida 275gtx
Asus 6PT
SB X-FI Xterme Audio

Quote:

A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Internal Timer Error
Processor ID: 0

The details view of this entry contains further information.

Any help will be greatful

Thanks

Hi and welcome

Well this one was caused by hardware. I would Stop overclocking, download and run memtestx86 for 5 passes to test your ram, and run a system file check
(type cmd in search>right click and run as admin>sfc /scannow

You really have to think if the overclock is worth the instabilty.

Ken

Code:

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


Loading Dump File [C:\Users\K\Desktop\031010-25693-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\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 Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a55000 PsLoadedModuleList = 0xfffff800`02c92e50
Debug session time: Wed Mar 10 08:45:35.115 2010 (GMT-5)
System Uptime: 0 days 0:00:17.270
Loading Kernel Symbols
................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80073d8038, 0, 0}

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: fffffa80073d8038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, 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:  
fffff880`0335b6f0 fffff800`02d0fa89 : fffffa80`073d8010 fffffa80`0551f040 00000000`00000010 00000000`00000246 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0335bc10 fffff800`02bf1547 : fffffa80`073d8010 fffff800`02c6a5f8 fffffa80`0551f040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0335bc40 fffff800`02b59b95 : fffff800`02ccc360 fffffa80`0651c878 fffffa80`0651c870 fffffa80`0551f040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0335bc80 fffff800`02ad4161 : fffff880`01106e00 fffff800`02b59b70 fffffa80`0551f040 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0335bcb0 fffff800`02d6a166 : 00000000`00000000 fffffa80`0551f040 00000000`00000080 fffffa80`05493b30 : nt!ExpWorkerThread+0x111
fffff880`0335bd40 fffff800`02aa5486 : fffff880`0316a180 fffffa80`0551f040 fffff880`031750c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0335bd80 00000000`00000000 : fffff880`0335c000 fffff880`03356000 fffff880`04131540 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

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

TheCase · 03-10-2010

Nothing is no longer overclocked, I just flashed my BOIS a day ago as well as updating my gpu

so my bios and gpu are update does this mean it could be something else

Im scanning now and running memtestx86 will post results,
thanks

zigzag3143 · 03-10-2010

Quote: Originally Posted by TheCase

Nothing is no longer overclocked, I just flashed my BOIS a day ago as well as updating my gpu

so my bios and gpu are update does this mean it could be something else

Im scanning now and running memtestx86 will post results,
thanks

You could also run the system file check and post its results
(type cmd in search>right click and run as admin>sfc /scannow)

Ken

TheCase · 03-10-2010

Quote:

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

Everything looks ok, any more suggestions. I guess ill just keep an eye out for odd things

Windows 7 - Bluescreen

Bluescreen problems?