From: OneDave on
I am experiencing what seem to be random Blue-Screen-of-Death errors on my
experimental Vista 64 machine. They don't correlate directly to any user
actions of mine. It does not happen in Safe Mode or Safe Mode with
Networking. I've done what I can by unloading software and driver, but this
is becoming over my head. I'm trying to avoid a complete re-install of Vista
64, if possible.

In antcipation of requests, the information below is the BSOD text and the
few reports I could find.

I would appreciate suggestions.

Thanks,
Dave

My configuration is:
Compaq Presario SR1630NX with an AMD Athalon 64 3500+ processor
Phoenix Technologies BIOS LTD 3.08,9/13/05
1 GB RAM
Vista Ultimate RC1 6.0.5600 Build 5600
Built-in graphics: Radeon Xpress 200
EVGA Video GeForce 7300 GT (NVidea G73) 512 MB PCI-E
GeForce-provided video driver nv3dum, nvd3dumx.dll
nviddmkm.sys driver, version 7.15.10.9685
No dual-boot partitions set up
All default installation selections

-------------------
This is what my blue screen of death looks like:

A problem has been detected and your computer has been shut down to prevent
damage
to your computer.

DRIVER_IRQL_NOT_LESS_OR_EQUAL

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 that any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or 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, press F8 to select Advanced setup options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x00000D1 (0x0000000000000010, 0x0000000000000002,
0x0000000000000000, 0
xFFFFF980007E9166)

*** ndis.sys - Address 0xFFFFF980007E9166 base at FFFFF9800065C000,
DateStamp
44f5584

Collecting data for crash dump...
Initializing disk for crash dump ...
Beginning dump of physical memory.
Dumping physical memory too disk: 100
Physical memory dump complete.
Contact your system admin or technical support group for further assistance.


After BSOD, at next system restart after User login, the following Windows
pop-up appears.


Windows has recovered from an unexpected shutdown.
Windows can check on line for a solution to the problem.
<View Problem details> <Check for solution> <Cancel>


The <View problem details> option gives the following:

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

Additional information about the problem:
BCCode: d1
BCP1: 0000000000000010
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF980007E9166
OS Version: 6_0_5600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini121006-07.dmp
C:\Users\Dave\AppData\Local\Temp\WER-49406-0.sysdata.xml
C:\Users\Dave\AppData\Local\Temp\WERE6F0.tmp.version.txt

Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409


C:\Windows\Minidump\Mini121006-07.dmp cannot be opened as text.

C:\Users\Dave\AppData\Local\Temp\WER-49406-0.sysdata.xml cannot be opened.

C:\Users\Dave\AppData\Local\Temp\WERE6F0.tmp.version.txt reads as follows:
Windows NT Version 6.0 Build: 5600
Product: workstation
Suite: (0x100) Single user TS Professional
Flavor: Free
Architecture: x64

If I reboot and select the check for solution option, I get a popup notice
that a device driver error occurred. When I click on the popup, I get a
window that contains:

Problem Reports and Solutions
Error caused by a device driver
Thank you for submitting an error report.
Problem description
A device driver installed on your computer caused the problem; however, we
Cannot determine the precise cause. To troubleshoot this problem, please see
Getting help.

Related links
Additional Technical Information
Error Message: STOP 0x000000EA
THREAD STUCK IN DEVICE DRIVER
(Q293078) <hyper link to: HTTP://Suppoprt.microsoft.com/?kbid=293078>

The referenced article discusses video driver errors and is a bit over my
head.



From: Colin Barnhorst on
Is there a BIOS update available? I have seen the 0x00000D1 error code once
in connection with a sound driver but I have no idea if it that specific.

