Hey all, new to the forums. Normally I'm the one giving advice on this kind of stuff, but now I'm stuck and I have no idea on how to fix my issue.
A few days ago, I purchased a new PC with custom parts. The specs are:
It came with a blank 250 gig HDD. I installed XP Home SP2 and immediately installed the Asus drivers that came with it, followed by nvidia drivers (which auto-installed nvidia control panel, firewall, and probably some other crap I wasn't aware of). I then continued to install AVG anti-virus and ZoneAlarm firewall.
Well, I don't remember exactly, but sometime during that first day I was hit with a ton of BSODs, and they keep coming. I hadn't turned off automatic restart at first, but I tried to remember the files/errors that came up as best I could. These are the files that kept showing up on the BSODs:
vsdatant.sys
portcls.sys
Nv4_disp.dll
afd.sys
win32k.sys
After some web surfing, I read that the NV one was caused by the nvidia firewall. So I went ahead and uninstalled the nvidia network manager thing and yeah, that one hasn't showed up since. I also read that zonealarm caused the vsdatant one, so after constant BSODs popping up when trying to uninstall it, I managed to remove the firewall. That fixed everything except afd.sys. afd.sys keeps messing up, and just when I thought that was the only problem I had, today I got win32k.sys.
So yeah, I'm decently angry. It's not like they occur during any specific action, they're almost random. Sometimes it doesn't even tell me a dll or system file that caused the problem, it just does a physical memory dump and is blank on the section that's supposed to contain the file that caused the BSOD.
I realize I probably should have written the stop hexes down too, but I forgot. I do, however, have the minidumps. I've uploaded a zip of all the minidumps. Remember though, vsdatant and nv4_disp.dll are probably fixed, and the portcls one only happened once with weird circumstances. I believe the real issue revolves around afd.sys.
if anyone has any suggestions, please let me know. Some say that zonealarm causes most of these. Could it be that it left some dlls or something that are screwing me? Oh, and, please don't suggest it's a virus/malware. I got the comp a few days ago, I had connected to the internet maybe 15 mins when I got the first BSOD with avg/za running. No way I got a virus.
I figure it's kind of beneficial that this is a new PC with a new XP install. I mean, I have almost nothing installed so there's not much clutter to go through. I have installed a few things since the first few BSODs, but nothing that is suspicious.
Sorry for the length, but I figure details are better than ambiguity.
A few days ago, I purchased a new PC with custom parts. The specs are:
Code:
Quad Core 2.4 ghz,
[SLI] Asus P5N-D Nvidia nForce 750i SLI Chipset w/7.1 Sound, Gb LAN, S-ATA Raid, USB 2.0, IEEE-1394, Dual PCI-E MB ,
2 gigs ram,
SLI nvidia 8800 GT (2x) 1gb graphics cardsWell, I don't remember exactly, but sometime during that first day I was hit with a ton of BSODs, and they keep coming. I hadn't turned off automatic restart at first, but I tried to remember the files/errors that came up as best I could. These are the files that kept showing up on the BSODs:
vsdatant.sys
portcls.sys
Nv4_disp.dll
afd.sys
win32k.sys
After some web surfing, I read that the NV one was caused by the nvidia firewall. So I went ahead and uninstalled the nvidia network manager thing and yeah, that one hasn't showed up since. I also read that zonealarm caused the vsdatant one, so after constant BSODs popping up when trying to uninstall it, I managed to remove the firewall. That fixed everything except afd.sys. afd.sys keeps messing up, and just when I thought that was the only problem I had, today I got win32k.sys.
So yeah, I'm decently angry. It's not like they occur during any specific action, they're almost random. Sometimes it doesn't even tell me a dll or system file that caused the problem, it just does a physical memory dump and is blank on the section that's supposed to contain the file that caused the BSOD.
I realize I probably should have written the stop hexes down too, but I forgot. I do, however, have the minidumps. I've uploaded a zip of all the minidumps. Remember though, vsdatant and nv4_disp.dll are probably fixed, and the portcls one only happened once with weird circumstances. I believe the real issue revolves around afd.sys.
if anyone has any suggestions, please let me know. Some say that zonealarm causes most of these. Could it be that it left some dlls or something that are screwing me? Oh, and, please don't suggest it's a virus/malware. I got the comp a few days ago, I had connected to the internet maybe 15 mins when I got the first BSOD with avg/za running. No way I got a virus.
I figure it's kind of beneficial that this is a new PC with a new XP install. I mean, I have almost nothing installed so there's not much clutter to go through. I have installed a few things since the first few BSODs, but nothing that is suspicious.
Sorry for the length, but I figure details are better than ambiguity.
