Solved BSOD PFN List Corrupt + Memory Management + Stop F4 + More

[Humor]

My PC has been having BSOD issues recently. I've had it for about 4-5 months and it's worked okay up until a few days ago. There isn't really a pattern to them, they just happen randomly. Most of the time I can't even get to my desktop, and when I do, it blue screens shortly after. The errors I've gotten so far have been PFN List is Corrupt, Memory Management, Stop Error F4, Stop Error 1E, and Page Fault in Nonpaged Area. I tried running the SF Diagnostic Tool, but I keep getting an error: "Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately. Could not complete operation on some files and directories. See the Data property of the exception for more details." I pasted what was in the details dialogue box into notepad and uploaded it here. http://puu.sh/20tvO When I click Continue, the progress bar freezes and won't move. I've ran it as administrator as instructed. I've tried running it in Safe Mode as well, with no luck. I've run memtest and everything passed 6-8 times (can't remember how many exactly, I ran it about two days ago when this problem was still going on). I'm running Windows 7 Professional x64. I have an Intel D955XBK motherboard and a Corsair HX650w PSU installed. I've checked to make sure I have the most recent graphics card driver and that hasn't helped at all (I have the most recent driver installed). I've tried having chkdsk fix whatever is wrong, but it can't complete. I'm completely lost as to what to do from here, so any help would be appreciated! Oh, I just got a new error. System Service Exception. There was a file included: Win32k.sys. No idea what this means.

 

[Northernsoul55]

Hi humor,

ok have you tried a System file check?

Click on the Start > Type in search cmd
Right click cmd at top and Run as Administrator
Type SFC /scannow at the prompt

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

and from boot:

http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html

let us know how you get on and post back any results you note.

cheers

dave

 

[Humor]

Hi humor,

ok have you tried a System file check?

Click on the Start > Type in search cmd
Right click cmd at top and Run as Administrator
Type SFC /scannow at the prompt

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

and from boot:

http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html

let us know how you get on and post back any results you note.

cheers

dave

I tried running the system file check from the desktop and it only got to 48% before I got the error "Windows Resource Protection could not perform the requested operation" When I tried it from boot, I got "Windows Resource Protection could not start the repair service."

 

[Northernsoul55]

Hi Humor,

That sounds like the Trustedinstaller service is disabled. TrustedInstaller service starts on-demand when running the System File Checker, so please try:

Click Start, type Services.msc and left click services

Double-click Windows Modules Installer

Set its Startup type to Manual

Then reboot and try to run SFC again.
Note the space between SFC and /scannow. SFC /scannow

Cheers

Dave

 

[Humor]

Hi Humor,

That sounds like the Trustedinstaller service is disabled. TrustedInstaller service starts on-demand when running the System File Checker, so please try:

Click Start, type Services.msc and left click services

Double-click Windows Modules Installer

Set its Startup type to Manual

Then reboot and try to run SFC again.
Note the space between SFC and /scannow. SFC /scannow

Cheers

Dave

Windows Modules Installer's Startup was already set to Manual, but I restarted anyway and tried running SFC again. Command Prompt shut itself down about halfway through the scan. I couldn't catch what it said before it shut down.

 

[Northernsoul55]

Hi Humor,

Perhaps you may want to try a repair install, as you have seemed to try everything without success, and without any .dmp files or SFC results etc, we do not have a lot to go on:

http://www.sevenforums.com/tutorials/3413-repair-install.html

Hope this helps. Good Luck and let us know any progress.

Cheers

Dave

 

[Humor]

Hi Humor,

Perhaps you may want to try a repair install, as you have seemed to try everything without success, and without any .dmp files or SFC results etc, we do not have a lot to go on:

http://www.sevenforums.com/tutorials/3413-repair-install.html

Hope this helps. Good Luck and let us know any progress.

Cheers

Dave

When I insert my Windows 7 disc, nothing happens. No autoplay window, and it doesn't even show up under Computer. I opened Device Manager and saw that my CD/DVD drive has the Code 19 error. Now, it works only when I boot from it, but I think that would just erase everything off of my hard drive if I installed it that way. Should I just do a clean install of Windows? I don't really care if what I have on my hard drive is erased, all of my important things are on my external hard drive, so I wouldn't be losing anything that matters.

 

[Northernsoul55]

Hi Humor,

