XP crashing - system errors - details

  • Thread starter Thread starter Big Bill
  • Start date Start date
B

Big Bill

XP Pro, SP2, crashes a lot when programs open or close, here's
details;

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 27/06/2008
Time: 21:06:22
User: N/A
Computer: SEMPRON
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


here's one I crashed earlier;

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 27/06/2008
Time: 12:55:10
User: N/A
Computer: SEMPRON
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

they look the same to my unpracticed eye.

Well, gentlemen, what do I do now please?

Many thanks,

BB
 
Try run,type:Msinfo32 Expand the top tree in submenu,click on memory,
chk youre data with listed memory data,you'll probably find a match..To get
technical,download the WHQL debugger,run the tests..
 
Hey Bill,

This error is often caused due to Hardware changes and/or Malicious
software in the background.

What you need to do is first trying using "Last known Good
Configuration" by holding the F8 key during bootup and selecting it.

Second Choice is to think about if you had made any changes to the
hardware. Make sure you update your drivers and also try removing any
unnecessary hardware.

Please reply,

Nathan F.
 
Bill

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

0x00000008, or Double Fault, indicates that an exception occurs during a
call to the handler for a prior exception. Typically, the two exceptions
are handled serially. However, there are several exceptions that cannot
be handled serially, and in this situation the processor signals a
double fault. There are two common causes of a double fault:
A kernel stack overflow. This overflow occurs when a guard page is hit,
and the kernel tries to push a trap frame. Because there is no stack
left, a stack overflow results, causing the double fault. If you think
this overview has occurred, use the !thread debugger extension to
determine the stack limits, and then use the kb (Display Stack
Backtrace) debugger command with a large parameter (for example, kb 100)
to display the full stack.
A hardware problem.


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.

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
Try run,type:Msinfo32 Expand the top tree in submenu,click on memory,
chk youre data with listed memory data,you'll probably find a match..To get
technical,download the WHQL debugger,run the tests..
Click to expand...

Thanks but that was too technical.

BB
 
Hey Bill,

This error is often caused due to Hardware changes and/or Malicious
software in the background.
Click to expand...

Turns out I have some grayware running. I'm now trying to remove it -
grrrrrrrrrrr!

BB
 
Back
Top