Problems? See this thread at archive.org.
When I'm downloading torrents while encoding videos and browsing all at the same time, this has happened twice already but even Who Crashed can't figure out the problem and the error tells me nothing.
WhoCrashed said this is not a driver related BSOD but I have to mention that for the Intel Chipset Drivers / IRST / IMEI I used the newer drivers stolen from the Windows 8.1 downloads section of my laptop
===================================================================
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 20-Aug, Wednesday 09:23:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082014-8205-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
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 Wed 20-Aug, Wednesday 04:24:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082014-20373-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000094, 0xFFFFF88019B940D0, 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.
Conclusion
2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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.
-
-
-
Did you get the recent Windows 8.1 Pro Update 2? 4 of the update packages are known to cause BSODs. MS14-045: Description of the security update for kernel-mode drivers: August 12, 2014
The BSOD error message would be really helpful but the Windows 8 message is totally useless. Get a copy of the exact message after the
face.
-
-
-
That's exactly what I'd do.
-
You could also try posting here: BSOD Help and Support - Windows 7 Help Forums
FWIW the last BSOD I had was due to a bad RST driver.
Ferris23 likes this.
Unknown BSODs
Discussion in 'Windows OS and Software' started by Spartan@HIDevolution, Aug 20, 2014.
