Constant shut downs, bsod's, and stop errors...

What is overclocking? This is my first time being back on for a bit cause my computer wouldn't make it to the desktop. The 2003 driver is probably for Adobe Audition 1.5 which is the only program I know how to mix vocals in, and I can't grasp the new versions of Adobe Audition. A new driver probably won't be compatible with it. I didn't run Memtest or drive verifier cause I don't have access to another computer.

do I need this driver? I don't know what that is exactly. If I don't need it can you guide me through removing it? I thought it may have to do with me having Adobe Auditon 1.5 on my comp based off of what I read at http://www.file.net/process/pfc.sys.html I'm not sure if I was allowed to post that link, just a reference point.

First time comp has been working for hours, was hoping there would be a reply. While I'm at it, does anyone know of any useful command prompts I could enter to help? I've tried bootrec/fixmbr and bootrec/fixboot, it helps once in awhile for me to get back on when my comp won't startup, but it usually doesn't.

Jaiz said:

First time comp has been working for hours, was hoping there would be a reply. While I'm at it, does anyone know of any useful command prompts I could enter to help? I've tried bootrec/fixmbr and bootrec/fixboot, it helps once in awhile for me to get back on when my comp won't startup, but it usually doesn't.

Reply about what? Have you removed the 2003 driver?

There are no relevant "cmd prompts" for removing the driver.

Jaiz said:

Just able to finally get back on my comp. I need to know how to remove all traces of the 2003 driver, and know it's not linked with Adobe Audition. I know it's not a simple process and involves editing the registry. Need to know exactly what to do

[Edit] Well I deleted pfc.sys from C:/windows/system32/drivers Additionally I removed pfc from the lower filter reference in regedit at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318} I don't know what else to delete in regedit cause I pressed ctrl+f to find any references to pcf.sys, and it seems to be linked to a bunch of stuff. I also see there is an entire folder for pfc located in reg edit HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet002\services\pfc I don't know if that's just random letters for files/drivers that start with pfc or what. I deleted the imagepath registry key in that folder which referenced C:/windows/system32/driver/pfc.sys I don't know what else I should delete from the folder, or if I should delete that whole pfc folder. I need to know specifically every entry I need to delete in regedit. I made a restore point before deleting anything involving pfc just in case I further screwed up my computer.

Im unsure abt PFC's association. I have gone to 4 places and all relate it to the mfr I specified.

I am a bit nervous about registry editing to fix the symptom rather than the cause.

At some point it may just be easier to do a clean install.

Let us know if you need help.

Well the OS has been cleanly installed several times over the past 2 years or so. The issues keep coming back with my comp shutting down with bsod's galore, and not starting up. My comp is still shutting down like crazy since my last post, and it's hard to stay on for long when it will actually start up and let me do something for a little bit. Have to save every few seconds in a text document to post on here. So I keep hoping for replies in the thread to try to at least fully remove this 2003 driver. I doubt I fully removed all traces of it. Here's some new minidump files, so let me know if it's still showing that driver, and if there's anything new.

Jaiz said:

Ok well I tried to take a much easier approach of updating drivers by find a program that automatically detected outdated drivers, and replace them. I also downloaded, installed, and ran Malware bytes as suggested. I felt good thinking maybe all this would help a bit, but sure enough my computer has been shutting down with bsod's. I've compiled the new minidump for the shutdowns today, and would like to know if the problems are anything new or it's the same issues. I also would like to know if there's anymore I can do without actually physically going into my computer, cause I don't know how to do that myself and I'll just further mess the computer up.

If you dont want to do the suggested tests I suggest the easiest course it to take it to a pro.

You can tell him/her they are memory exceptions.

K well I'm trying the Driver verifier process. I did it in safe mode, and when I tried to restart my comp wouldn't boot. I did a hard shut down and booted up again, and this time it went through. So is the verifier still gonna do it's job if my initial restart attempt wasn't successful?