Prev: Romdump.com error on administrative logon
Next: ATI Catalyst 8.31.100.3.2.1 for Vista x64 released
From: John Barnes on 11 Dec 2006 21:52
Where I live downloading something the size of Vista is not feasible. I
also would want to use it for daily activities, which the license for MSDN
and TechNet don't allow. Guess the rumor of a trial was false, so that
leaves 30 Jan. Based on the CPP RC1 problems I have had, I doubt I will be
on the Vista bandwagon for some time thereafter.
I will be using RC1 as long as it works and then decide if X64 or Vista64
makes more sense.


"Charlie Russel - MVP" <charlie(a)mvKILLALLSPAMMERSps.org> wrote in message
news:1BE71FC3-D697-43AC-AE06-C224BFB1DE99(a)microsoft.com...
> If you were on the beta, and filed bugs, you'd have it. If you have
> TechNet Plus or MSDN, you'd have it. If you are on an Enterprise Agreement
> or Software Assurance, you'd have it.
>
> If you weren't on any of the above, then yes it could be a problem.
> Frankly, I don't run beta software under those circumstances, but I can
> understand someone might. I'd also recognize that when I'm running an old
> build, things happen. In this case, I'm betting a bad network driver,
> which doesn't surprise me much.
>
> --
> Charlie.
> http://msmvps.com/xperts64
>
>
> "John Barnes" <jbarnes(a)email.net> wrote in message
> news:uQd8p4RHHHA.4712(a)TK2MSFTNGP04.phx.gbl...
>> Nice idea Charlie, but many, if not most, of us have no access to
>> anything after RC1. :-((
>>
>>
>> "Charlie Russel - MVP" <charlie(a)mvKILLALLSPAMMERSps.org> wrote in message
>> news:F75DB421-2D72-4B0E-82D0-989F2970369E(a)microsoft.com...
>>> 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.
>>>>
>>>>
>>>>
>>>
>>
>

From: Charlie Russel - MVP on 12 Dec 2006 03:10
Understood. FWIW, RTM is a good deal more stable and quite a bit faster than
RC1.

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


"John Barnes" <jbarnes(a)email.net> wrote in message
news:OUcthiZHHHA.5104(a)TK2MSFTNGP03.phx.gbl...
> Where I live downloading something the size of Vista is not feasible. I
> also would want to use it for daily activities, which the license for MSDN
> and TechNet don't allow. Guess the rumor of a trial was false, so that
> leaves 30 Jan. Based on the CPP RC1 problems I have had, I doubt I will
> be on the Vista bandwagon for some time thereafter.
> I will be using RC1 as long as it works and then decide if X64 or Vista64
> makes more sense.
>
>
> "Charlie Russel - MVP" <charlie(a)mvKILLALLSPAMMERSps.org> wrote in message
> news:1BE71FC3-D697-43AC-AE06-C224BFB1DE99(a)microsoft.com...
>> If you were on the beta, and filed bugs, you'd have it. If you have
>> TechNet Plus or MSDN, you'd have it. If you are on an Enterprise
>> Agreement or Software Assurance, you'd have it.
>>
>> If you weren't on any of the above, then yes it could be a problem.
>> Frankly, I don't run beta software under those circumstances, but I can
>> understand someone might. I'd also recognize that when I'm running an old
>> build, things happen. In this case, I'm betting a bad network driver,
>> which doesn't surprise me much.
>>
>> --
>> Charlie.
>> http://msmvps.com/xperts64
>>
>>
>> "John Barnes" <jbarnes(a)email.net> wrote in message
>> news:uQd8p4RHHHA.4712(a)TK2MSFTNGP04.phx.gbl...
>>> Nice idea Charlie, but many, if not most, of us have no access to
>>> anything after RC1. :-((
>>>
>>>
>>> "Charlie Russel - MVP" <charlie(a)mvKILLALLSPAMMERSps.org> wrote in
>>> message news:F75DB421-2D72-4B0E-82D0-989F2970369E(a)microsoft.com...
>>>> 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.
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>

From: jannerhank on 15 Dec 2006 14:40
Hi Jane,
Where did you get the Vista-64 Realtek driver from please? I
can't get my LAN working and my Linksys wireless card is waiting for Linksys
to finish writing the Vista drivers. I am using an older PC now.

OPEN QUESTION. "Where can you get a list of Hardware I.D.'s from? I got a
ACP\PNPB02F and *PNPB02F fault. It could mean anything but I need to know
what.

--
jannerhank


"OneDave" wrote:

> I checked and found a Vista-64 specific RealTek NIC driver & installed it.
> Unfortunately, the crash still happens.
> --
> Thanks
> Dave
>
> "Jane C" wrote:
>
> > 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 15 Dec 2006 16:09
PNPB02F refers to Gameport. As gameports are now not supported, you can
disable it in your BIOS.

Personally I don't have Realtek NIC. Have you tried the Realtek support
site?

--
Jane, not plain ;) 64 bit enabled :-)
Batteries not included. Braincell on vacation ;-)
"jannerhank" <jannerhank(a)discussions.microsoft.com> wrote in message
news:5392C990-8BB7-4928-BB73-EB599557D48F(a)microsoft.com...
> Hi Jane,
> Where did you get the Vista-64 Realtek driver from please? I
> can't get my LAN working and my Linksys wireless card is waiting for
> Linksys
> to finish writing the Vista drivers. I am using an older PC now.
>
> OPEN QUESTION. "Where can you get a list of Hardware I.D.'s from? I got a
> ACP\PNPB02F and *PNPB02F fault. It could mean anything but I need to know
> what.
>
> --
> jannerhank
>
>
> "OneDave" wrote:
>
>> I checked and found a Vista-64 specific RealTek NIC driver & installed
>> it.
>> Unfortunately, the crash still happens.
>> --
>> Thanks
>> Dave
>>
>> "Jane C" wrote:
>>
>> > 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: jannerhank on 16 Dec 2006 05:48
Onedave,
Can you please tell me where you got the 64 bit Realtek
driver from? I have been looking for almost a month and never found one. Can
not get the LAN to work at all, beleave it is the realtek driver.

Regards

jannerhank


"Charlie Russel - MVP" wrote:

> Afraid not. If you had an EA or SA agreement they are now available that
> way. Otherwise, you get to wait, I'm afraid. :(
>
> --
> Charlie.
> http://msmvps.com/xperts64
>
>
> "OneDave" <OneDave(a)discussions.microsoft.com> wrote in message
> news:9987903E-39B2-419D-BCC4-A82AF6B7ACE9(a)microsoft.com...
> > Hi Charlie,
> > I ran older beta versions of Vista, but I did not submit bugs that I
> > recall.
> > I don't think I was in any official bete test program. I was focused on
> > beta OneNote 2007, for which I did submit bugs. I don't think I have
> > access
> > to TechNet or MSDN, unless my Registered Partner status gets me that. Can
> > you suggest where I might get access to a later version of Vista to tide
> > me
> > over until the release?
> > --
> > Thanks
> > Dave
> >
> > "Charlie Russel - MVP" wrote:
> >
> >> 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.
> >> >
> >> >
> >> >
> >>
>
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Romdump.com error on administrative logon
Next: ATI Catalyst 8.31.100.3.2.1 for Vista x64 released