New
#1
BSOD: MOstly when playing online games, NTOSKRNL.EXE
Hi all, I hope someone here can help me get to the root of these BS's I have been experiencing. I have not changed anything on my PC recently except Anti virus updates from AVG, no new hardware etc. They mostly occur when I'm playing games. but also happen when browsing the web. System specs are as follows:
Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
Gigabyte Technology Co., Ltd. Z68A-D3-B3
Microsoft Windows 7 Professional 64-bit 7601 Multiprocessor Free Service Pack 1
Memory: 8GB
NVIDIA GeForce GTX 560 Ti
Here's a bit of info from WhoCrashed:
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 3/25/2012 5:43:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032512-20982-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
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 which cannot be identified at this time.
On Sun 3/25/2012 5:43:52 PM 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: 0xD1 (0x0, 0x2, 0x8, 0x0)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
I hope someone can help me, I'm really lost as to why this is happening, ty in advance.