BSOD on bootup!!

[KnickNut3]

Hey. When I turned on my computer this afternoon (running WinXP), I got a nice BSOD just as the mouse icon was about to pop up with the following error:

"An attempt was made to write to read-only memory.
blah blah blah
Technical Information:
*** Stop: 0X000000BE (0xF836C28D...)
*** ntfs.sys - Address F836C28D base at F8350000, datestamp 3b7dc5d0
Dump physical memory."

I have not made any major hardware/software changes to my machine in a while. I tried disabling all my startup programs when in safe mode, I tried the last good boot configuration, and logging, but I still get this same screen every time.

Is any piece of my hardware failing (possibly), or is it a software problem (that's why I put it here)? Thanks for any and all help.

KnickNut3

 

[ThatDumbGuy]

disable any bios caching or shadowing in your bios, does it work now?

 

[KnickNut3]

Nah. The only caching/shadowing in the BIOS not already diabled was Video BIOS Shadowing. I disabled it, but it made no difference. Thanks for the try. I'd appreciate any other ideas, thanks.

 

[ThatDumbGuy]

Looking at MS Knowledge Base, not finding anything really pertaining to that specific error... sorry bro. The only thing I could find is that errors with ntfs.sys could mean that that file is corrupted, or your ide drivers are screwy/corrupted, or your hard drive is going bad. Ick. Good luck troubleshooting it, maybe try posting this in the OS forum, too.

 

[KnickNut3]

Uh oh... is there any way I can tell? It was fine this morning...

 

[KnickNut3]

I'm crying 🙁 Help please! Bump!

 

[KnickNut3]

Just tried the "repair" option in Windows install... didn't help at all 🙁.

 

[CdnMade]

try clocking your cpu the way it should be.

 

[KnickNut3]

Tried that... thanks... Actually I was having some problems a couple weeks ago (ended up being a driver problem, been smooth ever since), but during the troubleshoot for that I unoverclocked it.

 

[CdnMade]

i might be offbase but did you do a upgrade to Xp. IF so i know for a fact that any 1 piece of software can cause funky errors in XP so try doing a format and rinstall of xp if you never did that.

 

[KnickNut3]

I've had 2 totally clean formats before I installed XP (one before each time I installed)... I don't update because I knew it would be off in one way or another.