Bluescreen error

[DoRcO]

Hey allemaal


Schrik niet van het lange verhaal!

mijn pc vertoont weer het volgende probleem...

Als de pc een tijdje lekker draait (soms heel lang, soms nog heel kort)
valt de pc uit... dit gebeurt zowel wanneer de CPU stressed werkt, als gewoon in rust.

net was ik gewoon met 1 persoon aan het msn'en, en bam.. weer bluescreen

windows herstel rapport word ik niet wijs van.. ik heb laatst een nieuwe CPU cooler gekocht, en ik vermoed dat het heel misschien daar iets mee te maken heeft,

CPU; AMD Athlon 64 X2 Dual Core 3.0 Ghz
COOLER; Arctic Cooling Freezer 64 Pro - AM2

deze cooler heb ik gekocht maar het word er niet echt beter op..
temp was rond de 39 graden
en nu via het bios blijkt de core tempperatuur 50 graden te zijn...
normaal zou deze processor dat toch aan moeten kunnen... ?

ik raad jullie aan mij systeem even na te kijken @ Mijn systeem (handtekening)

ALS JE NIET WEET WAT JE ZEGT, ZEG DAN A.U.B NIKS, WANT IK WIL GRAAG PROFESSIONELE HULP. Bedankt


****************************************************************
windows herstel raport....


Probleemhandtekening:
Gebeurtenisnaam van probleem: BlueScreen
Versie van besturingssysteem: 6.0.6001.2.1.0.256.1
Landinstelling-id: 1043

Aanvullende informatie over dit probleem:
BCCode: 50
BCP1: FFFFFFFFFFFFFF8B
BCP2: 0000000000000001
BCP3: FFFFF960001BA6ED
BCP4: 0000000000000000
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Bestanden die helpen bij het beschrijven van het probleem:
C:\Windows\Minidump\Mini052409-01.dmp
C:\Users\Admin\AppData\Local\Temp\WER-55676-0.sysdata.xml
C:\Users\Admin\AppData\Local\Temp\WER1831.tmp.version.txt

Lees onze privacyverklaring:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0413

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


Ik hoop echt dat iemand mij kan helpen, want dit is zwaar irritant !


Mvg, Remco

 

[dnties]

C:\Windows\Minidump\Mini052409-01.dmp

Lees die eens uit als Crash-dump uit met Debugging Tools for Windows.
Kijk even deze discussiedraad goed door voor links, aanwijzingen en 'bijzonderheden' van Vista (je moet in Vista WinDbg starten Als Administrator om toegang tot de C:\Windows\Minidump map te krijgen om het .dmp bestand uit te lezen).

Succes,

Tijs.

 

[DoRcO]

Ik heb de volgende error in Minidump geopend...
heeft dit iets met symbolen te maken ?? :O


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


Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini032909-01.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`01e65000 PsLoadedModuleList = 0xfffff800`0202adb0
Debug session time: Sun Mar 29 01:15:07.837 2009 (GMT+2)
System Uptime: 0 days 6:05:46.584
*********************************************************************
* 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 3B, {c000001d, fffff80001ec1768, fffffa600c8e10b0, 0}

***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+5c768 )

Followup: MachineOwner
---------

 

[dnties]

Die symbols zorgen er alleen voor dat de uitvoer van WinDBG iets beter te lezen is, zijn niet direct relevant voor de uitkomst van de analyse, en ze zijn ook niet de 'oorzaak' van het probleem dat je met WinDBG probeert te onderzoeken.

Ik mis de uitvoer van het !analyze -v commando in WinDBG, op het moment dat je het .dmp als crash-bestand geopend hebt.
Post die uitvoer ook nog even.

Tijs.

 

[DoRcO]

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

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.

MODULE_NAME: nt

FAULTING_MODULE: fffff80001e65000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1ba35

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {UITZONDERING} Ongeldige instructie Er is geprobeerd een ongeldige instructie uit te voeren.

FAULTING_IP:
nt+5c768
fffff800`01ec1768 ?? ???

CONTEXT: fffffa600c8e10b0 -- (.cxr 0xfffffa600c8e10b0)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=00000000000007ff rsi=fffffa8006bdb158 rdi=fffffa8006bdb060
rip=fffff80001ec1768 rsp=fffffa600c8e1910 rbp=fffffa80097cc7b0
r8=0000000000000000 r9=0000000000007e00 r10=000000000000000f
r11=fffffa80051afe7e r12=fffffa60005ec7f0 r13=0000000000000000
r14=fffffa60005ec180 r15=fffffa8006bdb118
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt+0x5c768:
fffff800`01ec1768 ?? ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80001ec1768