"OneDave" <OneDave(a)discussions.microsoft.com> wrote in message
news:ACA1393C-ADE1-4256-ADD6-C43589F264DD(a)microsoft.com...
>I am experiencing what seem to be random Blue-Screen-of-Death errors on my
> experimental Vista 64 machine. They don't correlate directly to any user
> actions of mine. It does not happen in Safe Mode or Safe Mode with
> Networking. I've done what I can by unloading software and driver, but
> this
> is becoming over my head. I'm trying to avoid a complete re-install of
> Vista
> 64, if possible.
>
> In antcipation of requests, the information below is the BSOD text and the
> few reports I could find.
>
> I would appreciate suggestions.
>
> Thanks,
> Dave
>
> My configuration is:
> Compaq Presario SR1630NX with an AMD Athalon 64 3500+ processor
> Phoenix Technologies BIOS LTD 3.08,9/13/05
> 1 GB RAM
> Vista Ultimate RC1 6.0.5600 Build 5600
> Built-in graphics: Radeon Xpress 200
> EVGA Video GeForce 7300 GT (NVidea G73) 512 MB PCI-E
> GeForce-provided video driver nv3dum, nvd3dumx.dll
> nviddmkm.sys driver, version 7.15.10.9685
> No dual-boot partitions set up
> All default installation selections
>
> -------------------
> This is what my blue screen of death looks like:
>
> A problem has been detected and your computer has been shut down to
> prevent
> damage
> to your computer.
>
> DRIVER_IRQL_NOT_LESS_OR_EQUAL
>
> 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 that any new hardware or software is properly
> installed.
> If this is a new installation, ask your hardware or software manufacturer
> for any windows updates you might need.
>
> If problems continue, disable or remove any newly installed hardware
> or 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, press F8 to select Advanced setup options, and then
> select Safe Mode.
>
> Technical Information:
>
> *** STOP: 0x00000D1 (0x0000000000000010, 0x0000000000000002,
> 0x0000000000000000, 0
> xFFFFF980007E9166)
>
> *** ndis.sys - Address 0xFFFFF980007E9166 base at FFFFF9800065C000,
> DateStamp
> 44f5584
>
> Collecting data for crash dump...
> Initializing disk for crash dump ...
> Beginning dump of physical memory.
> Dumping physical memory too disk: 100
> Physical memory dump complete.
> Contact your system admin or technical support group for further
> assistance.
>
>
> After BSOD, at next system restart after User login, the following Windows
> pop-up appears.
>
>
> Windows has recovered from an unexpected shutdown.
> Windows can check on line for a solution to the problem.
> <View Problem details> <Check for solution> <Cancel>
>
>
> The <View problem details> option gives the following:
>
> Problem signature:
> Problem Event Name: BlueScreen
> OS Version: 6.0.5600.2.0.0.256.1
> Locale ID: 1033
>
> Additional information about the problem:
> BCCode: d1
> BCP1: 0000000000000010
> BCP2: 0000000000000002
> BCP3: 0000000000000000
> BCP4: FFFFF980007E9166
> OS Version: 6_0_5600
> Service Pack: 0_0
> Product: 256_1
>
> Files that help describe the problem:
> C:\Windows\Minidump\Mini121006-07.dmp
> C:\Users\Dave\AppData\Local\Temp\WER-49406-0.sysdata.xml
> C:\Users\Dave\AppData\Local\Temp\WERE6F0.tmp.version.txt
>
> Read our privacy statement:
> http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
>
>
> C:\Windows\Minidump\Mini121006-07.dmp cannot be opened as text.
>
> C:\Users\Dave\AppData\Local\Temp\WER-49406-0.sysdata.xml cannot be opened.
>
> C:\Users\Dave\AppData\Local\Temp\WERE6F0.tmp.version.txt reads as follows:
> Windows NT Version 6.0 Build: 5600
> Product: workstation
> Suite: (0x100) Single user TS Professional
> Flavor: Free
> Architecture: x64
>
> If I reboot and select the check for solution option, I get a popup notice
> that a device driver error occurred. When I click on the popup, I get a
> window that contains:
>
> Problem Reports and Solutions
> Error caused by a device driver
> Thank you for submitting an error report.
> Problem description
> A device driver installed on your computer caused the problem; however, we
> Cannot determine the precise cause. To troubleshoot this problem, please
> see
> Getting help.
>
> Related links
> Additional Technical Information
> Error Message: STOP 0x000000EA
> THREAD STUCK IN DEVICE DRIVER
> (Q293078) <hyper link to: HTTP://Suppoprt.microsoft.com/?kbid=293078>
>
> The referenced article discusses video driver errors and is a bit over my
> head.
>
>
>

