Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD while loading Steam Games, Portal 2/ Borderlands 2

18 Sep 2012   #1
Jace

Windows 7 64 bit
 
 
BSOD while loading Steam Games, Portal 2/ Borderlands 2

This has been happening for awhile, but i never thought of doing anything about it because i didn't think it could be helped.

What happens is when i open Steam and click "Play" the game starts loading and then my computer freezes and the BSOD appears.

SF diagnostic zip file attached.

I hope you guys will be able to help me with this problem.
With much respect.
Jace



My System SpecsSystem Spec
.

18 Sep 2012   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Welcome

You are getting 2 famous bug checks, go through the threads below and let us know what you've tried.
STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg
Stop 0x124 - what it means and what to try

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

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: 0000000000000019, 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_8_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`03537e28 fffff800`03537efa : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`009b3180 : nt!KeBugCheckEx
fffff880`03537e30 fffff800`034eacd7 : 00000000`00000000 fffff800`00000004 00000000`00002710 fffff880`03538020 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`03537ec0 fffff800`03423895 : fffff800`03449460 fffff880`03538070 fffff800`03449460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`03537fc0 fffff800`034dd713 : 00000000`06fcdd3b fffff800`03653e80 fffffa80`0d976c60 fffff800`034f1f5c : hal!HalpHpetClockInterrupt+0x8d
fffff880`03537ff0 fffff800`034e5fe0 : fffff800`03653e80 fffffa80`00000001 00000000`00000000 fffff880`03538278 : nt!KiInterruptDispatchNoLock+0x163
fffff880`03538180 fffff800`03524fbc : fffff880`03538580 fffff880`03538540 00000000`00000000 fffff800`035233b1 : nt!KeFlushMultipleRangeTb+0x260
fffff880`03538250 fffff800`03521df1 : fffffa80`09b27b50 00000000`00000000 fffff880`03538580 fffff880`03538540 : nt!MmSetAddressRangeModified+0x2b0
fffff880`03538350 fffff880`016f86e1 : fffffa80`0aa32830 fffff800`00000000 fffffa80`00001000 fffff880`00001000 : nt!CcFlushCache+0x561
fffff880`03538450 fffff880`016fb8db : fffff880`03538970 fffffa80`0ac83180 fffff880`03538900 fffff880`0164e000 : Ntfs!NtfsCheckpointVolume+0xbc1
fffff880`03538850 fffff880`016fa27b : fffff880`03538970 fffffa80`0ac83180 fffffa80`0ac83188 fffff880`01641020 : Ntfs!NtfsCheckpointAllVolumesWorker+0x4b
fffff880`035388a0 fffff880`016fc398 : fffff880`03538970 00000000`00000000 fffff880`016fb890 fffff880`03538b78 : Ntfs!NtfsForEachVcb+0x167
fffff880`03538940 fffff800`034ea841 : 00000000`00000000 fffff800`037d3600 fffff800`0367e200 fffffa80`00000002 : Ntfs!NtfsCheckpointAllVolumes+0xb8
fffff880`03538b70 fffff800`03777e6a : 00000000`00000000 fffffa80`09b27b50 00000000`00000080 fffffa80`09a2e890 : nt!ExpWorkerThread+0x111
fffff880`03538c00 fffff800`034d1ec6 : fffff880`009b3180 fffffa80`09b27b50 fffff880`009be0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03538c40 00000000`00000000 : fffff880`03539000 fffff880`03533000 fffff880`035388a0 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_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner
---------
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80089b68f8, 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: fffffa80089b68f8, 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`035625b0 fffff800`036d3ca9 : fffffa80`089b68d0 fffffa80`06a95040 fffffa80`06b11b70 fffff880`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03562ad0 fffff800`035b4547 : fffffa80`089b68d0 fffff800`0362e2d8 fffffa80`06a95040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03562b00 fffff800`0351b945 : fffff800`0368fae0 00000000`00000001 fffffa80`0783ea00 fffffa80`06a95040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03562b40 fffff800`0349a841 : fffff800`0362e200 fffff800`0351b920 fffffa80`06a95000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03562b70 fffff800`03727e6a : 00000000`00000000 fffffa80`06a95040 00000000`00000080 fffffa80`069f79e0 : nt!ExpWorkerThread+0x111
fffff880`03562c00 fffff800`03481ec6 : fffff880`0336d180 fffffa80`06a95040 fffff880`033780c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03562c40 00000000`00000000 : fffff880`03563000 00000000`00000000 00000000`00000000 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
My System SpecsSystem Spec
Reply

 BSOD while loading Steam Games, Portal 2/ Borderlands 2




Thread Tools





Similar help and support threads
Thread Forum
BSOD When Installing Games on Steam/Launching Games Through Steam
It started yesterday when I attempted to launch a game (Civilization V) through Steam and got the BSOD error. I uninstalled and re-installed Steam, my graphics drivers, everything I can possibly think of, including a general fix Steam itself responded to me with (which was completely unspecific to...
BSOD Help and Support
BSOD when loading certain steam games.
Hey guys i posted here before about BSODs related to my RAM (hence the amount of dumps in the folder, i think you can ignore the majority of the older ones, the ones from today i presume will prove most helpful). I have since fixed that problem (afaik) and now present you genius' with another! ...
BSOD Help and Support
BSOD playing Borderlands 1 and 2, CS:GO, and Portal 2. Bugcheck 0x3b
So I just got Borderlands 2, and I installed it. Before I go on I'd just like to point out that the error I'm posting about happens also in Borderlands 1, CS:GO, Portal 2, and Darkness II. When I launch the game through steam, I get the standard DirectX installation that everybody usually...
BSOD Help and Support
BSOD Loading Portal 2,Deus Ex, error 0x00000101
Hello, I have recently build a new computer and I am experiencing some issues with a few games. Specs: AMD FX 4100 3.6 Quad core Gigabyte 970a-ud3 AM3+ motherboard 12gb Kingston hyper X ram (1600 DDR3) Nvidia Gefore GTX 460 1gb GDDR3 500 AND 7500 GB Western Digital Black Caviar HDD...
BSOD Help and Support
BSOD/Cold booting on FEAR 3 and Portal 2 loading screens
Hi all, new poster here, so please be fair. :) 2 days ago Portal 2 was playing fine, but yesterday I upgraded my CPU (to an AMD FX 4100 Quad Core Black edition), motherboard (Gigabyte 78LMT-S2P) and my Ram (4GB DDR 3). I figured I could just swap the components and keep going without...
BSOD Help and Support
BSOD loading Portal 2, error 0x00000101
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...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:47.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App