Bluscreens 0x0000003b ntoskrnl.exe

UntiBunti

Lieutenant
Dabei seit
März 2011
Beiträge
609
Guten Abend liebe CB User,
seit geraumer Zeit schon plagen mich "Bluescreens", sie sind zwar selten jedoch nerven sie. Das Problem dabei ist jedoch, dass ich die Ursache einfach nicht ausfindig machen kann. Der Bug Check Code 0x0000003b und "Treiber" ntoskrnl.exe treffen leider auf tausende Sachen zu, so zumindest wird es in anderen Foren beschrieben. Als Bug Check String wird meistens nichts angezeigt, wenn doch dann "SYSTEM_SERVICE_EXCEPTION"

Bei mir trifft der Fehler immer dann auf wenn ich en Computer mehrere Stunden laufen lasse bzw. mehrere Anwendungen gleichzeitig laufen habe. zB: Diablo III, Steam, Origin, Hardware Monitor, Interent Explorer ec.


Leider habe ich die alten "Bluescreens" nicht mehr im Minidump gespeichert nur den von heute:

Unbenannt.PNG

==================================================
Dump File : 033015-12214-01.dmp
Crash Time : 30.03.2015 18:49:18
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`0407ac2f
Parameter 3 : fffff880`0c8f0bb0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+74ec0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+74ec0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Processors Count : 6
Major Version : 15
Minor Version : 7601
Dump File Size : 276.400
Dump File Time : 30.03.2015 18:50:24
==================================================

Bisher habe ich:

Memtest86+ (12h) -> 0 Fehler

CPU auf Default für zwei Wochen -> Selber Bluescreen

Temperatur Überwacht von Graka und Prozessor

Updates Installiert Windows

Von MS den Hotfixe versucht zu installieren jedoch kommt die Fehlermeldung nicht für das System geeignet https://support.microsoft.com/de-at/kb/980932/de

Neu Aufgesetzt

Neue Grafikkarten Treiber (sauber Deinstalliert und wieder Installiert) (Hatte früher Probleme mit den Treibern und hatte auch immer Bluscreens "atisysdag" oder so...)

---------------------------------------

Leider alles ohne Erfolg die Bluescreens kommen immer wieder. Ich bin echt mit meinem Latein am ende :/.
PS: Weitere Bluscreens werde ich einfach jetzt mit den Details hier drunter posten.

Mein System:

Betriebssystem
Windows 7 Ultimate 64-bit SP1
CPU
AMD Phenom II X6 1100T 26 °C
Thuban 45nm Technologie
RAM
8,00GB Dual Kanal DDR3 @ 669MHz (9-9-9-24)
Motherboard
Gigabyte Technology Co., Ltd. GA-890FXA-UD7 (Socket M2) 38 °C
Grafik
MD 20400 (1920x1080@60Hz)
2048 MBATI AMD Radeon HD 6900 Series (Sapphire/PCPartner) 41 °C
2048 MBATI AMD Radeon HD 6900 Series (XFX Pine Group) 38°
CrossFire
Speicher
232GB Samsung SSD 840 EVO 250G SATA Disk Device (SSD) 27 °C
931GB Seagate ST310005 24AS SATA Disk Device (SATA) 30 °C
2794GB Seagate ST3000DM 001-1ER166 SATA Disk Device (SATA) 28 °C
Optische Laufwerke
ATAPI iHAS224 B ATA Device
HL-DT-ST DVDROM DH18NS40 ATA Device
 
Zuletzt bearbeitet:

Inteli

Lt. Junior Grade
Dabei seit
Dez. 2014
Beiträge
442
Stell bei den Subtimings tRFC Wert vom Ram mal 128 ein.
 

UntiBunti

Lieutenant
Ersteller dieses Themas
Dabei seit
März 2011
Beiträge
609
wie stell ich das ein, im BIOS finde ich den wert tRFC nicht
Ergänzung ()

Habs kann aber nur 90ns ,110ns <- Default, 160 ns, 300ns, 350ns....
Ergänzung ()

Das sagt der Debugger von MS



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


