Bluescreen unexpected shutdowns

Operating on an emachine with vista home premium for the six months that we
have had this machine we have been having these seemingly random and always
unexpected bluescreen errors. I just recently started to look into it and
have followed suggestions from the fine folks at Gateway to attempt full
factory recovery and startup repair procedures to no avail. The following is
the combined text from four (4) shutdowns over the course of 2 hours this
morning, there does not appear to be any one software or application that
triggers these events. Seems to be some educated assistance for these matters
in the forum search that I conducted here only hope someone can give me a
case specific fix. see error reports below, thanks

Product
Windows

Problem
Shut down unexpectedly

Date
2/24/2008 10:09 AM

Status
Report Sent

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033

Files that help describe the problem (some files may no longer be available)
Mini022408-01.dmp
sysdata.xml
Version.txt

Extra information about the problem
BCCode: 124
BCP1: 00000000
BCP2: 83108A60
BCP3: 00000000
BCP4: 00000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 768_1
Server information: 8c0093da-125c-42d6-9b0d-26aa065d818e



Product
Windows

Problem
Shut down unexpectedly

Date
2/24/2008 10:22 AM

Status
Report Sent

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033

Files that help describe the problem (some files may no longer be available)
Mini022408-03.dmp
sysdata.xml
Version.txt

Extra information about the problem
BCCode: 124
BCP1: 00000000
BCP2: 830DD028
BCP3: 00000000
BCP4: 00000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 768_1
Server information: 428eb43c-c2c4-4375-9d0a-b8cb5e8ede20


Product
Windows

Problem
Shut down unexpectedly

Date
2/24/2008 10:50 AM

Status
Report Sent

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033

Files that help describe the problem (some files may no longer be available)
Mini022408-04.dmp
sysdata.xml
Version.txt

Extra information about the problem
BCCode: 124
BCP1: 00000000
BCP2: 8325FB40
BCP3: 00000000
BCP4: 00000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 768_1
Server information: 1996a66d-2867-4882-9158-9a33bdc3909d


Product
Windows

Problem
Shut down unexpectedly

Date
2/24/2008 10:58 AM

Status
Report Sent

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033

Files that help describe the problem (some files may no longer be available)
Mini022408-05.dmp
sysdata.xml
Version.txt

Extra information about the problem
BCCode: 124
BCP1: 00000000
BCP2: 832FFD18
BCP3: 00000000
BCP4: 00000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 768_1
Server information: b806e066-a800-4c1b-937a-1269cec6c89d

Rightclick a Command Prompt icon on start, then 'run as administrator' Type
the command:

perfmon /rel

This may help diagnose your problems.

Also on start is /all programs/Maintenance/Problem Support and Solutions.

--
Was this helpful? Then click the "Yes" Ratings button. Voting helps the web
interface.
http://www.microsoft.com/wn3/locales....htm#RateAPost

Mark L. Ferguson

..
"Frustrated" <> wrote in message
news:573C857F-0134-4065-B467-...
> Operating on an emachine with vista home premium for the six months that
> we
> have had this machine we have been having these seemingly random and
> always
> unexpected bluescreen errors. I just recently started to look into it and
> have followed suggestions from the fine folks at Gateway to attempt full
> factory recovery and startup repair procedures to no avail. The following
> is
> the combined text from four (4) shutdowns over the course of 2 hours this
> morning, there does not appear to be any one software or application that
> triggers these events. Seems to be some educated assistance for these
> matters
> in the forum search that I conducted here only hope someone can give me a
> case specific fix. see error reports below, thanks
>
> Product
> Windows
>
> Problem
> Shut down unexpectedly
>
> Date
> 2/24/2008 10:09 AM
>
> Status
> Report Sent
>
> Problem signature
> Problem Event Name: BlueScreen
> OS Version: 6.0.6000.2.0.0.768.3
> Locale ID: 1033
>
> Files that help describe the problem (some files may no longer be
> available)
> Mini022408-01.dmp
> sysdata.xml
> Version.txt
>
> Extra information about the problem
> BCCode: 124
> BCP1: 00000000
> BCP2: 83108A60
> BCP3: 00000000
> BCP4: 00000000
> OS Version: 6_0_6000
> Service Pack: 0_0
> Product: 768_1
> Server information: 8c0093da-125c-42d6-9b0d-26aa065d818e
>
>
>
> Product
> Windows
>
> Problem
> Shut down unexpectedly
>
> Date
> 2/24/2008 10:22 AM
>
> Status
> Report Sent
>
> Problem signature
> Problem Event Name: BlueScreen
> OS Version: 6.0.6000.2.0.0.768.3
> Locale ID: 1033
>
> Files that help describe the problem (some files may no longer be
> available)
> Mini022408-03.dmp
> sysdata.xml
> Version.txt
>
> Extra information about the problem
> BCCode: 124
> BCP1: 00000000
> BCP2: 830DD028
> BCP3: 00000000
> BCP4: 00000000
> OS Version: 6_0_6000
> Service Pack: 0_0
> Product: 768_1
> Server information: 428eb43c-c2c4-4375-9d0a-b8cb5e8ede20
>
>
> Product
> Windows
>
> Problem
> Shut down unexpectedly
>
> Date
> 2/24/2008 10:50 AM
>
> Status
> Report Sent
>
> Problem signature
> Problem Event Name: BlueScreen
> OS Version: 6.0.6000.2.0.0.768.3
> Locale ID: 1033
>
> Files that help describe the problem (some files may no longer be
> available)
> Mini022408-04.dmp
> sysdata.xml
> Version.txt
>
> Extra information about the problem
> BCCode: 124
> BCP1: 00000000
> BCP2: 8325FB40
> BCP3: 00000000
> BCP4: 00000000
> OS Version: 6_0_6000
> Service Pack: 0_0
> Product: 768_1
> Server information: 1996a66d-2867-4882-9158-9a33bdc3909d
>
>
> Product
> Windows
>
> Problem
> Shut down unexpectedly
>
> Date
> 2/24/2008 10:58 AM
>
> Status
> Report Sent
>
> Problem signature
> Problem Event Name: BlueScreen
> OS Version: 6.0.6000.2.0.0.768.3
> Locale ID: 1033
>
> Files that help describe the problem (some files may no longer be
> available)
> Mini022408-05.dmp
> sysdata.xml
> Version.txt
>
> Extra information about the problem
> BCCode: 124
> BCP1: 00000000
> BCP2: 832FFD18
> BCP3: 00000000
> BCP4: 00000000
> OS Version: 6_0_6000
> Service Pack: 0_0
> Product: 768_1
> Server information: b806e066-a800-4c1b-937a-1269cec6c89d

Frustrated

The information you posted is from the Problem Reports and Solutions
component which is information and files that are sent to Microsoft to be
entered into their internal database. This information is fairly useless
unless a support person has access to that internal database.

What we can use here is some information from the blue screen. A blue screen
error is usually in the following format.

A number that that is included in any knowledgebase articles that may have
information on fixing this error.
Example: STOP: 0x0000007E

Following this number there should be a brief description of what component
the error occured in.
Example: IRQL_NOT_GREATER_OR_EQUAL

If you post these 2 bits of information it will go a long way in determining
what caused the error.

You can also look in the Event Viewer for any errors that occured at the
time the blue screen happened.

Open Control Panel/Administrative Tools/Event Viewer.

In the Event Viewer open Custom Views / Adminisdtrative Events. Look for any
error events with a 'red' icon that correspond to the date/time of the blue
screen. If you find any, double click the error message. At the bottom of
that dialog box, press the Copy Button. Paste the results back here in a
reply.

Example:

Log Name: Application
Source: Application Error
Date: 1/10/2008 12:54:52 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: xxx-PC
Description:
Faulting application WMIADAP.EXE, version 6.0.6000.16386, time stamp
0x4549af43, faulting module ntdll.dll, version 6.0.6000.16386, time stamp
0x4549bdc9, exception code 0xc0000043, fault offset 0x00008fc7, process id
0xc5c, application start time 0x01c853cb07287de7.
--

Ronnie Vernon
Microsoft MVP
Windows Desktop Experience


"Frustrated" <> wrote in message
news:573C857F-0134-4065-B467-...
> Operating on an emachine with vista home premium for the six months that
> we
> have had this machine we have been having these seemingly random and
> always
> unexpected bluescreen errors. I just recently started to look into it and
> have followed suggestions from the fine folks at Gateway to attempt full
> factory recovery and startup repair procedures to no avail. The following
> is
> the combined text from four (4) shutdowns over the course of 2 hours this
> morning, there does not appear to be any one software or application that
> triggers these events. Seems to be some educated assistance for these
> matters
> in the forum search that I conducted here only hope someone can give me a
> case specific fix. see error reports below, thanks
>
> Product
> Windows
>
> Problem
> Shut down unexpectedly
>
> Date
> 2/24/2008 10:09 AM
>
> Status
> Report Sent
>
> Problem signature
> Problem Event Name: BlueScreen
> OS Version: 6.0.6000.2.0.0.768.3
> Locale ID: 1033
>
> Files that help describe the problem (some files may no longer be
> available)
> Mini022408-01.dmp
> sysdata.xml
> Version.txt
>
> Extra information about the problem
> BCCode: 124
> BCP1: 00000000
> BCP2: 83108A60
> BCP3: 00000000
> BCP4: 00000000
> OS Version: 6_0_6000
> Service Pack: 0_0
> Product: 768_1
> Server information: 8c0093da-125c-42d6-9b0d-26aa065d818e
>
>
>
> Product
> Windows
>
> Problem
> Shut down unexpectedly
>
> Date
> 2/24/2008 10:22 AM
>
> Status
> Report Sent
>
> Problem signature
> Problem Event Name: BlueScreen
> OS Version: 6.0.6000.2.0.0.768.3
> Locale ID: 1033
>
> Files that help describe the problem (some files may no longer be
> available)
> Mini022408-03.dmp
> sysdata.xml
> Version.txt
>
> Extra information about the problem
> BCCode: 124
> BCP1: 00000000
> BCP2: 830DD028
> BCP3: 00000000
> BCP4: 00000000
> OS Version: 6_0_6000
> Service Pack: 0_0
> Product: 768_1
> Server information: 428eb43c-c2c4-4375-9d0a-b8cb5e8ede20
>
>
> Product
> Windows
>
> Problem
> Shut down unexpectedly
>
> Date
> 2/24/2008 10:50 AM
>
> Status
> Report Sent
>
> Problem signature
> Problem Event Name: BlueScreen
> OS Version: 6.0.6000.2.0.0.768.3
> Locale ID: 1033
>
> Files that help describe the problem (some files may no longer be
> available)
> Mini022408-04.dmp
> sysdata.xml
> Version.txt
>
> Extra information about the problem
> BCCode: 124
> BCP1: 00000000
> BCP2: 8325FB40
> BCP3: 00000000
> BCP4: 00000000
> OS Version: 6_0_6000
> Service Pack: 0_0
> Product: 768_1
> Server information: 1996a66d-2867-4882-9158-9a33bdc3909d
>
>
> Product
> Windows
>
> Problem
> Shut down unexpectedly
>
> Date
> 2/24/2008 10:58 AM
>
> Status
> Report Sent
>
> Problem signature
> Problem Event Name: BlueScreen
> OS Version: 6.0.6000.2.0.0.768.3
> Locale ID: 1033
>
> Files that help describe the problem (some files may no longer be
> available)
> Mini022408-05.dmp
> sysdata.xml
> Version.txt
>
> Extra information about the problem
> BCCode: 124
> BCP1: 00000000
> BCP2: 832FFD18
> BCP3: 00000000
> BCP4: 00000000
> OS Version: 6_0_6000
> Service Pack: 0_0
> Product: 768_1
> Server information: b806e066-a800-4c1b-937a-1269cec6c89d

