BleepingComputer.com: BSOD errors

Hi, I have a problem with one of my computers and BSOD and I hope this is the right place to post.

It's has an ASUS MB - A8V, with an AMD 64 Athlon Processor, socket 939, 3200+ (2GHz) , with 1gb of Kingston memory (2 pieces).
Video card is ATI Radeon 9250
Onboard sound and network card
It now has XP pro on it, It previously had XP home on it.

This is a brand new computer I put together about 4 years ago and never really used it.
Every once in a while I would update it but that's about it.
Never had any problems with it.

I decided to start using it and ever since then I've been getting the BSOD.

It could happen 2 or 3 times a day or you could go 2 days with no problems.

Here's what I've done so far:

Reseated all components
Tested memory ---OK
Tested hard drive - OK
Reinstalled OS - no change
Fully updated OS

I have BlueScreenView, VEW and WhoCrashed installed to view the logs, there's dumps to view.
They're too big to post, I could attach them, just let me know which ones you want.

Thanks, MrC

Post the log data generated by BlueScreenView, please.

What steps did you take to test the hard drive and RAM?

Louis

I ran Chkdsk and also a utility that I downloaded from Western Digital:
Data Lifeguard Diagnostic for DOS (Floppy)

Memory: I used memtest86 from a floppy to test memory.

Thanks!

This post has been edited by MrCharlie: 24 March 2010 - 02:53 PM

Memtest86 - Wikipedia, the free encyclopedia - http://en.wikipedia.org/wiki/Memtest

You might review Known Problems for Memtest86 and use Memtest86+, version 4 instead.

Memtest86+ - Advanced Memory Diagnostic Tool - http://www.memtest.org/#downiso

And...chkdsk /r is what you want to run. Running chkdsk without any parameters (/r, /f) may result in nothing but a read-only run, nothing fixed. If you run chkdsk using My Computer, both options selected are the equivalent of running chkdsk /r.

Louis

Quote

And...chkdsk /r is what you want to run. Running chkdsk without any parameters (/r, /f) may result in nothing but a read-only run, nothing fixed. If you run chkdsk using My Computer, both options selected are the equivalent of running chkdsk /r.

Yes that's the way I ran and found no errors, I ran it a couple of times and some different ways.

I'll run the new memory test now and get back to you.

Thanks MrC

Are all your drivers updated?

No, when I had XP home on it, I updated video card and ethernet controller drivers.

It now has XP pro on it and all drivers were installed by windows except for sound and ethernet controller, which I installed from MB installation cd.

Device manager looks fine.

Memory is being tested now, so far no errors.

Thanks, MrC

OK, memory tested OK....No errors.

MrC

Id upgrade all your drivers.

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card).

You have a ton of 50 STOP errors, I'd run Memtest86+ for a good while.

Icrontic » Diagnose with Memtest86+ - http://icrontic.com/articles/diagnose_with_memtest86

Louis

OK, I'll run it a some more.

It's Kingston memory, PC3200, 2 stick of 512mb.

Can I just run it on one stick to isolate one of them?

Thanks

Here's the report from WhoCrashed if it's of any help.

When I test RAM...I run each stick individually...in each motherboard slot...until I get an error.

One error is as good as a thousand, in my interpretation.

Then I run a different module in that slot.

On it goes until I have satisfied myself that I have or have not...a problem with each module in any given slot...or any given slot.

If that turns out OK, I also know that I don't have a problem with motherboard settings, which can also produce RAM errors.

Then I run pairs of modules.

I wind up testing all modules I have on hand at the same time in various slot configurations.

Generally...some of us who want to test our RAM allow Memtest to run overnight.

Louis

Perform system upgrades, and tell us the after effects.

IMO, your initial upload was more useful...both reflect the same basic data.

FWIW: Drivers often get flagged for BSODs on a system...when the driver is not necessarily the cause, but merely the scene where the crime becomes apparent.

If you look at all the different drivers and Windows processes mentioned...it should occur to you that it's highly unlikely that so many different files could be going bad at once.

To me, that says that a user should look elsewhere for cause/explanation.

50 STOP errors...memory...lots of 50 errors.

The only time I've seen a variety of STOP errors like that...was when I had a memory situation. I had about 8 different STOP errors in a short span.

I suppose that various other hardware items could achieve the same impact, it's just easier to start with RAM because that's the direction the STOP errors point, IMO.

I could be wrong, I am such often...but I follow the logic trail as best I can.

Louis