|
|||||||
|
|
|
 |
|
|
Strumenti |
18-02-2008, 21:30
|
#1 |
|
Senior Member
Iscritto dal: Sep 2002
Città: Como - Provincia
Messaggi: 4534
|
Crash con schermate Blu - Aiuto
Ogni tanto il mio nuovo PC, che vedete in firma, di botto crasha e da una schermata blu. Nono riesco a capire se è un problema hardware o software.
All'inizio pensavo fosse cola delle Ram downvoltate, ho messo i voltaggi a posto e crashava cmq. A un certo punto vista mi da un messaggio che è colpa della scheda video (non si capisce se driver o hardware). Ho appena fatto girare in loop 4 volte il 3dMark06 con tutto al massimo per stressare la scheda video, e ha passoto tutto tranquillamente. Ho provato a stressare ram e processore con prime 95 per 1 ora e mezza nulla. Cmq i crash persistono. Quello che mi sembra strano è che ho provato più sistemi operativi (Win XP Pro, Vista ultimate 32bit, Vista ultimate 64bit), e in tutti crasha, quindi mi pare strano che sia un problema software. Posto qui sotto gli errori rilevati dal "Visualizzatore Eventi", spero che qualcuno ci capisca un pò più di me: Errore di schermata Blu: Codice:
Nome registro: System
Origine: EventLog
Data: 18/02/2008 8.56.59
ID evento: 6008
Categoria attività:Nessuno
Livello: Errore
Parole chiave: Classico
Utente: N/D
Computer: PC-Wizard
Descrizione:
Precedente arresto del sistema inatteso a 8.53.07 su 18/02/2008.
XML evento:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6008</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2008-02-18T07:56:59.000Z" />
<EventRecordID>15209</EventRecordID>
<Channel>System</Channel>
<Computer>PC-Wizard</Computer>
<Security />
</System>
<EventData>
<Data>8.53.07</Data>
<Data>18/02/2008</Data>
<Data>
</Data>
<Data>
</Data>
<Data>38599</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>D8070200010012000800350007009700D80702000100120007003500070097003C0000003C000000000000000000000000000000000000000100000000000000</Binary>
</EventData>
</Event>
Codice:
Nome registro: System
Origine: Application Popup
Data: 18/02/2008 21.07.01
ID evento: 1060
Categoria attività:Nessuno
Livello: Errore
Parole chiave: Classico
Utente: N/D
Computer: PC-Wizard
Descrizione:
Caricamento del driver \??\C:\Windows\SysWow64\drivers\PciBus.sys bloccato a causa di incompatibilità con il sistema in uso. Rivolgersi al fornitore del software per richiedere una versione compatibile del driver.
XML evento:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Popup" />
<EventID Qualifiers="49152">1060</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2008-02-18T20:07:01.865Z" />
<EventRecordID>15275</EventRecordID>
<Channel>System</Channel>
<Computer>PC-Wizard</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>\??\C:\Windows\SysWow64\drivers\PciBus.sys</Data>
<Binary>000000000200300000000000240400C0000000006B0300C000000000000000000000000000000000</Binary>
</EventData>
</Event>
__________________
Intel Core i7 2600 - Zalman CNPS10X Performa - Asus P8P67 B3 - Corsair Vengeance 2x4Gb 1600Mhz 8-8-8-24 - Sapphire Radeon 6950@6970 2Gb - OCZ Agility 3 120GB + 2 x Seagate 500Gb SataII Raid - Samsung T220HD - Corsair 650W - Corsair Graphite 600T - Sony 7263S |
|
|
|
18-02-2008, 23:11
|
#2 |
|
Senior Member
Iscritto dal: Mar 2005
Messaggi: 4959
|
Prova ad identificare il driver colpevole (ammesso che sia un problema software) usando WinDbg.
__________________
Cerchi software open source? Vieni su OpenWanted e aiutami a creare la Lista Open!! -> Elenco BUG di Windows 7 <- |
|
|
|
|
19-02-2008, 09:46
|
#3 | |
|
Senior Member
Iscritto dal: Sep 2002
Città: Como - Provincia
Messaggi: 4534
|
Quote:
Sono sempre più convinto che sia un problema software legato al bus PCI, o di qualche conflitto tra driver. Stasera provo a staccare pure la Sk TV che ho. Io odio la pinnacle
__________________
Intel Core i7 2600 - Zalman CNPS10X Performa - Asus P8P67 B3 - Corsair Vengeance 2x4Gb 1600Mhz 8-8-8-24 - Sapphire Radeon 6950@6970 2Gb - OCZ Agility 3 120GB + 2 x Seagate 500Gb SataII Raid - Samsung T220HD - Corsair 650W - Corsair Graphite 600T - Sony 7263S Ultima modifica di Wizard77 : 19-02-2008 alle 09:48. |
|
|
|
|
|
19-02-2008, 17:03
|
#4 |
|
Senior Member
Iscritto dal: Jun 2001
Città: Cosenza
Messaggi: 2483
|
ops, ho sbagliato sezione......
__________________
Intel I7 3820@4.3Ghz ° Gigabyte x79 UP4 ° CORSAIR DDR3 32GB Dominator ° Zotac GTX980 Amp! ° SSD Samsung 850 EVO 256GB - Samsung 840 Evo 256GB - Seagate Barracuda 2TB ° Creative X-Fi Titanium Fatal1ty ° Enermax Infinity 720w ° Corsair Graphite 600T ° Asus ROG SWIFT ° AKG 272HD |
|
|
|
|
19-02-2008, 20:56
|
#5 |
|
Senior Member
Iscritto dal: Sep 2002
Città: Como - Provincia
Messaggi: 4534
|
mmm sono stordito non capisco come funziona windbg
ho provato a seguire queste istruzioni: http://blogs.dotnethell.it/michelen/...ool__1979.aspx e mi fa questo Codice:
Opened log file 'c:\debuglog.txt'
2: kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
2: kd>
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
2: kd> C:\Users\Wizard>
Address expression missing from ':\Users\Wizard>'
2: kd> C:\Users\Wizard>.logopen c:\debuglog.txt
Address expression missing from ':\Users\Wizard>.logopen c:\debuglog.txt'
2: kd> ".logopen" non è riconosciuto come comando interno o esterno,
^ Syntax error in '".logopen" non è riconosciuto come comando interno o esterno,'
2: kd> un programma eseguibile o un file batch.
^ Missing whitespace after u in ' un programma eseguibile o un file batch.'
2: kd>
2: kd> C:\Users\Wizard>
Address expression missing from ':\Users\Wizard>'
2: kd> C:\Users\Wizard>.sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbo
Address expression missing from ':\Users\Wizard>.sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbo'
2: kd> ls
No current source file
2: kd> ".sympath" non è riconosciuto come comando interno o esterno,
^ Syntax error in '".sympath" non è riconosciuto come comando interno o esterno,'
2: kd> un programma eseguibile o un file batch.
^ Missing whitespace after u in ' un programma eseguibile o un file batch.'
2: kd>
2: kd> C:\Users\Wizard>
Address expression missing from ':\Users\Wizard>'
2: kd> C:\Users\Wizard>.reload;!analyze -v;r;kv;lmnt;.logclose;q
Address expression missing from ':\Users\Wizard>.reload;!analyze -v;r;kv;lmnt;.logclose;q'
2: kd> ".reload" non è riconosciuto come comando interno o esterno,
^ Syntax error in '".reload" non è riconosciuto come comando interno o esterno,'
2: kd> un programma eseguibile o un file batch.
^ Missing whitespace after u in ' un programma eseguibile o un file batch.'
2: kd>
2: kd> C:\Users\Wizard>c:
Address expression missing from ':\Users\Wizard>c:'
2: kd>
2: kd> C:\Users\Wizard>c:\
Address expression missing from ':\Users\Wizard>c:\'
2: kd> "c:\" non è riconosciuto come comando interno o esterno,
^ Syntax error in '"c:\" non è riconosciuto come comando interno o esterno,'
2: kd> un programma eseguibile o un file batch.
^ Missing whitespace after u in ' un programma eseguibile o un file batch.'
2: kd>
2: kd> C:\Users\Wizard>cd..
Address expression missing from ':\Users\Wizard>cd..'
2: kd>
2: kd> C:\Users>cd..
Address expression missing from ':\Users>cd..'
2: kd>
2: kd> C:\>dir
Address expression missing from ':\>dir'
2: kd> Il volume nell'unità C non ha etichetta.
^ Syntax error in ' Il volume nell'unità C non ha etichetta.'
2: kd> Numero di serie del volume: 1C81-32DB
^ Syntax error in ' Numero di serie del volume: 1C81-32DB'
2: kd>
2: kd> Directory di C:\
*** ERROR: Module load completed but symbols could not be loaded for spldr.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for jraid.sys
*** ERROR: Module load completed but symbols could not be loaded for xusb21.sys
*** ERROR: Module load completed but symbols could not be loaded for GVTDrv64.sys
*** ERROR: Module load completed but symbols could not be loaded for nvoclk64.sys
*** ERROR: Module load completed but symbols could not be loaded for ET5Drv.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for a33fi4lv.SYS
*** ERROR: Module load completed but symbols could not be loaded for Ph3xIB64.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for drmk.sys -
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for secdrv.SYS
*** ERROR: Module load completed but symbols could not be loaded for avgntflt.sys
*** ERROR: Module load completed but symbols could not be loaded for markfun.a64
*** ERROR: Symbol file could not be found. Defaulted to export symbols for spsys.sys -
Couldn't resolve error at 'irectory di C:\'
2: kd>
2: kd> 18/02/2008 23.34 198 csb.log
^ Syntax error in '18/02/2008 23.34 198 csb.log'
2: kd> 16/02/2008 14.56 <DIR> Intel
^ Syntax error in '16/02/2008 14.56 <DIR> Intel'
2: kd> 16/02/2008 15.27 <DIR> NVIDIA
^ Syntax error in '16/02/2008 15.27 <DIR> NVIDIA'
2: kd> 19/02/2008 21.32 <DIR> Program Files
^ Syntax error in '19/02/2008 21.32 <DIR> Program Files'
2: kd> 18/02/2008 21.01 <DIR> Program Files (x86)
^ Syntax error in '18/02/2008 21.01 <DIR> Program Files (x86)'
2: kd> 16/02/2008 15.18 <DIR> RaidTool
^ Syntax error in '16/02/2008 15.18 <DIR> RaidTool'
2: kd> 18/02/2008 23.31 518 RHDSetup.log
^ Syntax error in '18/02/2008 23.31 518 RHDSetup.log'
2: kd> 16/02/2008 13.32 <DIR> Users
^ Syntax error in '16/02/2008 13.32 <DIR> Users'
2: kd> 19/02/2008 20.51 <DIR> Windows
^ Syntax error in '19/02/2008 20.51 <DIR> Windows'
2: kd> 2 File 716 byte
^ Syntax error in ' 2 File 716 byte'
2: kd> 7 Directory 14.741.155.840 byte disponibili
^ Syntax error in ' 7 Directory 14.741.155.840 byte disponibili'
2: kd>
2: kd> C:\>cd program files
Address expression missing from ':\>cd program files'
2: kd>
2: kd> C:\Program Files>dir
Address expression missing from ':\Program Files>dir'
2: kd> Il volume nell'unità C non ha etichetta.
^ Syntax error in ' Il volume nell'unità C non ha etichetta.'
2: kd> Numero di serie del volume: 1C81-32DB
^ Syntax error in ' Numero di serie del volume: 1C81-32DB'
2: kd>
2: kd> Directory di C:\Program Files
Couldn't resolve error at 'irectory di C:\Program Files'
2: kd>
2: kd> 19/02/2008 21.32 <DIR> .
^ Syntax error in '19/02/2008 21.32 <DIR> .'
2: kd> 19/02/2008 21.32 <DIR> ..
^ Syntax error in '19/02/2008 21.32 <DIR> ..'
2: kd> 16/02/2008 14.47 <DIR> BitLocker
^ Syntax error in '16/02/2008 14.47 <DIR> BitLocker'
2: kd> 02/11/2006 14.33 <DIR> Common Files
^ Syntax error in '02/11/2006 14.33 <DIR> Common Files'
2: kd> 19/02/2008 21.32 <DIR> Debugging Tools for Windows 64-bit
^ Syntax error in '19/02/2008 21.32 <DIR> Debugging Tools for Windows 64-bit'
2: kd> 16/02/2008 14.25 <DIR> Internet Explorer
^ Syntax error in '16/02/2008 14.25 <DIR> Internet Explorer'
2: kd> 16/02/2008 14.46 <DIR> Microsoft Games
^ Syntax error in '16/02/2008 14.46 <DIR> Microsoft Games'
2: kd> 02/11/2006 16.15 <DIR> Movie Maker
^ Syntax error in '02/11/2006 16.15 <DIR> Movie Maker'
2: kd> 02/11/2006 16.06 <DIR> MSBuild
^ Syntax error in '02/11/2006 16.06 <DIR> MSBuild'
2: kd> 02/11/2006 16.06 <DIR> MSN
^ Syntax error in '02/11/2006 16.06 <DIR> MSN'
2: kd> 02/11/2006 16.06 <DIR> Reference Assemblies
^ Syntax error in '02/11/2006 16.06 <DIR> Reference Assemblies'
2: kd> 16/02/2008 14.25 <DIR> Windows Calendar
^ Syntax error in '16/02/2008 14.25 <DIR> Windows Calendar'
2: kd> 02/11/2006 16.15 <DIR> Windows Collaboration
^ Syntax error in '02/11/2006 16.15 <DIR> Windows Collaboration'
2: kd> 16/02/2008 14.25 <DIR> Windows Defender
^ Syntax error in '16/02/2008 14.25 <DIR> Windows Defender'
2: kd> 02/11/2006 16.15 <DIR> Windows Journal
^ Syntax error in '02/11/2006 16.15 <DIR> Windows Journal'
2: kd> 16/02/2008 14.25 <DIR> Windows Mail
^ Syntax error in '16/02/2008 14.25 <DIR> Windows Mail'
2: kd> 16/02/2008 14.25 <DIR> Windows Media Player
^ Syntax error in '16/02/2008 14.25 <DIR> Windows Media Player'
2: kd> 16/02/2008 13.29 <DIR> Windows NT
^ Syntax error in '16/02/2008 13.29 <DIR> Windows NT'
2: kd> 02/11/2006 16.15 <DIR> Windows Photo Gallery
^ Syntax error in '02/11/2006 16.15 <DIR> Windows Photo Gallery'
2: kd> 16/02/2008 14.25 <DIR> Windows Sidebar
^ Syntax error in '16/02/2008 14.25 <DIR> Windows Sidebar'
2: kd> 0 File 0 byte
^ Syntax error in ' 0 File 0 byte'
2: kd> 20 Directory 14.741.155.840 byte disponibili
^ Syntax error in ' 20 Directory 14.741.155.840 byte disponibili'
2: kd>
2: kd> C:\Program Files>cd debugging Tools for Windows 64-bit
Address expression missing from ':\Program Files>cd debugging Tools for Windows 64-bit'
2: kd>
2: kd> C:\Program Files\Debugging Tools for Windows 64-bit>kd -z c:\windows\Memory.dmp
Address expression missing from ':\Program Files\Debugging Tools for Windows 64-bit>kd -z c:\windows\Memory.dmp'
2: kd>
2: kd> Microsoft (R) Windows Debugger Version 6.8.0004.0 AMD64
Couldn't resolve error at 'icrosoft (R) Windows Debugger Version 6.8.0004.0 AMD64'
2: kd> Copyright (c) Microsoft Corporation. All rights reserved.
Couldn't resolve error at 'opyright (c) Microsoft Corporation. All rights reserved.'
2: kd>
2: kd>
2: kd> Loading Dump File [c:\windows\Memory.dmp]
^ Syntax error in 'Loading Dump File [c:\windows\Memory.dmp]'
2: kd> Kernel Summary Dump File: Only kernel address space is available
Couldn't resolve error at 'ernel Summary Dump File: Only kernel address space is available'
2: kd>
2: kd> Symbol search path is: *** Invalid ***
Couldn't resolve error at 'ymbol search path is: *** Invalid ***'
2: kd> ****************************************************************************
2: kd> * Symbol loading may be unreliable without a symbol search path. *
2: kd> * Use .symfix to have the debugger choose a symbol path. *
2: kd> * After setting your symbol path, use .reload to refresh symbol locations. *
2: kd> ****************************************************************************
2: kd> Executable search path is:
Couldn't resolve error at 'xecutable search path is:'
2: kd> *********************************************************************
2: kd> * Symbols can not be loaded because symbol path is not initialized. *
2: kd> * *
2: kd> * The Symbol Path can be set by: *
2: kd> * using the _NT_SYMBOL_PATH environment variable. *
2: kd> * using the -y <symbol_path> argument when starting the debugger. *
2: kd> * using .sympath and .sympath+ *
2: kd> *********************************************************************
2: kd> *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkr
2: kd> nlmp.exe -
^ Syntax error in 'nlmp.exe -'
2: kd> Windows Vista Kernel Version 6000 MP (4 procs) Free x64
^ No runnable debuggees error in 'Windows Vista Kernel Version 6000 MP (4 procs) Free x64'
2: kd> Product: WinNt, suite: TerminalServer SingleUserTS
^ No runnable debuggees error in 'Product: WinNt, suite: TerminalServer SingleUserTS'
2: kd> Built by: 6000.16584.amd64fre.vista_gdr.071023-1545
^ Operation not supported by current debuggee error in 'Built by: 6000.16584.amd64fre.vista_gdr.071023-1545'
2: kd> Kernel base = 0xfffff800`01c00000 PsLoadedModuleList = 0xfffff800`01d9af70
Couldn't resolve error at 'ernel base = 0xfffff800`01c00000 PsLoadedModuleList = 0xfffff800`01d9af70'
2: kd> Debug session time: Mon Feb 18 08:54:02.905 2008 (GMT+1)
Couldn't resolve error at 'ebug session time: Mon Feb 18 08:54:02.905 2008 (GMT+1)'
2: kd> System Uptime: 0 days 10:44:17.627
Couldn't resolve error at 'ystem Uptime: 0 days 10:44:17.627'
2: kd> *********************************************************************
2: kd> * Symbols can not be loaded because symbol path is not initialized. *
2: kd> * *
2: kd> * The Symbol Path can be set by: *
2: kd> * using the _NT_SYMBOL_PATH environment variable. *
2: kd> * using the -y <symbol_path> argument when starting the debugger. *
2: kd> * using .sympath and .sympath+ *
2: kd> *********************************************************************
2: kd> *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkr
2: kd> nlmp.exe -
^ Syntax error in 'nlmp.exe -'
2: kd> Loading Kernel Symbols
^ Syntax error in 'Loading Kernel Symbols'
2: kd> ................................................................................
^ Syntax error in '................................................................................'
2: kd> ..............................................................
^ Syntax error in '..............................................................'
2: kd> Loading User Symbols
^ Syntax error in 'Loading User Symbols'
2: kd>
2: kd> Loading unloaded module list
^ Syntax error in 'Loading unloaded module list'
2: kd> .....
^ Syntax error in '.....'
2: kd> *******************************************************************************
2: kd> * *
2: kd> * Bugcheck Analysis *
2: kd> * *
2: kd> *******************************************************************************
2: kd>
2: kd> Use !analyze -v to get detailed debugging information.
^ Missing whitespace after u in 'Use !analyze -v to get detailed debugging information.'
2: kd>
2: kd> BugCheck A, {3e8000e, 2, 1, fffff80001c592b1}
^ Operation not supported by current debuggee error in 'BugCheck A, {3e8000e, 2, 1, fffff80001c592b1}'
2: kd>
2: kd> *** ERROR: Symbol file could not be found. Defaulted to export symbols for ndis
2: kd> .sys -
^ Syntax error in '.sys -'
2: kd> *** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
2: kd> *** ERROR: Module load completed but symbols could not be loaded for NETIO.SYS
2: kd> *** ERROR: Module load completed but symbols could not be loaded for pacer.sys
2: kd> *** ERROR: Module load completed but symbols could not be loaded for Rtlh64.sys
2: kd> ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
2: kd>
2: kd> *************************************************************************
2: kd> *** ***
2: kd> *** ***
2: kd> *** Your debugger is not using the correct symbols ***
2: kd> *** ***
2: kd> *** In order for this command to work properly, your symbol path ***
2: kd> *** must point to .pdb files that have full type information. ***
2: kd> *** ***
2: kd> *** Certain .pdb files (such as the public OS symbols) do not ***
2: kd> *** contain the required information. Contact the group that ***
2: kd> *** provided you with these symbols if you need this command to ***
2: kd> *** work. ***
2: kd> *** ***
2: kd> *** Type referenced: nt!_KPRCB ***
2: kd> *** ***
2: kd> *************************************************************************
2: kd> *************************************************************************
2: kd> *** ***
2: kd> *** ***
2: kd> *** Your debugger is not using the correct symbols ***
2: kd> *** ***
2: kd> *** In order for this command to work properly, your symbol path ***
2: kd> *** must point to .pdb files that have full type information. ***
2: kd> *** ***
2: kd> *** Certain .pdb files (such as the public OS symbols) do not ***
2: kd> *** contain the required information. Contact the group that ***
2: kd> *** provided you with these symbols if you need this command to ***
2: kd> *** work. ***
2: kd> *** ***
2: kd> *** Type referenced: nt!KPRCB ***
2: kd> *** ***
2: kd> *************************************************************************
2: kd> *************************************************************************
2: kd> *** ***
2: kd> *** ***
2: kd> *** Your debugger is not using the correct symbols ***
2: kd> *** ***
2: kd> *** In order for this command to work properly, your symbol path ***
2: kd> *** must point to .pdb files that have full type information. ***
2: kd> *** ***
2: kd> *** Certain .pdb files (such as the public OS symbols) do not ***
2: kd> *** contain the required information. Contact the group that ***
2: kd> *** provided you with these symbols if you need this command to ***
2: kd> *** work. ***
2: kd> *** ***
2: kd> *** Type referenced: nt!_KPRCB ***
2: kd> *** ***
2: kd> *************************************************************************
2: kd> *************************************************************************
2: kd> *** ***
2: kd> *** ***
2: kd> *** Your debugger is not using the correct symbols ***
2: kd> *** ***
2: kd> *** In order for this command to work properly, your symbol path ***
2: kd> *** must point to .pdb files that have full type information. ***
2: kd> *** ***
2: kd> *** Certain .pdb files (such as the public OS symbols) do not ***
2: kd> *** contain the required information. Contact the group that ***
2: kd> *** provided you with these symbols if you need this command to ***
2: kd> *** work. ***
2: kd> *** ***
2: kd> *** Type referenced: nt!KPRCB ***
2: kd> *** ***
2: kd> *************************************************************************
2: kd> *************************************************************************
2: kd> *** ***
2: kd> *** ***
2: kd> *** Your debugger is not using the correct symbols ***
2: kd> *** ***
2: kd> *** In order for this command to work properly, your symbol path ***
2: kd> *** must point to .pdb files that have full type information. ***
2: kd> *** ***
2: kd> *** Certain .pdb files (such as the public OS symbols) do not ***
2: kd> *** contain the required information. Contact the group that ***
2: kd> *** provided you with these symbols if you need this command to ***
2: kd> *** work. ***
2: kd> *** ***
2: kd> *** Type referenced: nt!_KPRCB ***
2: kd> *** ***
2: kd> *************************************************************************
2: kd> *************************************************************************
2: kd> *** ***
2: kd> *** ***
2: kd> *** Your debugger is not using the correct symbols ***
2: kd> *** ***
2: kd> *** In order for this command to work properly, your symbol path ***
2: kd> *** must point to .pdb files that have full type information. ***
2: kd> *** ***
2: kd> *** Certain .pdb files (such as the public OS symbols) do not ***
2: kd> *** contain the required information. Contact the group that ***
2: kd> *** provided you with these symbols if you need this command to ***
2: kd> *** work. ***
2: kd> *** ***
2: kd> *** Type referenced: nt!_KPRCB ***
2: kd> *** ***
2: kd> *************************************************************************
2: kd> *************************************************************************
2: kd> *** ***
2: kd> *** ***
2: kd> *** Your debugger is not using the correct symbols ***
2: kd> *** ***
2: kd> *** In order for this command to work properly, your symbol path ***
2: kd> *** must point to .pdb files that have full type information. ***
2: kd> *** ***
2: kd> *** Certain .pdb files (such as the public OS symbols) do not ***
2: kd> *** contain the required information. Contact the group that ***
2: kd> *** provided you with these symbols if you need this command to ***
2: kd> *** work. ***
2: kd> *** ***
2: kd> *** Type referenced: nt!_KPRCB ***
2: kd> *** ***
2: kd> *************************************************************************
2: kd> *************************************************************************
2: kd> *** ***
2: kd> *** ***
2: kd> *** Your debugger is not using the correct symbols ***
2: kd> *** ***
2: kd> *** In order for this command to work properly, your symbol path ***
2: kd> *** must point to .pdb files that have full type information. ***
2: kd> *** ***
2: kd> *** Certain .pdb files (such as the public OS symbols) do not ***
2: kd> *** contain the required information. Contact the group that ***
2: kd> *** provided you with these symbols if you need this command to ***
2: kd> *** work. ***
2: kd> *** ***
2: kd> *** Type referenced: nt!_KPRCB ***
2: kd> *** ***
2: kd> *************************************************************************
2: kd> *********************************************************************
2: kd> * Symbols can not be loaded because symbol path is not initialized. *
2: kd> * *
2: kd> * The Symbol Path can be set by: *
2: kd> * using the _NT_SYMBOL_PATH environment variable. *
2: kd> * using the -y <symbol_path> argument when starting the debugger. *
2: kd> * using .sympath and .sympath+ *
2: kd> *********************************************************************
2: kd> *********************************************************************
2: kd> * Symbols can not be loaded because symbol path is not initialized. *
2: kd> * *
2: kd> * The Symbol Path can be set by: *
2: kd> * using the _NT_SYMBOL_PATH environment variable. *
2: kd> * using the -y <symbol_path> argument when starting the debugger. *
2: kd> * using .sympath and .sympath+ *
2: kd> *********************************************************************
2: kd> Probably caused by : NETIO.SYS ( NETIO+2072 )
^ No runnable debuggees error in 'Probably caused by : NETIO.SYS ( NETIO+2072 )'
2: kd>
2: kd> Followup: MachineOwner
Couldn't resolve error at 'ollowup: MachineOwner'
2: kd> ---------
^ Syntax error in '---------'
2: kd>
2: kd> 2: kd> .logopen c:\debuglog.txt
^ Syntax error in '2: kd> .logopen c:\debuglog.txt'
2: kd> Opened log file 'c:\debuglog.txt'
^ Syntax error in 'Opened log file 'c:\debuglog.txt''
2: kd> 2: kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
^ Syntax error in '2: kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols'
2: kd> Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Couldn't resolve error at 'ymbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols'
2: kd>
2: kd> 2: kd>.reload;!analyze -v;r;kv;lmnt;.logclose;q
^ Syntax error in '2: kd>.reload;!analyze -v;r;kv;lmnt;.logclose;q'
2: kd>
__________________
Intel Core i7 2600 - Zalman CNPS10X Performa - Asus P8P67 B3 - Corsair Vengeance 2x4Gb 1600Mhz 8-8-8-24 - Sapphire Radeon 6950@6970 2Gb - OCZ Agility 3 120GB + 2 x Seagate 500Gb SataII Raid - Samsung T220HD - Corsair 650W - Corsair Graphite 600T - Sony 7263S |
|
|
|
|
13-05-2009, 11:25
|
#6 |
|
Member
Iscritto dal: Mar 2008
Messaggi: 72
|
come hai risolto il problema??anche ho lo stesso errore "Application popup evento 1060": Blocco del caricamento di \SystemRoot\SysWow64\Drivers\DgiVecp.sys per incompatibilità con il computer. Contattare i fornitori del software per ottenere una versione compatibile del driver.
Ho xp 64 e vista 32, all'avvio ho l aschermata che mi chiede quale sistema operativo scegliere, e poi in xp ho sempre questo errore ad ogni avvio! ciao ciao |
|
|
|
|
|
| Strumenti | |
|
|
Tutti gli orari sono GMT +1. Ora sono le: 16:57.