This is the latest info I was able to get from the event viewer. Two (2)
shutdowns this AM and both appear to have the same info from the event log.
Please Help.

Log Name: Security
Source: Microsoft-Windows-Eventlog
Date: 3/2/2008 2:15:47 PM
Event ID: 1101
Task Category: Event processing
Level: Error
Keywords: Audit Success
User: N/A
Computer: Jeff-PC
Description:
Audit events have been dropped by the transport. The real time backup file
was corrupt due to improper shutdown.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Eventlog"
Guid="{fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}" />
<EventID>1101</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>101</Task>
<Opcode>0</Opcode>
<Keywords>0x4020000000000000</Keywords>
<TimeCreated SystemTime="2008-03-02T19:15:47.320Z" />
<EventRecordID>680</EventRecordID>
<Correlation />
<Execution ProcessID="928" ThreadID="1548" />
<Channel>Security</Channel>
<Computer>Jeff-PC</Computer>
<Security />
</System>
<UserData>
<AuditEventsDropped
xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events"

xmlns="http://manifests.microsoft.com/win/2004/08/windows/eventlog">
<Reason>34</Reason>
</AuditEventsDropped>
</UserData>
</Event>

Thanks,
Frustrated


"Ronnie Vernon MVP" wrote:

> Frustrated
>
> The information you posted is from the Problem Reports and Solutions
> component which is information and files that are sent to Microsoft to be
> entered into their internal database. This information is fairly useless
> unless a support person has access to that internal database.
>
> What we can use here is some information from the blue screen. A blue screen
> error is usually in the following format.
>
> A number that that is included in any knowledgebase articles that may have
> information on fixing this error.
> Example: STOP: 0x0000007E
>
> Following this number there should be a brief description of what component
> the error occured in.
> Example: IRQL_NOT_GREATER_OR_EQUAL
>
> If you post these 2 bits of information it will go a long way in determining
> what caused the error.
>
> You can also look in the Event Viewer for any errors that occured at the
> time the blue screen happened.
>
> Open Control Panel/Administrative Tools/Event Viewer.
>
> In the Event Viewer open Custom Views / Adminisdtrative Events. Look for any
> error events with a 'red' icon that correspond to the date/time of the blue
> screen. If you find any, double click the error message. At the bottom of
> that dialog box, press the Copy Button. Paste the results back here in a
> reply.
>
> Example:
>
> Log Name: Application
> Source: Application Error
> Date: 1/10/2008 12:54:52 PM
> Event ID: 1000
> Task Category: (100)
> Level: Error
> Keywords: Classic
> User: N/A
> Computer: xxx-PC
> Description:
> Faulting application WMIADAP.EXE, version 6.0.6000.16386, time stamp
> 0x4549af43, faulting module ntdll.dll, version 6.0.6000.16386, time stamp
> 0x4549bdc9, exception code 0xc0000043, fault offset 0x00008fc7, process id
> 0xc5c, application start time 0x01c853cb07287de7.
> --
>
> Ronnie Vernon
> Microsoft MVP
> Windows Desktop Experience
>
>
> "Frustrated" <> wrote in message
> news:573C857F-0134-4065-B467-...
> > Operating on an emachine with vista home premium for the six months that
> > we
> > have had this machine we have been having these seemingly random and
> > always
> > unexpected bluescreen errors. I just recently started to look into it and
> > have followed suggestions from the fine folks at Gateway to attempt full
> > factory recovery and startup repair procedures to no avail. The following
> > is
> > the combined text from four (4) shutdowns over the course of 2 hours this
> > morning, there does not appear to be any one software or application that
> > triggers these events. Seems to be some educated assistance for these
> > matters
> > in the forum search that I conducted here only hope someone can give me a
> > case specific fix. see error reports below, thanks
> >
> > Product
> > Windows
> >
> > Problem
> > Shut down unexpectedly
> >
> > Date
> > 2/24/2008 10:09 AM
> >
> > Status
> > Report Sent
> >
> > Problem signature
> > Problem Event Name: BlueScreen
> > OS Version: 6.0.6000.2.0.0.768.3
> > Locale ID: 1033
> >
> > Files that help describe the problem (some files may no longer be
> > available)
> > Mini022408-01.dmp
> > sysdata.xml
> > Version.txt
> >
> > Extra information about the problem
> > BCCode: 124
> > BCP1: 00000000
> > BCP2: 83108A60
> > BCP3: 00000000
> > BCP4: 00000000
> > OS Version: 6_0_6000
> > Service Pack: 0_0
> > Product: 768_1
> > Server information: 8c0093da-125c-42d6-9b0d-26aa065d818e
> >
> >
> >
> > Product
> > Windows
> >
> > Problem
> > Shut down unexpectedly
> >
> > Date
> > 2/24/2008 10:22 AM
> >
> > Status
> > Report Sent
> >
> > Problem signature
> > Problem Event Name: BlueScreen
> > OS Version: 6.0.6000.2.0.0.768.3
> > Locale ID: 1033
> >
> > Files that help describe the problem (some files may no longer be
> > available)
> > Mini022408-03.dmp
> > sysdata.xml
> > Version.txt
> >
> > Extra information about the problem
> > BCCode: 124
> > BCP1: 00000000
> > BCP2: 830DD028
> > BCP3: 00000000
> > BCP4: 00000000
> > OS Version: 6_0_6000
> > Service Pack: 0_0
> > Product: 768_1
> > Server information: 428eb43c-c2c4-4375-9d0a-b8cb5e8ede20
> >
> >
> > Product
> > Windows
> >
> > Problem
> > Shut down unexpectedly
> >
> > Date
> > 2/24/2008 10:50 AM
> >
> > Status
> > Report Sent
> >
> > Problem signature
> > Problem Event Name: BlueScreen
> > OS Version: 6.0.6000.2.0.0.768.3
> > Locale ID: 1033
> >
> > Files that help describe the problem (some files may no longer be
> > available)
> > Mini022408-04.dmp
> > sysdata.xml
> > Version.txt
> >
> > Extra information about the problem
> > BCCode: 124
> > BCP1: 00000000
> > BCP2: 8325FB40
> > BCP3: 00000000
> > BCP4: 00000000
> > OS Version: 6_0_6000
> > Service Pack: 0_0
> > Product: 768_1
> > Server information: 1996a66d-2867-4882-9158-9a33bdc3909d
> >
> >
> > Product
> > Windows
> >
> > Problem
> > Shut down unexpectedly
> >
> > Date
> > 2/24/2008 10:58 AM
> >
> > Status
> > Report Sent
> >
> > Problem signature
> > Problem Event Name: BlueScreen
> > OS Version: 6.0.6000.2.0.0.768.3
> > Locale ID: 1033
> >
> > Files that help describe the problem (some files may no longer be
> > available)
> > Mini022408-05.dmp
> > sysdata.xml
> > Version.txt
> >
> > Extra information about the problem
> > BCCode: 124
> > BCP1: 00000000
> > BCP2: 832FFD18
> > BCP3: 00000000
> > BCP4: 00000000
> > OS Version: 6_0_6000
> > Service Pack: 0_0
> > Product: 768_1
> > Server information: b806e066-a800-4c1b-937a-1269cec6c89d
>

Frustrated

That event is a result of the blue screen shutdown, not the cause. Can you
post the information I requested from the blue screen?

--

Ronnie Vernon
Microsoft MVP
Windows Desktop Experience


