Re: Blue Kiss of Death Crash on Boot Up

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

On Mar 15, 7:12 pm, "AllanF" <not.kn...@xxxxxxxxxxxx> wrote:
Hi JMB,

Surprisingly, the BSOD Event may not be flagged as a warningIor an error,
just information. I have seen some "Save Dumps" with Event ID 1003. Event
Viewer has a search facility.

Start > RightClick [My Computer] > Manage > Expand Event Viewer > Cick
"System" in the Right-hand Pane > View on MenuBar > Find... > Type
"Bugcheck" in Description > Find Next > DoubleClick the Event.

Also search for more Events with "Bugcheck". And search the Applications
log.

One problem with Event Viewer is that it has a limited capacity, and
furthermore, if a particular log is set such that "When maximum log size is
reached...", not to overwrite events; Event Viewer gives the impression that
it is broken.

Not to fear! BSOD Information is always dumped to a file in
C:\WINDOWS\Minidump, with the FileName format "Mini[mmddyy-##].dmp". Reading
this file requires either a Debugger (for hard-core Geeks only!), or
Dumpchk.exe.

Start > Search > All files and folders > Type "dumpchk" (without quotation
marks). You should (I hope) locate the file in C:\SUPPORT\TOOLS\SUPPORT.CAB
DoubleClick "dumpchk.exe" > "Select a Destination" > Navigate to [My
Computer] > [Your] (C:) Drive > Documents and Settings > Hightlight [Your
Profile Name] > Extract. (This Destination is convenient because when you
run the Command Prompt later, you will automatically start in this
Directory, and you will need to be in the same Directory as dumpchk.exe in
order to run it.)

Start > Search > All files and folders > Type "mini*.dmp" (without quotes) >
Search

You should have a list of MiniDump Files. Write down the dates and ID
numbers (mmddyy-##).

Start > All Programs > Accessories > Command Prompt

Type accurately, "dumpchk.exe c:\windows\minidump\mini[mmddyy-##].dmp"
(without quotes), where "mmddyy-##" is from a file you have identified, and
assuming your system drive is "c:\".

Scroll up and down the Command Prompt Window to locate the BugCheckCode. The
information will vary depending on the particular Stop Error and what
facilities are available to the Memory Dump at the time of the BSOD.

If you are successful in following these instructions, I personally will
assign to you, the status of "Expert". :)

"JMB" <JMB48...@xxxxxxxxx> wrote in message

news:1173972713.471974.5750@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



On Mar 14, 5:17 pm, "AllanF" <not.kn...@xxxxxxxxxxxx> wrote:
Hi JMB,

Thanks for keeping us all informed. I'm not aware of issues with your
particular make of PC. A WebSearch with terms "Dell E520 BSOD" may reveal
others having the same problems. I suggest that you keep open the option
of
a complete replacement. Don't throw out the packaging! In my experience,
these things don't go away, but you have the consolation that your BSOD
occurs at start up, not when you're just finishing off an unsaved
document.

There are Drive-Imaging Software-Packages that would allow you to
recreate a
new PC with your current Programs, Settings, Documents, etc. I don't
think
it would be impertinent to ask Dell to provide you with Imaging Software.
Worth a shot!

Did you find the Bugcheck Code (that is, a number in the form
"0x????????"
followed by parameters in a similar form) in Event Viewer? Certain Codes
do
point in the general direction of a Hardware Failure, especially when the
BSOD occurs at start up. These include 0x......31, 0x5C, 0x5D, 0x5E,
0x5F,
and 0x60.

"JMB" <JMB48...@xxxxxxxxx> wrote in message

news:1173879487.284351.192840@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

On Mar 9, 4:44 pm, Gene E. Bloch <spamf...@xxxxxxxxxxxxxx> wrote:
Under the circumstances, I certainly would tend to agree with you, Mr
F, so I'd go ahead and replace the MB.

However, I change motherboards for fun (he says...), and the OP's
mileage may vary :-)

On 3/09/2007, AllanF posted this:

Dell's response suggests that they might know something about the
Motherboard
that we don't!? Keep us informed if you choose to delve into the
murky
world
of BSODs.

"JMB" <JMB48...@xxxxxxxxx> wrote in message
news:1173447008.994220.281100@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Mar 9, 8:02 am, "AllanF" <not.kn...@xxxxxxxxxxxx> wrote:
It is unusual that a Blue Screen ofDeathcan Trash individul System
Restore
Points. The BSOD can be related to hardware or software, or both.

