Suddenly getting various system errors.

[Jeff Leites]

My computer is 9 months old and has been stable until Jan. 1. Since then it
has crashed 3 times with 3 different system errors. I would think that if
the system errors were what they say they are, they would reoccur until they
are fixed. For instance, if I had a bad driver, I would get the same message
until the driver was repaired, but the computer works for days (I turn if off
at night), in between the different errors. Any fixes for this? I don't
think it's over heating, because the last error occured during the morning
boot.

Here are the errors:

System Error 1:
Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 1/1/2008
Time: 10:06:41 PM
User: N/A
Computer: OURDESKTOP
Description:
Error code 1000008e, parameter1 c0000005, parameter2 bf8011a3, parameter3
f77fda48, 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 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 62 66 38 30 31 31 61 33 bf8011a3
0040: 2c 20 66 37 37 66 64 61 , f77fda
0048: 34 38 2c 20 30 30 30 30 48, 0000
0050: 30 30 30 30 0000


System Error 2:
Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 1/7/2008
Time: 8:12:26 AM
User: N/A
Computer: OURDESKTOP
Description:
Error code 100000d1, parameter1 00000001, parameter2 00000002, parameter3
00000000, parameter4 aa67fc31.

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 64 100000d
0020: 31 20 20 50 61 72 61 6d 1 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 31 2c 20 000001,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 61 61 36 37 00, aa67
0050: 66 63 33 31 fc31



System Error 3:
Bug Check 0x19: BAD_POOL_HEADER

This error occured while booting up this morning. I was able to reboot.

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 1/10/2008
Time: 8:35:25 AM
User: N/A
Computer: OURDESKTOP
Description:
Error code 00000019, parameter1 00000020, parameter2 e5282330, parameter3
e5282370, parameter4 0c080808.

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 30 30 30 30 30 30 31 0000001
0020: 39 20 20 50 61 72 61 6d 9 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 32 30 2c 20 000020,
0038: 65 35 32 38 32 33 33 30 e5282330
0040: 2c 20 65 35 32 38 32 33 , e52823
0048: 37 30 2c 20 30 63 30 38 70, 0c08
0050: 30 38 30 38 0808

 

[Andrew E.]

RE: Suddenly getting various system errors.

Try running microsoft memory tester,its
at:http://oca.microsoft.com/en/windiag.asp

"Jeff Leites" wrote:

> My computer is 9 months old and has been stable until Jan. 1. Since then it
> has crashed 3 times with 3 different system errors. I would think that if
> the system errors were what they say they are, they would reoccur until they
> are fixed. For instance, if I had a bad driver, I would get the same message
> until the driver was repaired, but the computer works for days (I turn if off
> at night), in between the different errors. Any fixes for this? I don't
> think it's over heating, because the last error occured during the morning
> boot.
>
> Here are the errors:
>
> System Error 1:
> Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 1/1/2008
> Time: 10:06:41 PM
> User: N/A
> Computer: OURDESKTOP
> Description:
> Error code 1000008e, parameter1 c0000005, parameter2 bf8011a3, parameter3
> f77fda48, 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 38 1000008
> 0020: 65 20 20 50 61 72 61 6d e Param
> 0028: 65 74 65 72 73 20 63 30 eters c0
> 0030: 30 30 30 30 30 35 2c 20 000005,
> 0038: 62 66 38 30 31 31 61 33 bf8011a3
> 0040: 2c 20 66 37 37 66 64 61 , f77fda
> 0048: 34 38 2c 20 30 30 30 30 48, 0000
> 0050: 30 30 30 30 0000
>
>
> System Error 2:
> Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 1/7/2008
> Time: 8:12:26 AM
> User: N/A
> Computer: OURDESKTOP
> Description:
> Error code 100000d1, parameter1 00000001, parameter2 00000002, parameter3
> 00000000, parameter4 aa67fc31.
>
> 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 64 100000d
> 0020: 31 20 20 50 61 72 61 6d 1 Param
> 0028: 65 74 65 72 73 20 30 30 eters 00
> 0030: 30 30 30 30 30 31 2c 20 000001,
> 0038: 30 30 30 30 30 30 30 32 00000002
> 0040: 2c 20 30 30 30 30 30 30 , 000000
> 0048: 30 30 2c 20 61 61 36 37 00, aa67
> 0050: 66 63 33 31 fc31
>
>
>
> System Error 3:
> Bug Check 0x19: BAD_POOL_HEADER
>
> This error occured while booting up this morning. I was able to reboot.
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 1/10/2008
> Time: 8:35:25 AM
> User: N/A
> Computer: OURDESKTOP
> Description:
> Error code 00000019, parameter1 00000020, parameter2 e5282330, parameter3
> e5282370, parameter4 0c080808.
>
> 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 30 30 30 30 30 30 31 0000001
> 0020: 39 20 20 50 61 72 61 6d 9 Param
> 0028: 65 74 65 72 73 20 30 30 eters 00
> 0030: 30 30 30 30 32 30 2c 20 000020,
> 0038: 65 35 32 38 32 33 33 30 e5282330
> 0040: 2c 20 65 35 32 38 32 33 , e52823
> 0048: 37 30 2c 20 30 63 30 38 70, 0c08
> 0050: 30 38 30 38 0808
>
>
>

 