"Frustrated" <> wrote in message
news:3D0D9433-A7FE-4B84-8EAF-...
> This is the latest info I was able to get from the event viewer. Two (2)
> shutdowns this AM and both appear to have the same info from the event
> log.
> Please Help.
>
> Log Name: Security
> Source: Microsoft-Windows-Eventlog
> Date: 3/2/2008 2:15:47 PM
> Event ID: 1101
> Task Category: Event processing
> Level: Error
> Keywords: Audit Success
> User: N/A
> Computer: Jeff-PC
> Description:
> Audit events have been dropped by the transport. The real time backup
> file
> was corrupt due to improper shutdown.
> Event Xml:
> <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> <System>
> <Provider Name="Microsoft-Windows-Eventlog"
> Guid="{fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}" />
> <EventID>1101</EventID>
> <Version>0</Version>
> <Level>2</Level>
> <Task>101</Task>
> <Opcode>0</Opcode>
> <Keywords>0x4020000000000000</Keywords>
> <TimeCreated SystemTime="2008-03-02T19:15:47.320Z" />
> <EventRecordID>680</EventRecordID>
> <Correlation />
> <Execution ProcessID="928" ThreadID="1548" />
> <Channel>Security</Channel>
> <Computer>Jeff-PC</Computer>
> <Security />
> </System>
> <UserData>
> <AuditEventsDropped
> xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events"
>
> xmlns="http://manifests.microsoft.com/win/2004/08/windows/eventlog">
> <Reason>34</Reason>
> </AuditEventsDropped>
> </UserData>
> </Event>
>
> Thanks,
> Frustrated
>
>
> "Ronnie Vernon MVP" wrote:
>
>> Frustrated
>>
>> The information you posted is from the Problem Reports and Solutions
>> component which is information and files that are sent to Microsoft to be
>> entered into their internal database. This information is fairly useless
>> unless a support person has access to that internal database.
>>
>> What we can use here is some information from the blue screen. A blue
>> screen
>> error is usually in the following format.
>>
>> A number that that is included in any knowledgebase articles that may
>> have
>> information on fixing this error.
>> Example: STOP: 0x0000007E
>>
>> Following this number there should be a brief description of what
>> component
>> the error occured in.
>> Example: IRQL_NOT_GREATER_OR_EQUAL
>>
>> If you post these 2 bits of information it will go a long way in
>> determining
>> what caused the error.
>>
>> You can also look in the Event Viewer for any errors that occured at the
>> time the blue screen happened.
>>
>> Open Control Panel/Administrative Tools/Event Viewer.
>>
>> In the Event Viewer open Custom Views / Adminisdtrative Events. Look for
>> any
>> error events with a 'red' icon that correspond to the date/time of the
>> blue
>> screen. If you find any, double click the error message. At the bottom of
>> that dialog box, press the Copy Button. Paste the results back here in a
>> reply.
>>
>> Example:
>>
>> Log Name: Application
>> Source: Application Error
>> Date: 1/10/2008 12:54:52 PM
>> Event ID: 1000
>> Task Category: (100)
>> Level: Error
>> Keywords: Classic
>> User: N/A
>> Computer: xxx-PC
>> Description:
>> Faulting application WMIADAP.EXE, version 6.0.6000.16386, time stamp
>> 0x4549af43, faulting module ntdll.dll, version 6.0.6000.16386, time stamp
>> 0x4549bdc9, exception code 0xc0000043, fault offset 0x00008fc7, process
>> id
>> 0xc5c, application start time 0x01c853cb07287de7.
>> --
>>
>> Ronnie Vernon
>> Microsoft MVP
>> Windows Desktop Experience
>>
>>
>> "Frustrated" <> wrote in message
>> news:573C857F-0134-4065-B467-...
>> > Operating on an emachine with vista home premium for the six months
>> > that
>> > we
>> > have had this machine we have been having these seemingly random and
>> > always
>> > unexpected bluescreen errors. I just recently started to look into it
>> > and
>> > have followed suggestions from the fine folks at Gateway to attempt
>> > full
>> > factory recovery and startup repair procedures to no avail. The
>> > following
>> > is
>> > the combined text from four (4) shutdowns over the course of 2 hours
>> > this
>> > morning, there does not appear to be any one software or application
>> > that
>> > triggers these events. Seems to be some educated assistance for these
>> > matters
>> > in the forum search that I conducted here only hope someone can give me
>> > a
>> > case specific fix. see error reports below, thanks
>> >
>> > Product
>> > Windows
>> >
>> > Problem
>> > Shut down unexpectedly
>> >
>> > Date
>> > 2/24/2008 10:09 AM
>> >
>> > Status
>> > Report Sent
>> >
>> > Problem signature
>> > Problem Event Name: BlueScreen
>> > OS Version: 6.0.6000.2.0.0.768.3
>> > Locale ID: 1033
>> >
>> > Files that help describe the problem (some files may no longer be
>> > available)
>> > Mini022408-01.dmp
>> > sysdata.xml
>> > Version.txt
>> >
>> > Extra information about the problem
>> > BCCode: 124
>> > BCP1: 00000000
>> > BCP2: 83108A60
>> > BCP3: 00000000
>> > BCP4: 00000000
>> > OS Version: 6_0_6000
>> > Service Pack: 0_0
>> > Product: 768_1
>> > Server information: 8c0093da-125c-42d6-9b0d-26aa065d818e
>> >
>> >
>> >
>> > Product
>> > Windows
>> >
>> > Problem
>> > Shut down unexpectedly
>> >
>> > Date
>> > 2/24/2008 10:22 AM
>> >
>> > Status
>> > Report Sent
>> >
>> > Problem signature
>> > Problem Event Name: BlueScreen
>> > OS Version: 6.0.6000.2.0.0.768.3
>> > Locale ID: 1033
>> >
>> > Files that help describe the problem (some files may no longer be
>> > available)
>> > Mini022408-03.dmp
>> > sysdata.xml
>> > Version.txt
>> >
>> > Extra information about the problem
>> > BCCode: 124
>> > BCP1: 00000000
>> > BCP2: 830DD028
>> > BCP3: 00000000
>> > BCP4: 00000000
>> > OS Version: 6_0_6000
>> > Service Pack: 0_0
>> > Product: 768_1
>> > Server information: 428eb43c-c2c4-4375-9d0a-b8cb5e8ede20
>> >
>> >
>> > Product
>> > Windows
>> >
>> > Problem
>> > Shut down unexpectedly
>> >
>> > Date
>> > 2/24/2008 10:50 AM
>> >
>> > Status
>> > Report Sent
>> >
>> > Problem signature
>> > Problem Event Name: BlueScreen
>> > OS Version: 6.0.6000.2.0.0.768.3
>> > Locale ID: 1033
>> >
>> > Files that help describe the problem (some files may no longer be
>> > available)
>> > Mini022408-04.dmp
>> > sysdata.xml
>> > Version.txt
>> >
>> > Extra information about the problem
>> > BCCode: 124
>> > BCP1: 00000000
>> > BCP2: 8325FB40
>> > BCP3: 00000000
>> > BCP4: 00000000
>> > OS Version: 6_0_6000
>> > Service Pack: 0_0
>> > Product: 768_1
>> > Server information: 1996a66d-2867-4882-9158-9a33bdc3909d
>> >
>> >
>> > Product
>> > Windows
>> >
>> > Problem
>> > Shut down unexpectedly
>> >
>> > Date
>> > 2/24/2008 10:58 AM
>> >
>> > Status
>> > Report Sent
>> >
>> > Problem signature
>> > Problem Event Name: BlueScreen
>> > OS Version: 6.0.6000.2.0.0.768.3
>> > Locale ID: 1033
>> >
>> > Files that help describe the problem (some files may no longer be
>> > available)
>> > Mini022408-05.dmp
>> > sysdata.xml
>> > Version.txt
>> >
>> > Extra information about the problem
>> > BCCode: 124
>> > BCP1: 00000000
>> > BCP2: 832FFD18
>> > BCP3: 00000000
>> > BCP4: 00000000
>> > OS Version: 6_0_6000
>> > Service Pack: 0_0
>> > Product: 768_1
>> > Server information: b806e066-a800-4c1b-937a-1269cec6c89d
>>

The Bluescreen flashes so quickly that I am unable to view any details. It is
also so unpredictable that I cannot intentionally force it to happen, in
order to photograph it

"Ronnie Vernon MVP" wrote:

