Also when you reply include the results of this command line typed in a
command prompt

wmic recoveros get autoreboot,writetosystemlog,debuginfotype,writedebuginfo

To copy from the command prompt to the clipboard right click in the command
prompt window, choose Mark, select the area to be copied and press Enter.

debuginfotype return no.
-----------------------
0 None
1 Complete memory dump
2 Kernel memory dump
3 Small memory dump

--
..
--
<.> wrote in message news:%23LesjR7%23JHA.5092@TK2MSFTNGP03.phx.gbl...[color=blue]
> Type in Search on Start
> memory
> and choose Memory Diagnostic
>
> After this (and this will take hours) type command on Start's search box
> and choose Command Prompt. Type
>
> chkdsk c: /r
>
> However this appears to be a driver error rather than hardware problems
> although you say the errors are different.
>
> The error you quote
> *******************************************************
> From [url]http://msdn.microsoft.com/en-us/library/ms793232.aspx[/url]
> Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION
> The SYSTEM_SERVICE_EXCEPTION bug check has a value of 0x0000003B. This
> indicates that an exception happened while executing a routine that
> transitions from non-privileged code to privileged code.
>
> Parameters
> The following parameters are displayed on the blue screen.
>
> Parameter Description
> 1 The exception that caused the bug check
> 2 The address of the exception record for the exception that caused the
> bug check
> 3 The address of the context record for the exception that caused the bug
> check
> 4 0
>
>
>
> Cause
> This error has been linked to excessive paged pool usage and may occur due
> to user-mode graphics drivers crossing over and passing bad data to the
> kernel code.
> *******************************************************
> Parameter 1 (c0000005) means Access Violation
> --
> .
> --
> "quickie" <spambuster******.co.uk> wrote in message
> news:E59211DD-337F-4DC2-9968-380A1387CA13@microsoft.com...[color=green]
>>I keep getting random BSOD when coming out of sleep mode. one of the last
>>ones was
>>
>> Problem signature:
>> Problem Event Name: BlueScreen
>> OS Version: 6.0.6002.2.2.0.256.1
>> Locale ID: 2057
>>
>> Additional information about the problem:
>> BCCode: 3b
>> BCP1: 00000000C0000005
>> BCP2: FFFFFA6000A5B550
>> BCP3: FFFFFA600E802AF0
>> BCP4: 0000000000000000
>> OS Version: 6_0_6002
>> Service Pack: 2_0
>> Product: 256_1
>>
>> Bad Pool Header, someone was suggesting it was driver conflicts, but
>> getting other spurious errors messages when it goes the BSOD[/color]
>[/color]