STACK_TEXT:
fffffa60`0c8e1910 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`0000000a fffffa60`005ec180 : nt+0x5c768


FOLLOWUP_IP:
nt+5c768
fffff800`01ec1768 ?? ???

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+5c768

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

STACK_COMMAND: .cxr 0xfffffa600c8e10b0 ; kb

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

 

[dnties]

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

Helaas kan ik uit de uitvoer niet halen welke driver er verantwoordelijk is, maar er is iets mis met een driver (dit kan ook evt. een diepgravend stukje software zijn, zoals anti-virus e.d.).
Overigens kan het ook liggen aan geheugen dat te warm wordt of gewoon kapot is. Test even een hele nacht met een opstart-cd die je kunt maken van Memtest86+, kies daar "Download - Pre-Compiled Bootable ISO (.zip)", pak het gedownloade .zip bestand uit, en brand de resulterende .ISO als Image naar een CD-recordable, bijv. met programma's als ImgBurn of Nero.

Wat ik me afvraag is of je niet nog een of andere fix moet uitvoeren voor de ondersteuning van je Amd CPU: Andere crashdumps die ik op Internet heb gezien vermelden expliciet dat het om een Amd processor gaat, dat zie ik in jouw dump-informatie niet terug. Hieronder een voorbeeld waar Amd wél wordt vermeld:

Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18226.amd64fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0xfffff800`0200f000 PsLoadedModuleList = 0xfffff800`021d4db0

Succes,

Tijs.

 

[DoRcO]

Ok, heel appart...

zou een driver scanner werken ??
dan download ik driver genius eens,

die memtest86+ is iets dat je ram test?
wanneer krijg ik een soort uitslag ervan ??

thnx dat je me helpt

 

[DoRcO]

in de systemroot map (c/windows)
was ook een minidump.DMP file
daar kreeg ik de volgende LOG uit


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


Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18226.amd64fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0xfffff800`0285d000 PsLoadedModuleList = 0xfffff800`02a22db0
Debug session time: Sun May 24 22:44:09.011 2009 (GMT+2)
System Uptime: 0 days 0:27:03.928
*********************************************************************
* 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffffffffff8b, 1, fffff960001ba6ed, 0}

