F5F Stay Refreshed Hardware Desktop Error occurred with PNF file list and system fix applied.

Error occurred with PNF file list and system fix applied.

Error occurred with PNF file list and system fix applied.

L
lhuynh
Junior Member
Find
7
10-22-2023, 06:56 PM
#1
Hello everyone, I discovered the solution. It took me a few weeks to identify and fix it, as pinpointing the problem was challenging. Here’s what I found: the issue stemmed from multiple RGB software installations. Removing all of them resolved the matter. PROBLEM: My system would crash with the error code PFN LIST CORRUPT. Initially, it appeared random. By recording instances, it became clear it often happened after waking up from sleep or after launching or closing a game. CONTEXT: The problem began after adding a 2TB Seagate M.2 drive. I made numerous changes to my PC during this upgrade, complicating the tracking process. To simplify troubleshooting, keep modifications minimal. My motherboard has two M.2 slots—one under the CPU using the CPU PCIe lanes and another near the chipset via the south bridge PCIe lanes. My OS used a chipset M.2 slot because it was simpler to install, while the CPU slot remained empty. I swapped them for visual appeal since the new drive has RGB lighting. After installing both in their respective slots, I entered BIOS to verify everything was stable and noticed XMP wasn’t enabled. This seemed odd, so I turned it on at 3600MHz—possibly because I recently upgraded RAM. It felt strange, but it might have been the trigger. Once in Windows, I initialized and formatted the new drive; everything worked perfectly. The new M.2 had RGB, so I tried Open RGB, then Signal RGB, followed by Corsair iCue for compatibility with MSI Mystic Lighting. After uninstalling the unsupported programs, I connected it to my system and everything functioned well. Then the BSODs resumed a few days later. TROUBLESHOOTING: I suspected the M.2 was faulty since that was the only change I made. I updated BIOS, chipset drivers, and other components, but nothing resolved the issue. I checked for firmware updates on the SSD, found none. Event logs indicated crashes only after unexpected shutdowns, suggesting a potential hardware fault. Despite software tweaks—lowering XMP profiles, adjusting RAM settings—I still faced the same problem. Eventually, realizing I’d installed multiple RGB packages at once, I removed them all. After uninstalling the problematic software, the BSODs stopped. I gradually increased my RAM speeds back up to 3600MHz, and it resolved completely. Now, without the RGB software, my system runs smoothly. Event logs showed no errors, only crashes during unexpected shutdowns. It seems the RGB packages were the root cause. I reinstalled the M.2 drive, which worked fine. I still can’t sync my RGB without risking another crash. Event logs remained clean.
Reply
Reply
L
lhuynh
10-22-2023, 06:56 PM #1

Hello everyone, I discovered the solution. It took me a few weeks to identify and fix it, as pinpointing the problem was challenging. Here’s what I found: the issue stemmed from multiple RGB software installations. Removing all of them resolved the matter. PROBLEM: My system would crash with the error code PFN LIST CORRUPT. Initially, it appeared random. By recording instances, it became clear it often happened after waking up from sleep or after launching or closing a game. CONTEXT: The problem began after adding a 2TB Seagate M.2 drive. I made numerous changes to my PC during this upgrade, complicating the tracking process. To simplify troubleshooting, keep modifications minimal. My motherboard has two M.2 slots—one under the CPU using the CPU PCIe lanes and another near the chipset via the south bridge PCIe lanes. My OS used a chipset M.2 slot because it was simpler to install, while the CPU slot remained empty. I swapped them for visual appeal since the new drive has RGB lighting. After installing both in their respective slots, I entered BIOS to verify everything was stable and noticed XMP wasn’t enabled. This seemed odd, so I turned it on at 3600MHz—possibly because I recently upgraded RAM. It felt strange, but it might have been the trigger. Once in Windows, I initialized and formatted the new drive; everything worked perfectly. The new M.2 had RGB, so I tried Open RGB, then Signal RGB, followed by Corsair iCue for compatibility with MSI Mystic Lighting. After uninstalling the unsupported programs, I connected it to my system and everything functioned well. Then the BSODs resumed a few days later. TROUBLESHOOTING: I suspected the M.2 was faulty since that was the only change I made. I updated BIOS, chipset drivers, and other components, but nothing resolved the issue. I checked for firmware updates on the SSD, found none. Event logs indicated crashes only after unexpected shutdowns, suggesting a potential hardware fault. Despite software tweaks—lowering XMP profiles, adjusting RAM settings—I still faced the same problem. Eventually, realizing I’d installed multiple RGB packages at once, I removed them all. After uninstalling the problematic software, the BSODs stopped. I gradually increased my RAM speeds back up to 3600MHz, and it resolved completely. Now, without the RGB software, my system runs smoothly. Event logs showed no errors, only crashes during unexpected shutdowns. It seems the RGB packages were the root cause. I reinstalled the M.2 drive, which worked fine. I still can’t sync my RGB without risking another crash. Event logs remained clean.

Reply
Reply