New
#1
Bsod while playing diablo 3
i have been plagued with bsods while playing diablo 3, i notice my computer starting to run harder then i get a crash sooner or later
it is really starting to anger me
i used the program whocrashed and here is what it says
Code:Crash Dump Analysis Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Fri 8/31/2012 4:24:37 AM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: unknown_module_00000000`00000000.sys (Unloaded_Unknown_Module_00000000`00000000+0x6E4F4DB9) Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF88005BDD3C4, 0xFFFFF880069CA528, 0xFFFFF880069C9D80) 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`00000000.sys . Google query: unknown_module_00000000`00000000.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED On Tue 8/28/2012 7:16:15 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\082812-21949-01.dmp This was probably caused by the following module: unknown_module_fffff880`01fa4e50.sys (Unloaded_Unknown_Module_fffff880`01fa4e50+0x2AE39A2) Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800399A1E8, 0xFFFFF88003999A40, 0xFFFFF80002EB64F7) Error: NTFS_FILE_SYSTEM Bug check description: This indicates a problem occurred in the NTFS file system. 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_fffff880`01fa4e50.sys . Google query: unknown_module_fffff880`01fa4e50.sys NTFS_FILE_SYSTEM On Mon 8/27/2012 12:31:57 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\082612-25552-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xC5 (0x16800000008, 0x2, 0x0, 0xFFFFF80003010B05) Error: DRIVER_CORRUPTED_EXPOOL 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 the system attempted to access invalid 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. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sun 8/26/2012 5:59:15 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\082612-26208-01.dmp This was probably caused by the following module: Unknown (0xFFFFF80002E841C0) Bugcheck code: 0xD1 (0xFFFFF8800BC69A00, 0x2, 0x8, 0xFFFFF8800BC69A00) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL 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. 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 . Google query: Unknown DRIVER_IRQL_NOT_LESS_OR_EQUAL On Thu 8/2/2012 5:21:49 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\080212-22136-01.dmp This was probably caused by the following module: asmthub3.sys (asmthub3+0x15A2D) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88007DAEA2D, 0xFFFFF8800362E9C8, 0xFFFFF8800362E220) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\asmthub3.sys product: ASMedia USB 3.0 Host Drivers company: ASMedia Technology Inc description: ASMedia USB3 Hub Driver Bug check description: This indicates that a system thread 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. 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: asmthub3.sys (ASMedia USB3 Hub Driver, ASMedia Technology Inc). Google query: asmthub3.sys ASMedia Technology Inc SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M On Wed 8/1/2012 6:06:25 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\080112-21325-01.dmp This was probably caused by the following module: unknown_module_00000000_00000080.sys (Unknown_Module_00000000_00000080+0x2FD79D) Bugcheck code: 0x7E (0xFFFFFFFFC000001D, 0xFFFFF88005B9AB83, 0xFFFFF88006DB2348, 0xFFFFF88006DB1BA0) 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_00000080.sys . Google query: unknown_module_00000000_00000080.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED On Mon 7/23/2012 8:16:14 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\072312-24757-01.dmp This was probably caused by the following module: Unknown (0xFFFFF88004ABD7F2) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88005B2CBF6, 0xFFFFF88009E42D90, 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. 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 . Google query: Unknown SYSTEM_SERVICE_EXCEPTION On Tue 7/17/2012 7:22:34 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\071712-22604-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x87CF9) Bugcheck code: 0x19 (0x20, 0xFFFFF8A002CD6690, 0xFFFFF8A002CD6E70, 0x947E6921) Error: BAD_POOL_HEADER 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 pool header is corrupt. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. Conclusion 8 crash dumps have been found and analyzed. 5 third party drivers have 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: asmthub3.sys (ASMedia USB3 Hub Driver, ASMedia Technology Inc) unknown_module_fffff880`01fa4e50.sys unknown_module_00000000_00000080.sys unknown unknown_module_00000000`00000000.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.
Quote