Zufällige Bluescreens

drsommer1

Schraubenverwechsler(in)
Zufällige Bluescreens

Hallo, ich bin ein wenig am Verzweifeln und hoffe auf Hilfe (und darauf, dass das hier das richtige Unterforum ist)!
Ich bekomme komplett zufällig Bluescreens mit der Fehlermeldung IRQL_NOT_LESS_OR_EQUAL und ATTEMPTED_TO_WRITE_READONLY_MEMORY. Mein Betriebssystem ist Win10, die Treiber sind alle aktuell, den RAM habe ich mit memtest 86 bereits geprüft und der Fehler ist nicht reproduzierbar. Ich habe mal folgende Eckpunkte meines Systems und der Abstürze für euch parat:

Computer: MSI MS-7388
CPU: AMD Phenom II X4 920 (Deneb, RB-C2 (Ridgeback))
2800 MHz (14.00x200.0) @ 2800 MHz (14.00x200.0)
Motherboard: MSI MS-7388
BIOS: V1.11, 06/24/09
Chipset: AMD 790X (RD780) + SB600
Memory: 4096 MBytes @ 400 MHz, 6-6-6-18
- 2048 MB PC6400 DDR2-SDRAM - Nanya Technology NT2GT64U8HD0BY-AD
- 2048 MB PC6400 DDR2-SDRAM - Nanya Technology NT2GT64U8HD0BY-AD
Graphics: MSI N750Ti Gaming (MS-V310)
NVIDIA GeForce GTX 750 Ti, 2048 MB GDDR5 SDRAM
Drive: Samsung SSD 850 EVO 250GB, 244.2 GB, Serial ATA 6Gb/s @ 3Gb/s
Sound: ATI/AMD SB600 - High Definition Audio Controller
Sound: NVIDIA GM107 - High Definition Audio Controller
Network: RealTek Semiconductor RTL8168B/8111B PCI-E Gigabit Ethernet Adapter
Network: Realtek RTL8192CU Wireless LAN 802.11n USB 2.0 Network Adapter
OS: Microsoft Windows 10 Professional (x64) Build 17134.285 (1803/RS4)


Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Mon 08.10.2018 08:27:46 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100818-7125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9380)
Bugcheck code: 0xBE (0xFFFF966AF7D71818, 0x8A00000000200121, 0xFFFFFD8B2B0596D0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 08.10.2018 08:27:46 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (Ntfs+0xD6C92)
Bugcheck code: 0xBE (0xFFFF966AF7D71818, 0x8A00000000200121, 0xFFFFFD8B2B0596D0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\ntfs.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: NT-Dateisystemtreiber
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Sun 07.10.2018 18:01:31 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100718-6078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9380)
Bugcheck code: 0xA (0xFFFFFB8000000000, 0x2, 0x0, 0xFFFFF802DE18A99F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Zurück