BSOD: 0x0000003b, 0x000000d1, 0x00000119

Supertallmidget

Reputable
Sep 7, 2014
3
0
4,510
Crashing really often after lowering my overclock. Before I was getting lots of 0x00000124 related crashes from overclocking my CPU, but after lowering it I havent gotten one even while stress testing. Now I'm getting lots of system file crashes and have no idea how to fix them. I attached the last 3 minidump files in a zip, but the characters look totally random to me (this is what I see: PAGEDU64 ± °ðõ xâÐ øÿÿÐFÊ øÿÿÐcÈ øÿÿd? $ - Pastebin.com). Heres what Im getting from whocrashed:

On Sun 9/7/2014 10:50:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090714-5397-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800035D84C1, 0xFFFFF8800DF26EE0, 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 Sun 9/7/2014 10:47:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090714-4914-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x85D4)
Bugcheck code: 0xD1 (0x1001A8, 0x6, 0x1, 0xFFFFF88003D605D4)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Sun 9/7/2014 8:24:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090714-4664-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x21785E)
Bugcheck code: 0x119 (0x1, 0x101E84, 0x1E85, 0x1E83)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 340.52
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 340.52
Bug check description: This indicates that the video scheduler has detected a fatal violation.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 340.52 , NVIDIA Corporation).
Google query: NVIDIA Corporation VIDEO_SCHEDULER_INTERNAL_ERROR



On Sun 9/7/2014 7:30:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090714-6193-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800CEF3028, 0xBF800000, 0x124)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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.
 
What is your system specs including clock speeds and voltage?

It could be your RAM if you have it overclocked, your original 0x00000124 error is usually caused by insufficient power so boosting your voltage back then would of fixed it also. These new BSODs could be caused by your CPU aging and dying, or if your RAM wearing out if you have it overclocked.
 

Supertallmidget

Reputable
Sep 7, 2014
3
0
4,510


Original blue screens were at 4.6ghz/1.22 for the voltage. Swapped it back to 4ghz for a bit, and the hardware bluescreens went away. Now I'm back at stock speeds for everything.

Specs:

i7 4770k
Corsair H100i
MSI Z87-G45
Corsair Vengeance 16GB (2 x 8GB) DDR3-2133
Samsung 840 Pro Series 256GB 2.5" SSD
Seagate Barracuda 3TB 3.5" 7200RPM
EVGA GeForce GTX 780 Ti 3GB Superclocked
Fractal Design Define R4
EVGA 750W ATX12V / EPS12V
Microsoft Windows 7 Home Premium SP1 (64-bit)
 
If you are back to running stock speed and still getting blue-screens, either your RAM or CPU is dying.

Drop your RAM down to 1600Mhz and test to see if the blue-screens go away. If they don't, its likely your CPU needs replaced. If they do, your RAM needs replaced or you can live with the slower RAM speed.
 

Supertallmidget

Reputable
Sep 7, 2014
3
0
4,510


Nothing since Ive turned everything back to stock, so we'll see how things pan out