From: Jane C on
ndis.sys= network driver interface. Check that you do have the Vista
drivers for you NIC and modem.

--
Jane, not plain ;) 64 bit enabled :-)
Batteries not included. Braincell on vacation ;-)
"OneDave" <OneDave(a)discussions.microsoft.com> wrote in message
news:ACA1393C-ADE1-4256-ADD6-C43589F264DD(a)microsoft.com...
>I am experiencing what seem to be random Blue-Screen-of-Death errors on my
> experimental Vista 64 machine. They don't correlate directly to any user
> actions of mine. It does not happen in Safe Mode or Safe Mode with
> Networking. I've done what I can by unloading software and driver, but
> this
> is becoming over my head. I'm trying to avoid a complete re-install of
> Vista
> 64, if possible.
>
> In antcipation of requests, the information below is the BSOD text and the
> few reports I could find.
>
> I would appreciate suggestions.
>
> Thanks,
> Dave
>
> My configuration is:
> Compaq Presario SR1630NX with an AMD Athalon 64 3500+ processor
> Phoenix Technologies BIOS LTD 3.08,9/13/05
> 1 GB RAM
> Vista Ultimate RC1 6.0.5600 Build 5600
> Built-in graphics: Radeon Xpress 200
> EVGA Video GeForce 7300 GT (NVidea G73) 512 MB PCI-E
> GeForce-provided video driver nv3dum, nvd3dumx.dll
> nviddmkm.sys driver, version 7.15.10.9685
> No dual-boot partitions set up
> All default installation selections
>
> -------------------
> This is what my blue screen of death looks like:
>
> A problem has been detected and your computer has been shut down to
> prevent
> damage
> to your computer.
>
> DRIVER_IRQL_NOT_LESS_OR_EQUAL
>
> 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 that any new hardware or software is properly
> installed.
> If this is a new installation, ask your hardware or software manufacturer
> for any windows updates you might need.
>
> If problems continue, disable or remove any newly installed hardware
> or 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, press F8 to select Advanced setup options, and then
> select Safe Mode.
>
> Technical Information:
>
> *** STOP: 0x00000D1 (0x0000000000000010, 0x0000000000000002,
> 0x0000000000000000, 0
> xFFFFF980007E9166)
>
> *** ndis.sys - Address 0xFFFFF980007E9166 base at FFFFF9800065C000,
> DateStamp
> 44f5584
>
> Collecting data for crash dump...
> Initializing disk for crash dump ...
> Beginning dump of physical memory.
> Dumping physical memory too disk: 100
> Physical memory dump complete.
> Contact your system admin or technical support group for further
> assistance.
>
>
> After BSOD, at next system restart after User login, the following Windows
> pop-up appears.
>
>
> Windows has recovered from an unexpected shutdown.
> Windows can check on line for a solution to the problem.
> <View Problem details> <Check for solution> <Cancel>
>
>
> The <View problem details> option gives the following:
>
> Problem signature:
> Problem Event Name: BlueScreen
> OS Version: 6.0.5600.2.0.0.256.1
> Locale ID: 1033
>
> Additional information about the problem:
> BCCode: d1
> BCP1: 0000000000000010
> BCP2: 0000000000000002
> BCP3: 0000000000000000
> BCP4: FFFFF980007E9166
> OS Version: 6_0_5600
> Service Pack: 0_0
> Product: 256_1
>
> Files that help describe the problem:
> C:\Windows\Minidump\Mini121006-07.dmp
> C:\Users\Dave\AppData\Local\Temp\WER-49406-0.sysdata.xml
> C:\Users\Dave\AppData\Local\Temp\WERE6F0.tmp.version.txt
>
> Read our privacy statement:
> http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
>
>
> C:\Windows\Minidump\Mini121006-07.dmp cannot be opened as text.
>
> C:\Users\Dave\AppData\Local\Temp\WER-49406-0.sysdata.xml cannot be opened.
>
> C:\Users\Dave\AppData\Local\Temp\WERE6F0.tmp.version.txt reads as follows:
> Windows NT Version 6.0 Build: 5600
> Product: workstation
> Suite: (0x100) Single user TS Professional
> Flavor: Free
> Architecture: x64
>
> If I reboot and select the check for solution option, I get a popup notice
> that a device driver error occurred. When I click on the popup, I get a
> window that contains:
>
> Problem Reports and Solutions
> Error caused by a device driver
> Thank you for submitting an error report.
> Problem description
> A device driver installed on your computer caused the problem; however, we
> Cannot determine the precise cause. To troubleshoot this problem, please
> see
> Getting help.
>
> Related links
> Additional Technical Information
> Error Message: STOP 0x000000EA
> THREAD STUCK IN DEVICE DRIVER
> (Q293078) <hyper link to: HTTP://Suppoprt.microsoft.com/?kbid=293078>
>
> The referenced article discusses video driver errors and is a bit over my
> head.
>
>
>

