System crash without BSOD (event information follows)

[Dave Peck]

I'm seeing this crash quite regularly on my machine. I haven't found one
consistent thing that causes it, though I've noticed that trying to move
files around/deleting them often causes the crash. There is no bluescreen --
just a fast restart and then a error dialog after the reboot.

Can someone please advise? I'm convinced it is not RAM, power supply, etc.
Just don't know where to look anymore...

Here is the full information from my event log:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 10/28/2008
Time: 6:18:25 PM
User: N/A
Computer: DRUMS
Description:
Error code 1000007f, parameter1 00000008, parameter2 80042000, parameter3
00000000, parameter4 00000000.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 37 1000007
0020: 66 20 20 50 61 72 61 6d f Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 38 2c 20 000008,
0038: 38 30 30 34 32 30 30 30 80042000
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 30 30 30 30 00, 0000
0050: 30 30 30 30 0000

 

[Leonard Grey]

"General causes of "STOP 0x0000007F" errors"
http://support.microsoft.com/?kbid=137539&sd=RMVP

 

[usasma]

STOP 0x7F errors are most commonly hardware failures, with memory hardware
being the most common ( http://aumha.org/a/stop.php#0x7f )

Also, the first parameter indicates that this is a Double Fault - and they
are usually caused either by a kernel stack overflow or a hardware issue.

So, I'd run a memory diagnostic test. There's a free one here:
http://oca.microsoft.com/en/windiag.asp

- John

 

[Dave Peck]

I've run both the memory diagnostic you point me to, and memtest x86, and
both pass. I've replaced the power supply with a known good supply -- no
change. I've verified that the processor is (well) within thermal specs, etc.
I've removed all PCI cards, etc.

I do have a minidump which might be useful. Where should I send this?

-Dave

 

[Dave Peck]

Also, please note that the error code is 0x1000007f -- that is, the sign bit
is set. Does this make a difference about what kind of error this is?

-Dave

 

[Jim]

Also, please note that the error code is 0x1000007f -- that is, the sign
bit
is set. Does this make a difference about what kind of error this is?

-Dave

No, that is not the sign bit. Hex character strings for integers with the
sign bit set start with 8 and go through f. (For systems in which that
highest bit is the sign bit which I undertand includes PC processors).
Jim

 

[Dave Peck]

Oops, true. Brain fart on my end. Still, there is a bit set -- is it at all
interesting?

 

[Jim]

Oops, true. Brain fart on my end. Still, there is a bit set -- is it at
all
interesting?

The bit in question is still part of the error code. Exactly what it means
is not obvious to me.
Jim

 

[Gerry]

Dave

This is a Stop Error on my reckoning. I would disable automatic
restart/.

Does the error occur dring the boot process or after? Does it occur in
safe mode?

Disable automatic restart on system failure. This should help by
allowing time to write down the STOP code properly should they occur
again. Right click on the My Computer icon on the Desktop and select
Properties, Advanced, Start-Up and Recovery, System Failure and uncheck
box before Automatically Restart.

Background information on Stop Error message
http://msdn2.microsoft.com/en-us/library/ms795478.aspx

0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
One of three types of problems occurred in kernel-mode: (1) Hardware
failures. (2) Software problems. (3) A bound trap (i.e., a condition
that the kernel is not allowed to have or intercept). Hardware failures
are the most common cause (many dozen KB articles exist for this error
referencing specific hardware failures) and, of these, memory hardware
failures are the most common.
Source: http://aumha.org/a/stop.htm

Are there any yellow question marks in Device Manager? Right click on
the My Computer icon on your Desktop and select Properties,
Hardware,Device Manager. If yes what is the Device Error code?

Try Start, Run, type "sigverif.exe" without quotes and hit OK. What
drivers are listed as unsigned? Disregard those which are not checked.

Try HD Tune. It only gives information and does not fix any
problems.

Download and run it and see what it turns up. You want HD Tune
(freeware) version 2.55 not HD Tune Pro (not Freeware) version 3.00.
http://www.hdtune.com/

Select the Info tabs and place the cursor on the drive under Drive
letter and then double click the two page icon ( copy to Clipboard )
and copy into a further message.

Select the Health tab and then double click the two page icon ( copy to
Clipboard ) and copy into a further message. Make sure you do a full
surface scan with HD Tune.

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~