BSOD i need help please !

Sebastien · 23 Jun 2010

hi! i cannot start any game on my pc each time i'am trying to run a game The pc Crash with this code error

Signature du problème :
Nom d’événement de problème: BlueScreen
Version du système: 6.1.7600.2.0.0.768.3
Identificateur de paramètres régionaux: 3084

Informations supplémentaires sur le problème :
BCCode: 101
BCP1: 0000000000000018
BCP2: 0000000000000000
BCP3: FFFFF880009B2180
BCP4: 0000000000000004
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Fichiers aidant à décrire le problème :
C:\Windows\Minidump\061210-17359-01.dmp
C:\Users\Zorder\AppData\Local\Temp\WER-29062-0.sysdata.xml

Lire notre déclaration de confidentialité en ligne :
Search Microsoft.com

Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion :
C:\Windows\system32\fr-FR\erofflps.txt

sorry For the french language. code are still the same one i belive.

I have attached what i think its could help you to help me out.

Thanks !!

Lordbob75 · 23 Jun 2010

This looks to me that your CPU is causing it to crash.

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.

This sounds like it is saying the Processor clock was off, causing the system to shut down.

Not sure how to check this, but it seems like your CPU is bad. Lets make sure before we have to replace it though.

Code:

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


Loading Dump File [C:\Users\David\AppData\Local\Temp\7zO2DD3.tmp\061210-17359-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a64000 PsLoadedModuleList = 0xfffff800`02ca1e50
Debug session time: Fri Jun 11 22:11:38.828 2010 (UTC - 7:00)
System Uptime: 0 days 0:16:48.937
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {18, 0, fffff880009b2180, 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: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b2180, 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

PROCESS_NAME:  kh2.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`07267a58 fffff800`02a82443 : 00000000`00000101 00000000`00000018 00000000`00000000 fffff880`009b2180 : nt!KeBugCheckEx
fffff880`07267a60 fffff800`02ade5f7 : 00000000`00000000 fffff800`00000004 00000000`00002626 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`07267af0 fffff800`02a2f090 : 00000000`00000000 fffff880`07267ca0 fffff800`02a4a460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`07267bf0 fffff800`02ad23f3 : 00000000`fffffffe fffff800`02a4a460 fffffa80`05fe3840 00000000`00000001 : hal!HalpRtcClockInterrupt+0x130
fffff880`07267c20 00000000`77682246 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
00000000`0018f154 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77682246


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
---------

~Lordbob

reventon · 23 Jun 2010

Hi,

Please turn driver verifier on:

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Please upload all dump files that you get

Regards,
Reventon

Sebastien · 23 Jun 2010

[QUOTE=reventon;804411]Hi,

Please turn driver verifier on:

Perfect. i will plug my 2th computer, and will start doing all this step one by one. will let you know if anything hapend.

Thanks so much , already can see thats i could see this end of this probleme one day.

Sebastien · 24 Jun 2010

well i did everything , now. i know what does make it ''Blue screen'' I only need to start a game, put it to full Graphique and than ( full screen) and bang. crash, My Only prob at the moment its thats my pc stay in ''BSOD'' and Do not rebot by it self. its only hapened to me only once thats he reboted by it self. or else i will wait 5-10 mins and it wont rebot alone... what could i do to make it rebot alone?... dumb question i think theres no way but who noes....

and if i rebot manually, its doesnt give me the code when i get back on my desktop... mm..h.m. ,, still waithing thats he rebot alone...

reventon · 24 Jun 2010

It doesn't matter if it reboots automatically or not - what matters is if a minidump is created in C:\Windows\Minidump

Upload the latest dump files please.

Sebastien · 24 Jun 2010

oh okay, i though that files was created only when the pc was reboting alone. thanks im learning alot tonight!

There the lastest one.

Lordbob75 · 24 Jun 2010

To enable restarting after a BSoD, go to system (press start and pause/break) then advanced system settings. Click on Advanced system settings on the left, then go to the advance tab. Under that, click on startup and recovery settings. Under the system failure section, check automatically restart.

The "code" is in your dump file, located in C:\minidump as reventon said.

~Lordbob

Lordbob75 · 24 Jun 2010

Same as the last one.

Code:

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


Loading Dump File [C:\Users\David\AppData\Local\Temp\7zO61FE.tmp\061010-15515-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a03000 PsLoadedModuleList = 0xfffff800`02c40e50
Debug session time: Thu Jun 10 00:30:05.093 2010 (UTC - 7:00)
System Uptime: 0 days 0:13:06.187
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {18, 0, fffff88002f64180, 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: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002f64180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`0336fd88 fffff800`02a21443 : 00000000`00000101 00000000`00000018 00000000`00000000 fffff880`02f64180 : nt!KeBugCheckEx
fffff880`0336fd90 fffff800`02a7d5f7 : 00000000`00000000 fffff800`00000002 00000000`00002626 fffff880`033700c8 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`0336fe20 fffff800`02ff4090 : 00000000`00000000 fffff880`0336ffd0 fffff800`0300f460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0336ff20 fffff800`02a713f3 : fffff800`02bede80 fffff800`0300f460 00000000`00000001 00000000`00000000 : hal!HalpRtcClockInterrupt+0x130
fffff880`0336ff50 fffff800`02a342c9 : ffff0000`02407eb2 ffff0000`02407e62 fffffa80`06e2e0df fffffa80`08746c07 : nt!KiInterruptDispatchNoLock+0x163
fffff880`033700e0 fffff800`02d0b64f : 00000000`00000000 fffff880`03370700 00000000`00000000 fffffa80`078d0b20 : nt!KeFlushProcessWriteBuffers+0x65
fffff880`03370150 fffff800`02d6fa06 : fffff8a0`06d820a8 fffff880`0001ff58 fffff880`033702e0 00000000`00000000 : nt!ExpGetProcessInformation+0x7f
fffff880`033702a0 fffff800`02d70e49 : fffff8a0`06d820a8 fffffa80`6365734b 00000000`00000000 fffff880`03370c20 : nt!ExpQuerySystemInformation+0xf14
fffff880`03370640 fffff800`02a74153 : fffff880`03370710 fffff800`02a730fd 00000000`00000001 fffffa80`078b4060 : nt!NtQuerySystemInformation+0x4d
fffff880`03370680 fffff800`02a706f0 : fffff880`01506a9c 00000000`00000000 fffff880`03370844 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`03370818 fffff880`01506a9c : 00000000`00000000 fffff880`03370844 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage
fffff880`03370820 fffff880`0150656d : fffffa80`078b4060 00000000`00000000 fffff800`20206f49 fffff800`02a7fac1 : cng!GatherRandomKey+0x22c
fffff880`03370be0 fffff800`02d6e541 : 00000000`00000000 fffffa80`0887de00 fffffa80`0887de00 fffffa80`06a24680 : cng!scavengingWorkItemRoutine+0x3d
fffff880`03370c80 fffff800`02a82161 : fffff800`02c18500 fffff800`02d6e504 fffffa80`06a24680 00000000`00000000 : nt!IopProcessWorkItem+0x3d
fffff880`03370cb0 fffff800`02d18166 : 10101010`10101010 fffffa80`06a24680 00000000`00000080 fffffa80`06a08040 : nt!ExpWorkerThread+0x111
fffff880`03370d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspSystemThreadStartup+0x5a


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
---------

~Lordbob

Sebastien · 24 Jun 2010

that was the last one, i made it crash. and the automatically restart is Checked. mmh.. i dont know what to do now.

BSOD i need help please !

BSOD i need help please !

mh,,