• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

BSOD errors. Help

T

Traxan

Senior member
So since building my new system I've been plagued with BSODs. It tends to happen with games. In fact, I'm struggling to remember a time it didn't happen with a game. Not surprising, then, MemTest 4.0 came up clean.

System config:

Core i7-4770K
Gigabyte GA-Z87-D3HP
16GB of 1600MHz DDR3 memory
Nvidia GTX 670 card, latest drivers
Windows 7-64, fully up to date.
600w PSU

I guess the first move is to look at the dmp files generated by the crash, but I can't open them. What utility do you all recommend?

TIA.
 
Traxan said:
So since building my new system I've been plagued with BSODs. It tends to happen with games. In fact, I'm struggling to remember a time it didn't happen with a game. Not surprising, then, MemTest 4.0 came up clean.

System config:

Core i7-4770K
Gigabyte GA-Z87-D3HP
16GB of 1600MHz DDR3 memory
Nvidia GTX 670 card, latest drivers
Windows 7-64, fully up to date.
600w PSU

I guess the first move is to look at the dmp files generated by the crash, but I can't open them. What utility do you all recommend?

TIA.
Click to expand...

Is your VGA overclocked? Regardless if it is, run a GPU stress test like FurMark and see what happens then.
 
Furmark report:

BURN-IN SCORE: 3528 points

35017 frames, 38 FPS, 89°C
Resolution: 1920x1080 (FS) - AA:0 samples
FPS: min:39, max:40, avg:38 - OPTIONS: DynBkg
GeForce GTX 670/PCIe/SSE2 (10DE-1189)
9.18.13.2049 (6-21-2013) - GL:nvoglv64
GPU core: 914 MHz, memory: 3004 MHz
Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz

WhoCrashed report

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 8/10/2013 2:54:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081013-12058-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800033E75B0, 0xFFFFF8800C24BF40, 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 that cannot be identified at this time.



On Sat 8/10/2013 2:54:41 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800033E75B0, 0xFFFFF8800C24BF40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 that cannot be identified at this time.



On Thu 8/8/2013 12:07:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080813-14320-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCA2C6)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600010A2C6, 0xFFFFF88009912E40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 7/29/2013 6:20:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072913-13166-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x10E (0x1F, 0xFFFFF8A00137F370, 0x1, 0x1F3F14A)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
 
Everything points to the Nvidia driver. MS also confirms that error 0x3b, SYSTEM_SERVICE_EXCEPTION, may be caused by a third-party graphics driver:
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
Click to expand...
I'd suggest you first uninstall your current Nvidia driver then reboot and install an earlier WHQL driver version to test with.

.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top