Desktop

Ask something
Discussion Locked

System abruptly reboots. .dmp files

0 helpful
5 replies

by patternflyer 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi, All,
I am randomly having abrupt rebooting problem.
Event log shows below.
-------------------------------
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000024 (0x0019025e, 0xb8becae8, 0xb8bec740, 0xbff096e9). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini012003-01.dmp.
--------------------------------
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xc0000005, 0x8040079d, 0x00000001, 0x00000009). MicrosoftWindows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini011203-01.dmp.
--------------------------------
How can I fix the above?
Is there any way to look at the dump saved as xxxxxxx.dmp?

Are the above addresses from Memory?
All the bugcheck always happen while I am connected to internet.
I didn't install any new program within the last whole month. Bugcheck began to happen this month.
Norton Systemworks Pro 2001 doesn't get anything.

the system is AMP XP1700+, ECS K7S5A, 1G PC-133 SDRAM (I didn't use DDR), Maxtor 60G, Win 2K Pro, etc.

Thanks,

Ihncheol

5 replies

by rboggio1

The two error codes you have called both relate to execution of code.
Stop 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED
This Stop message, also known as Stop 0x1E, indicates that a kernel-mode process tried to execute an illegal or unknown processor instruction. This error handler is a default error handler that catches errors not associated with other specific error handlers.
Stop 0x00000024 or NTFS_FILE_SYSTEM
This Stop message, also known as Stop 0x24, indicates that a problem occurred within Ntfs.sys (the driver file that allows the system to read and write to NTFS drives).
It would appear there is a problem reading and writing to the memory bus. Several things could be wrong. I would start by
a. Check for updates on all device drivers.
b. Run scandisk and verify it will run and complete without any error's or reboots. (Run a complete scan and surface check. Then run Defrag. If that will complete without incident, or if it fails and reboots I would suspect there is a hiccup in the ram and it puts out an errant instruction. The reason I say pass or fail is if it defrags a lot it will use a lot of RAM. If it defrags a little, well you have a gig so it won't get used. If scandisk finds a problem in a cluster or clusters then you answer is found.
Check your ram
a In the BIOS under CPU setup change the speed to xxxx/100. Check and see if the problem re-occurs. If not I would suspect the ram has a problem running at 133MHz. If the problem reoccurs as described I would suspect bad ram.
b Try a different stick big enough to run the system. If the problem reoccurs I would suspect processor or supporting chipset. Either case will be hard to determine if you cannot test with a different part. There are several free RAM testers on the web. They test integrity points and not so much speed. The problem would be found by one of these.
Bottom line Bad code is being executed. My experiance is RAM.

by patternflyer

Thank you for the very detailed explanation, I think I found solution. The system was running at 1100MHz.
I went into BIOS to see any different thing. Well, It was reset to 100/100 that was supposed to be 133/133. This probably was the problem?

All device driverss are up to date.
Scandisk came up nothing (brand new disk).
Defrag went through without any glitch.
I downloaded system testers and every tests passed.
For the last three days, BIOS CPU setup has not change or had another stop.
Is it possible to have such error when running the CPU at slower speed?
I may go back to ASUS board with Intel CPU. I am still not convinced of AMD processor and those cheap motherboards. My PIII 866 slot 1 with ASUS P3V4X still runs perfectly since my purchase about 4 or more years ago.
Thank you,

by mdelyea

Also, check that "read around writes" is not enabled under your BIOS. Some tweak sites tell you to enable this, but my personal experience is that it tends to make your system less reliable.

by patternflyer

There wasn't anything related to read around write in the BIOS. However, I will keep this in my Tech database.
Thank you,

This discussion is closed to new replies.