New
#1
Bugcheck BSOD while gaming
Hi...
again :)
So while I was gaming in Star Citizen and having GPU-Z running in background, the game froze and I got BSOD with the message:
CLOCK_WATCHDOG_TIMEOUT
So I opened the .dmp file and this is what I got:
Loading Dump File [C:\Users\Gil\Desktop\021816-13859-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
I have no idea what to do next....Code:************* Symbol Path validation summary ************** Response Time (ms) Location Deferred SRV*D:\SymCache*http://msdl.microsoft.com/download/symbols Symbol search path is: SRV*D:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 10 Kernel Version 10586 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 10586.103.amd64fre.th2_release.160126-1819 Machine Name: Kernel base = 0xfffff800`a341c000 PsLoadedModuleList = 0xfffff800`a36facf0 Debug session time: Thu Feb 18 22:40:31.707 2016 (UTC + 11:00) System Uptime: 0 days 1:15:43.407 Loading Kernel Symbols . Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. .............................................................. ................................................................ ................................................................ ... Loading User Symbols Loading unloaded module list ........... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 101, {18, 0, ffffd000355e6180, 2} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner ---------
Some more info:
appreciate any help...Code:================================================== Dump File : 021816-13859-01.dmp Crash Time : 18/02/2016 10:40:31 PM Bug Check String : Bug Check Code : 0x00000101 Parameter 1 : 00000000`00000018 Parameter 2 : 00000000`00000000 Parameter 3 : ffffd000`355e6180 Parameter 4 : 00000000`00000002 Caused By Driver : ntoskrnl.exe Caused By Address : ntoskrnl.exe+142480 File Description : Product Name : Company : File Version : Processor : x64 Crash Address : ntoskrnl.exe+142480 Stack Address 1 : Stack Address 2 : Stack Address 3 : Computer Name : Full Path : C:\Users\Gil\Desktop\021816-13859-01.dmp Processors Count : 8 Major Version : 15 Minor Version : 10586 Dump File Time : 18/02/2016 10:41:16 PM ==================================================
EDIT: I have one theory. I saw in event viewer the WHEA warning as well... my current theory is that I run a 3.5GHz Ivy Bridge which is overclocked to 4.5GHz. BUT, yesterday I went to my BIOS settings and decided to ENABLE C3, C6 and C state package. I believe they are not desirable with OC CPUs. So I just disabled them but I still have C1E state set to enabled.
Also, I do not OC my GPU.
All my components are water cooled, both GPU's and CPU.
The Ivy bridge Core i7 3770K, is delidded and I used Cool Laboratory LiquidUltra thermal paste, so temps are not an issue with my current beast of cooling system (3 huge radiators and plenty of fans).
Additionally, this happened while playing Star Citizen, which currently only utilize CPU more over GPU for graphics and since my C states were enabled, probably this caused a conflict.
I'll have to retry this...
Attachment 64844
Attachment 64843
Last edited by gil; 18 Feb 2016 at 07:36.