Windows 7: BSOD loading Portal 2, error 0x00000101

SuperNachoMama · 03 Jan 2012

PC Specs:
Windows 7 64Bit OEM- Original Unmodified
1TB HDD
8GB RAM
NVIDIA Geforce GTX 550 Ti - Driver Version 285.62 (also tried beta 290.53)
AMD FX -6100 Six-Core Processor ~3.3GHz
System and Hardware = 9 Days old
23" LED Screen

Portal 2 starts up normally, gets to the loading screen where it says Portal 2, then Crashes/Blue Screens the Computer

writhziden · 03 Jan 2012

Code:

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


Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\SuperNachoMama\Windows_NT6_BSOD_jcgriff2\122411-35287-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02a4a000 PsLoadedModuleList = 0xfffff800`02c8f650
Debug session time: Sat Dec 24 21:12:25.630 2011 (UTC - 7:00)
System Uptime: 0 days 0:00:07.848
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, fffffa8008e48268, 0, 0}

Probably caused by : hardware

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

4: 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: fffffa8008e48268, 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`0336a5b0 fffff800`02d0cc59 : fffffa80`08e48240 fffffa80`06ab9040 00000000`0000000b 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0336aad0 fffff800`02becfa7 : fffffa80`08e48240 fffff800`02c672b8 fffffa80`06ab9040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0336ab00 fffff800`02b545c5 : fffff800`02cc8ac0 00000000`00000001 fffffa80`07918e00 fffffa80`06ab9040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0336ab40 fffff800`02ad4021 : fffff880`01066e00 fffff800`02b545a0 fffffa80`06ab9000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0336ab70 fffff800`02d6632e : 00000000`00000000 fffffa80`06ab9040 00000000`00000080 fffffa80`069f3040 : nt!ExpWorkerThread+0x111
fffff880`0336ac00 fffff800`02abb666 : fffff880`03289180 fffffa80`06ab9040 fffff880`03294040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0336ac40 00000000`00000000 : fffff880`0336b000 fffff880`03365000 fffff880`0354a400 00000000`00000000 : nt!KiStartSystemThread+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
---------

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\SuperNachoMama\Windows_NT6_BSOD_jcgriff2\122411-28282-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02c61000 PsLoadedModuleList = 0xfffff800`02ea6650
Debug session time: Sat Dec 24 22:16:35.939 2011 (UTC - 7:00)
System Uptime: 0 days 0:00:10.141
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, fffffa8007960848, 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: fffffa8007960848, 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`0338d5b0 fffff800`02f23c59 : fffffa80`07960820 fffffa80`06ad4b60 00000000`00000007 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0338dad0 fffff800`02e03fa7 : fffffa80`07960820 fffff800`02e7e2b8 fffffa80`06ad4b60 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0338db00 fffff800`02d6b5c5 : fffff800`02edfac0 00000000`00000001 fffffa80`08eab9d0 fffffa80`06ad4b60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0338db40 fffff800`02ceb021 : fffff880`00daae00 fffff800`02d6b5a0 fffffa80`06ad4b00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0338db70 fffff800`02f7d32e : 00000000`00000000 fffffa80`06ad4b60 00000000`00000080 fffffa80`069f2040 : nt!ExpWorkerThread+0x111
fffff880`0338dc00 fffff800`02cd2666 : fffff880`03289180 fffffa80`06ad4b60 fffff880`03294040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0338dc40 00000000`00000000 : fffff880`0338e000 fffff880`03388000 fffff880`0338d190 00000000`00000000 : nt!KiStartSystemThread+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
---------

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\SuperNachoMama\Windows_NT6_BSOD_jcgriff2\122411-28938-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02c61000 PsLoadedModuleList = 0xfffff800`02ea6650
Debug session time: Sat Dec 24 22:31:34.285 2011 (UTC - 7:00)
System Uptime: 0 days 0:15:08.487
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {21, 0, fffff880031d7180, 3}

Unable to load image Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000021, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880031d7180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_6_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT:  
fffff800`0418ffa8 fffff800`02d388f9 : 00000000`00000101 00000000`00000021 00000000`00000000 fffff880`031d7180 : nt!KeBugCheckEx
fffff800`0418ffb0 fffff800`02ceb4b7 : 00000000`00000000 fffff800`00000003 00000000`00002711 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff800`04190040 fffff800`02c22895 : fffff800`02c48460 fffff800`041901f0 fffff800`02c48460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`04190140 fffff800`02cdd233 : 00000000`00621881 fffff800`041901f0 fffffa80`0a13c630 00000000`aaaaaaab : hal!HalpHpetClockInterrupt+0x8d
fffff800`04190170 fffff800`02cc89c0 : 00000000`00000000 fffff880`152be096 00000000`00310d42 fffff800`041904d8 : nt!KiInterruptDispatchNoLock+0x163
fffff800`04190300 fffff800`02cd6c9f : fffff800`02e53e80 fffff800`02ce7f28 fffff800`00000000 00000000`00000000 : nt!KxWaitForSpinLockAndAcquire+0x20
fffff800`04190330 fffff880`04a9267d : fffffa80`0a13c000 00000000`aaaaaaab fffffa80`0a13c630 00000000`00000001 : nt!KeAcquireSpinLockAtDpcLevel+0x6f
fffff800`04190380 fffffa80`0a13c000 : 00000000`aaaaaaab fffffa80`0a13c630 00000000`00000001 00000000`00000100 : Rt64win7+0x1867d
fffff800`04190388 00000000`aaaaaaab : fffffa80`0a13c630 00000000`00000001 00000000`00000100 00000dfb`00000001 : 0xfffffa80`0a13c000
fffff800`04190390 fffffa80`0a13c630 : 00000000`00000001 00000000`00000100 00000dfb`00000001 fffff800`00000001 : 0xaaaaaaab
fffff800`04190398 00000000`00000001 : 00000000`00000100 00000dfb`00000001 fffff800`00000001 00000000`00000001 : 0xfffffa80`0a13c630
fffff800`041903a0 00000000`00000100 : 00000dfb`00000001 fffff800`00000001 00000000`00000001 fffff800`02e53e80 : 0x1
fffff800`041903a8 00000dfb`00000001 : fffff800`00000001 00000000`00000001 fffff800`02e53e80 fffff800`04190b18 : 0x100
fffff800`041903b0 fffff800`00000001 : 00000000`00000001 fffff800`02e53e80 fffff800`04190b18 00000000`00000000 : 0xdfb`00000001
fffff800`041903b8 00000000`00000001 : fffff800`02e53e80 fffff800`04190b18 00000000`00000000 fffff800`02e61c00 : 0xfffff800`00000001
fffff800`041903c0 fffff800`02e53e80 : fffff800`04190b18 00000000`00000000 fffff800`02e61c00 00000000`00000000 : 0x1
fffff800`041903c8 fffff800`04190b18 : 00000000`00000000 fffff800`02e61c00 00000000`00000000 fffff880`016e3138 : nt!KiInitialPCR+0x180
fffff800`041903d0 00000000`00000000 : fffff800`02e61c00 00000000`00000000 fffff880`016e3138 fffffa80`09f111a0 : 0xfffff800`04190b18


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\SuperNachoMama\Windows_NT6_BSOD_jcgriff2\122711-22635-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c19000 PsLoadedModuleList = 0xfffff800`02e5e670
Debug session time: Tue Dec 27 15:21:10.942 2011 (UTC - 7:00)
System Uptime: 0 days 2:43:36.799
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {21, 0, fffff880009b3180, 4}

Unable to load image ahcix64s.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ahcix64s.sys
*** ERROR: Module load completed but symbols could not be loaded for ahcix64s.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000021, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b3180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_6_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  portal2.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`09ac9c48 fffff800`02ced8c9 : 00000000`00000101 00000000`00000021 00000000`00000000 fffff880`009b3180 : nt!KeBugCheckEx
fffff880`09ac9c50 fffff800`02ca0497 : 00000000`00000000 fffff800`00000004 00000000`00002711 fffff8a0`1434f250 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`09ac9ce0 fffff800`0320c895 : fffff800`03232460 fffff880`09ac9e90 fffff800`03232460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`09ac9de0 fffff800`02c92173 : 00000000`343a810f fffff800`02e0be80 fffff800`02e0be80 00000000`00000002 : hal!HalpHpetClockInterrupt+0x8d
fffff880`09ac9e10 fffff800`02ca5792 : fffff800`02e0be80 fffff800`00000000 fffff880`09aca020 00000000`175a9000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`09ac9fa0 fffff800`02d3ef66 : 00000000`00000000 fffff800`02e0be80 00000000`175a9000 00000000`00000000 : nt!KiIpiSendRequestEx+0xb2
fffff880`09ac9fe0 fffff800`02d65efc : ffffffff`ffffffff fffff880`09aca0c0 a1f00000`cf7fc867 00000000`00000000 : nt!KeFlushSingleTb+0x126
fffff880`09aca060 fffff800`02d6702b : fffffa80`026e7f40 fffffa80`026e7f40 fffff6fc`40071be0 fffffa80`05b62630 : nt!MiStealPage+0x116c
fffff880`09aca2a0 fffff800`02d68181 : fffffa80`026e7f40 00000000`00000001 00000000`00000001 fffff6fc`40071be0 : nt!MiClaimPhysicalRun+0x60b
fffff880`09aca360 fffff800`02da2c15 : 00000000`00000000 00000000`000fffff 00000000`00100000 00000000`00000001 : nt!MiFindContiguousPages+0xc41
fffff880`09aca480 fffff800`02da3bb3 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`0179e6ea : nt!MiAllocateContiguousMemory+0x2a5
fffff880`09aca510 fffff880`0179a036 : 00000000`00000000 fffff880`0179eb21 00000000`00000000 fffffa80`0ba7a5c0 : nt!MmAllocateContiguousMemorySpecifyCache+0x53
fffff880`09aca550 fffff880`017ac6cf : 00000000`00000001 00000000`00000001 fffff880`017b2110 00000000`0004d014 : storport!StorAllocateContiguousIoResources+0x26
fffff880`09aca590 fffff880`017ac894 : fffffa80`0ba7a5c0 fffff880`01795a01 00000000`00000000 fffff880`00000000 : storport!RaidAdapterScsiMiniportIoctlWithAddress+0x8f
fffff880`09aca610 fffff880`017e6f2d : fffffa80`0ba7a5c0 fffffa80`079f64b0 00000000`00000001 fffff800`02000c00 : storport!RaidAdapterScsiMiniportIoctl+0x14
fffff880`09aca650 fffff880`017e60a0 : fffff880`017b2110 fffffa80`079f64b0 fffffa80`079f64b0 fffffa80`07269e80 : storport! ?? ::NNGAKEGL::`string'+0x486
fffff880`09aca6a0 fffff880`0183240d : fffffa80`07269e80 fffffa80`0ba7a5c0 fffffa80`07269e80 fffff880`09aca6f8 : storport!RaDriverDeviceControlIrp+0x90
fffff880`09aca6e0 fffffa80`07269e80 : fffffa80`0ba7a5c0 fffffa80`07269e80 fffff880`09aca6f8 fffff880`09aca6f8 : ahcix64s+0x240d
fffff880`09aca6e8 fffffa80`0ba7a5c0 : fffffa80`07269e80 fffff880`09aca6f8 fffff880`09aca6f8 fffff880`09aca708 : 0xfffffa80`07269e80
fffff880`09aca6f0 fffffa80`07269e80 : fffff880`09aca6f8 fffff880`09aca6f8 fffff880`09aca708 fffff880`09aca708 : 0xfffffa80`0ba7a5c0
fffff880`09aca6f8 fffff880`09aca6f8 : fffff880`09aca6f8 fffff880`09aca708 fffff880`09aca708 00000000`00000000 : 0xfffffa80`07269e80
fffff880`09aca700 fffff880`09aca6f8 : fffff880`09aca708 fffff880`09aca708 00000000`00000000 00000000`00000000 : 0xfffff880`09aca6f8
fffff880`09aca708 fffff880`09aca708 : fffff880`09aca708 00000000`00000000 00000000`00000000 00000000`0e8a9800 : 0xfffff880`09aca6f8
fffff880`09aca710 fffff880`09aca708 : 00000000`00000000 00000000`00000000 00000000`0e8a9800 00000000`0e8a9800 : 0xfffff880`09aca708
fffff880`09aca718 00000000`00000000 : 00000000`00000000 00000000`0e8a9800 00000000`0e8a9800 00000000`00000000 : 0xfffff880`09aca708


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\SuperNachoMama\Windows_NT6_BSOD_jcgriff2\123011-25116-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c1f000 PsLoadedModuleList = 0xfffff800`02e64670
Debug session time: Fri Dec 30 23:13:59.439 2011 (UTC - 7:00)
System Uptime: 0 days 1:03:37.656
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {21, 0, fffff88003165180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000021, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003165180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_6_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`033473e8 fffff800`02cf38c9 : 00000000`00000101 00000000`00000021 00000000`00000000 fffff880`03165180 : nt!KeBugCheckEx
fffff880`033473f0 fffff800`02ca6497 : fffff880`00000000 fffff800`00000002 00000000`00002711 00000000`0000004a : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`03347480 fffff800`03212895 : fffff800`03238460 fffff880`03347630 fffff800`03238460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`03347580 fffff800`02c98173 : 00000000`0c487701 fffff800`02e11e80 00000000`00000000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`033475b0 fffff800`02ca17a0 : fffff800`02e11e80 fffffa80`00000001 00000000`00000000 fffff880`03347838 : nt!KiInterruptDispatchNoLock+0x163
fffff880`03347740 fffff800`02ce07ac : fffff880`03347b18 00000000`00000000 00000000`00000000 fffff800`02cdeba1 : nt!KeFlushMultipleRangeTb+0x260
fffff880`03347810 fffff800`02cdd5e1 : fffffa80`06af2040 00000000`00000000 fffff880`03347b18 00000000`00000000 : nt!MmSetAddressRangeModified+0x2b0
fffff880`03347910 fffff800`02ce0f76 : fffffa80`07930830 00000000`00000001 fffffa80`00000001 fffffa80`00001000 : nt!CcFlushCache+0x561
fffff880`03347a10 fffff800`02ce1938 : fffff800`00000000 fffff880`03347b18 fffffa80`070893b0 fffff880`00e07d01 : nt!CcWriteBehind+0x1c6
fffff880`03347ac0 fffff800`02ca6001 : fffffa80`06a89830 fffff800`02e3c201 fffff800`02e9d8c0 00000000`00000005 : nt!CcWorkerThread+0x1c8
fffff880`03347b70 fffff800`02f36fee : 00000000`00000000 fffffa80`06af2040 00000000`00000080 fffffa80`069d8040 : nt!ExpWorkerThread+0x111
fffff880`03347c00 fffff800`02c8d5e6 : fffff880`03289180 fffffa80`06af2040 fffff880`03294040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03347c40 00000000`00000000 : fffff880`03348000 fffff880`03342000 fffff880`033478a0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\SuperNachoMama\Windows_NT6_BSOD_jcgriff2\010212-22791-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c09000 PsLoadedModuleList = 0xfffff800`02e4e670
Debug session time: Mon Jan  2 20:51:46.234 2012 (UTC - 7:00)
System Uptime: 0 days 3:58:33.091
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {21, 0, fffff88003165180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000021, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003165180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_6_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`033e83e8 fffff800`02cdd8c9 : 00000000`00000101 00000000`00000021 00000000`00000000 fffff880`03165180 : nt!KeBugCheckEx
fffff880`033e83f0 fffff800`02c90497 : 00000000`00000000 fffff800`00000002 00000000`00002711 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`033e8480 fffff800`031fc895 : fffff800`03222460 fffff880`033e8630 fffff800`03222460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`033e8580 fffff800`02c82173 : 00000000`13c84a1c fffff800`02dfbe80 fffff800`02dfbe80 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`033e85b0 fffff800`02c8b7a0 : fffff800`02dfbe80 00000000`00000001 00000000`00000000 fffffa80`08998018 : nt!KiInterruptDispatchNoLock+0x163
fffff880`033e8740 fffff800`02c706f4 : 00000000`00000002 00000000`00000001 fffff880`033e8a60 00000000`0000efd1 : nt!KeFlushMultipleRangeTb+0x260
fffff880`033e8810 fffff800`02d01ac5 : fffff800`02ebbac0 fffff800`00000001 00000000`00000001 fffff880`033e8a70 : nt!MiAgeWorkingSet+0x64a
fffff880`033e89c0 fffff800`02c70826 : 00000000`000037df 00000000`00000000 fffffa80`00000000 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x4d786
fffff880`033e8a40 fffff800`02c70cd3 : 00000000`00000008 fffff880`033e8ad0 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`033e8a90 fffff800`02f20fee : fffffa80`06aac680 00000000`00000080 fffffa80`069d8040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`033e8c00 fffff800`02c775e6 : fffff880`03165180 fffffa80`06aac680 fffff880`03170040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033e8c40 00000000`00000000 : fffff880`033e9000 fffff880`033e3000 fffff880`033e85c0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE

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

You received two hardware blue screen crashes. Follow the steps in Stop 0x124 - what it means and what to try to see if they resolve your stability problems. As to your problem with Portal 2, have you tried uninstalling and then installing the game again. It may have corrupted files that are causing the crashes.

I do not see anything obvious within your dmp files to indicate your blue screen errors with Portal 2, with the exception of Norton since it is a known cause of blue screen crashes on some systems. If running through the hardware crash suggestions does not fix your conflicts, and if the re-install of the software does not fix your conflicts, then try uninstalling Norton using The Norton Removal Tool and install Microsoft Security Essentials in its place to run with Windows Firewall turned on.

Also, if you are overclocking any of your hardware, stop!

Windows 7: BSOD loading Portal 2, error 0x00000101

BSOD loading Portal 2, error 0x00000101 problems?