> Frustrated
>
> That event is a result of the blue screen shutdown, not the cause. Can you
> post the information I requested from the blue screen?
>
> --
>
> Ronnie Vernon
> Microsoft MVP
> Windows Desktop Experience
>
>
> "Frustrated" <> wrote in message
> news:3D0D9433-A7FE-4B84-8EAF-...
> > This is the latest info I was able to get from the event viewer. Two (2)
> > shutdowns this AM and both appear to have the same info from the event
> > log.
> > Please Help.
> >
> > Log Name: Security
> > Source: Microsoft-Windows-Eventlog
> > Date: 3/2/2008 2:15:47 PM
> > Event ID: 1101
> > Task Category: Event processing
> > Level: Error
> > Keywords: Audit Success
> > User: N/A
> > Computer: Jeff-PC
> > Description:
> > Audit events have been dropped by the transport. The real time backup
> > file
> > was corrupt due to improper shutdown.
> > Event Xml:
> > <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> > <System>
> > <Provider Name="Microsoft-Windows-Eventlog"
> > Guid="{fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}" />
> > <EventID>1101</EventID>
> > <Version>0</Version>
> > <Level>2</Level>
> > <Task>101</Task>
> > <Opcode>0</Opcode>
> > <Keywords>0x4020000000000000</Keywords>
> > <TimeCreated SystemTime="2008-03-02T19:15:47.320Z" />
> > <EventRecordID>680</EventRecordID>
> > <Correlation />
> > <Execution ProcessID="928" ThreadID="1548" />
> > <Channel>Security</Channel>
> > <Computer>Jeff-PC</Computer>
> > <Security />
> > </System>
> > <UserData>
> > <AuditEventsDropped
> > xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events"
> >
> > xmlns="http://manifests.microsoft.com/win/2004/08/windows/eventlog">
> > <Reason>34</Reason>
> > </AuditEventsDropped>
> > </UserData>
> > </Event>
> >
> > Thanks,
> > Frustrated
> >
> >
> > "Ronnie Vernon MVP" wrote:
> >
> >> Frustrated
> >>
> >> The information you posted is from the Problem Reports and Solutions
> >> component which is information and files that are sent to Microsoft to be
> >> entered into their internal database. This information is fairly useless
> >> unless a support person has access to that internal database.
> >>
> >> What we can use here is some information from the blue screen. A blue
> >> screen
> >> error is usually in the following format.
> >>
> >> A number that that is included in any knowledgebase articles that may
> >> have
> >> information on fixing this error.
> >> Example: STOP: 0x0000007E
> >>
> >> Following this number there should be a brief description of what
> >> component
> >> the error occured in.
> >> Example: IRQL_NOT_GREATER_OR_EQUAL
> >>
> >> If you post these 2 bits of information it will go a long way in
> >> determining
> >> what caused the error.
> >>
> >> You can also look in the Event Viewer for any errors that occured at the
> >> time the blue screen happened.
> >>
> >> Open Control Panel/Administrative Tools/Event Viewer.
> >>
> >> In the Event Viewer open Custom Views / Adminisdtrative Events. Look for
> >> any
> >> error events with a 'red' icon that correspond to the date/time of the
> >> blue
> >> screen. If you find any, double click the error message. At the bottom of
> >> that dialog box, press the Copy Button. Paste the results back here in a
> >> reply.
> >>
> >> Example:
> >>
> >> Log Name: Application
> >> Source: Application Error
> >> Date: 1/10/2008 12:54:52 PM
> >> Event ID: 1000
> >> Task Category: (100)
> >> Level: Error
> >> Keywords: Classic
> >> User: N/A
> >> Computer: xxx-PC
> >> Description:
> >> Faulting application WMIADAP.EXE, version 6.0.6000.16386, time stamp
> >> 0x4549af43, faulting module ntdll.dll, version 6.0.6000.16386, time stamp
> >> 0x4549bdc9, exception code 0xc0000043, fault offset 0x00008fc7, process
> >> id
> >> 0xc5c, application start time 0x01c853cb07287de7.
> >> --
> >>
> >> Ronnie Vernon
> >> Microsoft MVP
> >> Windows Desktop Experience
> >>
> >>
> >> "Frustrated" <> wrote in message
> >> news:573C857F-0134-4065-B467-...
> >> > Operating on an emachine with vista home premium for the six months
> >> > that
> >> > we
> >> > have had this machine we have been having these seemingly random and
> >> > always
> >> > unexpected bluescreen errors. I just recently started to look into it
> >> > and
> >> > have followed suggestions from the fine folks at Gateway to attempt
> >> > full
> >> > factory recovery and startup repair procedures to no avail. The
> >> > following
> >> > is
> >> > the combined text from four (4) shutdowns over the course of 2 hours
> >> > this
> >> > morning, there does not appear to be any one software or application
> >> > that
> >> > triggers these events. Seems to be some educated assistance for these
> >> > matters
> >> > in the forum search that I conducted here only hope someone can give me
> >> > a
> >> > case specific fix. see error reports below, thanks
> >> >
> >> > Product
> >> > Windows
> >> >
> >> > Problem
> >> > Shut down unexpectedly
> >> >
> >> > Date
> >> > 2/24/2008 10:09 AM
> >> >
> >> > Status
> >> > Report Sent
> >> >
> >> > Problem signature
> >> > Problem Event Name: BlueScreen
> >> > OS Version: 6.0.6000.2.0.0.768.3
> >> > Locale ID: 1033
> >> >
> >> > Files that help describe the problem (some files may no longer be
> >> > available)
> >> > Mini022408-01.dmp
> >> > sysdata.xml
> >> > Version.txt
> >> >
> >> > Extra information about the problem
> >> > BCCode: 124
> >> > BCP1: 00000000
> >> > BCP2: 83108A60
> >> > BCP3: 00000000
> >> > BCP4: 00000000
> >> > OS Version: 6_0_6000
> >> > Service Pack: 0_0
> >> > Product: 768_1
> >> > Server information: 8c0093da-125c-42d6-9b0d-26aa065d818e
> >> >
> >> >
> >> >
> >> > Product
> >> > Windows
> >> >
> >> > Problem
> >> > Shut down unexpectedly
> >> >
> >> > Date
> >> > 2/24/2008 10:22 AM
> >> >
> >> > Status
> >> > Report Sent
> >> >
> >> > Problem signature
> >> > Problem Event Name: BlueScreen
> >> > OS Version: 6.0.6000.2.0.0.768.3
> >> > Locale ID: 1033
> >> >
> >> > Files that help describe the problem (some files may no longer be
> >> > available)
> >> > Mini022408-03.dmp
> >> > sysdata.xml
> >> > Version.txt
> >> >
> >> > Extra information about the problem
> >> > BCCode: 124
> >> > BCP1: 00000000
> >> > BCP2: 830DD028
> >> > BCP3: 00000000
> >> > BCP4: 00000000
> >> > OS Version: 6_0_6000
> >> > Service Pack: 0_0
> >> > Product: 768_1
> >> > Server information: 428eb43c-c2c4-4375-9d0a-b8cb5e8ede20
> >> >
> >> >
> >> > Product
> >> > Windows
> >> >
> >> > Problem
> >> > Shut down unexpectedly
> >> >
> >> > Date
> >> > 2/24/2008 10:50 AM
> >> >
> >> > Status
> >> > Report Sent
> >> >
> >> > Problem signature
> >> > Problem Event Name: BlueScreen
> >> > OS Version: 6.0.6000.2.0.0.768.3
> >> > Locale ID: 1033
> >> >
> >> > Files that help describe the problem (some files may no longer be
> >> > available)
> >> > Mini022408-04.dmp
> >> > sysdata.xml
> >> > Version.txt
> >> >
> >> > Extra information about the problem
> >> > BCCode: 124
> >> > BCP1: 00000000
> >> > BCP2: 8325FB40
> >> > BCP3: 00000000
> >> > BCP4: 00000000
> >> > OS Version: 6_0_6000
> >> > Service Pack: 0_0
> >> > Product: 768_1
> >> > Server information: 1996a66d-2867-4882-9158-9a33bdc3909d
> >> >
> >> >
> >> > Product
> >> > Windows
> >> >
> >> > Problem
> >> > Shut down unexpectedly
> >> >
> >> > Date
> >> > 2/24/2008 10:58 AM
> >> >
> >> > Status
> >> > Report Sent
> >> >
> >> > Problem signature
> >> > Problem Event Name: BlueScreen
> >> > OS Version: 6.0.6000.2.0.0.768.3
> >> > Locale ID: 1033
> >> >
> >> > Files that help describe the problem (some files may no longer be
> >> > available)
> >> > Mini022408-05.dmp
> >> > sysdata.xml
> >> > Version.txt
> >> >
> >> > Extra information about the problem
> >> > BCCode: 124
> >> > BCP1: 00000000
> >> > BCP2: 832FFD18
> >> > BCP3: 00000000
> >> > BCP4: 00000000
> >> > OS Version: 6_0_6000
> >> > Service Pack: 0_0
> >> > Product: 768_1
> >> > Server information: b806e066-a800-4c1b-937a-1269cec6c89d
> >>
>

Frustrated

Open Control Panel, click Classic View in the left side menu. Open System
and select Advanced System Settings in the left side menu.

In Start Up and Recovery, click the Settings Button. In the System Failure
section, remove the check mark from Automatically Restart. This will leave
the blue screen up long enough to write down the pertinent details.

--

Ronnie Vernon
Microsoft MVP
Windows Desktop Experience