Page bc782 not present in the dump file. Type ".hh dbgerr004" for details
*** ERROR: Symbol file could not be found. Defaulted to export symbols for win32k.sys -
Page 15ffb5 not present in the dump file. Type ".hh dbgerr004" for details
Page 15ffb5 not present in the dump file. Type ".hh dbgerr004" for details
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Page 1737cb not present in the dump file. Type ".hh dbgerr004" for details
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Page 1737cb not present in the dump file. Type ".hh dbgerr004" for details
Page 15ffb5 not present in the dump file. Type ".hh dbgerr004" for details
Page 15ffb5 not present in the dump file. Type ".hh dbgerr004" for details
Page 15ffb5 not present in the dump file. Type ".hh dbgerr004" for details
Page 15ffb5 not present in the dump file. Type ".hh dbgerr004" for details
*************************************************************************
*** ***
*** ***
*** 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 : win32k.sys ( win32k!W32pArgumentTable+5db1 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffffffffff8b, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff960001ba6ed, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------

Page 15ffb5 not present in the dump file. Type ".hh dbgerr004" for details
Page 15ffb5 not present in the dump file. Type ".hh dbgerr004" for details
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Page 1737cb not present in the dump file. Type ".hh dbgerr004" for details
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Page 1737cb not present in the dump file. Type ".hh dbgerr004" for details
Page 15ffb5 not present in the dump file. Type ".hh dbgerr004" for details
Page 15ffb5 not present in the dump file. Type ".hh dbgerr004" for details
Page 15ffb5 not present in the dump file. Type ".hh dbgerr004" for details
Page 15ffb5 not present in the dump file. Type ".hh dbgerr004" for details
*************************************************************************
*** ***
*** ***
*** 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+ *
*********************************************************************

















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.

MODULE_NAME: win32k

FAULTING_MODULE: fffff8000285d000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 498fa36b

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
ffffffffffffff8b

FAULTING_IP:
win32k!W32pArgumentTable+5db1
fffff960`001ba6ed ff488b dec dword ptr [rax-75h]

MM_INTERNAL_CODE: 0

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800028c0671 to fffff800028b1650

STACK_TEXT:
fffffa60`0c838918 fffff800`028c0671 : 00000000`00000050 ffffffff`ffffff8b 00000000`00000001 fffffa60`0c838a10 : nt!KeBugCheckEx
fffffa60`0c838920 fffff800`028b01d9 : 00000000`00000001 fffffa80`06adbbb0 00000000`74a43300 00000000`0026e1b0 : nt!ExReleaseResourceLite+0x1391
fffffa60`0c838a10 fffff960`001ba6ed : 00000000`0026e1b0 fffffa60`0c838ca0 00000000`00000000 fffff800`028bf172 : nt!ZwUnloadKeyEx+0x11b9
fffffa60`0c838ba0 00000000`0026e1b0 : fffffa60`0c838ca0 00000000`00000000 fffff800`028bf172 fffffa60`0c838bc8 : win32k!W32pArgumentTable+0x5db1
fffffa60`0c838ba8 fffffa60`0c838ca0 : 00000000`00000000 fffff800`028bf172 fffffa60`0c838bc8 fffffa60`0c838ca0 : 0x26e1b0
fffffa60`0c838bb0 00000000`00000000 : fffff800`028bf172 fffffa60`0c838bc8 fffffa60`0c838ca0 00000000`00000001 : 0xfffffa60`0c838ca0


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!W32pArgumentTable+5db1
fffff960`001ba6ed ff488b dec dword ptr [rax-75h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: win32k!W32pArgumentTable+5db1

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: win32k.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

 

[dnties]

Nog even een vraag: Heb je recent nog video-kaartdrivers geupdate?
Zie hier iemand die ong. dezelfde problemen lijkt te hebben gehad. Hij ging terug in driver, jij zou gewoon naar v. 185.85 (Vista 32-bit) danwel v. 185.85 (Vista 64-bit) kunnen gaan. Als ik goed gezien heb heb jij een Nvidia 8 serie videokaart en Vista 64-bit, dus zou je de laatstgenoemde driver kunnen proberen. De 185.85 drivers zijn flink getest (want WHQL gecertificeerd), dus installatie daarvan zou in ieder geval de videokaart-drivers als bron van je problemen moeten uitsluiten.

Blijft wel overeind dat het zinvol is eerst de hardware-tests (geheugen-test) te doen voordat je besluit de videokaart-driver te updaten.

Succes,

Tijs.

 

[DoRcO]

Ok, ik kwam via Driver Detective er inderdaad achtre dat een deel niet Up-To-Date was,
maar dan moet je weer een licentie hebben om ze te updaten,
ik heb ook al proberen de driver te zoeken, maar kan deze niet vinden (op de offi. site ook niet)

ik heb offli. de
NVIDIA 8800 GTS Alpha Dog Edition

 

[dnties]

Memtest 86+ is inderdaad een RAM-tester. Gewoon een hele nacht laten lopen, en dan kijken of er meldingen staan.

Wellicht zou driver genius je inderdaad kunnen melden of je drivers bij zijn of niet. Voor wat betreft je videokaart-driver: Zie mijn vorige posting.

Je andere log geeft geen extra informatie waar ik direct wat mee kan.

Succes,

Tijs.

 

[dnties]

Die driver die ik aanwees lijkt mij wel degelijk voor jouw grafische kaart, want in het tabblad Systems supported van die driver staat o.a.:

GeForce 8800 Ultra
GeForce 8800 GTX
GeForce 8800 GTS 512
GeForce 8800 GTS
GeForce 8800 GT
GeForce 8800 GS

Succes,

Tijs.

 

[DoRcO]

waar vind je die 8800 GST 512 ??
ik zie alleen:

NVIDIA GeForce 8800 Ultra |
Learn More NVIDIA GeForce 8800 GTX |
Learn More NVIDIA GeForce 8800 GTS | >>> is het niet
Learn More NVIDIA GeForce 8800 GT Alpha Dog | >>> is het niet
Learn More NVIDIA GeForce 8800 GS |
Learn More NVIDIA GeForce 8600 GTS |
Learn More NVIDIA GeForce 8600 GT |
Learn More NVIDIA GeForce 8500 GT |
Learn More NVIDIA GeForce 8400 GS |
Learn More NVIDIA GeForce 8300 GS |
Learn More

 

[dnties]

Ik ben ervan overtuigd dat het wel degelijk de goede driver is. De driver is nl. voor de hele Geforce 8-serie van videokaarten met nvidia chips erop.

Op je foto staat duidelijk 8800 GTS, en die zie ik in mijn lijstje van ondersteunde videokaarten toch echt staan (zie mijn vorige posting).

Tijs.

 

[DoRcO]

Ik ben ervan overtuigd dat het wel degelijk de goede driver is. De driver is nl. voor de hele Geforce 8-serie van videokaarten met nvidia chips erop.

Op je foto staat duidelijk 8800 GTS, en die zie ik in mijn lijstje van ondersteunde videokaarten toch echt staan (zie mijn vorige posting).

Tijs.

Ja, weet ik... maar dat lijstje wat jij vond kan ik nergen vinden,
op de video kaart is 8800 GTS Alpha Dog Edition te zien (512 MB)

kun je misschien een link sturen naar dat lijstje ?

bedankt
Mvg,

 

[dnties]

Staat op die link van de driver die ik je al gegeven heb. Daar staan 3 'tabbladen', waaronder "Products supported".

Tijs.

 

[DoRcO]

o, je bedoel de
v. 185.85 (Vista 64-bit)
... ik zat telkens rond te zoeken op xfxforce.com
daar kon ik de drivers dus ook niet vinden
ik ga ze installeren... ook gaf driver genius een aantal anderen aan...

185.85_desktop_winvista_64bit_whql (nvidia driver)
amd_9-5_vista32-64_raid
amd_9-5_vista32-64_sb
Ralink_RT256x_drv2130
realtek_hdaudio_224_vista
realtek_rtl8139_6110_vista
realtek_rts5101_60620113_vista


deze allemaal, gewoon wat soud en graphic drivers

waarom installeerd hij met de AMD 9-5 installaties ATI Catalyst ??
ik heb geen ATI hardware in m'n kast

 

[DoRcO]

Het gebeurde zojuist weer,
ik zal nog een keer de debug posten...





Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini052509-01.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`02859000 PsLoadedModuleList = 0xfffff800`02a1edb0
Debug session time: Mon May 25 10:46:09.559 2009 (GMT+2)
System Uptime: 0 days 0:15:21.761
*********************************************************************
* 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, {28, c, 0, fffff80002895e1e}

***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+3ce1e )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000028, memory referenced
Arg2: 000000000000000c, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002895e1e, address which referenced memory

Debugging Details:
------------------

***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************

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.

MODULE_NAME: nt

FAULTING_MODULE: fffff80002859000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 49ac93e1

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
0000000000000028

CURRENT_IRQL: 0

FAULTING_IP:
nt+3ce1e
fffff800`02895e1e ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from fffff800028ad3ee to fffff800028ad650

STACK_TEXT:
fffffa60`0e2f2ad8 fffff800`028ad3ee : 00000000`0000000a 00000000`00000028 00000000`0000000c 00000000`00000000 : nt+0x54650
fffffa60`0e2f2ae0 00000000`0000000a : 00000000`00000028 00000000`0000000c 00000000`00000000 fffff800`02895e1e : nt+0x543ee
fffffa60`0e2f2ae8 00000000`00000028 : 00000000`0000000c 00000000`00000000 fffff800`02895e1e fffff6fb`7e200470 : 0xa
fffffa60`0e2f2af0 00000000`0000000c : 00000000`00000000 fffff800`02895e1e fffff6fb`7e200470 00000000`00000000 : 0x28
fffffa60`0e2f2af8 00000000`00000000 : fffff800`02895e1e fffff6fb`7e200470 00000000`00000000 00000000`00000000 : 0xc


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt+3ce1e
fffff800`02895e1e ?? ???

SYMBOL_NAME: nt+3ce1e

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

 

[dnties]

[...]waarom installeerd hij met de AMD 9-5 installaties ATI Catalyst ??
ik heb geen ATI hardware in m'n kast

Geen idee. Wel is het natuurlijk zo dat AMD en ATI nu bij elkaar horen, maar het installeren van Catalyst zou eigenlijk alleen moeten gebeuren als je een ATI grafische kaart zou hebben (maar die heb je juist niet).
EDIT: Je nieuwe dump-analyse voegt niets toe: Weer mogelijk driver probleem of hardware/temperatuur probleem. Beter eerst de hardware/geheugen testen en de drivers updaten en dan nog eens kijken.

Tijs.

 

[DoRcO]

zal ik doen, heb inmiddels de nvidia vista x64 geinstalleerd, en nu maar af wachten :/