New
#1
BSOD while playing or watching Youtube.
Hey guys!
Since a few days, I've been having these strange BSOD errors. Did a clean Windows reinstall yesterday, the error persists. Thought the errors had to do with my RAMs, so I've tried pulling them out but got crashes with each of them.
I've vacuumed the dust from my computer.
Usually I'm having this issue when I'm playing a game, or using Chrome in hardware accelerated mode (for example playing videos on Youtube), but it's kind of random. Sometimes the screen has colored stripes before it crashes.
system_service_exception 0x3b, 0x01e,0x07e - ntoskrnl.exe
Logs:
According to BlueScreenView it's ntoskrnl.exe. Log: https://dl.dropboxusercontent.com/u/...ash%20log.html
WhoCrashed error:
I've uploaded my dump files to my Dropbox with the SF Diagnostic Tool.Code:System Information (local) -------------------------------------------------------------------------------- computer name: SILGROND-PC windows version: Windows 7 , 6.1, build: 7600 windows dir: C:\Windows Hardware: ASUSTeK Computer INC., M4A785TD-M EVO CPU: AuthenticAMD AMD Phenom(tm) II X4 955 Processor AMD586, level: 16 4 logical processors, active mask: 15 RAM: 8589070336 total VM: 2147352576, free: 1990963200 -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Wed 2014.01.01. 17:34:00 GMT your computer crashed crash dump file: C:\Windows\Minidump\010114-23665-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002AC40D6, 0xFFFFF880092980A0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR 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 Wed 2014.01.01. 17:34:00 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, 0xFFFFF80002AC40D6, 0xFFFFF880092980A0, 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 Wed 2014.01.01. 17:24:31 GMT your computer crashed crash dump file: C:\Windows\Minidump\010114-24258-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002A9B91B, 0x0, 0xFFFFFFFFFFFFFFFF) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR 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 2014.01.01. 17:02:56 GMT your computer crashed crash dump file: C:\Windows\Minidump\010114-24164-01.dmp This was probably caused by the following module: unknown_module_00000000`00000001.sys (Unloaded_Unknown_Module_00000000`00000001+0x2FAF4B) Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF88004175F00, 0xFFFFF880023D56A8, 0xFFFFF880023D4F00) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch. 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: unknown_module_00000000`00000001.sys . Google query: unknown_module_00000000`00000001.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED On Wed 2014.01.01. 15:15:40 GMT your computer crashed crash dump file: C:\Windows\Minidump\010114-31044-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88004505C80, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR 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 -------------------------------------------------------------------------------- 5 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: unknown_module_00000000`00000001.sys If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems. 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.
https://dl.dropboxusercontent.com/u/...01-01-2014.rar
Thank you very much for your kind help!
Silgrond
Quote