Nedan hittar mina rapporter från Whocrashed:
On Sun 2014-01-19 15:33:05 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011914-15484-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x16916)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001D7916, 0xFFFFD000214FB060, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32k.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: Win32-drivrutin för flera användare
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 Sat 2014-01-18 19:25:32 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011814-14015-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x2C2F9)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8000143E2F9, 0xFFFFD00020A36498, 0xFFFFD00020A35CA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.
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 Sat 2014-01-18 15:47:55 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011814-15515-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x7BC5)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80000C07BC5, 0xFFFFD00021D58EE8, 0xFFFFD00021D586F0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 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 Sat 2014-01-18 13:56:27 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011814-15203-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF8000085695F)
Bugcheck code: 0xD1 (0xFFFFE00082FB9A60, 0x2, 0x0, 0xFFFFF8000085695F)
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 Sat 2014-01-18 13:12:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011814-15859-01.dmp
This was probably caused by the following module: srtsp64.sys (SRTSP64+0x22668)
Bugcheck code: 0x3B (0x80000003, 0xFFFFF80004F54668, 0xFFFFD000272796E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\System32\Drivers\NISx64\1404000.028\SRTSP64.SYS
product: AutoProtect
company: Symantec Corporation
description: Symantec AutoProtect
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: srtsp64.sys (Symantec AutoProtect, Symantec Corporation).
Google query: Symantec Corporation SYSTEM_SERVICE_EXCEPTION
On Sat 2014-01-18 11:34:42 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011814-16265-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x1298B)
Bugcheck code: 0xD1 (0x10, 0x2, 0x1, 0xFFFFF8000081298B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 Sat 2014-01-18 03:31:12 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011814-14843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8016B2E6359, 0xFFFFD00026F4D6E0, 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 Thu 2014-01-16 23:32:39 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011714-15218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xD1 (0xFFFFF80010CBCE00, 0x2, 0x8, 0xFFFFF80010CBCE00)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 2014-01-16 20:19:29 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011614-14953-01.dmp
This was probably caused by the following module: e22w8x64.sys (e22w8x64+0x8549)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800025D4549, 0xFFFFD00020F386E8, 0xFFFFD00020F37EF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\e22w8x64.sys
product: Killer e2200 PCI-E Gigabit Ethernet Controller
company: Qualcomm Atheros, Inc.
description: Killer e2200 PCI-E Gigabit Ethernet Controller
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: e22w8x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Wed 2014-01-15 20:44:54 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011514-16750-01.dmp
This was probably caused by the following module: pacer.sys (pacer+0x2A53)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80001605A53, 0xFFFFD00020FB6378, 0xFFFFD00020FB5B80)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\pacer.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: QoS Packet Scheduler
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 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.
