Jakke Skrevet 17. juli 2009 Del Skrevet 17. juli 2009 Får diverse ulike BSoD ved spilling av Age of Conan. En på win32k.sys, og en på IRQL_NOT_LESS_OR_EQUAL. Fikk ikke med meg numrene, men om noen vet hvor loggene ligger, så pling på. Er Vista x64 Lenke til kommentar
Jakke Skrevet 17. juli 2009 Forfatter Del Skrevet 17. juli 2009 Laster ned debugging fra Microsoft nå. Skal sjekke hva den får ut av memory.dmp Lenke til kommentar
Jakke Skrevet 17. juli 2009 Forfatter Del Skrevet 17. juli 2009 En stk minidump. Den siste av tre fra tre BSOD Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\Mini071709-03.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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff800`01a13000 PsLoadedModuleList = 0xfffff800`01bd8db0 Debug session time: Fri Jul 17 06:42:43.696 2009 (GMT+2) System Uptime: 0 days 0:19:06.645 ********************************************************************* * 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 A, {fffffa8028898010, 2, 1, fffff80001a14767} ***** 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 : ntoskrnl.exe ( nt+1767 ) Followup: MachineOwner --------- Og de to første sier Win32k.sys. Laster ned 50 updates fra Windows update. Eneste som er installert på PCen er: AoC Drivere Debugger Lenke til kommentar
Locklear Skrevet 17. juli 2009 Del Skrevet 17. juli 2009 Hadde kjørt en sjekke på RAM'en som første forsøk på feilsøking, spesielt når det er så lite installert på maskinen. memtest86+ eller liknende. Regner med at du bruker siste drivere. Lenke til kommentar
SilentNET Skrevet 17. juli 2009 Del Skrevet 17. juli 2009 Du må legge til følgende i Symbol Path: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols Deretter kan du kjøre analysen på nytt. Så kanskje vi får noe fornuftig ut av den. Men som Locklear sier, det hadde vært greit å kjøre en test av minne, for å se om det kan være feil der. Det kan også være innstillinger i BIOS (er systemet overklokket?) - merk at man i enkelte tilfeller kan få feil innstillinger for minne i BIOS ved å bruke auto på en del settings. Det beste er egentlig å finne ut hva minnebrikkene er spesifisert for, også sette dette manuelt. Enkelte brikker klarer faktisk ikke original hastighet heller. Har du gjort noe som helst endringer i BIOS? Prøvd å sette ned hastighet på minnet ditt? Jeg ville kanskje ha prøvd det aller først. Resett BIOS, flash til nyeste versjon, prøv igjen. Fortsatt feil, juster _ned_ hastighet og timings på minnet ditt (det vil si, øk timings, så dem blir slappere - høyere tall). Prøv igjen, fortsatt feil? Lenke til kommentar
fenderebest Skrevet 17. juli 2009 Del Skrevet 17. juli 2009 Enten legg ved minidump filene eller legg til Symbol og Image path i debuggeren og post outputet av !analyze -v her. Har skrevet litt om emnet her: https://www.diskusjon.no/index.php?showtopic=919442 (CTRL+S i debuggeren for å sette symbol path, CTRL+I for å sette image path) Symbol path og image path skal være likens. Lenke til kommentar
SilentNET Skrevet 17. juli 2009 Del Skrevet 17. juli 2009 Hvis du mener at Age of Conan fungerer i XP, men ikke nå i Vista 64bit så er det nesten garantert et driverproblem. For da har vi nesten utelukket hardwareproblemer. Hvis du har 32bit XP og 64bit Vista kan det allikevel være minne. Spørs litt hvor mye minne du har. I 64bit får du jo tilgang til mer minne enn du gjør i XP (32bit) og dermed kan feilen være i en del av minne som XP ikke får tilgang til. Men mest sannsynlig er det da et driverproblem i Vista. Lenke til kommentar
Jakke Skrevet 18. juli 2009 Forfatter Del Skrevet 18. juli 2009 Har 8GB RAM, så jeg kjører nok 64bit XP også Problemet er at i XP så kjører jeg så mye lavere FPS enn i Vista. Mange som har vært plaget med det. Men har kjøpt meg en 500GB disk, skal prøve å lagre det jeg MÅ ha på den disken (1TB inn på 500gb=masse sletting) så skal jeg installere Vista på den andre og partisjonere opp til tre disker: Vista, Spill og Programmer, Mac OS X (ikke brukbar i Win), pluss backupdisken da Lenke til kommentar
Anbefalte innlegg
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 kontoLogg inn
Har du allerede en konto? Logg inn her.
Logg inn nå