Tjena!
Min dator har alldeles nyligen börjat bluescreenat, formaterade om allting i hopp om att det skulle bli bättre, problemet kvarstår dock.
Hittar ingen logik i när det händer. Samtidigt så kraschar flikar i Chrome väldigt ofta, Diablo 3 får ofta felmeddelanden/kraschar.
Datorn är alldeles strax 2 år gammal.
Processor: Intel(R) Core i5-3570K CPU @ 3.40 GHz, 3401 Mhz, 4 kärnor.
Operativsystem: Windows 7 Ultimate, 64 bitars.
Grafikkort: GeForce GTX 670
Hårddisk 1: Corsair Force 3 SSD ATA Device, 120 GB
Hårddisk 2: Seagate Barracuda 2TB
Moderkort: Asus P8Z77-M PRO
Ram: 2x Corsair Vengenace 4GB
Nätagg: OCZ ModXStream PRO 500W
Laddade hem programmet "Whocrashed" för att kika efter felkoder, samtliga finns med här under. (Under Spoiler)
Hjälp mottages tacksamt då jag själv inte är alltför kunnig inom området..
Min dator har alldeles nyligen börjat bluescreenat, formaterade om allting i hopp om att det skulle bli bättre, problemet kvarstår dock.
Hittar ingen logik i när det händer. Samtidigt så kraschar flikar i Chrome väldigt ofta, Diablo 3 får ofta felmeddelanden/kraschar.
Datorn är alldeles strax 2 år gammal.
Processor: Intel(R) Core i5-3570K CPU @ 3.40 GHz, 3401 Mhz, 4 kärnor.
Operativsystem: Windows 7 Ultimate, 64 bitars.
Grafikkort: GeForce GTX 670
Hårddisk 1: Corsair Force 3 SSD ATA Device, 120 GB
Hårddisk 2: Seagate Barracuda 2TB
Moderkort: Asus P8Z77-M PRO
Ram: 2x Corsair Vengenace 4GB
Nätagg: OCZ ModXStream PRO 500W
Laddade hem programmet "Whocrashed" för att kika efter felkoder, samtliga finns med här under. (Under Spoiler)
Hjälp mottages tacksamt då jag själv inte är alltför kunnig inom området..
On Fri 5/16/2014 5:22:00 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051514-11528-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0xA (0xFFFFFA8020554010, 0x2, 0x1, 0xFFFFF80002D3AB07)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Fri 5/16/2014 5:22:00 AM 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: 0xA (0xFFFFFA8020554010, 0x2, 0x1, 0xFFFFF80002D3AB07)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 5/15/2014 3:19:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051514-7519-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFFA8006885130, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. 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.
crash dump file: C:\Windows\Minidump\051514-11528-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0xA (0xFFFFFA8020554010, 0x2, 0x1, 0xFFFFF80002D3AB07)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Fri 5/16/2014 5:22:00 AM 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: 0xA (0xFFFFFA8020554010, 0x2, 0x1, 0xFFFFF80002D3AB07)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 5/15/2014 3:19:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051514-7519-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFFA8006885130, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. 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.
