Weird BSOD

By keeperocrumbs ·
I have a strange problem with my XP installation. Once a day fairly soon after starting up in the morning (but not at a constant time after), my machine crashes with a BSOD. The message is mostly ntfs.sys address B9E35A54 but I have had other messages about attempting to execute a non executable part of memory (something to that effect). The comp is happy for the rest of the day after that. If I happen to need to switch off at some point in the day, on switching on again the same thing will happen just once.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

See, the thing about a BSOD, is that it is there to provide information.

by seanferd In reply to Weird BSOD

So, if you don't pass that along, a BSOD is meaningless.

Write down the code, and post it here or look it up yourself. Get more than one BSOD? Get the code from any further unique crashes as well.

Ntfs.sys is almost a hint, but your memory address is rather more irrelevant.

For giggles in the interim, test your RAM.

Collapse -

In addition to the above answer

by OH Smeg Moderator In reply to Weird BSOD

You could also try changing the BIOS Battery in your system. It very much sounds as if it's going flat and on it's way out.

When this occures the system is unstable for the first turn on of the day and tends to work properly after a Hot Start. It's only when the power is completely removed in a normal shut down that the system then defaults to relying on the BIOS Battery and causes the settings to stray slightly.


Collapse -

BSOD & Bios Battery

by keeperocrumbs In reply to In addition to the above ...

That's the thing about the BSOD - not much info.
It's says mostly STOP 0X00000024
Then all the gumpf about if this is the first time....
Then ntfs.sys and memory address.
Will certainly write down anything else it says next time I see it.

BIOS Battery: Worth a shot but the computer is only a few months old and actually has been back to supplier under warranty with a completely bricked SATA HD - so HD is new too.
In the meantime WEB searches have turned up a bit about a possible corrupted NTFS system and to try repairing it with a win2000 recovery console. - www.techspot.com/vb/topic5352-2.html

Collapse -

Some more advice...

by cmiller5400 In reply to BSOD & Bios Battery

Excerpt from --> http://www.aumha.org/a/stop.php

0x00000024: NTFS_FILE_SYSTEM
(Click to consult the online MSDN article.)
A problem occurred within NTFS.SYS, the driver file that allows the system to read and write to NTFS file system drives. There may be a physical problem with the disk, or an Interrupt Request Packet (IRP) may be corrupted. Other common causes include heavy hard drive fragmentation, heavy file I/O, problems with some types of drive-mirroring software, or some antivirus software. I suggest running ChkDsk or ScanDisk as a first step; then disable all file system filters such as virus scanners, firewall software, or backup utilities. Check the file properties of NTFS.SYS to ensure it matches the current OS or SP version. Update all disk, tape backup, CD-ROM, or removable device drivers to the most current versions.

* General Discussion {KB 228888} Win 2000, Win XP
* Caused by Open Handles while closing an application {KB 195857} Win NT, Win 2000, Win XP

Collapse -

Well as you have an Answer to the BSOD Error Above

by OH Smeg Moderator In reply to BSOD & Bios Battery

You could also address the other possibility a Faulty HDD/Controller.

If you know who made the HDD you can download the Drive Makers Testing Utility and not rely on the Computers Makers Diagnostics.


The way to use these is to run the Drive Makers Utility in your computer and if it passes the Drive and M'Board are OK. But if it fails any part of the test you then remove the drive fit to another computer and retest.

If it still fails the test the drive is on it's way to Silicon Heaven but if it passes the second test the M'Board, Data Lead or Power Supply from the first computer are faulty and need attention. With all HDD it's possible that the Drive Controller on the M'Board can be contributing to this behavior so you need to test for things like this.


Collapse -

"completely bricked SATA HD"

by seanferd In reply to BSOD & Bios Battery

You may just have another brick in the oven, then.

Collapse -


by POPPA G In reply to Weird BSOD

The batt sounds proable, but test the ps just to be sure.

Related Discussions

Related Forums