[LØST] Lese dump filer

6 innlegg i emnet

Skrevet

Hei.

For det første. så var jeg litt usikker på hvor denne tråden skulle plaseres, men da OS gjelder Win 7 håper jeg den er på rett plass:)

Problem:

Har hatt 2 blue-screen siden jeg la inn RC utgaven, og da er det generert dump filer, men får ikke til å lese ut av de..

Har lastet den WinDebugg og symbols, men klarer ikke få dette til å passe sammen..

Er det noen her som ev kan lese ut av dumpfilene? Har kjørt XP fast og stødig uten noe BS, så lurer på om det kan være noe driverkluss.

Men legger med det som jeg får opp i de 2 filene, så kan noen se om det er rett:

Dump 1 - 050609-21140-01.dmp (klikk for å vise/skjule)

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\mini2.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?ffffffff`80d8ada4?

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\ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows 7 Kernel Version 7100 MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7100.0.x86fre.winmain_win7rc.090421-1700

Machine Name:

Kernel base = 0x82804000 PsLoadedModuleList = 0x82943570

Debug session time: Wed May 6 17:45:12.307 2009 (GMT+2)

System Uptime: 0 days 11:25:10.367

*********************************************************************

* 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\ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Loading Kernel Symbols

...............................................................

................................................................

........................

Loading User Symbols

Loading unloaded module list

....

Dump 2 - 050609-26359-01.dmp (klikk for å vise/skjule)

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\mini1.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\ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows 7 Kernel Version 7100 MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7100.0.x86fre.winmain_win7rc.090421-1700

Machine Name:

Kernel base = 0x8280a000 PsLoadedModuleList = 0x82949570

Debug session time: Wed May 6 21:57:54.861 2009 (GMT+2)

System Uptime: 0 days 0:02:10.783

*********************************************************************

* 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\ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Loading Kernel Symbols

...............................................................

................................................................

......................

Loading User Symbols

Loading unloaded module list

....

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {80917fb8, 2, 0, 80917fb8}

*** WARNING: Unable to verify timestamp for dxgmms1.sys

*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys

*** WARNING: Unable to verify timestamp for dxgkrnl.sys

*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys

*** WARNING: Unable to verify timestamp for atikmdag.sys

*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

***** 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 : dxgmms1.sys ( dxgmms1+b01d )

Followup: MachineOwner

---------

Er det noe skikkelig galt her?

Håper på kjappe svar/tips :)

Mvh

0

Del dette innlegget


Lenke til innlegg
Del på andre sider

Skrevet

Ja kan se på dem,men da må du poste dmp-filene.

Dette er ting en må regne med når win 7 ikke er ferdig og drivere som regel gir bluesrceen ikke er ferdig utarbeidet.

0

Del dette innlegget


Lenke til innlegg
Del på andre sider

Skrevet

Ja kan se på dem,men da må du poste dmp-filene.

Dette er ting en må regne med når win 7 ikke er ferdig og drivere som regel gir bluesrceen ikke er ferdig utarbeidet.

Hei.

Ja, hadde jo ikke forventet noe annet egentlig, men kjørte jo beta i lang tid uten problemer..

Men her er linkene til dumpfilene...:

http://s1.filesdump.com/file/a747647ea91c/mini1.dmp.html

http://s3.filesdump.com/file/e77e1842a1c9/mini2.dmp.html

Mvh

0

Del dette innlegget


Lenke til innlegg
Del på andre sider

Skrevet (endret)

Slår ut på "dxgmms1.sys" directX driver for win 7.

I stacken ser jeg at den kontakter "atikmdag.sys"

Da heller konklusjonen mot skjermkortdrivere som kræsjer mot directX

Prøve og finne nye skjermkortdrivere.

Stikkord for søk google.

"dxgmms1.sys", "atikmdag.sys", "win 7"

Endret av snippsat
0

Del dette innlegget


Lenke til innlegg
Del på andre sider

Skrevet

Slår ut på "dxgmms1.sys" directX driver for win 7.

I stacken ser jeg at den kontakter "atikmdag.sys"

Da heller konklusjonen mot skjermkortdrivere som kræsjer mot directX

Prøve og finne nye skjermkortdrivere.

Stikkord for søk google.

"dxgmms1.sys", "atikmdag.sys", "win 7"

Hei.

Takker for den:)

Da sliter jeg litt, da jeg har prøvd legge inn de siste driverne til ATI kortet, som desverre ikke er kompatibelt med Win 7.. Enda..

Men da får jeg bare se hvordan dette går da:=)

Mvh

0

Del dette innlegget


Lenke til innlegg
Del på andre sider

Skrevet

Da er det på tide å oppdatere tråden og sette den som løst, da maskinen har snurret i dagevis uten blåskjerm..

Var antagelig bare noe "smuss" på driverne :)

Mvh

0

Del dette innlegget


Lenke til innlegg
Del på andre sider

Opprett en konto eller logg inn for å kommentere

Du må være et medlem for å kunne skrive en kommentar

Opprett konto

Det er enkelt å melde seg inn for å starte en ny konto!


Start en konto

Logg inn

Har du allerede en konto? Logg inn her.


Logg inn nå

  • Hvem er aktive   0 medlemmer

    Ingen innloggede medlemmer aktive