Loading Dump File [C:\Users\Unti\Desktop\033015-12214-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
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
Machine Name:
Kernel base = 0xfffff800`03c60000 PsLoadedModuleList = 0xfffff800`03ea4890
Debug session time: Mon Mar 30 18:49:18.117 2015 (UTC + 2:00)
System Uptime: 0 days 8:55:34.209
*********************************************************************
* 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
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
...........

************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8000407ac2f, fffff8800c8f0bb0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 : ntoskrnl.exe ( nt+41ac2f )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8000407ac2f, Address of the instruction which caused the bugcheck
Arg3: fffff8800c8f0bb0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: fffff80003c60000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 54d0317d

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

FAULTING_IP:
nt+41ac2f
fffff800`0407ac2f 488b4908 mov rcx,qword ptr [rcx+8]

CONTEXT: fffff8800c8f0bb0 -- (.cxr 0xfffff8800c8f0bb0;r)
rax=fffffa80091a1620 rbx=fffff8a001bfa5b0 rcx=f7fff8a001bfa590
rdx=fffff8800c8f1648 rsi=fffffa8006caebf0 rdi=0000000000000000
rip=fffff8000407ac2f rsp=fffff8800c8f1590 rbp=fffff8800c8f1710
r8=fffff8800146a038 r9=0000000000000000 r10=0000000000000000
r11=fffffa80091a15d0 r12=fffff8800c8f1648 r13=0000000000000000
r14=0000000000000000 r15=fffffa8006caec00
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+0x41ac2f:
fffff800`0407ac2f 488b4908 mov rcx,qword ptr [rcx+8] ds:002b:f7fff8a0`01bfa598=????????????????
Last set context:
rax=fffffa80091a1620 rbx=fffff8a001bfa5b0 rcx=f7fff8a001bfa590
rdx=fffff8800c8f1648 rsi=fffffa8006caebf0 rdi=0000000000000000
rip=fffff8000407ac2f rsp=fffff8800c8f1590 rbp=fffff8800c8f1710
r8=fffff8800146a038 r9=0000000000000000 r10=0000000000000000
r11=fffffa80091a15d0 r12=fffff8800c8f1648 r13=0000000000000000
r14=0000000000000000 r15=fffffa8006caec00
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+0x41ac2f:
fffff800`0407ac2f 488b4908 mov rcx,qword ptr [rcx+8] ds:002b:f7fff8a0`01bfa598=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x3B

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8000407ac2f

STACK_TEXT:
fffff880`0c8f1590 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x41ac2f


FOLLOWUP_IP:
nt+41ac2f
fffff800`0407ac2f 488b4908 mov rcx,qword ptr [rcx+8]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+41ac2f

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

STACK_COMMAND: .cxr 0xfffff8800c8f0bb0 ; kb

BUCKET_ID: WRONG_SYMBOLS

FAILURE_BUCKET_ID: WRONG_SYMBOLS

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:wrong_symbols

FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}

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

Ergänzung ()

Ich weiß nicht weiter ich führe einfach nochmal einen memtest durch heute nacht
Ergänzung ()

liegt definitiv nicht am Speicher
 
Zuletzt bearbeitet:

UntiBunti

Lieutenant
Ersteller dieses Themas
Dabei seit
März 2011
Beiträge
609
habe ich ja schon versucht steht oben im Text
Ergänzung ()

Jetzt sind es die AMD Treiber wieder -,- nach dem Motto "i have no idea what my computer is doing" ...

wieso schießen sich die Treiber immer wieder ab -,- ???
Unbenannt.PNG
 
Zuletzt bearbeitet:

UntiBunti

Lieutenant
Ersteller dieses Themas
Dabei seit
März 2011
Beiträge
609
ja ist beides installiert und der Treibers ist schon auf 14.12
Unbenannt.PNG

habe mal im BIOS die Spannungen angehoben vom HT link...ich bin gezwungen den mit dem IMC gleichzeitig anzuheben da die "Bluscreens" ja verschiedene Ursachen haben dachte ich mit wäre das momentan die plausibelste erklärung ...
 
Zuletzt bearbeitet:

Darlis

Commodore
Dabei seit
Jan. 2011
Beiträge
4.458
Du hast 2 Grafikkarten drin -> Bau' mal eine aus.
Du hast übertaktet? Bios-Reset machen und Defaults laden.
Dann Screenshots von CPU-Z von den Arbeitsspeicher-Reitern machen sowie von CrystalDiskInfo von allen Platten mit aufgezogenem Fenster.
 
Top