For a quick analysis, Open Event Viewer: Go to Start > RightClick
My
Computer > Manage > Expand Event Viewer > Application or System
Log.
Search
for your BSOD Events (Usually an Event ID 1001). The bugcheck
codes
are
important: the reason for the Stop can be determined in very
general
and
obscure terms, and sometimes the offending file/driver is
identified.
It
could be anything, and sometimes each Dump can report a different
code or
file/driver.

Anyway, it was nice of Dell to send you the new hardware. Is it a
replacement or an upgrade?

"JMB" <JMB48...@xxxxxxxxx> wrote in message

news:1173441536.106235.42340@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

I got a new Dell E520 w/ XP MCE back in Dec '06. Three (3) times
now,
at random, I've had the PC crash on what otherwise should have
been
just a normal boot up. You get the blue screen saying something
to
the effect that it has suffered a fatal crash and is dumping its
memory. And if it happens again to contact the manufacturer.
The
1st
2 times it happened it rebooted fine with no apparent adverse
effects. But this most recent time (which was the 1st start of
the
day), I lost all but 1 of my System Restore points.

I contacted Dell, just to advise them of the issue (on this most
recent crash) and without hardly any dialog on the matter I was
sent a
new motherboard and microprocessor (2.8 GHz Core 2 Dual Intel).
I'm
reluctant to just start swaping parts if the issue 1st of all is
really that serious, and 2nd is this likely a hardware problem?

I'm not a PC geek..... one iota. So any responses, please speak
in
layman's terms. Also, I'm stuck with a painfully slow dial-up
connection out in the 'sticks' where I live, so I can't easily
communicate via the internet from home. I'll have to monitor
responses from work.

Thanks!

John- Hide quoted text -

- Show quoted text -

Thanks Alan for the quick response... and one that I can
understand!
When I get home, I'll check the Event Viewer. And yes, I'm not
critical of Dell's fast response to my inquiry, but I wasn't quite
ready to start swapping hardware w/o some justifiable reason to do
so. I have email to their C/S to this effect.

I don't know whether the motherboard & processor are upgrades or
replacements. I would imagine it is the latter. I didn't even
take
them out of the box!

Thanks again

--
Gene E. Bloch (Gino)
letters617blochg3251
(replace the numbers by "at" and "dotcom")- Hide quoted text -

- Show quoted text -

I don't know if this dialog is still active, but FYI, Dell now wants
to replace my entire PC. I find it odd that after specifically asking
Dell FOUR (4) times whether they have had any issues with E520's built
in the timeframe that mine was built (mid-Dec-'06), they have declined
to respond. I can't complain about their willingness, nor
responsiveness to my concern. But I'd just like to know whether their
are known problems with any of the components in my PC's vintage.

Any suggestions? I hate to replace the PC and jump through all the
hoops to get it re-configured back to the way I have it now. I don't
have that kind of time... The BSOD has only happened 3 times in 3
-1/2 months and the PC seems to be working fine now.

Thanks for the help to all!- Hide quoted text -

- Show quoted text -

Hi Alan and thanks again for your follow-up input.

Just last night I got around to looking at the event viewer for hints
at what may have caused the BSOD on boot-up. Mind you, I'm not real
"PC fluent" beyond the basics. That's why I'm relying on YOU
experts! : ) You had mentioned to look for a ID "1001"? Under
'Applications", I found a few "1001's" (warnings), but none of these
were on the date that the BSOD occured. There were consistent errors,
ID "7000" (I think,?), but seemingly not linked to any pattern that I
could identify, but again, I'm not sure what to look for. There were
no errors under 'System', which is probably a good sign. When I get
home tonight, I'll look for the codes you suggest above.

If Dell replaces the PC, I don't know if that means the whole set-up
or just the tower. I don't know enough how to re-image the new PC
without having two complete systems with keyboards & monitors. I do
have the Detto transfer software. Also, I thought I could arrange
with Dell to keep my existing hard drive and swap it into the new PC.
The only problem with that is if my BSOD issue is in the hard drive.
But if I could hold onto my old drive, time would tell if the issue
would reappear. For all the trouble I have had with this PC, I'd
think that Dell would be accomodating. Besides I have a lot of
personal data that

...

read more »- Hide quoted text -

- Show quoted text -

