New
#1
BSOD playing 3D games (The Witcher 2, FFXIV beta, SC5) various errors
My PC works normally during normal browsing and office work. When playing some games like The Witcher 2 and not 2D games like FTL, they sometimes crash to desktop, and sometimes I get BSODs. SF diagnostic tool report is attached.
Temps appear normal. CPU is 35-40 idle, 65 or so during gaming. GPU is about 65 idle, 70-75 gaming.
Example of two recent crashes from whocrashed. Most recent was while playing SimCity5
On Wed 3/20/2013 1:30:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031913-26613-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFF80003A4ECC0, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. 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 which cannot be identified at this time.
On Sat 3/9/2013 7:19:14 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030913-23914-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800038C1F94, 0xFFFFF8800E42F4A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 which cannot be identified at this time.