From: Jane C on
Correction: check that you do have the appropriate Vista drivers for your
NIC and modem.

--
Jane, not plain ;) 64 bit enabled :-)
Batteries not included. Braincell on vacation ;-)
"Jane C" <jellybean(a)NOSPAMxjgarage.org> wrote in message
news:59EDCE71-7277-44B8-B33F-E85E338D0754(a)microsoft.com...
> ndis.sys= network driver interface. Check that you do have the Vista
> drivers for you NIC and modem.
>
> --
> Jane, not plain ;) 64 bit enabled :-)
> Batteries not included. Braincell on vacation ;-)
> "OneDave" <OneDave(a)discussions.microsoft.com> wrote in message
> news:ACA1393C-ADE1-4256-ADD6-C43589F264DD(a)microsoft.com...
>>I am experiencing what seem to be random Blue-Screen-of-Death errors on my
>> experimental Vista 64 machine. They don't correlate directly to any user
>> actions of mine. It does not happen in Safe Mode or Safe Mode with
>> Networking. I've done what I can by unloading software and driver, but
>> this
>> is becoming over my head. I'm trying to avoid a complete re-install of
>> Vista
>> 64, if possible.
>>
>> In antcipation of requests, the information below is the BSOD text and
>> the
>> few reports I could find.
>>
>> I would appreciate suggestions.
>>
>> Thanks,
>> Dave
>>
>> My configuration is:
>> Compaq Presario SR1630NX with an AMD Athalon 64 3500+ processor
>> Phoenix Technologies BIOS LTD 3.08,9/13/05
>> 1 GB RAM
>> Vista Ultimate RC1 6.0.5600 Build 5600
>> Built-in graphics: Radeon Xpress 200
>> EVGA Video GeForce 7300 GT (NVidea G73) 512 MB PCI-E
>> GeForce-provided video driver nv3dum, nvd3dumx.dll
>> nviddmkm.sys driver, version 7.15.10.9685
>> No dual-boot partitions set up
>> All default installation selections
>>
>> -------------------
>> This is what my blue screen of death looks like:
>>
>> A problem has been detected and your computer has been shut down to
>> prevent
>> damage
>> to your computer.
>>
>> DRIVER_IRQL_NOT_LESS_OR_EQUAL
>>
>> 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 that any new hardware or software is properly
>> installed.
>> If this is a new installation, ask your hardware or software manufacturer
>> for any windows updates you might need.
>>
>> If problems continue, disable or remove any newly installed hardware
>> or 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, press F8 to select Advanced setup options, and then
>> select Safe Mode.
>>
>> Technical Information:
>>
>> *** STOP: 0x00000D1 (0x0000000000000010, 0x0000000000000002,
>> 0x0000000000000000, 0
>> xFFFFF980007E9166)
>>
>> *** ndis.sys - Address 0xFFFFF980007E9166 base at
>> FFFFF9800065C000,
>> DateStamp
>> 44f5584
>>
>> Collecting data for crash dump...
>> Initializing disk for crash dump ...
>> Beginning dump of physical memory.
>> Dumping physical memory too disk: 100
>> Physical memory dump complete.
>> Contact your system admin or technical support group for further
>> assistance.
>>
>>
>> After BSOD, at next system restart after User login, the following
>> Windows
>> pop-up appears.
>>
>>
>> Windows has recovered from an unexpected shutdown.
>> Windows can check on line for a solution to the problem.
>> <View Problem details> <Check for solution> <Cancel>
>>
>>
>> The <View problem details> option gives the following:
>>
>> Problem signature:
>> Problem Event Name: BlueScreen
>> OS Version: 6.0.5600.2.0.0.256.1
>> Locale ID: 1033
>>
>> Additional information about the problem:
>> BCCode: d1
>> BCP1: 0000000000000010
>> BCP2: 0000000000000002
>> BCP3: 0000000000000000
>> BCP4: FFFFF980007E9166
>> OS Version: 6_0_5600
>> Service Pack: 0_0
>> Product: 256_1
>>
>> Files that help describe the problem:
>> C:\Windows\Minidump\Mini121006-07.dmp
>> C:\Users\Dave\AppData\Local\Temp\WER-49406-0.sysdata.xml
>> C:\Users\Dave\AppData\Local\Temp\WERE6F0.tmp.version.txt
>>
>> Read our privacy statement:
>> http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
>>
>>
>> C:\Windows\Minidump\Mini121006-07.dmp cannot be opened as text.
>>
>> C:\Users\Dave\AppData\Local\Temp\WER-49406-0.sysdata.xml cannot be
>> opened.
>>
>> C:\Users\Dave\AppData\Local\Temp\WERE6F0.tmp.version.txt reads as
>> follows:
>> Windows NT Version 6.0 Build: 5600
>> Product: workstation
>> Suite: (0x100) Single user TS Professional
>> Flavor: Free
>> Architecture: x64
>>
>> If I reboot and select the check for solution option, I get a popup
>> notice
>> that a device driver error occurred. When I click on the popup, I get a
>> window that contains:
>>
>> Problem Reports and Solutions
>> Error caused by a device driver
>> Thank you for submitting an error report.
>> Problem description
>> A device driver installed on your computer caused the problem; however,
>> we
>> Cannot determine the precise cause. To troubleshoot this problem, please
>> see
>> Getting help.
>>
>> Related links
>> Additional Technical Information
>> Error Message: STOP 0x000000EA
>> THREAD STUCK IN DEVICE DRIVER
>> (Q293078) <hyper link to: HTTP://Suppoprt.microsoft.com/?kbid=293078>
>>
>> The referenced article discusses video driver errors and is a bit over my
>> head.
>>
>>
>>
>

