a couple crashes have recently happened on my PC and I cannot find the problem online my self
the only change I remember preforming is changing a few settings on Nvidia control panel to play Dark souls 2. I believe it was changing the scaling to the GPU.
Windows reliability monitor is saying this is a video hardware issue if that helps.
it crashed while running League of Legends, Dark Souls 2, and Visual Studios 2013.
there was also one more crash, but a dump file was not created.
PC specs:
OS: window 7 Home Premium 64 SP1
CPU: AMD FX-8350
Ram: 16 DC DDR3
Motherboard: asus M5A99FX
GPU: Nvidia GeForce GTX 660 x2 (SLI'ed)
PSU: 750w (maybe, I can't remember of the top of my head)
From WhoCrashed
On Wed 2/18/2015 4:03:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021715-61932-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0xD49C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88000EEC49C, 0xFFFFF8800AD14DC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
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 Wed 2/18/2015 4:03:05 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0xD49C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88000EEC49C, 0xFFFFF8800AD14DC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
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 2/16/2015 9:01:14 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021615-32261-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880009B3180, 0x4)
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.
the only change I remember preforming is changing a few settings on Nvidia control panel to play Dark souls 2. I believe it was changing the scaling to the GPU.
Windows reliability monitor is saying this is a video hardware issue if that helps.
it crashed while running League of Legends, Dark Souls 2, and Visual Studios 2013.
there was also one more crash, but a dump file was not created.
PC specs:
OS: window 7 Home Premium 64 SP1
CPU: AMD FX-8350
Ram: 16 DC DDR3
Motherboard: asus M5A99FX
GPU: Nvidia GeForce GTX 660 x2 (SLI'ed)
PSU: 750w (maybe, I can't remember of the top of my head)
From WhoCrashed
On Wed 2/18/2015 4:03:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021715-61932-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0xD49C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88000EEC49C, 0xFFFFF8800AD14DC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
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 Wed 2/18/2015 4:03:05 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0xD49C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88000EEC49C, 0xFFFFF8800AD14DC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
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 2/16/2015 9:01:14 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021615-32261-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880009B3180, 0x4)
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.