Windows has recoverd from an unexpected shutdown ?

[uscool]

Hi, computer just freezes then restarts no blue screen no error untill windows restarts this can happen when pc is idle or general browsing , my temps are fine 34c idle, load 50c, noting overclocked, using ram from qualified list, My spec is below if you wanna check and i have uploaded the mini dump if someone can look at it and tell me whats causing it hope someone can help me , this is causing me too much trouble, got all the latest drivers, and using nod32 thats all its really just a fresh windows installation with not much but essential stuff

 

[Jonathan_King]

Hello,

Let's try a few things. First, open an elevated command prompt and run sfc /scannow. That will scan for bad system files, repairing as necessary.

Next, download a copy of Memtest86 and burn the ISO to a CD using ImgBurn. Boot from the CD, and run at least 5 passes.

If that does not solve the problem, disconnect all unnecessary hardware, like external hard drive, video cards, etc.

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


Loading Dump File [C:\Users\Jonathan\Desktop\021510-10233-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
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a50000 PsLoadedModuleList = 0x82b98810
Debug session time: Mon Feb 15 06:12:25.336 2010 (GMT-5)
System Uptime: 0 days 0:00:06.506
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, 8619a8fc, 0, 0}

Probably caused by : hardware

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

3: 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: 8619a8fc, 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_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
8d993cc4 82b1efc5 8619a8e0 82bb7c28 82bb7c20 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8d993ce4 82b1fdef 82bb7c20 8619a8e0 82bb7c50 nt!WheapProcessWorkQueueItem+0x56
8d993d00 82abdf2b 82bb7c20 00000000 8519dd48 nt!WheapWorkQueueWorkerRoutine+0x1f
8d993d50 82c5e66d 00000001 a3668fe8 00000000 nt!ExpWorkerThread+0x10d
8d993d90 82b100d9 82abde1e 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_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

3: 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: 8619a8fc, 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_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
8d993cc4 82b1efc5 8619a8e0 82bb7c28 82bb7c20 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8d993ce4 82b1fdef 82bb7c20 8619a8e0 82bb7c50 nt!WheapProcessWorkQueueItem+0x56
8d993d00 82abdf2b 82bb7c20 00000000 8519dd48 nt!WheapWorkQueueWorkerRoutine+0x1f
8d993d50 82c5e66d 00000001 a3668fe8 00000000 nt!ExpWorkerThread+0x10d
8d993d90 82b100d9 82abde1e 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_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

 

[uscool]

Hello,

Let's try a few things. First, open an elevated command prompt and run sfc /scannow. That will scan for bad system files, repairing as necessary.

Next, download a copy of Memtest86 and burn the ISO to a CD using ImgBurn. Boot from the CD, and run at least 5 passes.

If that does not solve the problem, disconnect all unnecessary hardware, like external hard drive, video cards, etc.

I did the first and said no volations so think that means thats fine, i also ran memtest 4v for few hours and came back with error with 2 installed, im gonna try one at a time and run test, the settings are right cause the ram is on the qualified list and also set according to what board manual for this ram, thanks for your help this as been so fustrating, PC can run for 7 or so hours no problems, can also happen within 1 hour, completly random, even when pc is left on idle

Thanks

 

[Capt.Jack Sparrow]

Hello,

You could also follow this link http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

Good Luck,
Captain

 

[uscool]

just using 1 stick now, will do another memtest test over night with the 1 stick installed and see if any errors, if not will keep it in pc and use pc for week and see if any random restarts come up, too bad cant really games with 2gb now

 

[uscool]

you think the ram could be causing this. i just got the 1 installed now. will run a memtest over night and report back,

Thanks hope this is the problem

by the way can someone be kind enough to look at my mini dump and tell me what could be causing it ?

Thanks

 

[uscool]

2 tests with 1 stick installed at a time, gave this to OCZ and they said RMA it, so do you think this was causing the restarts ??

Thanks

 

[Jonathan_King]

I suspect that is the problem. Replace your RAM, and they should go away. If not, post the minidumps and we will take a look.

 

[uscool]

can you check the mini dumps i posted already for me please can you find out from minidump if it was memory fault ?

Thanks

 

[Jonathan_King]

The truth is your dmps are giving random errors. That often points to memory issues. Even if it tells us a certain driver is the culprit, we can't trust it.

 

[uscool]

Thanks i sent the ram back for replacements hope replacements, this new build been alot of trouble, I got a faulty motherboard first, now its the ram hope this is the end, i think it must be the ram, cause some of the downloads i have done been corrupt, also ran windows 7 memory diagnostic and it came up saying faulty memory, it says OCZ Platinum DDR3 module is 100% hand-tested for quality assurance, really ???. i will report back when i got the replacements

Thanks for your help would be lost without it

 

[Jonathan_King]

No problem, good luck with the RMA!

 

[uscool]

it was the ram it was faulty, it was OCZ 1333mhz 7-7-7-20 1.8v gave errors in memtest and prime95, but when set the ram at auto it passed and worked fine but this reduced speed to 1066mhz, but ram spec was to run at 1333mhz and also it was on my qualified list for ram, so i bought kingston 1333mhz 7-7-7-20 1.7v ran it at that settings and fine on prime95, and no errors in memtest, so very happy now at last after few weeks of trying to sort this, by the way windows diagnostic tool is rubbish, said it never found any errors even on the extended test

Thanks again for your help