Yes I would do a Clean Install as your issues are pointing towards serious system and/or registry errors. A code 19 error on cd/dvd drives is usually registry related also.

Just back up any data you need and follow this guide:

http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html

Good luck and pop back and let us know how you get on

cheers

Dave

 

[Humor]

Hi Humor,

Yes I would do a Clean Install as your issues are pointing towards serious system and/or registry errors. A code 19 error on cd/dvd drives is usually registry related also.

Just back up any data you need and follow this guide:

http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html

Good luck and pop back and let us know how you get on

cheers

Dave

I'm getting an error during the installation. "Windows cannot install required files. The file may be corrupt or missing. Make sure all files required for installation are available, and restart the installation. Error code: 0x80070570" There shouldn't be anything wrong with the disc. No scratches or anything. I fixed the error with CD/DVD drive, too, and I still get this error. I guess I'll go with the repair install unless there's a way to fix this problem.

edit: I went ahead with the repair installation and it blue screened in the middle of it. 'ntfs.sys.' Starting to wonder if the hard drive is shot or something.

 

[Northernsoul55]

Hi Humor,

I am not 100% but i think an error code:0x80070570 is related to memory and possibly bad RAM, this would fit with the way your computer is behaving also.

Firstly try this:

When you see the error "0x80070570 can't access files" --> Cancel the install ---> you will be returned to the "Install Now" startup screen and - WITHOUT REBOOTING - just re-start the install.

See if that lets you install?

If not take memtest again. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.
If you get errors, stop the test and continue with the next step.
1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.
2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.
If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.
In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Errors are sometimes found after 8 passes.
Tip
Do this test overnight, before going to bed

Let us know how you get on.

Cheers

Dave

 

[Northernsoul55]

Hi Sorry just seen your Edit about ntfs.sys:

Run chkdsk /f/r in an elevated command prompt.

http://www.sevenforums.com/tutorials/433-disk-check.html

Click on the Start > Type in search cmd
Right click cmd at top and Run as Administrator
At the command prompt please type: chkdsk /f/r
(Note: there is a space between chkdsk and /f/r)

cheers

Dave

 

[Humor]

Hi Humor,

I am not 100% but i think an error code:0x80070570 is related to memory and possibly bad RAM, this would fit with the way your computer is behaving also.

Firstly try this:

When you see the error "0x80070570 can't access files" --> Cancel the install ---> you will be returned to the "Install Now" startup screen and - WITHOUT REBOOTING - just re-start the install.

See if that lets you install?

If not take memtest again. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.
If you get errors, stop the test and continue with the next step.
1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.
2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.
If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.
In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Errors are sometimes found after 8 passes.
Tip
Do this test overnight, before going to bed

Let us know how you get on.

Cheers

Dave

Well, I'm running memtest right now. 8 minutes in and so far it found 9984 errors. Huh. I guess that must've been the problem.

 

[Northernsoul55]

Hi Humor,

Ok, well let it run, follow the procedure, and you should be able to determine bad Ram from good, and let me know how you get on.

Just perhaps boot with one good known stick for now and see if you can boot into windows.

Also run the SFC if you successfully boot.

Cheers

Dave

 

[Humor]

Hi Humor,

Ok, well let it run, follow the procedure, and you should be able to determine bad Ram from good, and let me know how you get on.

Just perhaps boot with one good known stick for now and see if you can boot into windows.

Also run the SFC if you successfully boot.

Cheers

Dave

Alright, I ran all of the memtests and found out that one stick is bad, so I replaced that pair with a new pair and have successfully done a clean install of Windows. I'm currently updating and SFC can't be run because of it ("Another servicing or repair operation is currently running. Wait for this to finish and run sfc again"). As of right now, my computer has been running for about 2 hours. So far everything is working nicely. Replacing the sticks seemed to have fixed the problem. Will post again if I run into anything. Also, if you'd still like for me to run the SFC test when the updates are finished, I can do that. Anyway, thanks for the help! You've saved me! Oh, I'd also like to ask what causes a RAM stick to go bad like that? It's worked for months without problems and I'm just curious about it.

 

[Northernsoul55]

Hi Humor,

Great news
you wont have to run SFC now that you have carried out a clean install.

Ram can go bad for many a reason, overclocking, age, power surges, temperature etc.

Use the computer for a few days or so and if you feel the issue has been resolved, please mark solved.

Thanks

Dave