Windows 7 Troubleshooting BSODs: PFN_LIST_CORRUPT and MEMORY_MANAGEMENT Errors on Windows

[KrashDozer]

Ok, I dont usually complain about windows, but I have been having issues with BSODs. Now I have formatted, ran memtest, windows memory diagnostics, and numerous other things. But all of the test came back good. I did a chkdisk /f and scan disk, All good. I dont get it before I formatted the BSOD was happening about 4 times a day. now about once ever 3 days.

==================================================
Dump File         : 110611-35646-01.dmp
Crash Time        : 11/6/2011 11:26:41 AM
Bug Check String  : MEMORY_MANAGEMENT
Bug Check Code    : 0x0000001a
Parameter 1       : 00000000`00000403
Parameter 2       : fffff680`0006a578
Parameter 3       : c1300002`1f60a825
Parameter 4       : fffff680`00017f30
Caused By Driver  : 
Caused By Address : 
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : 
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\110611-35646-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 262,144
==================================================

==================================================
Dump File         : 110711-26956-01.dmp
Crash Time        : 11/7/2011 3:24:37 PM
Bug Check String  : PFN_LIST_CORRUPT
Bug Check Code    : 0x0000004e
Parameter 1       : 00000000`00000099
Parameter 2       : 00000000`002ba218
Parameter 3       : 00000000`00000002
Parameter 4       : 00000000`002ba216
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor         : x64
Crash Address     : ntoskrnl.exe+705c0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\110711-26956-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 292,504
==================================================

Link RemovedLink RemovedLink Removed

 

[ChatGPT]

It looks like you've been encountering frequent Blue Screen of Death (BSOD) errors, even after carrying out various diagnostic tests and formatting your system. The error codes you provided give insights into potential issues causing these crashes. Let's break down the information provided:

1. MEMORY_MANAGEMENT (0x0000001a):
   • Dump File: 110611-35646-01.dmp
   • Crash Time: 11/6/2011 11:26:41 AM
   • Bug Check String: MEMORY_MANAGEMENT
   • Bug Check Code: 0x0000001a
   • Parameters:
     • Parameter 1: 00000000`00000403
     • Parameter 2: fffff680`0006a578
     • Parameter 3: c1300002`1f60a825
     • Parameter 4: fffff680`00017f30
   []PFN_LIST_CORRUPT (0x0000004e):
   • Dump File: 110711-26956-01.dmp
   • Crash Time: 11/7/2011 3:24:37 PM
   • Bug Check String: PFN_LIST_CORRUPT
   • Bug Check Code: 0x0000004e
   • Parameters:
     • Parameter 1: 00000000`00000099
     • Parameter 2: 00000000`002ba218
     • Parameter 3: 00000000`00000002
     • Parameter 4: 00000000`002ba216
     [
   • ]Caused By Driver: ntoskrnl.exe Possible steps to address these issues:
   []Update Drivers: Since one of the errors mentions ntoskrnl.exe, a core Windows component, ensure your system drivers are up to date. Outdated or corrupt drivers can cause such issues. []Check Hardware: Although you've run memory tests, consider checking other hardware components like the hard drive, graphics card, and CPU. Faulty hardware can lead to BSOD errors. []System File Checker (SFC): Run the System File Checker tool to scan and repair corrupted system files that might be triggering these crashes. []Check for Malware: Perform a thorough scan for malware and viruses. Malicious software can cause system instability and lead to BSOD errors. []Windows Update: Ensure your system is up to date with the latest Windows updates. Updates often include fixes to known issues that could be causing the crashes. []Review Recent Changes: Reflect on any recent software installations or changes that coincide with the start of these BSOD errors. Reverting such changes might help identify the root cause.
2. System Restore: Consider using System Restore to revert your system to a point before these issues started. If you need further assistance or guidance on any of these steps, feel free to ask for more detailed instructions!