Je gaat het toch niet opgeven , daar op Tech Support Guy Forums ?
http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx
http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx
Bluescreen met memory dump
- Onderwerp starter Guido001
- Startdatum
- Status
Nee ik ga het proberen zelf te doen en de gegevens naar die meneer sturen als hij dat wilt doen.
Maar ik weet niet precies wat ik moet downloaden want als ik het zo lees zijn het meerdere applicaties.
Ah nvm hij heeft al een mooie link gelinkt.
Maar ik weet niet precies wat ik moet downloaden want als ik het zo lees zijn het meerdere applicaties.
Ah nvm hij heeft al een mooie link gelinkt.
Laatst bewerkt:
Voor vanavond ga ik stoppen. Ik heb aan die meneer gevraagd welke ik precies moet downloaden want er staan wel 20 links ik dacht zelf 1 van de onderste maar ik wil het zeker weten.
To do list voor als ik wakker word:
Pc aanzetten douche etc etc.
Film kijken met mijn broer en daarna voor de pc de juiste tools downloaden en dat uitvogelen en hopelijk wat progressie.
To do list voor als ik wakker word:
Pc aanzetten douche etc etc.
Film kijken met mijn broer en daarna voor de pc de juiste tools downloaden en dat uitvogelen en hopelijk wat progressie.
Hmm ik heb alles gedownload
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini011010-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\Windows\Symbols
Executable search path is:
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 6002 (Service Pack 2) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`01e03000 PsLoadedModuleList = 0xfffff800`01fc7dd0
Debug session time: Sun Jan 10 03:26:53.139 2010 (UTC + 2:00)
System Uptime: 0 days 12:40:47.556
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
.........
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80094414e0, fffffa6002aee220, 0, 2}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.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 ***
*** ***
*************************************************************************
Probably caused by : nvlddmkm.sys ( nvlddmkm!perfQueryBiosPowerMizerLimit+1680 )
Followup: MachineOwner
---------
Zegt het, dus volgens mij heb ik niet de juist symbools.
Bijgeleverd screenshot waarin staat waar ik mijn file location naar toe heb gewezen.
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini011010-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\Windows\Symbols
Executable search path is:
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 6002 (Service Pack 2) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`01e03000 PsLoadedModuleList = 0xfffff800`01fc7dd0
Debug session time: Sun Jan 10 03:26:53.139 2010 (UTC + 2:00)
System Uptime: 0 days 12:40:47.556
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
.........
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80094414e0, fffffa6002aee220, 0, 2}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.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 ***
*** ***
*************************************************************************
Probably caused by : nvlddmkm.sys ( nvlddmkm!perfQueryBiosPowerMizerLimit+1680 )
Followup: MachineOwner
---------
Zegt het, dus volgens mij heb ik niet de juist symbools.
Bijgeleverd screenshot waarin staat waar ik mijn file location naar toe heb gewezen.
Bijlagen
Laatst bewerkt:
Symbols
"dus volgens mij heb ik niet de juist symbols."
Daar lijkt het wel op ,helaas.
Geef me nog even het adres van de link die je kreeg , dan kijk ik even mee .
Je hebt één persoonlijk bericht op het Nvidia Forum.
De topic wordt wel goed bekeken , maar verder ........
"dus volgens mij heb ik niet de juist symbols."
Daar lijkt het wel op ,helaas.
Geef me nog even het adres van de link die je kreeg , dan kijk ik even mee .
Je hebt één persoonlijk bericht op het Nvidia Forum.
De topic wordt wel goed bekeken , maar verder ........
http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx deze uit die tutorial en dan heb ik gewoon vista aangeklikt.
En dan bij Windows Vista SP2 Symbol heb ik daar onder
Windows Vista SP2 and Windows Server 2008 SP2 x64 retail symbols, all languages (File size: 226 MB)
Ik denk dat die man van Tech support wel weet wat ik fout heb gedaan dus ik wacht op een reactive van hem.
Overigens toen ik op de file ergs op klikte kreeg ik
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
FAULTING_MODULE: fffff80001e15000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4abfff56
FAULTING_IP:
nvlddmkm!perfQueryBiosPowerMizerLimit+1680
fffffa60`02ced220 ?? ???
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
CURRENT_IRQL: 0
STACK_TEXT:
fffffa60`0477fc18 fffffa60`03727ad4 : 00000000`00000116 fffffa80`07aec4e0 fffffa60`02ced220 00000000`00000000 : nt+0x5a450
fffffa60`0477fc20 00000000`00000116 : fffffa80`07aec4e0 fffffa60`02ced220 00000000`00000000 00000000`00000002 : dxgkrnl!TdrTimedOperationWaitForSingleObject+0x4
fffffa60`0477fc28 fffffa80`07aec4e0 : fffffa60`02ced220 00000000`00000000 00000000`00000002 fffffa80`094ee780 : 0x116
fffffa60`0477fc30 fffffa60`02ced220 : 00000000`00000000 00000000`00000002 fffffa80`094ee780 00000000`00000081 : 0xfffffa80`07aec4e0
fffffa60`0477fc38 00000000`00000000 : 00000000`00000000 00000000`004da25e fffffa60`036e11c6 00000000`004da25e : nvlddmkm!perfQueryBiosPowerMizerLimit+0x1680
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm!perfQueryBiosPowerMizerLimit+1680
fffffa60`02ced220 ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nvlddmkm!perfQueryBiosPowerMizerLimit+1680
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
Te zien.
En dan bij Windows Vista SP2 Symbol heb ik daar onder
Windows Vista SP2 and Windows Server 2008 SP2 x64 retail symbols, all languages (File size: 226 MB)
Ik denk dat die man van Tech support wel weet wat ik fout heb gedaan dus ik wacht op een reactive van hem.
Overigens toen ik op de file ergs op klikte kreeg ik
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
FAULTING_MODULE: fffff80001e15000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4abfff56
FAULTING_IP:
nvlddmkm!perfQueryBiosPowerMizerLimit+1680
fffffa60`02ced220 ?? ???
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
CURRENT_IRQL: 0
STACK_TEXT:
fffffa60`0477fc18 fffffa60`03727ad4 : 00000000`00000116 fffffa80`07aec4e0 fffffa60`02ced220 00000000`00000000 : nt+0x5a450
fffffa60`0477fc20 00000000`00000116 : fffffa80`07aec4e0 fffffa60`02ced220 00000000`00000000 00000000`00000002 : dxgkrnl!TdrTimedOperationWaitForSingleObject+0x4
fffffa60`0477fc28 fffffa80`07aec4e0 : fffffa60`02ced220 00000000`00000000 00000000`00000002 fffffa80`094ee780 : 0x116
fffffa60`0477fc30 fffffa60`02ced220 : 00000000`00000000 00000000`00000002 fffffa80`094ee780 00000000`00000081 : 0xfffffa80`07aec4e0
fffffa60`0477fc38 00000000`00000000 : 00000000`00000000 00000000`004da25e fffffa60`036e11c6 00000000`004da25e : nvlddmkm!perfQueryBiosPowerMizerLimit+0x1680
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm!perfQueryBiosPowerMizerLimit+1680
fffffa60`02ced220 ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nvlddmkm!perfQueryBiosPowerMizerLimit+1680
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
Te zien.
Laatst bewerkt:
Symbols
"Windows Vista SP2 and Windows Server 2008 SP2 x64 retail symbols, all languages (File size: 226 MB)"
Dit kan de juiste keuze zijn , maar er is ook nog :
"Windows Vista SP2 and Windows Server 2008 SP2 x64 checked symbols, all languages (File size: 225 MB)"
Kun je de eesrte download gemakkelijk verwijderen ? Probeer dan de tweede.
Misschien wordt je hier nog wat wijzer :
http://www.microsoft.com/whdc/devtools/toolsupport.mspx
"Windows Vista SP2 and Windows Server 2008 SP2 x64 retail symbols, all languages (File size: 226 MB)"
Dit kan de juiste keuze zijn , maar er is ook nog :
"Windows Vista SP2 and Windows Server 2008 SP2 x64 checked symbols, all languages (File size: 225 MB)"
Kun je de eesrte download gemakkelijk verwijderen ? Probeer dan de tweede.
Misschien wordt je hier nog wat wijzer :
http://www.microsoft.com/whdc/devtools/toolsupport.mspx
Ik zie niet zozeer waar ik het kan verwijderen maar zal het wel proberen.
Maar kun jij mij vertellen wat al die Microsoft visual C++ zijn ?
Ik weet dat c++ een programmeer taal is maar dit weet ik niet precies.
En wat is dat bij die download nou 86* en 64* wat is het verschil ik weet wel dat ik program files gewoon heb op mijn pc en een program files 86*.
Of is dat 64/32 bits bij elkaar in die download ?
Maar kun jij mij vertellen wat al die Microsoft visual C++ zijn ?
Ik weet dat c++ een programmeer taal is maar dit weet ik niet precies.
En wat is dat bij die download nou 86* en 64* wat is het verschil ik weet wel dat ik program files gewoon heb op mijn pc en een program files 86*.
Of is dat 64/32 bits bij elkaar in die download ?
Laatst bewerkt:
Symbols
Wanneer je de eerste download niet kunt vinden en/of verwijderen , zet dan de tweede erover heen ?!
Windows zal tijdens de installatie vast één en ander zelf 'regelen'.
Welke driver heb je nu eigenlijk geïnstalleerd voor de GTX295 ? Nvidia 185.2. ?
Zie evt.: http://www.softpedia.com/get/System/System-Info/Double-Driver.shtml
Wanneer je de eerste download niet kunt vinden en/of verwijderen , zet dan de tweede erover heen ?!
Windows zal tijdens de installatie vast één en ander zelf 'regelen'.
Welke driver heb je nu eigenlijk geïnstalleerd voor de GTX295 ? Nvidia 185.2. ?
Zie evt.: http://www.softpedia.com/get/System/System-Info/Double-Driver.shtml
Laatst bewerkt:
Hmm http://forum.computeridee.nl/showthread.php?t=57140 is misschien wat wat denk jij ?
Heb momenteel bezoek. Zal het iets later doorlezen.
Zoek even op Google naar de relatie GTX295 en 185.2. Niet altijd even positief .
How about de tweede download voor Symbols ? Het proberen toch waard ?
Ik had heel de dag alleen maar World of warcraft gespeeld van ongeveer 14:00 t/m 0:15 ik start Countrer strike source op en ik oppeens valt mijn beeldscherm uit ik probeer nog wat stekkers niks lukt. Ik doe de reset knop ik log in op mijn pc en dan krijg ik dit te staan.
Laatst bewerkt:
Haal dat screenshot maar beter weg !
86* en 64*
Kijk hier eens : http://www.computing.net/answers/cpus/find-out-if-i-have-86-or-64-bit/14145.html
Kijk hier eens : http://www.computing.net/answers/cpus/find-out-if-i-have-86-or-64-bit/14145.html
Vanwege het adres dat er in staat.
- Status
