BSOD on wake after changing CPU

[SubstreamAI]

I have filled out my system specs in the forum facility. The system was originally built with an Athlon II X2 255 Regor CPU. I changed it out with an Athlon II X4 630 and now I get the BSOD when waking the computer from sleep.

Attached are the results of Windows_NT6_BSOD_v3.03_jcgriff2_.exe wit PerfMon report added ("PerfMon_Report.html").

Your help is much appreciated, thank you.

 

[zigzag3143]

I have filled out my system specs in the forum facility. The system was originally built with an Athlon II X2 255 Regor CPU. I changed it out with an Athlon II X4 630 and now I get the BSOD when waking the computer from sleep.

Attached are the results of Windows_NT6_BSOD_v3.03_jcgriff2_.exe wit PerfMon report added ("PerfMon_Report.html").

Your help is much appreciated, thank you.

Memory corruption probably Related to PSINAflt.sys PSINAflt Filter Driver from Panda Security, S.L.. I would remove it and replace with Microsoft Security essentials.

These were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org/#downiso

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

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



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[SubstreamAI]

PSINAflt.sys is part of Panda Cloud AV. If I remove PCAV and put the computer to sleep, when I wake it up, everything is fine. With it installed, it will get the BSOD very quickly after waking. If I set PCAV to not scan just before I put it to sleep, then when I wake it up (and turn scanning back on), the OS will limp along with odd errors here and there until eventually it gets a BSOD. If I log out before putting the computer to sleep, when I wake it up and try to log in, it will get a BSOD almost immediatly. I'm fairly certain PCAV is the problem.

In the PCAV forum there are countless threads on PSINAflt.sys causing BSODs though none are related to waking. I will post a thread there and see where that goes. When I know something I will update this thread with what I find.

I find it odd that it worked fine with the old CPU? I think I will also swap out the CPUs again and see if the problem persists.

Notes:
As part of my testing I uninstalled PCAV and reinstalled several times using the absolute latest copy possible (that is not in beta).
While I wait for a response in the PCAV forum, I will run memtest from an Ubuntu 10.10 live CD. I expect to find no errors at all, but you never know.
I really don't want to lose PCAV (in favor of something like MSEssentials). If that seems odd, take a look at PC Magazines review of the best free AV products (not sure if I can post a link here, so just google that).