"Frustrated" <> wrote in message
news:437F0B74-F1CB-47C2-8621-...
> The Bluescreen flashes so quickly that I am unable to view any details. It
> is
> also so unpredictable that I cannot intentionally force it to happen, in
> order to photograph it
>
> "Ronnie Vernon MVP" wrote:
>
>> Frustrated
>>
>> That event is a result of the blue screen shutdown, not the cause. Can
>> you
>> post the information I requested from the blue screen?
>>
>> --
>>
>> Ronnie Vernon
>> Microsoft MVP
>> Windows Desktop Experience
>>
>>
>> "Frustrated" <> wrote in message
>> news:3D0D9433-A7FE-4B84-8EAF-...
>> > This is the latest info I was able to get from the event viewer. Two
>> > (2)
>> > shutdowns this AM and both appear to have the same info from the event
>> > log.
>> > Please Help.
>> >
>> > Log Name: Security
>> > Source: Microsoft-Windows-Eventlog
>> > Date: 3/2/2008 2:15:47 PM
>> > Event ID: 1101
>> > Task Category: Event processing
>> > Level: Error
>> > Keywords: Audit Success
>> > User: N/A
>> > Computer: Jeff-PC
>> > Description:
>> > Audit events have been dropped by the transport. The real time backup
>> > file
>> > was corrupt due to improper shutdown.
>> > Event Xml:
>> > <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
>> > <System>
>> > <Provider Name="Microsoft-Windows-Eventlog"
>> > Guid="{fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}" />
>> > <EventID>1101</EventID>
>> > <Version>0</Version>
>> > <Level>2</Level>
>> > <Task>101</Task>
>> > <Opcode>0</Opcode>
>> > <Keywords>0x4020000000000000</Keywords>
>> > <TimeCreated SystemTime="2008-03-02T19:15:47.320Z" />
>> > <EventRecordID>680</EventRecordID>
>> > <Correlation />
>> > <Execution ProcessID="928" ThreadID="1548" />
>> > <Channel>Security</Channel>
>> > <Computer>Jeff-PC</Computer>
>> > <Security />
>> > </System>
>> > <UserData>
>> > <AuditEventsDropped
>> > xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events"
>> >
>> > xmlns="http://manifests.microsoft.com/win/2004/08/windows/eventlog">
>> > <Reason>34</Reason>
>> > </AuditEventsDropped>
>> > </UserData>
>> > </Event>
>> >
>> > Thanks,
>> > Frustrated
>> >
>> >
>> > "Ronnie Vernon MVP" wrote:
>> >
>> >> Frustrated
>> >>
>> >> The information you posted is from the Problem Reports and Solutions
>> >> component which is information and files that are sent to Microsoft to
>> >> be
>> >> entered into their internal database. This information is fairly
>> >> useless
>> >> unless a support person has access to that internal database.
>> >>
>> >> What we can use here is some information from the blue screen. A blue
>> >> screen
>> >> error is usually in the following format.
>> >>
>> >> A number that that is included in any knowledgebase articles that may
>> >> have
>> >> information on fixing this error.
>> >> Example: STOP: 0x0000007E
>> >>
>> >> Following this number there should be a brief description of what
>> >> component
>> >> the error occured in.
>> >> Example: IRQL_NOT_GREATER_OR_EQUAL
>> >>
>> >> If you post these 2 bits of information it will go a long way in
>> >> determining
>> >> what caused the error.
>> >>
>> >> You can also look in the Event Viewer for any errors that occured at
>> >> the
>> >> time the blue screen happened.
>> >>
>> >> Open Control Panel/Administrative Tools/Event Viewer.
>> >>
>> >> In the Event Viewer open Custom Views / Adminisdtrative Events. Look
>> >> for
>> >> any
>> >> error events with a 'red' icon that correspond to the date/time of the
>> >> blue
>> >> screen. If you find any, double click the error message. At the bottom
>> >> of
>> >> that dialog box, press the Copy Button. Paste the results back here in
>> >> a
>> >> reply.
>> >>
>> >> Example:
>> >>
>> >> Log Name: Application
>> >> Source: Application Error
>> >> Date: 1/10/2008 12:54:52 PM
>> >> Event ID: 1000
>> >> Task Category: (100)
>> >> Level: Error
>> >> Keywords: Classic
>> >> User: N/A
>> >> Computer: xxx-PC
>> >> Description:
>> >> Faulting application WMIADAP.EXE, version 6.0.6000.16386, time stamp
>> >> 0x4549af43, faulting module ntdll.dll, version 6.0.6000.16386, time
>> >> stamp
>> >> 0x4549bdc9, exception code 0xc0000043, fault offset 0x00008fc7,
>> >> process
>> >> id
>> >> 0xc5c, application start time 0x01c853cb07287de7.
>> >> --
>> >>
>> >> Ronnie Vernon
>> >> Microsoft MVP
>> >> Windows Desktop Experience
>> >>
>> >>
>> >> "Frustrated" <> wrote in message
>> >> news:573C857F-0134-4065-B467-...
>> >> > Operating on an emachine with vista home premium for the six months
>> >> > that
>> >> > we
>> >> > have had this machine we have been having these seemingly random and
>> >> > always
>> >> > unexpected bluescreen errors. I just recently started to look into
>> >> > it
>> >> > and
>> >> > have followed suggestions from the fine folks at Gateway to attempt
>> >> > full
>> >> > factory recovery and startup repair procedures to no avail. The
>> >> > following
>> >> > is
>> >> > the combined text from four (4) shutdowns over the course of 2 hours
>> >> > this
>> >> > morning, there does not appear to be any one software or application
>> >> > that
>> >> > triggers these events. Seems to be some educated assistance for
>> >> > these
>> >> > matters
>> >> > in the forum search that I conducted here only hope someone can give
>> >> > me
>> >> > a
>> >> > case specific fix. see error reports below, thanks
>> >> >
>> >> > Product
>> >> > Windows
>> >> >
>> >> > Problem
>> >> > Shut down unexpectedly
>> >> >
>> >> > Date
>> >> > 2/24/2008 10:09 AM
>> >> >
>> >> > Status
>> >> > Report Sent
>> >> >
>> >> > Problem signature
>> >> > Problem Event Name: BlueScreen
>> >> > OS Version: 6.0.6000.2.0.0.768.3
>> >> > Locale ID: 1033
>> >> >
>> >> > Files that help describe the problem (some files may no longer be
>> >> > available)
>> >> > Mini022408-01.dmp
>> >> > sysdata.xml
>> >> > Version.txt
>> >> >
>> >> > Extra information about the problem
>> >> > BCCode: 124
>> >> > BCP1: 00000000
>> >> > BCP2: 83108A60
>> >> > BCP3: 00000000
>> >> > BCP4: 00000000
>> >> > OS Version: 6_0_6000
>> >> > Service Pack: 0_0
>> >> > Product: 768_1
>> >> > Server information: 8c0093da-125c-42d6-9b0d-26aa065d818e
>> >> >
>> >> >
>> >> >
>> >> > Product
>> >> > Windows
>> >> >
>> >> > Problem
>> >> > Shut down unexpectedly
>> >> >
>> >> > Date
>> >> > 2/24/2008 10:22 AM
>> >> >
>> >> > Status
>> >> > Report Sent
>> >> >
>> >> > Problem signature
>> >> > Problem Event Name: BlueScreen
>> >> > OS Version: 6.0.6000.2.0.0.768.3
>> >> > Locale ID: 1033
>> >> >
>> >> > Files that help describe the problem (some files may no longer be
>> >> > available)
>> >> > Mini022408-03.dmp
>> >> > sysdata.xml
>> >> > Version.txt
>> >> >
>> >> > Extra information about the problem
>> >> > BCCode: 124
>> >> > BCP1: 00000000
>> >> > BCP2: 830DD028
>> >> > BCP3: 00000000
>> >> > BCP4: 00000000
>> >> > OS Version: 6_0_6000
>> >> > Service Pack: 0_0
>> >> > Product: 768_1
>> >> > Server information: 428eb43c-c2c4-4375-9d0a-b8cb5e8ede20
>> >> >
>> >> >
>> >> > Product
>> >> > Windows
>> >> >
>> >> > Problem
>> >> > Shut down unexpectedly
>> >> >
>> >> > Date
>> >> > 2/24/2008 10:50 AM
>> >> >
>> >> > Status
>> >> > Report Sent
>> >> >
>> >> > Problem signature
>> >> > Problem Event Name: BlueScreen
>> >> > OS Version: 6.0.6000.2.0.0.768.3
>> >> > Locale ID: 1033
>> >> >
>> >> > Files that help describe the problem (some files may no longer be
>> >> > available)
>> >> > Mini022408-04.dmp
>> >> > sysdata.xml
>> >> > Version.txt
>> >> >
>> >> > Extra information about the problem
>> >> > BCCode: 124
>> >> > BCP1: 00000000
>> >> > BCP2: 8325FB40
>> >> > BCP3: 00000000
>> >> > BCP4: 00000000
>> >> > OS Version: 6_0_6000
>> >> > Service Pack: 0_0
>> >> > Product: 768_1
>> >> > Server information: 1996a66d-2867-4882-9158-9a33bdc3909d
>> >> >
>> >> >
>> >> > Product
>> >> > Windows
>> >> >
>> >> > Problem
>> >> > Shut down unexpectedly
>> >> >
>> >> > Date
>> >> > 2/24/2008 10:58 AM
>> >> >
>> >> > Status
>> >> > Report Sent
>> >> >
>> >> > Problem signature
>> >> > Problem Event Name: BlueScreen
>> >> > OS Version: 6.0.6000.2.0.0.768.3
>> >> > Locale ID: 1033
>> >> >
>> >> > Files that help describe the problem (some files may no longer be
>> >> > available)
>> >> > Mini022408-05.dmp
>> >> > sysdata.xml
>> >> > Version.txt
>> >> >
>> >> > Extra information about the problem
>> >> > BCCode: 124
>> >> > BCP1: 00000000
>> >> > BCP2: 832FFD18
>> >> > BCP3: 00000000
>> >> > BCP4: 00000000
>> >> > OS Version: 6_0_6000
>> >> > Service Pack: 0_0
>> >> > Product: 768_1
>> >> > Server information: b806e066-a800-4c1b-937a-1269cec6c89d
>> >>
>>

I have also incountered this problem. It seems to go in spurts of when it
happens. One morning it happened a 1/2 a dozen times. It occured twice last
week and once again this morning. Like Frustrated, the blue screen is up so
little time I cannot get any information down. I have changed my settings so
it does not automatically restart and I will hope (I guess) for it to happen
again so that I can write down the information. I'm just glad to know I'm
not the only one having problems.
I will post the information from my blue screen whenever it happens again.

"Ronnie Vernon MVP" wrote:

