System Service Exception

D

Daryl_Dixon

Komplett-PC-Käufer(in)
Gestern neues System zusammen gebaut mit i9 9900k msi z390 board

Win10 installiert sowie Treiber gab keine Probleme.

So jetzt habe ich ein neues Problem: system service exception Bluescreen

Hier die Debug

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff800`17c18000 PsLoadedModuleList = 0xfffff800`18032a50
Debug session time: Sat Jan 12 09:41:09.000 2019 (UTC + 1:00)
System Uptime: 0 days 15:18:52.739
Loading Kernel Symbols
...............................................................
................................................................
.........................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`00a26018). Type ".hh dbgerr001" for details
Loading unloaded module list
..............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`17dc9b40 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffd8e`bff0de40=000000000000003b
6: 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: fffff80017d32b7b, Address of the instruction which caused the bugcheck
Arg3: fffffd8ebff0e770, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
KEY_VALUES_STRING: 1

PROCESSES_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1

DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434
SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd.
SYSTEM_PRODUCT_NAME: MS-7B17
SYSTEM_SKU: Default string
SYSTEM_VERSION: 1.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 1.10
BIOS_DATE: 09/28/2018
BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd.
BASEBOARD_PRODUCT: MPG Z390 GAMING PRO CARBON AC (MS-7B17)
BASEBOARD_VERSION: 1.0
DUMP_TYPE: 1
BUGCHECK_P1: c0000005
BUGCHECK_P2: fffff80017d32b7b
BUGCHECK_P3: fffffd8ebff0e770
BUGCHECK_P4: 0
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.

FAULTING_IP:
nt!ObReferenceObjectSafeWithTag+b
fffff800`17d32b7b 488b01 mov rax,qword ptr [rcx]

CONTEXT: fffffd8ebff0e770 -- (.cxr 0xfffffd8ebff0e770)
rax=0000000000000000 rbx=ffffb9097ba7b480 rcx=ffdfb90978984050
rdx=000000006e457350 rsi=ffdfb90978984368 rdi=ffffb90979ce5080
rip=fffff80017d32b7b rsp=fffffd8ebff0f160 rbp=fffffd8ebff0fa80
r8=fffffd8ebff0f198 r9=0000000000000000 r10=00000000000000f4
r11=fffffd8ebff0f160 r12=0000000000000000 r13=fffff80018026680
r14=0000000000000000 r15=ffdfb90978984080
iopl=0 nv up ei ng nz na po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010287
nt!ObReferenceObjectSafeWithTag+0xb:
fffff800`17d32b7b 488b01 mov rax,qword ptr [rcx] ds:002b:ffdfb909`78984050=????????????????
Resetting default scope
BUGCHECK_STR: 0x3B_c0000005
CPU_COUNT: 10
CPU_MHZ: e10
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: c
CPU_MICROCODE: 6,9e,c,0 (F,M,S,R) SIG: 9E'00000000 (cache) 9E'00000000 (init)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: Steam.exe
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-LAEPECP
ANALYSIS_SESSION_TIME: 01-12-2019 12:04:40.0485
ANALYSIS_VERSION: 10.0.18303.1000 amd64fre
LAST_CONTROL_TRANSFER: from fffff800182bc5f4 to fffff80017d32b7b
STACK_TEXT:
fffffd8e`bff0f160 fffff800`182bc5f4 : ffffb909`7ba7b480 00000000`00000000 00000000`00000000 00000000`00000016 : nt!ObReferenceObjectSafeWithTag+0xb
fffffd8e`bff0f190 fffff800`182bf62a : 00000000`00000000 00000000`00010400 00000000`00000000 00000000`00000000 : nt!ExpGetProcessInformation+0x7c4
fffffd8e`bff0f7b0 fffff800`182bed8b : 00000000`00000000 00000000`77713600 00000000`099ef824 00000000`0924fda0 : nt!ExpQuerySystemInformation+0x77a
fffffd8e`bff0f9c0 fffff800`17ddad85 : ffffb909`00000000 00000000`00000001 00000000`01d4aa52 fffffd8e`bff0fa80 : nt!NtQuerySystemInformation+0x2b
fffffd8e`bff0fa00 00007fff`f9bdfd24 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`0924e4b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`f9bdfd24


