Aktuelle Zeit: Fr 24. Nov 2017, 06:48

 [Zurück]   Alle Zeiten sind UTC + 1 Stunde


 Menü 
 Anmelden 
Benutzername:


Passwort:

>> Passwort vergessen

Mich bei jedem Besuch automatisch anmelden

 Links
Energiespartipps
 Statistiken 
Beiträge insgesamt: 5386
Themen insgesamt: 830
Dateianhänge: 40

Themen pro Tag: 0
Beiträge pro Tag: 2
Benutzer pro Tag: 0
Themen pro Benutzer: 3
Beiträge pro Benutzer: 18
Beiträge pro Thema: 6

Mitglieder insgesamt: 299
Unser neuestes Mitglied: beetlejuice


 Seite 1 von 1
Bookmark and Share  
Autor Deine Nachricht
Mitglied
Ständiger Bluescreen - Verdacht Treiberprobleme bei aktuelle
Beitrag Nummer:#1  BeitragVerfasst: Di 12. Mai 2015, 23:13  BeitragZeige einzelnen Beitrag 
(Threadstarter)
Mitglied

Registriert: Di 12. Mai 2015, 22:26
Beiträge: 1
Themen: 1
Danke abgegeben: 0 mal
Danke erhalten: 0 mal
Guten Tag,
seit ein paar Wochen habe ich Probleme mit relativ regelmäßigen Abstürzen.
Die Bluescreennachrichten wechseln hierbei unter anderem:
page fault in nonpaged area
Reference by Pointer
IRQL_not_less_or_equal

Die Auswertung der letzten 3 dmp dateien(who crashed) schicke ich mit keine Sorge. Davor aber noch ein paar Anmerkungen:

Mein System:
Intel i5-2400 3,1
4 GB ram

Ich habe vor Kurzem die Grafikkarte gewechselt von
GTX 460 zu GTX 550 ti

Aus den Auswertungen von Who crashed entnehme ich, dass anscheinend sowohl die Grafikkartentreiber, Kaspersky und acedrv08.sys für die Abstürze verantwortlich sind. Allerdings ist der Grafikkartentreiber aktuell, genau wie kaspersky. Tatsächlich verwirrt mich die acedrv08.sys datei, da sie weder ein akitver prozess ist noch sich in der Systemdatei auftaucht in der sie eigentlich existieren sollte. Ich habe bereits meine gesamt Systempartion nach dieser mysteriösen Systemdatei durchsucht - nichts.

Schon einmal im Vorraus vielen Dank für eure Hilfe. Wenn ihr noch mehr Infos braucht, sagt bitte bescheid.

Liebe Grüße,
Xen

PS: Noch zu erwähnen wäre vielleicht, dass ich mit dem Freeware Programm WiseRegistryCleaner meine registry "geprüft und repariert" habe.
Ebenso habe ich eine Windows Speicherdiagnose durchgeführt die allerdings keine weiteren Erkenntisse brachte



Hier die Auswertungen von WhoCrashed:

computer name: XENAVANON
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: MS-7673, MSI, P67A-C45 (MS-7673)
CPU: GenuineIntel Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4274507776 total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 12.05.2015 21:16:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051215-15771-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0xA (0xFFFFDA8004DD3500, 0x2, 0x1, 0xFFFFF800032C44FC)
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 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 Tue 12.05.2015 21:16:17 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: 0xA (0xFFFFDA8004DD3500, 0x2, 0x1, 0xFFFFF800032C44FC)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Tue 12.05.2015 19:26:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051215-15241-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0x18 (0xFFFFFA8003D0C350, 0xFFFFFA800495B530, 0x1, 0x200000000000)
Error: REFERENCE_BY_POINTER
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 09.05.2015 22:32:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051015-13618-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0x50 (0xFFFFD8A00C1C4000, 0x0, 0xFFFFF800032BFA16, 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 Sat 09.05.2015 12:17:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050915-26192-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF880059A33B2)
Bugcheck code: 0x50 (0xFFFFDA80043BDA40, 0x0, 0xFFFFF880059A33B2, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 08.05.2015 13:46:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050815-13525-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x19D8C5)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880050848C5, 0xFFFFF880040FE530, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 350.12
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 350.12
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 350.12 , NVIDIA Corporation).
Google query: NVIDIA Corporation SYSTEM_SERVICE_EXCEPTION



On Thu 07.05.2015 14:35:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050715-20841-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0x19 (0x22, 0x200000000000, 0x0, 0x0)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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 06.05.2015 20:30:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050615-14944-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF880051E9ABA)
Bugcheck code: 0x50 (0xFFFFDA8006E02170, 0x0, 0xFFFFF880051E9ABA, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 350.12
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 350.12
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 350.12 , NVIDIA Corporation).
Google query: NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA



On Wed 06.05.2015 19:57:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050615-23930-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0xA (0xFFFFDA8007D97508, 0x2, 0x0, 0xFFFFF800032D1A22)
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 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 Tue 05.05.2015 23:21:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050615-16816-01.dmp
This was probably caused by the following module: usbehci.sys (usbehci+0x6C04)
Bugcheck code: 0xD1 (0x4F44465C, 0x2, 0x1, 0xFFFFF88004E3BC04)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbehci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: EHCI eUSB Miniport Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

18 crash dumps have been found and analyzed. Only 10 are included in this report. 3 third party drivers have 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:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 350.12 , NVIDIA Corporation)
kneps.sys (KNEPS Power [fre_wnet_amd64], Kaspersky Lab ZAO)
acedrv08.sys

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


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

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


Offline
 Profil  
Up 
Bot
Bot
 
Online  
PC Anfänger
Re: Ständiger Bluescreen - Verdacht Treiberprobleme bei aktu
Beitrag Nummer:#2  BeitragVerfasst: Mi 19. Aug 2015, 11:03  BeitragZeige einzelnen Beitrag 
PC Anfänger
Benutzeravatar

Registriert: Di 30. Jun 2015, 13:18
Beiträge: 17
Danke abgegeben: 0 mal
Danke erhalten: 0 mal
Klingt kompliziert. Hast du das Problem inzwischen lösen können?


Offline
 Profil  
Up 
Beiträge der letzten Zeit anzeigen:  Sortiere nach  
 Seite 1 von 1
« Vorheriges Thema | Nächstes Thema »
Gehe zu:  

Wer ist online?

Mitglieder in diesem Forum: 0 Mitglieder und 1 Gast

Ähnliche Themen
Betreff der Nachricht Forum Autor Antworten 
Script bekommt von aktuelle $location nicht mit !? Websprachen    PCFreund  20
Du darfst keine neuen Themen in diesem Forum erstellen.
Du darfst keine Antworten zu Themen in diesem Forum erstellen.
Du darfst deine Beiträge in diesem Forum nicht ändern.
Du darfst deine Beiträge in diesem Forum nicht löschen.
Du darfst keine Dateianhänge in diesem Forum erstellen.
cron