> Frustrated
>
> Open Control Panel, click Classic View in the left side menu. Open System
> and select Advanced System Settings in the left side menu.
>
> In Start Up and Recovery, click the Settings Button. In the System Failure
> section, remove the check mark from Automatically Restart. This will leave
> the blue screen up long enough to write down the pertinent details.
>
> --
>
> Ronnie Vernon
> Microsoft MVP
> Windows Desktop Experience
>
>
> "Frustrated" <> wrote in message
> news:437F0B74-F1CB-47C2-8621-...
> > The Bluescreen flashes so quickly that I am unable to view any details. It
> > is
> > also so unpredictable that I cannot intentionally force it to happen, in
> > order to photograph it
> >
> > "Ronnie Vernon MVP" wrote:
> >
> >> Frustrated
> >>
> >> That event is a result of the blue screen shutdown, not the cause. Can
> >> you
> >> post the information I requested from the blue screen?
> >>
> >> --
> >>
> >> Ronnie Vernon
> >> Microsoft MVP
> >> Windows Desktop Experience
> >>
> >>
> >> "Frustrated" <> wrote in message
> >> news:3D0D9433-A7FE-4B84-8EAF-...
> >> > This is the latest info I was able to get from the event viewer. Two
> >> > (2)
> >> > shutdowns this AM and both appear to have the same info from the event
> >> > log.
> >> > Please Help.
> >> >
> >> > Log Name: Security
> >> > Source: Microsoft-Windows-Eventlog
> >> > Date: 3/2/2008 2:15:47 PM
> >> > Event ID: 1101
> >> > Task Category: Event processing
> >> > Level: Error
> >> > Keywords: Audit Success
> >> > User: N/A
> >> > Computer: Jeff-PC
> >> > Description:
> >> > Audit events have been dropped by the transport. The real time backup
> >> > file
> >> > was corrupt due to improper shutdown.
> >> > Event Xml:
> >> > <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> >> > <System>
> >> > <Provider Name="Microsoft-Windows-Eventlog"
> >> > Guid="{fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}" />
> >> > <EventID>1101</EventID>
> >> > <Version>0</Version>
> >> > <Level>2</Level>
> >> > <Task>101</Task>
> >> > <Opcode>0</Opcode>
> >> > <Keywords>0x4020000000000000</Keywords>
> >> > <TimeCreated SystemTime="2008-03-02T19:15:47.320Z" />
> >> > <EventRecordID>680</EventRecordID>
> >> > <Correlation />
> >> > <Execution ProcessID="928" ThreadID="1548" />
> >> > <Channel>Security</Channel>
> >> > <Computer>Jeff-PC</Computer>
> >> > <Security />
> >> > </System>
> >> > <UserData>
> >> > <AuditEventsDropped
> >> > xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events"
> >> >
> >> > xmlns="http://manifests.microsoft.com/win/2004/08/windows/eventlog">
> >> > <Reason>34</Reason>
> >> > </AuditEventsDropped>
> >> > </UserData>
> >> > </Event>
> >> >
> >> > Thanks,
> >> > Frustrated
> >> >
> >> >
> >> > "Ronnie Vernon MVP" wrote:
> >> >
> >> >> Frustrated
> >> >>
> >> >> The information you posted is from the Problem Reports and Solutions
> >> >> component which is information and files that are sent to Microsoft to
> >> >> be
> >> >> entered into their internal database. This information is fairly
> >> >> useless
> >> >> unless a support person has access to that internal database.
> >> >>
> >> >> What we can use here is some information from the blue screen. A blue
> >> >> screen
> >> >> error is usually in the following format.
> >> >>
> >> >> A number that that is included in any knowledgebase articles that may
> >> >> have
> >> >> information on fixing this error.
> >> >> Example: STOP: 0x0000007E
> >> >>
> >> >> Following this number there should be a brief description of what
> >> >> component
> >> >> the error occured in.
> >> >> Example: IRQL_NOT_GREATER_OR_EQUAL
> >> >>
> >> >> If you post these 2 bits of information it will go a long way in
> >> >> determining
> >> >> what caused the error.
> >> >>
> >> >> You can also look in the Event Viewer for any errors that occured at
> >> >> the
> >> >> time the blue screen happened.
> >> >>
> >> >> Open Control Panel/Administrative Tools/Event Viewer.
> >> >>
> >> >> In the Event Viewer open Custom Views / Adminisdtrative Events. Look
> >> >> for
> >> >> any
> >> >> error events with a 'red' icon that correspond to the date/time of the
> >> >> blue
> >> >> screen. If you find any, double click the error message. At the bottom
> >> >> of
> >> >> that dialog box, press the Copy Button. Paste the results back here in
> >> >> a
> >> >> reply.
> >> >>
> >> >> Example:
> >> >>
> >> >> Log Name: Application
> >> >> Source: Application Error
> >> >> Date: 1/10/2008 12:54:52 PM
> >> >> Event ID: 1000
> >> >> Task Category: (100)
> >> >> Level: Error
> >> >> Keywords: Classic
> >> >> User: N/A
> >> >> Computer: xxx-PC
> >> >> Description:
> >> >> Faulting application WMIADAP.EXE, version 6.0.6000.16386, time stamp
> >> >> 0x4549af43, faulting module ntdll.dll, version 6.0.6000.16386, time
> >> >> stamp
> >> >> 0x4549bdc9, exception code 0xc0000043, fault offset 0x00008fc7,
> >> >> process
> >> >> id
> >> >> 0xc5c, application start time 0x01c853cb07287de7.
> >> >> --
> >> >>
> >> >> Ronnie Vernon
> >> >> Microsoft MVP
> >> >> Windows Desktop Experience
> >> >>
> >> >>
> >> >> "Frustrated" <> wrote in message
> >> >> news:573C857F-0134-4065-B467-...
> >> >> > Operating on an emachine with vista home premium for the six months
> >> >> > that
> >> >> > we
> >> >> > have had this machine we have been having these seemingly random and
> >> >> > always
> >> >> > unexpected bluescreen errors. I just recently started to look into
> >> >> > it
> >> >> > and
> >> >> > have followed suggestions from the fine folks at Gateway to attempt
> >> >> > full
> >> >> > factory recovery and startup repair procedures to no avail. The
> >> >> > following
> >> >> > is
> >> >> > the combined text from four (4) shutdowns over the course of 2 hours
> >> >> > this
> >> >> > morning, there does not appear to be any one software or application
> >> >> > that
> >> >> > triggers these events. Seems to be some educated assistance for
> >> >> > these
> >> >> > matters
> >> >> > in the forum search that I conducted here only hope someone can give
> >> >> > me
> >> >> > a
> >> >> > case specific fix. see error reports below, thanks
> >> >> >
> >> >> > Product
> >> >> > Windows
> >> >> >
> >> >> > Problem
> >> >> > Shut down unexpectedly
> >> >> >
> >> >> > Date
> >> >> > 2/24/2008 10:09 AM
> >> >> >
> >> >> > Status
> >> >> > Report Sent
> >> >> >
> >> >> > Problem signature
> >> >> > Problem Event Name: BlueScreen
> >> >> > OS Version: 6.0.6000.2.0.0.768.3
> >> >> > Locale ID: 1033
> >> >> >
> >> >> > Files that help describe the problem (some files may no longer be
> >> >> > available)
> >> >> > Mini022408-01.dmp
> >> >> > sysdata.xml
> >> >> > Version.txt
> >> >> >
> >> >> > Extra information about the problem
> >> >> > BCCode: 124
> >> >> > BCP1: 00000000
> >> >> > BCP2: 83108A60
> >> >> > BCP3: 00000000
> >> >> > BCP4: 00000000
> >> >> > OS Version: 6_0_6000
> >> >> > Service Pack: 0_0
> >> >> > Product: 768_1
> >> >> > Server information: 8c0093da-125c-42d6-9b0d-26aa065d818e
> >> >> >
> >> >> >
> >> >> >
> >> >> > Product
> >> >> > Windows
> >> >> >
> >> >> > Problem
> >> >> > Shut down unexpectedly
> >> >> >
> >> >> > Date
> >> >> > 2/24/2008 10:22 AM
> >> >> >
> >> >> > Status
> >> >> > Report Sent
> >> >> >
> >> >> > Problem signature
> >> >> > Problem Event Name: BlueScreen
> >> >> > OS Version: 6.0.6000.2.0.0.768.3
> >> >> > Locale ID: 1033
> >> >> >
> >> >> > Files that help describe the problem (some files may no longer be
> >> >> > available)
> >> >> > Mini022408-03.dmp
> >> >> > sysdata.xml
> >> >> > Version.txt
> >> >> >
> >> >> > Extra information about the problem
> >> >> > BCCode: 124
> >> >> > BCP1: 00000000
> >> >> > BCP2: 830DD028
> >> >> > BCP3: 00000000
> >> >> > BCP4: 00000000
> >> >> > OS Version: 6_0_6000
> >> >> > Service Pack: 0_0
> >> >> > Product: 768_1
> >> >> > Server information: 428eb43c-c2c4-4375-9d0a-b8cb5e8ede20
> >> >> >
> >> >> >
> >> >> > Product
> >> >> > Windows
> >> >> >
> >> >> > Problem
> >> >> > Shut down unexpectedly
> >> >> >
> >> >> > Date
> >> >> > 2/24/2008 10:50 AM
> >> >> >
> >> >> > Status
> >> >> > Report Sent
> >> >> >
> >> >> > Problem signature
> >> >> > Problem Event Name: BlueScreen
> >> >> > OS Version: 6.0.6000.2.0.0.768.3
> >> >> > Locale ID: 1033
> >> >> >
> >> >> > Files that help describe the problem (some files may no longer be
> >> >> > available)
> >> >> > Mini022408-04.dmp
> >> >> > sysdata.xml
> >> >> > Version.txt
> >> >> >
> >> >> > Extra information about the problem
> >> >> > BCCode: 124
> >> >> > BCP1: 00000000
> >> >> > BCP2: 8325FB40
> >> >> > BCP3: 00000000
> >> >> > BCP4: 00000000
> >> >> > OS Version: 6_0_6000
> >> >> > Service Pack: 0_0
> >> >> > Product: 768_1
> >> >> > Server information: 1996a66d-2867-4882-9158-9a33bdc3909d
> >> >> >
> >> >> >
> >> >> > Product
> >> >> > Windows
> >> >> >

