General discussion

Locked

Bugcheck Crashes

By info ·
My dual pIII600 server (Nt4.0/sp6a/Backoffice) intermittently crashes. Usually in the middle of the night. The errors are uniform:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x00007fff, 0x00000002, 0x00000000, 0x00007fff). Microsoft Windows NT [v15.1381]. A full dump was not saved.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007f (0x00000008, 0x00000000, 0x00000000, 0x00000000).

The bugcheck was: 0x0000007f (0x00000008, 0x00000000,0x00000000, 0x00000000).
snip ...
The bugcheck was: 0x0000000a (0x7d0000f8, 0x00000002, 0x00000000, 0x8010ab27).

The bugcheck was: 0x0000001e (0xc0000005, 0x80137598, 0x00000000, 0x00000008).

The bugcheck was: 0x0000001e (0xc0000005, 0xf20433c1, 0x00000000, 0x041c3900).

The bugcheck was: 0x0000007f (0x00000008, 0x00000000, 0x00000000, 0x00000000).

The bugcheck was: 0x00000050 (0xf05c2790, 0x00000000, 0x00000000, 0x00000003).

The bugcheck was: 0x0000007f (0x00000008, 0x00000000, 0x00000000, 0x00000000).

The bugcheck was: 0x0000007f (0x00000008, 0x00000000, 0x00000000, 0x00000000).

The bugcheck was: 0x0000000a (0x00000ad4, 0x0000001c, 0x00000001, 0x80116f1d).

The bugcheck was: 0x0000007f (0x00000008, 0x00000000, 0x00000000, 0x00000000).

The bugcheck was: 0x0000007f (0x00000008, 0x00000000, 0x00000000, 0x00000000).

The bugcheck was: 0x0000007f (0x00000008, 0x00000000, 0x00000000, 0x00000000).

The bugcheck was: 0x0000007f (0x00000008, 0x00000000, 0x00000000, 0x00000000).

Anyone have an idea what the problem is, or where to go to translate the Hex into something approaching english.

This conversation is currently closed to new comments.

11 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Bugcheck Crashes

by Bill Cassada In reply to Bugcheck Crashes

No clue but I am having the same problem on a system here...are you using software someone in-house has written? We think that a goof in the custom code may be causing this but have yet to narrow it down. I'd like to know it you figure it out.

Thanks!

Collapse -

Bugcheck Crashes

by info In reply to Bugcheck Crashes

I didn't think I was alone...

Collapse -

Bugcheck Crashes

by Slora In reply to Bugcheck Crashes

Descriptions of bug codes can be found at http://support.microsoft.com/support/kb/articles/Q103/0/59.asp

Look at each one of your bugchecks - the first hex number is the field that identifies the type of error. For example, the last bugcheck you listed would be 0x0000007f. This could also be expressed as 0x7f. 0x7f is an UNEXPECTED_KERNEL_MODE_TRAP according to the above KB article.

To find solutions based on all this gibberish, search the KB 3 times for each error: once for the longhand hex number, once for the shorthand hex number, and once for the "English" translation from the above KB article. You should normally start to see a pattern in the articles that are found based on your search.

In your particular case, you are getting a variety of STOP codes. Either you have a lot of problems on your system, or you are likely to have a disk or controller problem that causes intermittent, random failures. Check your event logs carefully, and reexamine any RAID that you might be using.

Collapse -

Bugcheck Crashes

by info In reply to Bugcheck Crashes

The question was auto-closed by TechRepublic

Collapse -

Bugcheck Crashes

by McKayTech In reply to Bugcheck Crashes

If this is a Compaq server, I'd be looking carefully at the RAID and SCSI drivers.

Also, I've seen this pattern from defective backup software. Is there any time relationship to the backup process or some other process that runs at night (e.g. virus scanning)?

paul

Collapse -

Bugcheck Crashes

by info In reply to Bugcheck Crashes

Not Compaq...

Collapse -

Bugcheck Crashes

by Todd Rathier In reply to Bugcheck Crashes

Another possibility may be the memory chips. I've experienced problems when the latency of the chips doesn't match what the bios says. The solution was change the bios to match. Another incident of the same type had the solution of put in new memory chips and all the errors went away!

Collapse -

Bugcheck Crashes

by info In reply to Bugcheck Crashes

The question was auto-closed by TechRepublic

Collapse -

Bugcheck Crashes

by rclermont In reply to Bugcheck Crashes

I digging for an answer to this problem, I found this information: Windows NT Server and NT Workstation version 4.0 has the ability to report exceptions generated by the MCE or MCA features.

The Pentium and Pentium Pro processors provides a mechanism to detect and to report hardware-related problems such as memory parity errors and cache errors. To signal a hardware error, the processor signals the detection of a machine check error by generating a machine check exception (INT 18). Windows NT simply reports the fact that the error occurred and displays parameters that you can use to decode the exception.

I believe this is being caused by a recent insertion of additional RAM in my system. I don't know that for sure, but I will investigate it and report my findings.

Collapse -

Bugcheck Crashes

by info In reply to Bugcheck Crashes

The question was auto-closed by TechRepublic

Back to Windows Forum
11 total posts (Page 1 of 2)   01 | 02   Next

Operating Systems Forums