THREAD_SHA1_HASH_MOD_FUNC: 682e836043c394197e635db551ed01ec735b1513
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 8749be01a63d7f2b2248404b569e57221119f278
THREAD_SHA1_HASH_MOD: f08ac56120cad14894587db086f77ce277bfae84
FOLLOWUP_IP:
nt!ObReferenceObjectSafeWithTag+b
fffff800`17d32b7b 488b01 mov rax,qword ptr [rcx]
FAULT_INSTR_CODE: 48018b48
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ObReferenceObjectSafeWithTag+b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .cxr 0xfffffd8ebff0e770 ; kb
BUCKET_ID_FUNC_OFFSET: b
FAILURE_BUCKET_ID: 0x3B_c0000005_nt!ObReferenceObjectSafeWithTag
BUCKET_ID: 0x3B_c0000005_nt!ObReferenceObjectSafeWithTag
PRIMARY_PROBLEM_CLASS: 0x3B_c0000005_nt!ObReferenceObjectSafeWithTag
TARGET_TIME: 2019-01-12T08:41:09.000Z
OSBUILD: 17763
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: unknown_date
BUILDDATESTAMP_STR: 180914-1434
BUILDLAB_STR: rs5_release
BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434
ANALYSIS_SESSION_ELAPSED_TIME: 20ba
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x3b_c0000005_nt!obreferenceobjectsafewithtag
FAILURE_ID_HASH: {014d8bdc-ae92-986d-30ac-113aabd76764}
Followup: MachineOwner

Wäre cool wenn ihr mir da helfen könntet.
 
c0000005 Speicherzugriffsverletzung
Können veraltete Treiber sein ,oder Fremdsoftware
Bios mal aktuallisieren
Chipsatztreiber vom Boardhersteller
Windows 10 ist die neuste Version?Mal nach Updates suchen lassen?
 
grafik treiber ist aus netz.
mainboard von der cd
updates aktualisiere ich immer kommt immer mal was neues zum installieren bis jetzt
 
Mach mal einen Systemcheck mit:
SFC/Scannow in der Eingabeauf.

Bios könnte man auch mal aktuallisieren,weil das ja noch eine recht neue CPU ist
 
habe ich gemacht hat kein Fehler gefunden inzwischen hatte ich wieder ein Bluescreen mit IRQL NOT LESS OR EQUAL

mit win7 hatte ich noch nie probs dieses drecks win10 kotzt mich sowas von an
 
Bios mal aktuallisiert?
Wie sieht der letzte BSOD genau aus?
Der wird gespeichert unter C:Windows/Minidump
Kann man mit Bluescreenviewer oder Windows Debugger auswerten.
Übertaktet ist nix am PC?
 
ne habe noch nix übertaktet



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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff802`19e1c000 PsLoadedModuleList = 0xfffff802`1a236a50
Debug session time: Sun Jan 13 14:54:06.079 2019 (UTC + 1:00)
System Uptime: 0 days 3:16:37.827
Loading Kernel Symbols
...............................................................
................................................................
..........................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`00eb9018). Type ".hh dbgerr001" for details
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`19fcdb40 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff305`3f0873e0=000000000000000a
5: 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: 00000000000000b8, memory referenced
Arg2: 0000000000000002, 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: fffff80219ed4a01, address which referenced memory

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd.

SYSTEM_PRODUCT_NAME: MS-7B17

SYSTEM_SKU: Default string

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1.10

BIOS_DATE: 09/28/2018

BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd.

BASEBOARD_PRODUCT: MPG Z390 GAMING PRO CARBON AC (MS-7B17)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 1

BUGCHECK_P1: b8

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80219ed4a01

READ_ADDRESS: 00000000000000b8

CURRENT_IRQL: 2