Alan,

I'm trying this from home. Thanks for your last set of suggestions
and I'll read it over more closely later. At the moment, I'm about
ready to call it a day. I'm still trying to follow up more on your
last suggestion in event viewer.

I found a normal boot pattern under System as follows:

Information 3/5/2007 6:38:06 PM Service Control Manager None 7036 N/A
Information 3/5/2007 6:38:06 PM Service Control Manager None 7035
SYSTEM
Information 3/5/2007 6:38:06 PM Service Control Manager None 7035
SYSTEM
Information 3/5/2007 6:38:03 PM Service Control Manager None 7035
SYSTEM
Error 3/5/2007 6:38:02 PM Service Control Manager None 7000 N/A
Information 3/5/2007 6:37:59 PM eventlog None 6005 N/A
Information 3/5/2007 6:37:59 PM eventlog None 6009 N/A

The above is the normal boot pattern before & after the BSOD, even up
to today. I don't know what that "error" means but it has apparently
always done it since I had to re-install XP a month earlier. I think
I may have mislead you in my previous reply by stating 'no errors'. I
was doing that from memory, and I guess I was wrong.

However, on 3/6/07 on the 1st boot of the day the pattern was like
this:

Information 3/6/2007 6:35:05 PM Service Control Manager None 7036 N/A
Information 3/6/2007 6:35:05 PM Service Control Manager None 7035
SYSTEM
Information 3/6/2007 6:35:05 PM Service Control Manager None 7035
SYSTEM
Information 3/6/2007 6:35:03 PM Service Control Manager None 7035
SYSTEM
Error 3/6/2007 6:35:02 PM Service Control Manager None 7000 N/A
Information 3/6/2007 6:35:00 PM Save Dump None 1001 N/A
Information 3/6/2007 6:34:59 PM eventlog None 6005 N/A
Information 3/6/2007 6:34:59 PM eventlog None 6009 N/A
Information 3/6/2007 6:33:36 PM eventlog None 6005 N/A
Information 3/6/2007 6:33:36 PM eventlog None 6009 N/A

The bugcheck of the 1001 Dump read like this:

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 3/6/2007
Time: 6:35:00 PM
User: N/A
Computer:
Description:
The computer has rebooted from a bugcheck. The bugcheck was:
0x000000d1 (0x00000030, 0x00000005, 0x00000000, 0xb9143613). A dump
was saved in: C:\WINDOWS\MEMORY.DMP

All this looks like what you said to be on the prowl for in your above
msgs. Let me know what you think.... hardware or software? I saved
text files of the whole system event viewer, but I didn't want to put
that out to the public, nor overwhelm you or anyone else. If more
info is needed let me know.

I've got a busy weekend coming up, so if I get time, I'll try to wade
through your last set of suggestions. To be honest I don't know how
you or others in your 'class' keep up with this stuff. I'm a dumb ol'
mechanical engineer and would just like to use a PC without having to
know what makes it tick. I really appreciate the tips and patience.

John


.

Relevant Pages

  • Re: Kernel_data_inpage-error
    ... Source: Service Control Manager ... I cannot say for sure whether the frequncy of BSOD is more when connected to ... and carefully remove one memory card from it's slot and run the ... The system log in Event Viewer could yield clues as to the nature of the ...
    (microsoft.public.windowsxp.general)
  • Re: interesting crash
    ... What I don't understand is his Event Source. ... Oh I see this is not an indication of the BSOD. ... It is just the information that a dump was being created. ... >> The computer has rebooted from a bugcheck. ...
    (microsoft.public.win2000.general)
  • Re: interesting crash
    ... What I don't understand is his Event Source. ... Oh I see this is not an indication of the BSOD. ... It is just the information that a dump was being created. ... >> The computer has rebooted from a bugcheck. ...
    (microsoft.public.win2000.hardware)
  • Re: Blue Kiss of Death Crash on Boot Up
    ... However, I change motherboards for fun, and the OP's ... The BSOD can be related to hardware or software, ... Computer> Manage> Expand Event Viewer> Application or System Log. ... responses from work. ...
    (microsoft.public.windows.mediacenter)
  • Re: Blue screen after disc eject
    ... including Spyware Doctor and after burning to disc the BSOD was back. ... "gaz" wrote: ... Please post a copy of the full Error Report from Event Viewer. ...
    (microsoft.public.windowsxp.general)