Blue Screen

Loxa · 28 Jul 2013 at 17:19

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

Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\072813-8985-01.dmp
C:\Users\Loxa\AppData\Local\Temp\WER-10623-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

-------

Is this to do with not enough Voltage on my GPU? I undervolted it because of the weather. Thanks in advance

Loxa · 29 Jul 2013 at 16:15

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 28/07/2013 16:16:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072813-8985-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BD0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 23/07/2013 03:36:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072313-8985-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88003102180, 0x6)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.

Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Loxa · 29 Jul 2013 at 16:27

i7-3770K
ASRock Z77 Extreme4
GeIL EVO Veloce Hot-Rod Red 16GB (2x8GB) DDR3 PC3-17000C11 2133MHz
Gigabyte ATi Radeon HD 7950 Windforce 3X 3072MB
OCZ 700W

The BSOD for 101 I already sorted just not sure about the BSOD for 1e.

Loxa · 29 Jul 2013 at 16:38

Ok ill give it a go, one quick question. Is it possible for the error from under volting my GPU to much? Because the day it happened I used a voltage of 1125v and the day before I used 1131v which was stable.

Loxa · 29 Jul 2013 at 16:50

Ok, i just checked my memory in the bios which is currently running at 1600mhz - 11-11-11-28 - 1.65v

When i tryed to run it at 2133mhz - 11-11-11-36 it boot looped, kinda strange since thats the speed it comes out of the box

Loxa · 29 Jul 2013 at 16:54

Ok, thanks for all the help.