New
#1
BSOD ntoskrnl.exe PFN_LIST_CORRUPT & IRQL_GT_ZERO_AT_SYSTEM_SERVICE
Hello,
I just received two BSOD in a row and I'm wondering what caused these and how to prevent these errors. The only thing I recall doing recently is installing the latest NVIDIA drivers (353.62) for my GTX 670.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: 4a
BCP1: 00000000770EDC2A
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF8800930BB60
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\080115-18486-01.dmp
C:\Users\Fate\AppData\Local\Temp\WER-28688-0.sysdata.xml
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
On Sat 8/1/2015 4:18:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080115-18486-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x4A (0x770EDC2A, 0x2, 0x0, 0xFFFFF8800930BB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 8/1/2015 4:15:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080115-16021-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x4E (0x99, 0x2AD1AD, 0x2, 0xC2F02)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
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 that cannot be identified at this time.
Quote