From: Charlie Russel - MVP on
This is a very old build (5600). Many things have changed since then. I'd
suggest you use the RTM build. It's a good deal more stable and have much
better drivers in it. NDIS is networking, so it appears to be related to
networking.

--
Charlie.
http://msmvps.com/xperts64


"OneDave" <OneDave(a)discussions.microsoft.com> wrote in message
news:ACA1393C-ADE1-4256-ADD6-C43589F264DD(a)microsoft.com...
>I am experiencing what seem to be random Blue-Screen-of-Death errors on my
> experimental Vista 64 machine. They don't correlate directly to any user
> actions of mine. It does not happen in Safe Mode or Safe Mode with
> Networking. I've done what I can by unloading software and driver, but
> this
> is becoming over my head. I'm trying to avoid a complete re-install of
> Vista
> 64, if possible.
>
> In antcipation of requests, the information below is the BSOD text and the
> few reports I could find.
>
> I would appreciate suggestions.
>
> Thanks,
> Dave
>
> My configuration is:
> Compaq Presario SR1630NX with an AMD Athalon 64 3500+ processor
> Phoenix Technologies BIOS LTD 3.08,9/13/05
> 1 GB RAM
> Vista Ultimate RC1 6.0.5600 Build 5600
> Built-in graphics: Radeon Xpress 200
> EVGA Video GeForce 7300 GT (NVidea G73) 512 MB PCI-E
> GeForce-provided video driver nv3dum, nvd3dumx.dll
> nviddmkm.sys driver, version 7.15.10.9685
> No dual-boot partitions set up
> All default installation selections
>
> -------------------
> This is what my blue screen of death looks like:
>
> A problem has been detected and your computer has been shut down to
> prevent
> damage
> to your computer.
>
> DRIVER_IRQL_NOT_LESS_OR_EQUAL
>
> 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 that any new hardware or software is properly
> installed.
> If this is a new installation, ask your hardware or software manufacturer
> for any windows updates you might need.
>
> If problems continue, disable or remove any newly installed hardware
> or 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, press F8 to select Advanced setup options, and then
> select Safe Mode.
>
> Technical Information:
>
> *** STOP: 0x00000D1 (0x0000000000000010, 0x0000000000000002,
> 0x0000000000000000, 0
> xFFFFF980007E9166)
>
> *** ndis.sys - Address 0xFFFFF980007E9166 base at FFFFF9800065C000,
> DateStamp
> 44f5584
>
> Collecting data for crash dump...
> Initializing disk for crash dump ...
> Beginning dump of physical memory.
> Dumping physical memory too disk: 100
> Physical memory dump complete.
> Contact your system admin or technical support group for further
> assistance.
>
>
> After BSOD, at next system restart after User login, the following Windows
> pop-up appears.
>
>
> Windows has recovered from an unexpected shutdown.
> Windows can check on line for a solution to the problem.
> <View Problem details> <Check for solution> <Cancel>
>
>
> The <View problem details> option gives the following:
>
> Problem signature:
> Problem Event Name: BlueScreen
> OS Version: 6.0.5600.2.0.0.256.1
> Locale ID: 1033
>
> Additional information about the problem:
> BCCode: d1
> BCP1: 0000000000000010
> BCP2: 0000000000000002
> BCP3: 0000000000000000
> BCP4: FFFFF980007E9166
> OS Version: 6_0_5600
> Service Pack: 0_0
> Product: 256_1
>
> Files that help describe the problem:
> C:\Windows\Minidump\Mini121006-07.dmp
> C:\Users\Dave\AppData\Local\Temp\WER-49406-0.sysdata.xml
> C:\Users\Dave\AppData\Local\Temp\WERE6F0.tmp.version.txt
>
> Read our privacy statement:
> http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
>
>
> C:\Windows\Minidump\Mini121006-07.dmp cannot be opened as text.
>
> C:\Users\Dave\AppData\Local\Temp\WER-49406-0.sysdata.xml cannot be opened.
>
> C:\Users\Dave\AppData\Local\Temp\WERE6F0.tmp.version.txt reads as follows:
> Windows NT Version 6.0 Build: 5600
> Product: workstation
> Suite: (0x100) Single user TS Professional
> Flavor: Free
> Architecture: x64
>
> If I reboot and select the check for solution option, I get a popup notice
> that a device driver error occurred. When I click on the popup, I get a
> window that contains:
>
> Problem Reports and Solutions
> Error caused by a device driver
> Thank you for submitting an error report.
> Problem description
> A device driver installed on your computer caused the problem; however, we
> Cannot determine the precise cause. To troubleshoot this problem, please
> see
> Getting help.
>
> Related links
> Additional Technical Information
> Error Message: STOP 0x000000EA
> THREAD STUCK IN DEVICE DRIVER
> (Q293078) <hyper link to: HTTP://Suppoprt.microsoft.com/?kbid=293078>
>
> The referenced article discusses video driver errors and is a bit over my
> head.
>
>
>