Serious system help! I think I isolated the problem..

A

AxiOn IXI

n00b
Joined
Feb 10, 2004
Messages
62
My problem: Windows is EXTREMELY unstable. Crashes during most games.. whether it be a blue screen of death or an error report. It will also bluescreen me when installing stuff or brosing the internet.

Im running windows 2000, and before, i had the option "restart on system failuire" checked, so everytime something would go wrong.. the system would just restart on me, and i had no clue why. I unchecked it, and i now get blue screens in its place.

When i do get the blue screen it usually reads:

"***STOP: 0x0000001 (0xc0000005, 0x804B8CEB, 0x00000000, 0x00000024)
kmode_exception_not_handled
***Address 804b8ceb base at 80400000, Date Stamp 39760637 - NTOSKRNL.exe
Physical memory dump complete. Contact your system administrator or support group."


What is ntoskrnl.exe?


I still have this problem, after reformatting AND installing a new motherboard, processor, video card, and case (;)).

The only common hardware between the 2 systems was the ram (which i beleive is the cause, or atleast hope so), 2 hard drives (which i dont think it is.. cause i reformatted them, installed windows on both of them, and the problem remains.) and the PSU (thats not it).

Now, is this sort of behavior typical of faulty ram? I think my old motherboard is damaged and may have corrupted the ram when i put it in once....

Please, and help is appreciated.
 
I should also add..

I threw in my friends stick of ram and the system didnt give me a problem running 3dmark 03 (which usually crashes, but not always with my other ram.)

And when I run 3dmark 03, it will crash and just give me a straight blue screen, with no error report. Also.. 3dmark 01 and 03 may just crash and go to the desktop.

What are the chances that a stick of ram can damage a motherboard permanantly? Thats what im worried about... I hope its just a faulty stick of ram causing this.
 
It sounds like memory to me. Correct me if I"m wrong, but I don't think RAM can destroy a motherboard, unless physically by installing it wrong. The symptoms all point to bad RAM though.

NTOSKRNL....I'm guessing from the name is the system kernel. (You have to replace this to change boot up screens) If you google that term, then you will see a lot of stop errors that may pertain to you and help you fix your problem. Good Luck
 
Alright.. Help me explain this... In my old system.. while having this problem, I figured it was a ram problem. So my friend hooked me up with some perfectly fine Samsung pc3200 512mb.. i put it in, started it up and was first greeted with a blue screen on the windows loadup (maybe due to the fact that my motherboard didnt support that speed). I took it out.. then held on to it untill i got my new system. Athlon 64 3000, ms neo-fsr mobo. I used that ram, and i still get the crashing problem. So.. im hoping it is the ram, which would make for an easy fix.
 
That is definatly a ram problem. When you start getting address errors with syntax like 0x000000 or something, those are memory addresses, (0x000000 is NULL).
 
The athlon 64 requires ECC memory.

You may have corrosion in the dim slots , was the samy memroy gold plated?

If you live in a high humidity environment the samy memory may have coroded the dim slots.
 
All A64's do not require ECC memory, only the fx's. And no, im pretty sure i know what may have happend to the ram.

Just wanted to know if those symptoms and errors were typical with ram problems.
 
You must log in or register to reply here.
Back
Top