My Dell Precision M6300 laptop has started to shut down or reboot when left
alone for a while so it appears to have BSOD problems. I have not been
around when the actual BSOD happens so how do I go about tracking down the
problem? When it starts up again it tells me that it has recovered from an
unexpected shutdown but it doesn't seem to be able to determine the cause
after submitting the details.

--
And loving it,

-Qu0ll (Rare, not extinct)
_________________________________________________
Qu0llSixFour@xxxxxx
[Replace the "SixFour" with numbers to email me]

Control Panel
System
Advanced System Properties
Advanced tab
Startup and Recovery area, settings button
Under System failure, uncheck Automatically restart

If system is failing with a BSOD, then the error message will remain on
screen.

Michael


"Qu0ll" <Qu0llSixFour@xxxxxx> wrote in message
news:uH$M8uq6IHA.4988@xxxxxx

> My Dell Precision M6300 laptop has started to shut down or reboot when
> left alone for a while so it appears to have BSOD problems. I have not
> been around when the actual BSOD happens so how do I go about tracking
> down the problem? When it starts up again it tells me that it has
> recovered from an unexpected shutdown but it doesn't seem to be able to
> determine the cause after submitting the details.
>
> --
> And loving it,
>
> -Qu0ll (Rare, not extinct)
> _________________________________________________
> Qu0llSixFour@xxxxxx
> [Replace the "SixFour" with numbers to email me]

"Michael Walraven" <mexxwalraven@xxxxxx> wrote in message
news:5A6D9F74-69F9-4CC0-88CC-FCEE08D711C0@xxxxxx

> Control Panel
> System
> Advanced System Properties
> Advanced tab
> Startup and Recovery area, settings button
> Under System failure, uncheck Automatically restart
>
> If system is failing with a BSOD, then the error message will remain on
> screen.

Thanks Michael, I have configured it that way now. I did see one BSOD from
afd.sys a while ago but it disappeared before I could get the details.
Apparently a lot of people experience blue screens relating to this file
too.

--
And loving it,

-Qu0ll (Rare, not extinct)
_________________________________________________
Qu0llSixFour@xxxxxx
[Replace the "SixFour" with numbers to email me]

"Michael Walraven" <mexxwalraven@xxxxxx> wrote in message
news:0805E570-1D9F-4289-B1B7-BC0B56444F83@xxxxxx

> FYI, my c:\windows\system32\drivers\afd.sys
> is file version 6.0.6001.1800, dated 1/19/2008

Yes, that's the version I have too.

> as it is about network communications I would try finding the latest
> drivers for your Ethernet interface.

I'll look into it but I am pretty sure I have the latest Ethernet drivers.

--
And loving it,

-Qu0ll (Rare, not extinct)
_________________________________________________
Qu0llSixFour@xxxxxx
[Replace the "SixFour" with numbers to email me]

"Qu0ll" <Qu0llSixFour@xxxxxx> wrote in message
news:uj7bFUr6IHA.2332@xxxxxx

> "Michael Walraven" <mexxwalraven@xxxxxx> wrote in message
> news:5A6D9F74-69F9-4CC0-88CC-FCEE08D711C0@xxxxxx

>> Control Panel
>> System
>> Advanced System Properties
>> Advanced tab
>> Startup and Recovery area, settings button
>> Under System failure, uncheck Automatically restart
>>
>> If system is failing with a BSOD, then the error message will remain on
>> screen.

>
> Thanks Michael, I have configured it that way now. I did see one BSOD
> from afd.sys a while ago but it disappeared before I could get the
> details. Apparently a lot of people experience blue screens relating to
> this file too.

Look in the Event Viewer to find the error messages. Right-click My
Computer, Manage, Event Viewer. If you know the approximate time of the
BSOD or restart, it should be easy to find.

HTH
-pk

>
> --
> And loving it,
>
> -Qu0ll (Rare, not extinct)
> _________________________________________________
> Qu0llSixFour@xxxxxx
> [Replace the "SixFour" with numbers to email me]

"Patrick Keenan" <test@xxxxxx> wrote in message
news:#eO#jxu6IHA.4352@xxxxxx

[...]

> Look in the Event Viewer to find the error messages. Right-click My
> Computer, Manage, Event Viewer. If you know the approximate time of the
> BSOD or restart, it should be easy to find.

Thanks Patrick, I have checked the event log and although there is one event
that notes that the previous shutdown was unexpected, there are no errors or
other interesting events just before the actual time of the crash or after
it.

What does this indicate?

--
And loving it,

-Qu0ll (Rare, not extinct)
_________________________________________________
Qu0llSixFour@xxxxxx
[Replace the "SixFour" with numbers to email me]

One cause that cannot be recorded is an AC power failure (or power supply
failure),
Michael

"Qu0ll" <Qu0llSixFour@xxxxxx> wrote in message
news:eEai6bv6IHA.1204@xxxxxx

> "Patrick Keenan" <test@xxxxxx> wrote in message
> news:#eO#jxu6IHA.4352@xxxxxx
>
> [...]
>

>> Look in the Event Viewer to find the error messages. Right-click My
>> Computer, Manage, Event Viewer. If you know the approximate time of
>> the BSOD or restart, it should be easy to find.

>
> Thanks Patrick, I have checked the event log and although there is one
> event that notes that the previous shutdown was unexpected, there are no
> errors or other interesting events just before the actual time of the
> crash or after it.
>
> What does this indicate?
>
> --
> And loving it,
>
> -Qu0ll (Rare, not extinct)
> _________________________________________________
> Qu0llSixFour@xxxxxx
> [Replace the "SixFour" with numbers to email me]

"Michael Walraven" <mexxwalraven@xxxxxx> wrote in message
news:0805E570-1D9F-4289-B1B7-BC0B56444F83@xxxxxx

> as it is about network communications I would try finding the latest
> drivers for your Ethernet interface.

OK I have the BSOD info now. It's a DRIVER_IRQL_NOT_LESS_OR_EQUAL error in
afd.sys and it appears to be happening at around 5:45am each day. Just
before the crash, SQL Browser reports that it's unable to process a request
repeatedly but I can't see any other interesting events in the log.

My suspicion is that it has something to do with my Kaspersky Internet
Security 2009 application as previous afd.sys BSODs were identified as being
caused by Kaspersky. Windows doesn't tell me that with this one but perhaps
there is another bug in the latest version of KIS.

Any thoughts?

--
And loving it,

-Qu0ll (Rare, not extinct)
_________________________________________________
Qu0llSixFour@xxxxxx
[Replace the "SixFour" with numbers to email me]