Random Lock up Win7 64bit

[Skype]

Hi guys,

I'm running a new install of W7. I get random lockups that require a force-restart.

I get this on reboot.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8007CB88F8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\110710-19780-01.dmp
C:\Users\Jon\AppData\Local\Temp\WER-43071-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

Sys Specs;

• AMD Phenom II X4 955 Quad Core @ 3.2 GHz
• ASUS M4N82 Deluxe
• 8 GB DDR2 @ 800 MHz
• Windows 7 Home Premium
• nVidia GeForce GTX 275 Dual SLi

Wasn't getting this error before the fresh install. Tried updating my graphic drivers and mobo drivers.

Any ideas?

Thanks

 

[richc46]

Welcome
The bad news is that BC code is a hardware problem. We have this excellent thread on the subject. Follow it carefully and you may be able to solve the problem. I have also given you a link showining how to download any information regarding future BSODs

Your .dmp file shows a stop error of 0x124 which is a general hardware error .. A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try

A blue screen is a BSOD as stated in your post.

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[Skype]

Only thing is, it doesn't actually display a blue screen. It just locks up.

Also how can it be a hardware error if it was just a reinstall :/

Edit: It also behaves in a very odd way. It will lock up when I start my PC, but after the crash and a reboot, it doesn't do it again.

This used to happen before I reinstalled, but after uninstalling an edimax networking driver it fixed. That driver is no longer installed and the error is still happening, although this time (after the os reinstall) it's a little more frequent.

 

[richc46]

First because something happens after a reinstall, does not mean it cant be hardware; it can be a conincidence.

The printout clearly says code 124 and that is a BSOD code. That is all I have at the moment.

Follow this and the prior instructions and submit the minidump report, if any
http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

 

[Skype]

Here's the minidump.

 

[richc46]

Ok its official, you had a code 124 BSOD.

icrosoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_110710-19780-01[1].zip\110710-19780-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 x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c5f000 PsLoadedModuleList = 0xfffff800`02e9ce50
Debug session time: Sat Nov  6 22:27:47.471 2010 (GMT-4)
System Uptime: 0 days 0:00:09.266
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, fffffa8007cb88f8, 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: 0000000000000000, Machine Check Exception
Arg2: fffffa8007cb88f8, 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_AuthenticAMD
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
STACK_TEXT:  
fffff880`031b66f0 fffff800`02f19a89 : fffffa80`07cb88d0 fffffa80`06d36b60 00000000`0000000b 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031b6c10 fffff800`02dfb667 : fffffa80`07cb88d0 fffff800`02e745f8 fffffa80`06d36b60 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031b6c40 fffff800`02d63c45 : fffff800`02ed6360 fffffa80`086b2be8 fffffa80`086b2be0 fffffa80`06d36b60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031b6c80 fffff800`02cdc961 : fffff880`0104de00 fffff800`02d63c20 fffffa80`06d36b60 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031b6cb0 fffff800`02f73c06 : 00000000`00000000 fffffa80`06d36b60 00000000`00000080 fffffa80`06ca8890 : nt!ExpWorkerThread+0x111
fffff880`031b6d40 fffff800`02cadc26 : fffff880`02f64180 fffffa80`06d36b60 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031b6d80 00000000`00000000 : fffff880`031b7000 fffff880`031b1000 fffff880`037925e0 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_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Followup: MachineOwner
---------
3: kd> lmtsmn
start             end                 module name
fffff880`00f94000 fffff880`00feb000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`00dbe000 fffff880`00dc9000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`00d8b000 fffff880`00d94000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00d94000 fffff880`00dbe000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`00cb1000 fffff880`00d71000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`018df000 fffff880`0190f000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c53000 fffff880`00cb1000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`010f0000 fffff880`01163000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`0190f000 fffff880`0191d000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`018c9000 fffff880`018df000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01929000 fffff880`01932000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0191d000 fffff880`01929000   dump_ataport dump_ataport.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01932000 fffff880`01945000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`01069000 fffff880`0107d000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`0101d000 fffff880`01069000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`0122b000 fffff880`01235000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`0188f000 fffff880`018c9000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`01400000 fffff880`0144a000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`02c16000 fffff800`02c5f000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`015ec000 fffff880`015f5000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff800`00bcd000 fffff800`00bd7000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`01200000 fffff880`0121a000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`015af000 fffff880`015da000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`0107d000 fffff880`01092000   Lbd      Lbd.sys      Tue May 25 03:45:36 2010 (4BFB8020)
fffff880`00c32000 fffff880`00c3f000   mcupdate mcupdate.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`00d71000 fffff880`00d8b000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00ff4000 fffff880`00ffe000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01092000 fffff880`010f0000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`015da000 fffff880`015ec000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`0145d000 fffff880`0154f000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`0154f000 fffff880`015af000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff800`02c5f000 fffff800`0323b000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`0125a000 fffff880`013fd000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`00e40000 fffff880`00e55000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00e00000 fffff880`00e33000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00ec6000 fffff880`00ecd000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00ecd000 fffff880`00edd000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`0121a000 fffff880`0122b000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00c3f000 fffff880`00c53000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`011af000 fffff880`011e9000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`0144a000 fffff880`01452000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`01602000 fffff880`017ff000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`00e33000 fffff880`00e40000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`00e55000 fffff880`00e6a000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e6a000 fffff880`00ec6000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01163000 fffff880`011af000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`00ee1000 fffff880`00f85000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f85000 fffff880`00f94000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00feb000 fffff880`00ff4000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
Mini Kernel Dump does not contain unloaded driver list

If you get another download the new minidump report in this thread and we shall compare. As of now you have a hardware problem
Check memory first that is the most common

Download memtest86 and test RAM
www.sevenforums.com/tutorials/105647-ram-test-memtest86.html