On 3ÔÂ3ÈÕ, ÉÏÎç3ʱ34·Ö, Frustrated <Frustra...@discussions.microsoft.com>
wrote:
> This is the latest info I was able to get from the event viewer. Two (2)
> shutdowns this AM and both appear to have the same info from the event log..
> Please Help.
>
> Log Name: Security
> Source: Microsoft-Windows-Eventlog
> Date: 3/2/2008 2:15:47 PM
> Event ID: 1101
> Task Category: Event processing
> Level: Error
> Keywords: Audit Success
> User: N/A
> Computer: Jeff-PC
> Description:
> Audit events have been dropped by the transport. The real timebackupfile
> wascorruptdue to improper shutdown.
> Event Xml:
> <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> <System>
> <Provider Name="Microsoft-Windows-Eventlog"
> Guid="{fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}" />
> <EventID>1101</EventID>
> <Version>0</Version>
> <Level>2</Level>
> <Task>101</Task>
> <Opcode>0</Opcode>
> <Keywords>0x4020000000000000</Keywords>
> <TimeCreated SystemTime="2008-03-02T19:15:47.320Z" />
> <EventRecordID>680</EventRecordID>
> <Correlation />
> <Execution ProcessID="928" ThreadID="1548" />
> <Channel>Security</Channel>
> <Computer>Jeff-PC</Computer>
> <Security />
> </System>
> <UserData>
> <AuditEventsDropped
> xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events"
>
> xmlns="http://manifests.microsoft.com/win/2004/08/windows/eventlog">
> <Reason>34</Reason>
> </AuditEventsDropped>
> </UserData>
> </Event>
>
> Thanks,
> Frustrated
>
>
>
> "Ronnie Vernon MVP" wrote:
> > Frustrated
>
> > The information you posted is from the Problem Reports and Solutions
> > component which is information and files that are sent to Microsoft to be
> > entered into their internal database. This information is fairly useless
> > unless a support person has access to that internal database.
>
> > What we can use here is some information from the blue screen. A blue screen
> > error is usually in the following format.
>
> > A number that that is included in any knowledgebase articles that may have
> > information on fixing this error.
> > Example: STOP: 0x0000007E
>
> > Following this number there should be a brief description of what component
> > the error occured in.
> > Example: IRQL_NOT_GREATER_OR_EQUAL
>
> > If you post these 2 bits of information it will go a long way in determining
> > what caused the error.
>
> > You can also look in the Event Viewer for any errors that occured at the
> > time the blue screen happened.
>
> > Open Control Panel/Administrative Tools/Event Viewer.
>
> > In the Event Viewer open Custom Views / Adminisdtrative Events. Look forany
> > error events with a 'red' icon that correspond to the date/time of the blue
> > screen. If you find any, double click the error message. At the bottom of
> > that dialog box, press the Copy Button. Paste the results back here in a
> > reply.
>
> > Example:
>
> > Log Name: Application
> > Source: Application Error
> > Date: 1/10/2008 12:54:52 PM
> > Event ID: 1000
> > Task Category: (100)
> > Level: Error
> > Keywords: Classic
> > User: N/A
> > Computer: xxx-PC
> > Description:
> > Faulting application WMIADAP.EXE, version 6.0.6000.16386, time stamp
> > 0x4549af43, faulting module ntdll.dll, version 6.0.6000.16386, time stamp
> > 0x4549bdc9, exception code 0xc0000043, fault offset 0x00008fc7, process id
> > 0xc5c, application start time 0x01c853cb07287de7.
> > --
>
> > Ronnie Vernon
> > Microsoft MVP
> > Windows Desktop Experience
>
> > "Frustrated" <Frustra...@discussions.microsoft.com> wrote in message
> >news:573C857F-0134-4065-B467-...
> > > Operating on an emachine with vista home premium for the six months that
> > > we
> > > have had this machine we have been having these seemingly random and
> > > always
> > > unexpected bluescreen errors. I just recently started to look into it and
> > > have followed suggestions from the fine folks at Gateway to attempt full
> > > factory recovery and startup repair procedures to no avail. The following
> > > is
> > > the combined text from four (4) shutdowns over the course of 2 hours this
> > > morning, there does not appear to be any one software or application that
> > > triggers these events. Seems to be some educated assistance for these
> > > matters
> > > in the forum search that I conducted here only hope someone can give me a
> > > case specific fix. see error reports below, thanks
>
> > > Product
> > > Windows
>
> > > Problem
> > > Shut down unexpectedly
>
> > > Date
> > > 2/24/2008 10:09 AM
>
> > > Status
> > > Report Sent
>
> > > Problem signature
> > > Problem Event Name: BlueScreen
> > > OS Version: 6.0.6000.2.0.0.768.3
> > > Locale ID: 1033
>
> > > Files that help describe the problem (some files may no longer be
> > > available)
> > > Mini022408-01.dmp
> > > sysdata.xml
> > > Version.txt
>
> > > Extra information about the problem
> > > BCCode: 124
> > > BCP1: 00000000
> > > BCP2: 83108A60
> > > BCP3: 00000000
> > > BCP4: 00000000
> > > OS Version: 6_0_6000
> > > Service Pack: 0_0
> > > Product: 768_1
> > > Server information: 8c0093da-125c-42d6-9b0d-26aa065d818e
>
> > > Product
> > > Windows
>
> > > Problem
> > > Shut down unexpectedly
>
> > > Date
> > > 2/24/2008 10:22 AM
>
> > > Status
> > > Report Sent
>
> > > Problem signature
> > > Problem Event Name: BlueScreen
> > > OS Version: 6.0.6000.2.0.0.768.3
> > > Locale ID: 1033
>
> > > Files that help describe the problem (some files may no longer be
> > > available)
> > > Mini022408-03.dmp
> > > sysdata.xml
> > > Version.txt
>
> > > Extra information about the problem
> > > BCCode: 124
> > > BCP1: 00000000
> > > BCP2: 830DD028
> > > BCP3: 00000000
> > > BCP4: 00000000
> > > OS Version: 6_0_6000
> > > Service Pack: 0_0
> > > Product: 768_1
> > > Server information: 428eb43c-c2c4-4375-9d0a-b8cb5e8ede20
>
> > > Product
> > > Windows
>
> > > Problem
> > > Shut down unexpectedly
>
> > > Date
> > > 2/24/2008 10:50 AM
>
> > > Status
> > > Report Sent
>
> > > Problem signature
> > > Problem Event Name: BlueScreen
> > > OS Version: 6.0.6000.2.0.0.768.3
> > > Locale ID: 1033
>
> > > Files that help describe the problem (some files may no longer be
> > > available)
> > > Mini022408-04.dmp
> > > sysdata.xml
> > > Version.txt
>
> > > Extra information about the problem
> > > BCCode: 124
> > > BCP1: 00000000
> > > BCP2: 8325FB40
> > > BCP3: 00000000
> > > BCP4: 00000000
> > > OS Version: 6_0_6000
> > > Service Pack: 0_0
> > > Product: 768_1
> > > Server information: 1996a66d-2867-4882-9158-9a33bdc3909d
>
> > > Product
> > > Windows
>
> > > Problem
> > > Shut down unexpectedly
>
> > > Date
> > > 2/24/2008 10:58 AM
>
> > > Status
> > > Report Sent
>
> > > Problem signature
> > > Problem Event Name: BlueScreen
> > > OS Version: 6.0.6000.2.0.0.768.3
> > > Locale ID: 1033
>
> > > Files that help describe the problem (some files may no longer be
> > > available)
> > > Mini022408-05.dmp
> > > sysdata.xml
> > > Version.txt
>
> > > Extra information about the problem
> > > BCCode: 124
> > > BCP1: 00000000
> > > BCP2: 832FFD18
> > > BCP3: 00000000
> > > BCP4: 00000000
> > > OS Version: 6_0_6000
> > > Service Pack: 0_0
> > > Product: 768_1
> > > Server information: b806e066-a800-4c1b-937a-1269cec6c89d- Òþ²Ø±»ÒýÓÃÎÄ×Ö -
>
> - ÏÔʾÒýÓõÄÎÄ×Ö -
Hi,

You can try a popular BKF file recovery tool called Advanced BKF
Repair to repair your BKF file. It is a powerful tool to repair
corrupt or damaged BKF files.

Detailed information about Advanced BKF Repair can be found at
http://www.datanumen.com/abr/

And you can also download a free demo version at http://www.datanumen.com/abr/abr.exe

Alan

Here is the following information that is on the bluescreen when the computer
decides to randomly shut down... my sister in law is having the same problem
and she is getting the same message on her blue screen as well, on saturday
it was happening so often she could not even use her computer - she called
Dell and they had her do a system restore to the previous day and said it was
some sort of software issue - here we are just a few days later and her
computer starts doing it again (but only occasionally this time) my is very
random as well as to when it happens - nothing seems to prevoke it and it
usually only happens once-ish a week

the bluescreen message says something about BIOS (now, I know nothing much
about computers so i have no idea what it is talking about) but i know that
recently either windows or dell support had me install a bios update (not
sure if this was before or after the problems) - but if i downloaded this
bios update - i'm sure my sister in law did too because she also has a dell

here is the bluescreen information - someone please help!!!!!

A problem has been detected and windows has been shut down to prevent damage
to your computer.
DRIVER_POWER_STATE_FAILURE
If this is the first time you’ve seen this stop error screen, restart your
computer. If this screen appears again, follow these steps:
Check to make sure any new hardware or software is properly installed. If
this is a new installation, ask your hardware of software manufacturer for
any windows updates you might need.
If problems continue, disable or remove any newly installed hardware of
software. Disable BIOS Memory options such as caching or shadowing. If you
need to use Safe Mode to remove or disable components, restart your computer,
pres F8 to select Advanced Start Options, and then select Safe Mode.
Technical Information�
***STOP: 0x0000009F (0x00000003, 0x9CACA938, 0x9CDE6900, 0x9C655B70)
Collecting data for crash dump…
Initializing disk for crash dump…
Beginning dump of physical memory.
Dumping physical memory to disk: 100
Physical memory dump complete.
Contact your system admin or technical support group for further assistance.



"jowen" wrote:

