Unknown cause BSOD 0x0000007E

My crash occurs at least once daily, seemingly without provocation. I do not game or tax my system, to my knowledge, beyond its capabilities. I use Photoshop and related imaging programs most often, with Outlook and Word following. This accounts for about 90% of my computing.

Running a program called "BlueScreenView", it hints that the file afd.sys is possibly responsible. My BSOD log file is attached. I would appreciate any help that might hint at the cause of this.

The only other symptom is that sometimes my computer CRAWLS at a snails pace. Occasionally it's because my scheduled backup is running, but often there is very little running, but yet I get several second pauses between typing characters, and very jumpy and delayed mouse movement. Not sure if this is connected somehow. I've run various malware scans and virus scans to no avail.

Thanks in advance for any help.

bobrock111565 said:

My crash occurs at least once daily, seemingly without provocation. I do not game or tax my system, to my knowledge, beyond its capabilities. I use Photoshop and related imaging programs most often, with Outlook and Word following. This accounts for about 90% of my computing.

Running a program called "BlueScreenView", it hints that the file afd.sys is possibly responsible. My BSOD log file is attached. I would appreciate any help that might hint at the cause of this.

The only other symptom is that sometimes my computer CRAWLS at a snails pace. Occasionally it's because my scheduled backup is running, but often there is very little running, but yet I get several second pauses between typing characters, and very jumpy and delayed mouse movement. Not sure if this is connected somehow. I've run various malware scans and virus scans to no avail.

Thanks in advance for any help.

Memory corruption probably caused by a driver(afd.sys). please run these three tests



1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

*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.

RAM - Test with Memtest86+



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.

Driver Verifier - Enable and Disable


3-System file check
Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Read here for more information SFC /SCANNOW Command - System File Checker

Let us know the results from the report at the end.

Thanks SO very much for your very detailed and thorough advice and suggestions. I will work on this first thing tomorrow morning and report back. Again, many thanks.

ZigZag: Thanks again for your help. I ran the MemTest this morning. By the way, the newer v4 did not run for some reason. I got the first opening screen, but then no action and no response from keyboard entries. So, I had to run the 3.? version. All checked okay. Getting ready to run verifier following your suggestions. Will report back. Meanwhile, it crashed again last night (I left it on all night). New BSOD report attached. Not sure if this adds any new useful information?

bobrock111565 said:

ZigZag: Thanks again for your help. I ran the MemTest this morning. By the way, the newer v4 did not run for some reason. I got the first opening screen, but then no action and no response from keyboard entries. So, I had to run the 3.? version. All checked okay. Getting ready to run verifier following your suggestions. Will report back. Meanwhile, it crashed again last night (I left it on all night). New BSOD report attached. Not sure if this adds any new useful information?

These are memory exceptions perhaps caused by a driver (afd.sys) which is pat of the OS. Waiting on the verified DMPS

ZigZag: What do you mean by DMPS? Is that the results of my running the Verifier, or something else? Just want to make sure I give you everything you might need. Thanks.
Bob

bobrock111565 said:

ZigZag: What do you mean by DMPS? Is that the results of my running the Verifier, or something else? Just want to make sure I give you everything you might need. Thanks.
Bob

Sorry Bob.

"DMPS" (minidumps) are the files created when your computer crashes. They are stored to the pagefile file and written on the next boot.

They are the record of what happened when your computer crashed. IF verifier was running it may (should) have the offending driver written. It needs to crash your computer to write it to page file so we can look at it on the next boot.

ZigZag: As always, thanks for your ongoing help with this.
Well, I didn't crash all day yesterday, but finally last night my computer was once again brought to its knees. I'm hoping this latest report will bring me (you) a bit closer to getting this annoyance resolved. Attached is the latest BSOD report which I hope contains some new useful information. Let me know if you can help.

Thanks,
Bob Rock

bobrock111565 said:

ZigZag: As always, thanks for your ongoing help with this.
Well, I didn't crash all day yesterday, but finally last night my computer was once again brought to its knees. I'm hoping this latest report will bring me (you) a bit closer to getting this annoyance resolved. Attached is the latest BSOD report which I hope contains some new useful information. Let me know if you can help.

Thanks,
Bob Rock

Bob

It did. This driver verified crash was Related to pwipf6.sys Privacyware Filter Driver from Privacyware/PWI, Inc. I would remove it at least to test.

Other items of note. "codemeter.exe" was running at the time of the crash and may have played a part.