8800 gtx, FX5200 og Vista!
KjetilAK
Har et 8800GTX PCI-e skjermkort og et FX5200 PCI skjermkort. Fungerer fint i
XP. men får bare BSOD i Vista. Må deaktivere FX5200-kortet for å få Vista
til å starte opp. Har prøvd ulike drivere for Vista, men det ser ikke ut til
å hjelpe. Noen som vet om en løsning eller "work-around"?
HK: Gigabyte GA-P35-DS3R (rev. 2.1)
CPU: Intel C2D-E8400
Med vennlig hilsen
KjetilAK
Clas Mehus
wrote:
Hva sier BSOD-en?
--
Clas Mehus
- "Den som har flest prylar när han dör vinner..."
KjetilAK
> --
> Clas Mehus
Har du noen anelse om hvor jeg finner en fil med de opplysninger du
etterspør? La merke til at Vista dumpet et eller annet og at det skal
befinne seg i en mappe på disken med Vista. Men jeg vet ikke hvor, eller hva
filen skal hete..
KjetilAK
KjetilAK
"Clas Mehus" <clas....@idg.no> skrev i melding
news:ugk0r3tma66ie216v...@4ax.com...
> On Mon, 11 Feb 2008 14:40:11 +0100, "KjetilAK" <kje...@kaltdalen.net>
> wrote:
>
>>Hei.
>>
>>Har et 8800GTX PCI-e skjermkort og et FX5200 PCI skjermkort. Fungerer fint
>>i
>>XP. men får bare BSOD i Vista. Må deaktivere FX5200-kortet for å få Vista
>>til å starte opp. Har prøvd ulike drivere for Vista, men det ser ikke ut
>>til
>>å hjelpe. Noen som vet om en løsning eller "work-around"?
>>
>>HK: Gigabyte GA-P35-DS3R (rev. 2.1)
>>CPU: Intel C2D-E8400
>
> Hva sier BSOD-en?
Har funnet noen opplysninger som kanskje kan hjelpe. Klarer å rekonstruere
hendelsesforløpet om det skulle bli nødvendig.
Fant en fil med disse opplysningene:
Problemsignatur:
Navn på problemhendelse: BlueScreen
OS-versjon: 6.0.6000.2.0.0.768.3
ID for nasjonal innstilling: 1044
Tilleggsinformasjon om problemet:
BCCode: d1
BCP1: 8AC4E930
BCP2: 00000002
BCP3: 00000008
BCP4: 8AC4E930
OS Version: 6_0_6000
Service Pack: 0_0
Product: 768_1
Har lastet ned microsoft debugger. Blir litt vel avansert for meg. Men fikk
åpnet .dmp-filen. Her er innholdet i den:
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\Windows\Minidump\Mini021108-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntkrnlpa.exe
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Mon Feb 11 18:54:12.246 2008 (GMT+1)
System Uptime: 0 days 0:06:52.120
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntkrnlpa.exe
Loading Kernel Symbols
.................................................................................................................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {8ac4e930, 2, 8, 8ac4e930}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : nvlddmkm.sys ( nvlddmkm+86930 )
Followup: MachineOwner
---------
Håper dette hjelper...
Med vennlig hilsen
KjetilAK
KjetilAK
Har jeg gjort noe galt nå igjen?