> I have also incountered this problem. It seems to go in spurts of when it
> happens. One morning it happened a 1/2 a dozen times. It occured twice last
> week and once again this morning. Like Frustrated, the blue screen is up so
> little time I cannot get any information down. I have changed my settings so
> it does not automatically restart and I will hope (I guess) for it to happen
> again so that I can write down the information. I'm just glad to know I'm
> not the only one having problems.
> I will post the information from my blue screen whenever it happens again.
>
> "Ronnie Vernon MVP" wrote:
>
> > Frustrated
> >
> > Open Control Panel, click Classic View in the left side menu. Open System
> > and select Advanced System Settings in the left side menu.
> >
> > In Start Up and Recovery, click the Settings Button. In the System Failure
> > section, remove the check mark from Automatically Restart. This will leave
> > the blue screen up long enough to write down the pertinent details.
> >
> > --
> >
> > Ronnie Vernon
> > Microsoft MVP
> > Windows Desktop Experience
> >
> >
> > "Frustrated" <> wrote in message
> > news:437F0B74-F1CB-47C2-8621-...
> > > The Bluescreen flashes so quickly that I am unable to view any details. It
> > > is
> > > also so unpredictable that I cannot intentionally force it to happen, in
> > > order to photograph it
> > >
> > > "Ronnie Vernon MVP" wrote:
> > >
> > >> Frustrated
> > >>
> > >> That event is a result of the blue screen shutdown, not the cause. Can
> > >> you
> > >> post the information I requested from the blue screen?
> > >>
> > >> --
> > >>
> > >> Ronnie Vernon
> > >> Microsoft MVP
> > >> Windows Desktop Experience
> > >>
> > >>
> > >> "Frustrated" <> wrote in message
> > >> news:3D0D9433-A7FE-4B84-8EAF-...
> > >> > This is the latest info I was able to get from the event viewer. Two
> > >> > (2)
> > >> > shutdowns this AM and both appear to have the same info from the event
> > >> > log.
> > >> > Please Help.
> > >> >
> > >> > Log Name: Security
> > >> > Source: Microsoft-Windows-Eventlog
> > >> > Date: 3/2/2008 2:15:47 PM
> > >> > Event ID: 1101
> > >> > Task Category: Event processing
> > >> > Level: Error
> > >> > Keywords: Audit Success
> > >> > User: N/A
> > >> > Computer: Jeff-PC
> > >> > Description:
> > >> > Audit events have been dropped by the transport. The real time backup
> > >> > file
> > >> > was corrupt due to improper shutdown.
> > >> > Event Xml:
> > >> > <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> > >> > <System>
> > >> > <Provider Name="Microsoft-Windows-Eventlog"
> > >> > Guid="{fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}" />
> > >> > <EventID>1101</EventID>
> > >> > <Version>0</Version>
> > >> > <Level>2</Level>
> > >> > <Task>101</Task>
> > >> > <Opcode>0</Opcode>
> > >> > <Keywords>0x4020000000000000</Keywords>
> > >> > <TimeCreated SystemTime="2008-03-02T19:15:47.320Z" />
> > >> > <EventRecordID>680</EventRecordID>
> > >> > <Correlation />
> > >> > <Execution ProcessID="928" ThreadID="1548" />
> > >> > <Channel>Security</Channel>
> > >> > <Computer>Jeff-PC</Computer>
> > >> > <Security />
> > >> > </System>
> > >> > <UserData>
> > >> > <AuditEventsDropped
> > >> > xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events"
> > >> >
> > >> > xmlns="http://manifests.microsoft.com/win/2004/08/windows/eventlog">
> > >> > <Reason>34</Reason>
> > >> > </AuditEventsDropped>
> > >> > </UserData>
> > >> > </Event>
> > >> >
> > >> > Thanks,
> > >> > Frustrated
> > >> >
> > >> >
> > >> > "Ronnie Vernon MVP" wrote:
> > >> >
> > >> >> Frustrated
> > >> >>
> > >> >> The information you posted is from the Problem Reports and Solutions
> > >> >> component which is information and files that are sent to Microsoft to
> > >> >> be
> > >> >> entered into their internal database. This information is fairly
> > >> >> useless
> > >> >> unless a support person has access to that internal database.
> > >> >>
> > >> >> What we can use here is some information from the blue screen. A blue
> > >> >> screen
> > >> >> error is usually in the following format.
> > >> >>
> > >> >> A number that that is included in any knowledgebase articles that may
> > >> >> have
> > >> >> information on fixing this error.
> > >> >> Example: STOP: 0x0000007E
> > >> >>
> > >> >> Following this number there should be a brief description of what
> > >> >> component
> > >> >> the error occured in.
> > >> >> Example: IRQL_NOT_GREATER_OR_EQUAL
> > >> >>
> > >> >> If you post these 2 bits of information it will go a long way in
> > >> >> determining
> > >> >> what caused the error.
> > >> >>
> > >> >> You can also look in the Event Viewer for any errors that occured at
> > >> >> the
> > >> >> time the blue screen happened.
> > >> >>
> > >> >> Open Control Panel/Administrative Tools/Event Viewer.
> > >> >>
> > >> >> In the Event Viewer open Custom Views / Adminisdtrative Events. Look
> > >> >> for
> > >> >> any
> > >> >> error events with a 'red' icon that correspond to the date/time of the
> > >> >> blue
> > >> >> screen. If you find any, double click the error message. At the bottom
> > >> >> of
> > >> >> that dialog box, press the Copy Button. Paste the results back here in
> > >> >> a
> > >> >> reply.
> > >> >>
> > >> >> Example:
> > >> >>
> > >> >> Log Name: Application
> > >> >> Source: Application Error
> > >> >> Date: 1/10/2008 12:54:52 PM
> > >> >> Event ID: 1000
> > >> >> Task Category: (100)
> > >> >> Level: Error
> > >> >> Keywords: Classic
> > >> >> User: N/A
> > >> >> Computer: xxx-PC
> > >> >> Description:
> > >> >> Faulting application WMIADAP.EXE, version 6.0.6000.16386, time stamp
> > >> >> 0x4549af43, faulting module ntdll.dll, version 6.0.6000.16386, time
> > >> >> stamp
> > >> >> 0x4549bdc9, exception code 0xc0000043, fault offset 0x00008fc7,
> > >> >> process
> > >> >> id
> > >> >> 0xc5c, application start time 0x01c853cb07287de7.
> > >> >> --
> > >> >>
> > >> >> Ronnie Vernon
> > >> >> Microsoft MVP
> > >> >> Windows Desktop Experience
> > >> >>
> > >> >>
> > >> >> "Frustrated" <> wrote in message
> > >> >> news:573C857F-0134-4065-B467-...
> > >> >> > Operating on an emachine with vista home premium for the six months
> > >> >> > that
> > >> >> > we
> > >> >> > have had this machine we have been having these seemingly random and
> > >> >> > always
> > >> >> > unexpected bluescreen errors. I just recently started to look into
> > >> >> > it
> > >> >> > and
> > >> >> > have followed suggestions from the fine folks at Gateway to attempt
> > >> >> > full
> > >> >> > factory recovery and startup repair procedures to no avail. The
> > >> >> > following
> > >> >> > is
> > >> >> > the combined text from four (4) shutdowns over the course of 2 hours
> > >> >> > this
> > >> >> > morning, there does not appear to be any one software or application
> > >> >> > that
> > >> >> > triggers these events. Seems to be some educated assistance for
> > >> >> > these
> > >> >> > matters
> > >> >> > in the forum search that I conducted here only hope someone can give
> > >> >> > me
> > >> >> > a
> > >> >> > case specific fix. see error reports below, thanks
> > >> >> >
> > >> >> > Product
> > >> >> > Windows
> > >> >> >
> > >> >> > Problem
> > >> >> > Shut down unexpectedly
> > >> >> >
> > >> >> > Date
> > >> >> > 2/24/2008 10:09 AM
> > >> >> >
> > >> >> > Status
> > >> >> > Report Sent
> > >> >> >
> > >> >> > Problem signature
> > >> >> > Problem Event Name: BlueScreen
> > >> >> > OS Version: 6.0.6000.2.0.0.768.3
> > >> >> > Locale ID: 1033
> > >> >> >
> > >> >> > Files that help describe the problem (some files may no longer be
> > >> >> > available)
> > >> >> > Mini022408-01.dmp
> > >> >> > sysdata.xml
> > >> >> > Version.txt
> > >> >> >
> > >> >> > Extra information about the problem
> > >> >> > BCCode: 124
> > >> >> > BCP1: 00000000
> > >> >> > BCP2: 83108A60
> > >> >> > BCP3: 00000000
> > >> >> > BCP4: 00000000
> > >> >> > OS Version: 6_0_6000
> > >> >> > Service Pack: 0_0
> > >> >> > Product: 768_1
> > >> >> > Server information: 8c0093da-125c-42d6-9b0d-26aa065d818e
> > >> >> >
> > >> >> >
> > >> >> >
> > >> >> > Product
> > >> >> > Windows
> > >> >> >
> > >> >> > Problem
> > >> >> > Shut down unexpectedly
> > >> >> >
> > >> >> > Date
> > >> >> > 2/24/2008 10:22 AM
> > >> >> >
> > >> >> > Status
> > >> >> > Report Sent
> > >> >> >
> > >> >> > Problem signature
> > >> >> > Problem Event Name: BlueScreen
> > >> >> > OS Version: 6.0.6000.2.0.0.768.3
> > >> >> > Locale ID: 1033
> > >> >> >
> > >> >> > Files that help describe the problem (some files may no longer be
> > >> >> > available)
> > >> >> > Mini022408-03.dmp
> > >> >> > sysdata.xml
> > >> >> > Version.txt
> > >> >> >
> > >> >> > Extra information about the problem
> > >> >> > BCCode: 124
> > >> >> > BCP1: 00000000
> > >> >> > BCP2: 830DD028
> > >> >> > BCP3: 00000000
> > >> >> > BCP4: 00000000
> > >> >> > OS Version: 6_0_6000
> > >> >> > Service Pack: 0_0
> > >> >> > Product: 768_1
> > >> >> > Server information: 428eb43c-c2c4-4375-9d0a-b8cb5e8ede20
> > >> >> >
> > >> >> >
> > >> >> > Product
> > >> >> > Windows
> > >> >> >
> > >> >> > Problem
> > >> >> > Shut down unexpectedly
> > >> >> >
> > >> >> > Date
> > >> >> > 2/24/2008 10:50 AM
> > >> >> >
> > >> >> > Status
> > >> >> > Report Sent
> > >> >> >
> > >> >> > Problem signature
> > >> >> > Problem Event Name: BlueScreen
> > >> >> > OS Version: 6.0.6000.2.0.0.768.3
> > >> >> > Locale ID: 1033
> > >> >> >
> > >> >> > Files that help describe the problem (some files may no longer be
> > >> >> > available)
> > >> >> > Mini022408-04.dmp
> > >> >> > sysdata.xml
> > >> >> > Version.txt
> > >> >> >
> > >> >> > Extra information about the problem
> > >> >> > BCCode: 124
> > >> >> > BCP1: 00000000
> > >> >> > BCP2: 8325FB40