[Gerry]

Re: Suddenly getting various system errors.

Jeff

Hunt the needle in the haystack!

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

0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
A kernel mode program generated an exception which the error handler
didn't catch. These are nearly always hardware compatibility issues
(which sometimes means a driver issue or a need for a BIOS upgrade).
Source: http://aumha.org/a/stop.htm

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

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
The system attempted to access pageable memory using a kernel process
IRQL that was too high. The most typical cause is a bad device driver
(one that uses improper addresses). It can also be caused by caused by
faulty or mismatched RAM, or a damaged pagefile.
Source: http://aumha.org/a/stop.htm

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

0x00000019: BAD_POOL_HEADER
A pool header issue is a problem with Windows memory allocation. Device
driver issues are probably the mstt common, but this can have diverse
causes including bad sectors or other disk write issues, and problems
with some routers. (By theory, RAM problems would be suspect for memory
pool issues, but I haven't been able to confirm this as a cause.)
Source: http://aumha.org/a/stop.htm

The first question you need to ask yourself is what hardware / software
changes did you make immediately prior to the first error occuring.

Even though you have dismissed overheating remove any dust bunnies from
inside the computer casing using an Air Duster and check all fans are
running.

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.

tTy Start, Run, type "sfc /scannow" without quotes and hit Enter.

Description of Windows XP and Windows Server 2003 System
File Checker (Sfc.exe)
http://support.microsoft.com/default.aspx?scid=kb;en-us;310747

You will need your CD.

Check for motherboard updates to drivers and the BIOS. Third party not
Microsoft.

Is the computer still under warranty?

--



Hope this helps.

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


Jeff Leites wrote:
> My computer is 9 months old and has been stable until Jan. 1. Since
> then it has crashed 3 times with 3 different system errors. I would
> think that if the system errors were what they say they are, they
> would reoccur until they are fixed. For instance, if I had a bad
> driver, I would get the same message until the driver was repaired,
> but the computer works for days (I turn if off at night), in between
> the different errors. Any fixes for this? I don't think it's over
> heating, because the last error occured during the morning boot.
>
> Here are the errors:
>
> System Error 1:
> Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 1/1/2008
> Time: 10:06:41 PM
> User: N/A
> Computer: OURDESKTOP
> Description:
> Error code 1000008e, parameter1 c0000005, parameter2 bf8011a3,
> parameter3 f77fda48, 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 38 1000008
> 0020: 65 20 20 50 61 72 61 6d e Param
> 0028: 65 74 65 72 73 20 63 30 eters c0
> 0030: 30 30 30 30 30 35 2c 20 000005,
> 0038: 62 66 38 30 31 31 61 33 bf8011a3
> 0040: 2c 20 66 37 37 66 64 61 , f77fda
> 0048: 34 38 2c 20 30 30 30 30 48, 0000
> 0050: 30 30 30 30 0000
>
>
> System Error 2:
> Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 1/7/2008
> Time: 8:12:26 AM
> User: N/A
> Computer: OURDESKTOP
> Description:
> Error code 100000d1, parameter1 00000001, parameter2 00000002,
> parameter3 00000000, parameter4 aa67fc31.
>
> 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 64 100000d
> 0020: 31 20 20 50 61 72 61 6d 1 Param
> 0028: 65 74 65 72 73 20 30 30 eters 00
> 0030: 30 30 30 30 30 31 2c 20 000001,
> 0038: 30 30 30 30 30 30 30 32 00000002
> 0040: 2c 20 30 30 30 30 30 30 , 000000
> 0048: 30 30 2c 20 61 61 36 37 00, aa67
> 0050: 66 63 33 31 fc31
>
>
>
> System Error 3:
> Bug Check 0x19: BAD_POOL_HEADER
>
> This error occured while booting up this morning. I was able to
> reboot.
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 1/10/2008
> Time: 8:35:25 AM
> User: N/A
> Computer: OURDESKTOP
> Description:
> Error code 00000019, parameter1 00000020, parameter2 e5282330,
> parameter3 e5282370, parameter4 0c080808.
>
> 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 30 30 30 30 30 30 31 0000001
> 0020: 39 20 20 50 61 72 61 6d 9 Param
> 0028: 65 74 65 72 73 20 30 30 eters 00
> 0030: 30 30 30 30 32 30 2c 20 000020,
> 0038: 65 35 32 38 32 33 33 30 e5282330
> 0040: 2c 20 65 35 32 38 32 33 , e52823
> 0048: 37 30 2c 20 30 63 30 38 70, 0c08
> 0050: 30 38 30 38 0808

 

[Jeff Leites]

Re: Suddenly getting various system errors.

Gerry - Thank you for through explaination. It is still under warranty, but
only if it is a hardware issue.

I have researched these messages (I admit I don't fully understand the
complete meaning of each one), but I don't understand why my dirvers or bios
would work one day and not the next, then work again after rebooting. So far
not one of these messages have reocurred.

I have already run "sigverif.exe". The only thing to come up were some
Symantec files, not any hardware drivers. I don't know why Symantec has
drivers, but I'm afraid my A/V program would stop working without them.

I also ran the memory tester, but stopped it after 6 passes because the
instructions said if it passed the first test, the memory was probably ok. I
since read that I should let it run much longer, and plan to do that as soon
as I have a chance.

I haven't tried SFC yet, but as I said about the drivers, if a file is bad,
I would expect continuous failures.

I'm leaning towards thinking there is a memory problem, and I hope a longer
test will verify that.





"Gerry" wrote:

> Jeff
>
> Hunt the needle in the haystack!
>
> Background information on Stop Error message 0x8E
> http://msdn2.microsoft.com/en-us/library/ms794023.aspx
>
> 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
> A kernel mode program generated an exception which the error handler
> didn't catch. These are nearly always hardware compatibility issues
> (which sometimes means a driver issue or a need for a BIOS upgrade).
> Source: http://aumha.org/a/stop.htm
>
> Background information on Stop Error message 0xD1
> http://msdn2.microsoft.com/en-us/library/ms795930.aspx
>
> 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
> The system attempted to access pageable memory using a kernel process
> IRQL that was too high. The most typical cause is a bad device driver
> (one that uses improper addresses). It can also be caused by caused by
> faulty or mismatched RAM, or a damaged pagefile.
> Source: http://aumha.org/a/stop.htm
>
> Background information on Stop Error message 0x19
> http://msdn2.microsoft.com/en-us/library/ms793223.aspx
>
> 0x00000019: BAD_POOL_HEADER
> A pool header issue is a problem with Windows memory allocation. Device
> driver issues are probably the mstt common, but this can have diverse
> causes including bad sectors or other disk write issues, and problems
> with some routers. (By theory, RAM problems would be suspect for memory
> pool issues, but I haven't been able to confirm this as a cause.)
> Source: http://aumha.org/a/stop.htm
>
> The first question you need to ask yourself is what hardware / software
> changes did you make immediately prior to the first error occuring.
>
> Even though you have dismissed overheating remove any dust bunnies from
> inside the computer casing using an Air Duster and check all fans are
> running.
>
> 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.
>
> tTy Start, Run, type "sfc /scannow" without quotes and hit Enter.
>
> Description of Windows XP and Windows Server 2003 System
> File Checker (Sfc.exe)
> http://support.microsoft.com/default.aspx?scid=kb;en-us;310747
>
> You will need your CD.
>
> Check for motherboard updates to drivers and the BIOS. Third party not
> Microsoft.
>
> Is the computer still under warranty?
>
> --
>
>
>
> Hope this helps.
>
> Gerry
> ~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>

 

[Gerry]

Re: Suddenly getting various system errors.

Jeff

Are there any other errors or warnings in Event Viewer?

Please post copies of all Error and Warning Reports appearing in
the System and Application logs in Event Viewer for the last boot. No
Information Reports or Duplicates please. Indicate which also appear in
a previous boot.

You can access Event Viewer by selecting Start, Control Panel,
Administrative Tools, and Event Viewer.

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Click the button and close Event
Viewer.Now start your message (email) and do a paste into the body of
the message. Make sure this is the first paste after exiting from
Event Viewer.

You might also try HD Tune(freeware) as you can see the SMART
information relating to the drive etc.

Download and run it and see what it turns up.
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
~~~~~~~~~~~~~~~~~~~


Jeff Leites wrote:
> Gerry - Thank you for through explaination. It is still under
> warranty, but only if it is a hardware issue.
>
> I have researched these messages (I admit I don't fully understand the
> complete meaning of each one), but I don't understand why my dirvers
> or bios would work one day and not the next, then work again after
> rebooting. So far not one of these messages have reocurred.
>
> I have already run "sigverif.exe". The only thing to come up were some
> Symantec files, not any hardware drivers. I don't know why Symantec
> has drivers, but I'm afraid my A/V program would stop working without
> them.
>
> I also ran the memory tester, but stopped it after 6 passes because
> the instructions said if it passed the first test, the memory was
> probably ok. I since read that I should let it run much longer, and
> plan to do that as soon as I have a chance.
>
> I haven't tried SFC yet, but as I said about the drivers, if a file
> is bad, I would expect continuous failures.
>
> I'm leaning towards thinking there is a memory problem, and I hope a
> longer test will verify that.
>
>
>
>
>
> "Gerry" wrote:
>
>> Jeff
>>
>> Hunt the needle in the haystack!
>>
>> Background information on Stop Error message 0x8E
>> http://msdn2.microsoft.com/en-us/library/ms794023.aspx
>>
>> 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
>> A kernel mode program generated an exception which the error handler
>> didn't catch. These are nearly always hardware compatibility issues
>> (which sometimes means a driver issue or a need for a BIOS upgrade).
>> Source: http://aumha.org/a/stop.htm
>>
>> Background information on Stop Error message 0xD1
>> http://msdn2.microsoft.com/en-us/library/ms795930.aspx
>>
>> 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
>> The system attempted to access pageable memory using a kernel process
>> IRQL that was too high. The most typical cause is a bad device driver
>> (one that uses improper addresses). It can also be caused by caused
>> by faulty or mismatched RAM, or a damaged pagefile.
>> Source: http://aumha.org/a/stop.htm
>>
>> Background information on Stop Error message 0x19
>> http://msdn2.microsoft.com/en-us/library/ms793223.aspx
>>
>> 0x00000019: BAD_POOL_HEADER
>> A pool header issue is a problem with Windows memory allocation.
>> Device driver issues are probably the mstt common, but this can have
>> diverse causes including bad sectors or other disk write issues, and
>> problems with some routers. (By theory, RAM problems would be
>> suspect for memory pool issues, but I haven't been able to confirm
>> this as a cause.) Source: http://aumha.org/a/stop.htm
>>
>> The first question you need to ask yourself is what hardware /
>> software changes did you make immediately prior to the first error
>> occuring.
>>
>> Even though you have dismissed overheating remove any dust bunnies
>> from inside the computer casing using an Air Duster and check all
>> fans are running.
>>
>> 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.
>>
>> tTy Start, Run, type "sfc /scannow" without quotes and hit Enter.
>>
>> Description of Windows XP and Windows Server 2003 System
>> File Checker (Sfc.exe)
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;310747
>>
>> You will need your CD.
>>
>> Check for motherboard updates to drivers and the BIOS. Third party
>> not Microsoft.
>>
>> Is the computer still under warranty?
>>
>> --
>>
>>
>>
>> Hope this helps.
>>
>> Gerry
>> ~~~~
>> FCA
>> Stourport, England
>> Enquire, plan and execute
>> ~~~~~~~~~~~~~~~~~~~

 

[rbd]

Re: Suddenly getting various system errors.

Another memory possibility - assuming you are not overclocking -

Download a copy of CPU-Z and look at the memory timings for each stick of
memory.

Then go into the BIOS and be sure the the BIOS memory settings match the
CPU-Z ratings.

Not likely, but ....


"Jeff Leites" <Jeff Leites@discussions.microsoft.com> wrote in message
news:245024D9-9A64-4EA9-A0C0-C6D59151F997@microsoft.com...
> My computer is 9 months old and has been stable until Jan. 1. Since then
> it
> has crashed 3 times with 3 different system errors. I would think that if
> the system errors were what they say they are, they would reoccur until
> they
> are fixed. For instance, if I had a bad driver, I would get the same
> message
> until the driver was repaired, but the computer works for days (I turn if
> off
> at night), in between the different errors. Any fixes for this? I don't
> think it's over heating, because the last error occured during the morning
> boot.
>
> Here are the errors:
>
> System Error 1:
> Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 1/1/2008
> Time: 10:06:41 PM
> User: N/A
> Computer: OURDESKTOP
> Description:
> Error code 1000008e, parameter1 c0000005, parameter2 bf8011a3, parameter3
> f77fda48, 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 38 1000008
> 0020: 65 20 20 50 61 72 61 6d e Param
> 0028: 65 74 65 72 73 20 63 30 eters c0
> 0030: 30 30 30 30 30 35 2c 20 000005,
> 0038: 62 66 38 30 31 31 61 33 bf8011a3
> 0040: 2c 20 66 37 37 66 64 61 , f77fda
> 0048: 34 38 2c 20 30 30 30 30 48, 0000
> 0050: 30 30 30 30 0000
>
>
> System Error 2:
> Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 1/7/2008
> Time: 8:12:26 AM
> User: N/A
> Computer: OURDESKTOP
> Description:
> Error code 100000d1, parameter1 00000001, parameter2 00000002, parameter3
> 00000000, parameter4 aa67fc31.
>
> 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 64 100000d
> 0020: 31 20 20 50 61 72 61 6d 1 Param
> 0028: 65 74 65 72 73 20 30 30 eters 00
> 0030: 30 30 30 30 30 31 2c 20 000001,
> 0038: 30 30 30 30 30 30 30 32 00000002
> 0040: 2c 20 30 30 30 30 30 30 , 000000
> 0048: 30 30 2c 20 61 61 36 37 00, aa67
> 0050: 66 63 33 31 fc31
>
>
>
> System Error 3:
> Bug Check 0x19: BAD_POOL_HEADER
>
> This error occured while booting up this morning. I was able to reboot.
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 1/10/2008
> Time: 8:35:25 AM
> User: N/A
> Computer: OURDESKTOP
> Description:
> Error code 00000019, parameter1 00000020, parameter2 e5282330, parameter3
> e5282370, parameter4 0c080808.
>
> 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 30 30 30 30 30 30 31 0000001
> 0020: 39 20 20 50 61 72 61 6d 9 Param
> 0028: 65 74 65 72 73 20 30 30 eters 00
> 0030: 30 30 30 30 32 30 2c 20 000020,
> 0038: 65 35 32 38 32 33 33 30 e5282330
> 0040: 2c 20 65 35 32 38 32 33 , e52823
> 0048: 37 30 2c 20 30 63 30 38 70, 0c08
> 0050: 30 38 30 38 0808
>
>
>