Re: Stop error message

Hi Joshua,

I did what you said and will put the system back in service and will see
what happens. When it happens again I will send you the bug check. Should
I send it to the group or you email account since I am not sure how long
this will take. It's inconsistent at most.

Thanks
Adam Raff

"Joshua Smith [MSFT]" <joshsm@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23gDwGiOeFHA.3032@xxxxxxxxxxxxxxxxxxxxxxx
> Hi Adam,
>
> If you follow these instructions and send me the dump I can see if I can
> see what the faulting module is. To determine what driver is causing the
> problem I need you to enable driver verifier.
> Steps:
> 1) Windows Key + R
> 2) Type in 'verifier' and hit enter
> 3) Make sure 'Create Standard Setting' is selected and hit next
> 4) Click on 'Select all drivers installed on this computer' and hit Finish
> 5) Reboot
>
> There is a possibility that your computer will crash on reboot. If this
> occurs hit F8 when rebooting just before the windows logo screen and
> select the safe mode boot option. Follow the same steps above but on step
> 4 choose 'Select driver names from a list'; hit next; check the box next
> to any driver where the provider is not Microsoft; hit Finish; reboot.
>
> This will slow the performance of you computer a little while enabled but
> will hopefully catch the driver causing corruption. Next time you crash
> the blue screen will hopefully say something like
> "DRIVER_VERIFIER_DETECTED_VIOLATION". If this occurs please send the
> corresponding minidump (by default it is at c:\windows\Minidump ) my way.
> If you have any questions or I didn't explain something well enough don't
> hesitate to e-mail me (remove "online") back. Good Luck,
>
>
> Joshua Smith
> OpenGL Test Lab
> Microsoft
> -----
>
> Get Secure! www.microsoft.com/security
>
> This posting is provided "AS IS" with no warranties, and confers no rights
>
>
> "Adam Raff" <adam@xxxxxxxxxxxxxxxx> wrote in message
> news:%23gJngFOeFHA.4040@xxxxxxxxxxxxxxxxxxxxxxx
>> Good Day,
>>
>> I am getting these errors on Windows XP Pro with SP2. All critcal
>> updates have been applied.
>>
>> Event Type: Error
>> Event Source: System Error
>> Event Category: (102)
>> Event ID: 1003
>> Date: 5/26/2005
>> Time: 10:20:46 AM
>> User: N/A
>> Computer: FRONTDESK
>> Description:
>> Error code 100000be, parameter1 e4514e84, parameter2 17537162, parameter3
>> f34fe608, parameter4 0000000f.
>>
>> 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 62 100000b
>> 0020: 65 20 20 50 61 72 61 6d e Param
>> 0028: 65 74 65 72 73 20 65 34 eters e4
>> 0030: 35 31 34 65 38 34 2c 20 514e84,
>> 0038: 31 37 35 33 37 31 36 32 17537162
>> 0040: 2c 20 66 33 34 66 65 36 , f34fe6
>> 0048: 30 38 2c 20 30 30 30 30 08, 0000
>> 0050: 30 30 30 66 000f
>>
>>
>> Event Type: Error
>> Event Source: System Error
>> Event Category: (102)
>> Event ID: 1003
>> Date: 5/27/2005
>> Time: 9:21:53 AM
>> User: N/A
>> Computer: FRONTDESK
>> Description:
>> Error code 1000008e, parameter1 c0000005, parameter2 805165ea, parameter3
>> f3346b38, 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: 38 30 35 31 36 35 65 61 805165ea
>> 0040: 2c 20 66 33 33 34 36 62 , f3346b
>> 0048: 33 38 2c 20 30 30 30 30 38, 0000
>> 0050: 30 30 30 30 0000
>>
>> The system would get the error or BSOD out of the blue. I have looked on
>> MS site and found very little info on this error. I have checked the
>> system hardware and found no errors. If any body has any ideas how to
>> test this system, it would be a great help.
>>
>> Thank You,
>> Adam Raff
>>
>
>


.

Relevant Pages

  • Re: XP BSOD reboots SP2
    ... To determine what driver is causing the problem I need you to enable driver ... Windows Key + R ... Make sure 'Create Standard Setting' is selected and hit next ... There is a possibility that your computer will crash on reboot. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: computer sporadically rebooting itself
    ... > causing the problem I need you to enable driver verifier. ... > 3) Make sure 'Create Standard Setting' is selected and hit next ... > There is a possibility that your computer will crash on reboot. ... > occurs hit F8 when rebooting just before the windows logo screen and select ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Windows Restarts randomly
    ... Blue Screens. ... The reboot might happen at any time but I can make it happen almost every ... This is usually caused by a driver.To determine what driver is causing the ... Make sure 'Create Standard Setting' is selected and hit next ...
    (microsoft.public.windowsxp.hardware)
  • Re: Windows XP Pro Random Reboot
    ... "Error Caused by Graphics Device Driver" and I did what the web page said to ... > 3) Make sure 'Create Standard Setting' is selected and hit next ... > There is a possibility that your computer will crash on reboot. ... > to any driver where the provider is not Microsoft; hit Finish; reboot. ...
    (microsoft.public.windowsxp.device_driver.dev)
  • Re: Spontaneous Reboots
    ... To determine what driver is causing the problem I need you to enable driver ... Windows Key + R ... Make sure 'Create Standard Setting' is selected and hit next ... There is a possibility that your computer will crash on reboot. ...
    (microsoft.public.windowsxp.help_and_support)
Loading