FAULTING_IP:
nt!NtGetWriteWatch+711
fffff802`19ed4a01 0fb687b8000000 movzx eax,byte ptr [rdi+0B8h]

CPU_COUNT: 10

CPU_MHZ: e10

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: c

CPU_MICROCODE: 6,9e,c,0 (F,M,S,R) SIG: 9E'00000000 (cache) 9E'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

ANALYSIS_SESSION_HOST: DESKTOP-LAEPECP

ANALYSIS_SESSION_TIME: 01-13-2019 16:44:49.0637

ANALYSIS_VERSION: 10.0.18303.1000 amd64fre

TRAP_FRAME: fffff3053f087520 -- (.trap 0xfffff3053f087520)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=f0e64895ff150000
rdx=00000000000c00e1 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80219ed4a01 rsp=fffff3053f0876b0 rbp=0000000000000000
r8=00000000000008e1 r9=00000000000000e1 r10=fffff80219e8c5b0
r11=fffff3053f087420 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!NtGetWriteWatch+0x711:
fffff802`19ed4a01 0fb687b8000000 movzx eax,byte ptr [rdi+0B8h] ds:00000000`000000b8=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80219fdf369 to fffff80219fcdb40

STACK_TEXT:
fffff305`3f0873d8 fffff802`19fdf369 : 00000000`0000000a 00000000`000000b8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff305`3f0873e0 fffff802`19fdb78e : ffffce08`bf107080 ffffe281`98bcb180 ffff03e3`779d8b25 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff305`3f087520 fffff802`19ed4a01 : ffffe281`98bcb180 00000000`00000000 ffffe281`98cc9400 fffff802`1a257800 : nt!KiPageFault+0x44e
fffff305`3f0876b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtGetWriteWatch+0x711


THREAD_SHA1_HASH_MOD_FUNC: 266c45e23eda1deab9c8af0e9f2e0bbb2d7af161

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: bf278d60904441cbae7ace2dab8e6b2e89c1ff21

THREAD_SHA1_HASH_MOD: d084f7dfa548ce4e51810e4fd5914176ebc66791

FOLLOWUP_IP:
nt!NtGetWriteWatch+711
fffff802`19ed4a01 0fb687b8000000 movzx eax,byte ptr [rdi+0B8h]

FAULT_INSTR_CODE: b887b60f

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!NtGetWriteWatch+711

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 711

FAILURE_BUCKET_ID: AV_nt!NtGetWriteWatch

BUCKET_ID: AV_nt!NtGetWriteWatch

PRIMARY_PROBLEM_CLASS: AV_nt!NtGetWriteWatch

TARGET_TIME: 2019-01-13T13:54:06.000Z

OSBUILD: 17763

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: unknown_date

BUILDDATESTAMP_STR: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: aaa

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nt!ntgetwritewatch

FAILURE_ID_HASH: {d031f7d2-21da-1d74-fd66-f6c99ed20bf4}

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

Fast 1000€ ausgegeben und nur probs -.-
 
Läuft der Ram auch mit standard Takt,oder mit 3000mhz?
Wieder 08/15 Windows datei Fehler mit dem man nix anfangen kann.IMAGE_NAME: ntkrnlmp.exe
Muss aber nicht immer nur am BS liegen wenn die Maschine nicht stabil läuft.
Kannst ja die System Dateien überprüfen mit SFC/Scannow,aber ich vermute eher das es nicht direkt an Windows liegt.

Kann deinen Frust verstehen wenn das Sys nich ordentlich läuft bei dem Geld was man investiert hat.

Ist das Bios jetzt auf dem neusten Stand?
 
Den Ram würde ich auch mal Testweise mit Stock Werten (2133Mhz)laufen lassen.Läuft der mit dem XMP Profil?
Sicher das das Mainboard nicht automatisch was OC?
Das sind oft eben Instabilitäten von Treibern oder von der Hardware würde ich sagen und nicht unbedingt immer von Windows.
Laut den BSOD ist es aber eben kein spezieller Treiber.
 
Einloggen o. Registrieren zum Antworten.

Ähnliche Themen

G
PC startet ohne ersichtlichen Grund neu.
Antworten
14
Aufrufe
2K
wuselsurfer
W
T
Gelegentllicher Bluescreen
Antworten
7
Aufrufe
4K
tomtom19861
T
K
Bluescreen IRQL_NOT_LESS_OR_EQUAL
Antworten
4
Aufrufe
1K
Farkadonitis
Farkadonitis
T
Rechner - Bluescreen-Abstürze, unterschiedliche Fehlermeldungen
Antworten
7
Aufrufe
2K
TDXL
T
H
IRQL_NOT_LESS_OR_EQUAL nach frischer Windows 10 Installation
Antworten
14
Aufrufe
7K
haudegen16
H
Oben Unten
Zurück