Nvidia GeForce 9500 GT Bluescreen nvlddmkm.sys

[Razor®]

ist das richtig so?

[Razor®]

Informationsliste Wert
North Bridge Eigenschaften
North Bridge Intel Eaglelake G41
Revision / Stepping 03 / A3
Gehäusetyp 1254 Pin FC-BGA
Gehäusegröße 3.4 cm x 3.4 cm
Fertigungstechnologie 65 nm
Kern Spannung 1.125 V
In-Order Queue Depth 12

Speichercontroller
Typ Dual Channel (128 Bit)
Aktiv-Modus Single Channel (64 Bit)

Speicher Timings
CAS Latency (CL) 6T
RAS To CAS Delay (tRCD) 6T
RAS Precharge (tRP) 6T
RAS Active Time (tRAS) 15T
Row Refresh Cycle Time (tRFC) 44T
Command Rate (CR) 1T
RAS To RAS Delay (tRRD) 3T
Write Recovery Time (tWR) 15T
Read To Read Delay (tRTR) Same Rank: 4T, Different Rank: 9T
Read To Write Delay (tRTW) 8T
Write To Read Delay (tWTR) Same Rank: 13T, Different Rank: 8T
Write To Write Delay (tWTW) Same Rank: 4T, Different Rank: 7T
Read To Precharge Delay (tRTP) 6T
Write To Precharge Delay (tWTP) 15T
Precharge To Precharge Delay (tPTP) 1T
Refresh Period (tREF) 3120T
DRAM Read ODT 3T
DRAM Write ODT 7T
MCH Read ODT 8T
Performance Level 4
Read Delay Phase Adjust Neutral
DIMM3 Clock Fine Delay 11T
DIMM4 Clock Fine Delay 1T

Fehlerkorrektur
ECC Nicht unterstützt
ChipKill ECC Nicht unterstützt
RAID Nicht unterstützt
ECC Scrubbing Nicht unterstützt

Speichersteckplätze
DRAM Steckplatz #1 2 GB (DDR3-1333 DDR3 SDRAM)

Integrierter Grafik-Controller
Grafik-Controllertyp Intel GMA X4500
Grafik-Controllerstatus Deaktiviert

PCI Express Controller
PCI-E 2.0 x16 port #2 Belegt @ x16 (nVIDIA GeForce 9500 GT Video Adapter)

Chipsatzhersteller
Firmenname Intel Corporation
Produktinformation Intel Chipsets
Treiberdownload Support for Chipsets
BIOS Aufrüstungen BiosAgentPlus.com - Extend your PC's life with a BIOS update
Treiberupdate DriverAgent - Device Driver Downloads, Updates, and Scans

[Razor®]

Haste so alles was du brauchst
Und leider war mein RAM nit schuldig an mein Bluescreen problem

[Razor®]

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


Loading Dump File [C:\Windows\Minidump\083111-17706-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 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a00000 PsLoadedModuleList = 0xfffff800`02c45e90
Debug session time: Wed Aug 31 13:49:41.388 2011 (UTC + 2:00)
System Uptime: 0 days 0:41:51.136
************************************************** *******************
* 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
.....
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8003ceb390, fffff8800f184cd8, 0, 2}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded 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+170cd8 )

Followup: MachineOwner
---------
Also das ist mit das windows Debugger tool

[Razor®]

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: fffff80002a00000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4e391010

FAULTING_IP:
nvlddmkm+170cd8
fffff880`0f184cd8 4883ec28 sub rsp,28h

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`061ea988 fffff880`0fcd5000 : 00000000`00000116 fffffa80`03ceb390 fffff880`0f184cd8 00000000`00000000 : nt+0x80640
fffff880`061ea990 00000000`00000116 : fffffa80`03ceb390 fffff880`0f184cd8 00000000`00000000 00000000`00000002 : dxgkrnl+0x5d000
fffff880`061ea998 fffffa80`03ceb390 : fffff880`0f184cd8 00000000`00000000 00000000`00000002 00000000`00000000 : 0x116
fffff880`061ea9a0 fffff880`0f184cd8 : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 : 0xfffffa80`03ceb390
fffff880`061ea9a8 00000000`00000000 : 00000000`00000002 00000000`00000000 00000000`00000000 fffff880`0fcd4d0a : nvlddmkm+0x170cd8


STACK_COMMAND: kb

FOLLOWUP_IP:
nvlddmkm+170cd8
fffff880`0f184cd8 4883ec28 sub rsp,28h

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nvlddmkm+170cd8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

[Invincible]

Hier meine Angaben Informationsliste Wert
Motherboard Eigenschaften
Motherboard ID 64-0100-009999-00101111-030310-Eaglelake$1ETON000_
Motherboard Name Foxconn H-I41-uATX (Eton)

Front Side Bus Eigenschaften



Bustyp Intel AGTL+
Busbreite 64 Bit
Tatsächlicher Takt 200 MHz (QDR)
Effektiver Takt 800 MHz
Bandbreite 6400 MB/s

Speicherbus-Eigenschaften
Bustyp DDR3 SDRAM
Busbreite 64 Bit
DRAM:FSB Verhältnis 12:6
Tatsächlicher Takt 400 MHz (DDR)
Effektiver Takt 800 MHz
Bandbreite 6400 MB/s

Chipsatzbus-Eigenschaften
Bustyp Intel Direct Media Interface

Motherboardhersteller
Firmenname Hon Hai Precision Industry Co., Ltd.
Produktinformation Foxconn - Products: Motherboard
BIOS Download Foxconn - Support - Downloads
Treiberupdate DriverAgent - Device Driver Downloads, Updates, and Scans
BIOS Aufrüstungen BiosAgentPlus.com - Extend your PC's life with a BIOS update

da hast du doch dein Treiber !

[Razor®]

Mein Problem ist immer noch nicht gelöst und NVIDIA® finde ich was für'n Arsch! Ich habe gehört das die von ATI günstiger und im Vergleich bessere Qualität haben als die von Nvidia. Aber leider ist dies nivht meiner Lösung

[simpel1970]

Speicher Timings
CAS Latency (CL) 6T
RAS To CAS Delay (tRCD) 6T
RAS Precharge (tRP) 6T
RAS Active Time (tRAS) 15T
Row Refresh Cycle Time (tRFC) 44T
Command Rate (CR) 1T

Stelle die Command Rate im Bios auf 2T. Wird es dann besser?
Wenn nicht, poste ein paar Screenshots von CPU-Z (Reiter Mainboard, CPU, Memory und SPD).