Du bist nicht eingeloggt! Möglicherweise kannst du deswegen nicht alles sehen.
  (Noch kein mods.de-Account? / Passwort vergessen?)
Zur Übersichtsseite powered by supergeek.de Live Long - T-Shirt Genuine Vault Shelter - T-Shirt Dino Bot - T-Shirt
Hallo anonymer User.
Bitte logge dich ein
oder registriere dich!
 Moderiert von: Atomsk, buschi


 Thema: Täglicher BSOD
erste ungelesene Seite | letzter Beitrag 
Achumani

AUP Achumani 27.11.2007
Frage
Hi,

in dem System sind

Windows 7 Pro x64,
Intel Xeon E3-1231v3,
eine Crucial MX100 512GB SSD,
eine (alte) Samsung HD501J HDD und
16GB Crucial Ballistix Sport DDR3-1600 RAM verbaut.

Mittlerweile bekomme ich fast jedes Mal wenn ich den PC aus dem Energiesparmodus starte einen BSOD. Öfter mal SYSTEM_SERVICE_EXCEPTION oder MEMORY_MANAGEMENT, aber auch viele andere Varianten treten auf.

Ich hab schon mal das 'Diagnostizieren von Arbeitsspeicherproblemen'-Tool laufen lassen, aber da war alles in Ordnung. Woran kann es sonst liegen? Sollte ich besser das System neu aufsetzen?
22.10.2015 18:51:31 Zum letzten Beitrag
[ zitieren ] [ pm ] [ diesen post melden ]
Zunami das Dod0

AUP Zunami das Dod0 22.02.2014
Probier mal WhoCrashed.
Dann weißt du, ob es an irgendeinem Treiber liegt.

Bei mir lag es an dieser verhurten ASUS-Mainboard-Optimierungssoftware, die genau gar nichts bringt, außer BSOD beim Zocken.
23.10.2015 11:55:50 Zum letzten Beitrag
[ zitieren ] [ pm ] [ diesen post melden ]
Achumani

AUP Achumani 27.11.2007
 
Code:
Crash dumps are enabled on your computer.

On Thu 22.10.2015 16:41:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102215-6084-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200) 
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8005FFFE80, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Thu 22.10.2015 16:41:25 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8005FFFE80, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Thu 22.10.2015 08:54:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102215-6271-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000355EFAF, 0xFFFFF88004853DD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
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 Wed 21.10.2015 16:04:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102115-6676-01.dmp
This was probably caused by the following module: srvnet.sys (0xFFFFF88005D740BF) 
Bugcheck code: 0x50 (0xFFFFF8A102D6994A, 0x0, 0xFFFFF88005D740BF, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\srvnet.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Server Network driver
Bug check description: This indicates that invalid system memory has been referenced.
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 standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Fri 09.10.2015 23:00:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101015-3978-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x83240) 
Bugcheck code: 0x18 (0xFFFFFA800C7AD270, 0xFFFFFA80112E3780, 0x1, 0x1)
Error: REFERENCE_BY_POINTER
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy
drivers, not because of faulty RAM modules. 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices,
Inc.). 
Google query: Advanced Micro Devices, Inc. REFERENCE_BY_POINTER



On Sun 20.09.2015 20:51:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092015-7488-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0) 
Bugcheck code: 0x50 (0xFFFFFA60110D2370, 0x1, 0xFFFFF8000327B344, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Wed 12.08.2015 06:16:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081215-6052-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003413157, 0xFFFFF8800A0F4E10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
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 Fri 07.08.2015 14:15:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080715-6474-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4211) 
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800944B2A8, 0xFFFFF8800944AB00, 0xFFFFF880010A2290)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: NT-Dateisystemtreiber
Bug check description: This indicates a problem occurred in the NTFS file system. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Wed 05.08.2015 11:20:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080515-6333-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0) 
Bugcheck code: 0x4E (0x99, 0x3AF0E9, 0x2, 0x3AE9E8)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy
drivers, not because of faulty RAM modules. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Wed 22.07.2015 05:54:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072215-5787-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800032CAA9C, 0xFFFFF88003B72AA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
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. 




Conclusion

25 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for
updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: 

atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your
computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information. 




Also einmal war es die Grafikkarte, aber ansonsten immer was am Speicher. Laut dem Windows 'Diagnostizieren von Arbeitsspeicherproblemen'-Tool ist der aber in Ordnung. Gibt es ein besseres Speicher Diagnosetool, ohne dass ich die Riegel rausnehmen muss?
[Dieser Beitrag wurde 1 mal editiert; zum letzten Mal von Achumani am 23.10.2015 13:38]
23.10.2015 13:37:30 Zum letzten Beitrag
[ zitieren ] [ pm ] [ diesen post melden ]
Zunami das Dod0

AUP Zunami das Dod0 22.02.2014
http://www.memtest.org/
23.10.2015 13:48:40 Zum letzten Beitrag
[ zitieren ] [ pm ] [ diesen post melden ]
Achumani

AUP Achumani 27.11.2007
missmutig gucken
Hmm, memtest findet Fehler. Aber Umtausch dauert 10 Arbeitstage, das mache ich dann bevor ich das nächste mal in Urlaub fahre. Noch gehts ja (meistens).
27.10.2015 1:42:06 Zum letzten Beitrag
[ zitieren ] [ pm ] [ diesen post melden ]
 Thema: Täglicher BSOD


mods.de - Forum » Windows » 

Hop to:  

mods.de | | tech | blog | T-Shirt Shop


powered by supergeek.de Live Long - T-Shirt Genuine Vault Shelter - T-Shirt Dino Bot - T-Shirt