pienjo`
Legacy Member
Hoi
Sinds geruime tijd heb ik last van BSOD's die zich meestal voordoen tijdens het gamen. De afgelopen maanden is dit ongeveer 11x voorgevallen.
Het programma 'Who Crashed' geeft onderstaande error aan.
On Mon 27/08/2012 21:06:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082712-10576-01.dmp
uptime: 00:36:53
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF800030A1668)
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 which cannot be identified at this time.
Crash dump file: C:\Windows\Minidump\082712-10576-01.dmp
Date/time: 27/08/2012 21:06:20 GMT
Uptime: 00:36:53
Machine:
Bug check name: IRQL_NOT_LESS_OR_EQUAL
Bug check code: 0xA
Bug check parm 1: 0x40
Bug check parm 2: 0x2
Bug check parm 3: 0x1
Bug check parm 4: 0xFFFFF800030A1668
Probably caused by: ntoskrnl.exe
Driver description: NT Kernel & System
Driver product: Microsoft® Windows® Operating System
Driver company: Microsoft Corporation
OS build: Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Architecture: x64 (64 bit)
CPU count: 6
Page size: 4096
Bug check description:
This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
Comments:
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 which cannot be identified at this time.
Reeds ondernomen stappen:
- Memtest, 11 passes geen errors.
- Prime95 ongeveer een halve dag laten lopen zonder problemen.
- Furmark stresstest, passed zonder problemen.
- Alle drivers uninstalled met Driver Sweeper en recente drivers geïnstalleerd.
- Microsoft Security essentials laten scannen zonder problemen.
- MalwareBytes laten scannen zonder problemen.
CPU-Z Systeemspecs
Graag een beetje hulp! Alvast bedankt
Sinds geruime tijd heb ik last van BSOD's die zich meestal voordoen tijdens het gamen. De afgelopen maanden is dit ongeveer 11x voorgevallen.
Het programma 'Who Crashed' geeft onderstaande error aan.
On Mon 27/08/2012 21:06:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082712-10576-01.dmp
uptime: 00:36:53
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF800030A1668)
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 which cannot be identified at this time.
Crash dump file: C:\Windows\Minidump\082712-10576-01.dmp
Date/time: 27/08/2012 21:06:20 GMT
Uptime: 00:36:53
Machine:
Bug check name: IRQL_NOT_LESS_OR_EQUAL
Bug check code: 0xA
Bug check parm 1: 0x40
Bug check parm 2: 0x2
Bug check parm 3: 0x1
Bug check parm 4: 0xFFFFF800030A1668
Probably caused by: ntoskrnl.exe
Driver description: NT Kernel & System
Driver product: Microsoft® Windows® Operating System
Driver company: Microsoft Corporation
OS build: Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Architecture: x64 (64 bit)
CPU count: 6
Page size: 4096
Bug check description:
This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
Comments:
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 which cannot be identified at this time.
Reeds ondernomen stappen:
- Memtest, 11 passes geen errors.
- Prime95 ongeveer een halve dag laten lopen zonder problemen.
- Furmark stresstest, passed zonder problemen.
- Alle drivers uninstalled met Driver Sweeper en recente drivers geïnstalleerd.
- Microsoft Security essentials laten scannen zonder problemen.
- MalwareBytes laten scannen zonder problemen.
CPU-Z Systeemspecs
Graag een beetje hulp! Alvast bedankt