Series of BSOD's: Oh how I have NOT missed them ><

Dear readers,

It's been quite a while (though I have been browsing around here ) that I needed assistance.

As of recent, my dear computer (cough cough) is giving me a difficulties again by serving me a fresh batch of various BSOD's.
It seems vaguely familiar, but last time it happened badly was back in 2011. Had the occasional hiccup in-between then and now, but not as bad as it is now.

I attached today's fresh MiniDumps, in the hope that some can help me figure out what is going on this time 'round.
(something went wrong here. Didn't add them?)

Hope anyone can help me, and thank you in advance for taking the time to read my plea for help.

Sincerely,
Marti

Below is some data about my PC (Thank you for posting BelArc!) (Hope I did it right!) DIMM0 is unused as it is busted (instant BSOD when in use, sadly the dodos I bought this PC didn't believe me so I didn't get a new MoBO)

Operating System System Model
Windows XP Home Edition Service Pack 3 (build 2600)
Install Language: English (United States)
System Locale: English (United States)
Installed: 29-8-2011 21:26:49
Boot Mode: BIOS (Secure Boot not supported) No details available
Processor a Main Circuit Board b
2,90 gigahertz AMD Athlon II X2 245
256 kilobyte primary memory cache
2048 kilobyte secondary memory cache
64-bit ready
Multi-core (2 total)
Not hyper-threaded Board: ASUSTeK Computer INC. M2N68-AM SE2 Rev X.0x
Serial Number: MT7099K17805572
Bus Clock: 200 megahertz
BIOS: American Megatrends Inc. 1409 04/29/2010
Drives Memory Modules c,d
320,06 Gigabytes Usable Hard Drive Capacity
211,13 Gigabytes Hard Drive Free Space

TSSTcorp CDDVDW SH-S223C SCSI CdRom Device [Optical drive]

WDC WD3200AAKS-00V1A0 [Hard drive] (320,07 GB) -- drive 0, s/n WD-WCAWF2717275, rev 05.01D05, SMART Status: Healthy 1024 Megabytes Usable Installed Memory

Slot 'DIMM0' is Empty
Slot 'DIMM1' has 1024 MB
Local Drive Volumes


c: (NTFS on drive 0) * 26,21 GB 2,39 GB free
d: (NTFS on drive 0) 157,28 GB 125,17 GB free
e: (NTFS on drive 0) 136,56 GB 83,57 GB free

* Operating System is installed on c:

 

Apologies for the double post, didn't know how to fix the attachment mishap

 

Hi, Marti.

The latest crash feels like it might be related to interference from an old security/firewall software remnant, list of uninstallers/removal tools here for any that you no longer have installed.

The others don't suggest much, can you copy the dumps from C:\WINDOWS\Minidump\ to your Desktop then zip and attach them, please?

 

Thank you for your reply.

I ran the removal tool, but it didn't find my old Internet Security, so I ran it forced (chose the old program manually to be removed).

I have (hopefully, am a bit rusty when it comes to compressing files :-o ) the zip-file of the 3 latest Minidumps.

Hope anyone can help me figure it out.
Personally, I begin to think the HD begins to fail. Not sure :banghead

 

Marti, we need the dumps copied to the Desktop and then zipped and attached, not shortcuts to them ^^

 

I think my computer has seen too many Harry Potter movies and is now thinking: "I solemnly swear I'm up to no good." Seems to enjoy annoying me rolleyes

I tried again, hopefully it has worked this time around.

(Todays Mini added as well, just noticed it when I looked at the files in the zip).

 

Adding today's series as well.
It rebooted due to BSOD's more often than that there are Minidump-files.

Took about 9 attempts until Chkdsk finally managed to fully run (it did choose to run by itself, I tried manually with every method I could find, but nothing worked :S). After Chkdsk finished, Windows booted normally and showed me a message that a Registry file had been recovered(restored?)

 

Did a repair-installation of Windows, everything is freshly updated, yet sadly the *bleep* issue remains.

Added the MiniDump files from the last 4 days

I think, it'd be best if I bought a new HD and rebuild my PC with the parts of my husband's computer (he upgraded his, thought he had a hardware issue when it was a windows issue :-D, so now we have a working MoBo -intact- and various components, spare).
I'm literally at wits end.. and ready to throw the towel in the ring - and I don't give up easy

 

At the moment I'm thinking ram issue. I'm seeing: Page_fault_in_nonpaged_area, bad_pool_header, etc.

I've seen a similar issue that required a bios update, but that is extreme. Or you could use this: http://www.majorgeeks.com/files/details/memcheck_pro.html

To check if you have bad ram. Another option is to buy new ram modules, which are quite cheap, pending on what motherboard you have.

http://www.crucial.com/upgrade/ASUS-memory/ASUS+Motherboards/M2N68-AM+SE2-upgrades.html

It may be cheaper (kinda) to just buy a new modern computer. Since, if it the ram issue, buying new ram may be expensive to buying a cheap newer computer for $500.

 

I have seen dozens of various errors, literally. I already have run memtest, and nothing was found.
Also, I am using a different ram as when the BSOD series began. Had a 2gb bank before, but thought that caused the issues. Exchanged it for a 1 GB, ran smooth for a day or two, and then the proverbial brown stuff hit the fan - again.

I have ran chkdsk once more, defragged as well, and had my internet security's tool run a tune-up on my system. Cleared out almost 6GB of garbage

Updating a bios is a mystery to me, and not really excited about attempting it in the first place. Getting a new Mobo with chip is cheaper / safer (current mobo is half broken anyway, only 1 ram-bank working of the 2. Plus, currently runs on DDR2, 3 is a heck of a lot cheaper).

 

All but 1 dump seem to be pointing to a number of hardware issues, from 'unknown' to NTFS (HDD problem?) to a USB device, there's no 3rd party driver flagged at all, so it does look like hardware - but what?!

I think, if you have the spare cash, a full upgrade/new build would be the best long-term solution, it could take weeks to figure out the culprit here.

 

Thank you, that is what we feared.
I think I know the culprit, but to be safe better save up and get new bits and bobs..
Had a batch of BSOD's again today.. Got me even more mad than I already was, since I was trying to write a post here rolleyes

Can post them, maybe they reveal something? I know 2 mentioned something about windows (think it was).

 

I'm thinking the NTFS (HDD) problem is related to the crashing. Multiple crashed computers can cause corruption in NTFS.

To check NTFS corruptions you could run chkdsk /r c: at the command prompt. Reboot and let it do its thing. Could take quite a bit of time.

But, overall, I'd backup your important data and look to getting a new computer.

 

I already have, and it found nothing.