Hallo,
ich bin mit meinem Latein am Ende. Ich hatte mir Windows 7 neu installiert und einige Updates gemacht. Seit dem Update auf framework 4.6.1 ging das Win Update nicht mehr, also habe ich mittels Systemwiederherstellung das Update rückgängig gemacht, was auch funktionierte. Updates gehen nun wieder. Allerdings bekomme ich nun öfter mal einen BSOD
Variante 1:
Variante 2:
Variante 3:
Ich hatte erst den GraKa Treiber in Verdacht und den noch einmal installiert, was beim zweiten Versuch auch klappte. Ich verwende Win 7 32bit (mit sp1) mit 4gb ram (3,25 verwendet), eine geForce 9500 GT und einen amdx64 dualcore prozessor.
Das win eigene ram test tool fand nichts und die festplatte ist laut crystaldiskinfo auch ok.
Kann jemand helfen? Schonmal danke im voraus
EDIT: Bisher traten die BSOD nur beim installieren von Programmen auf. nVidia, chrome usw. sfc /scannow fand auch nichts
EDIT2: hier der Report von WhoCrashed:
Verstehe ich das richtig, dass ein Treiber schuld ist? Die meisten hat Windows automatisch beim installieren erkannt. Netzwerkadapter habe ich über Win Update aktualisiert (Realtek PCIe GBE Family Controller) und nVidia den hier: 341.92-desktop-win8-win7-winvista-32bit-international
EDIT3:
habe mal die dumps angehängt. Mag sie bitte jemand debuggen? Bei mir klappt das nicht mit debugDiag2 analyse.
ich bin mit meinem Latein am Ende. Ich hatte mir Windows 7 neu installiert und einige Updates gemacht. Seit dem Update auf framework 4.6.1 ging das Win Update nicht mehr, also habe ich mittels Systemwiederherstellung das Update rückgängig gemacht, was auch funktionierte. Updates gehen nun wieder. Allerdings bekomme ich nun öfter mal einen BSOD
Variante 1:
==================================================
Dump File : 021116-21859-01.dmp
Crash Time : 11.02.2016 10:11:19
Bug Check String : ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug Check Code : 0x000000be
Parameter 1 : 0x0075008c
Parameter 2 : 0x48166005
Parameter 3 : 0x943dd6f4
Parameter 4 : 0x0000000a
Caused By Driver : halmacpi.dll
Caused By Address : halmacpi.dll+5ba9
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+8e3c1
Stack Address 1 : ntkrnlpa.exe+40be8
Stack Address 2 : ntkrnlpa.exe+a2d8a
Stack Address 3 : ntkrnlpa.exe+31d5c
Computer Name :
Full Path : C:\Windows\Minidump\021116-21859-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 153.888
Dump File Time : 11.02.2016 10:13:08
==================================================
Dump File : 021116-21859-01.dmp
Crash Time : 11.02.2016 10:11:19
Bug Check String : ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug Check Code : 0x000000be
Parameter 1 : 0x0075008c
Parameter 2 : 0x48166005
Parameter 3 : 0x943dd6f4
Parameter 4 : 0x0000000a
Caused By Driver : halmacpi.dll
Caused By Address : halmacpi.dll+5ba9
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+8e3c1
Stack Address 1 : ntkrnlpa.exe+40be8
Stack Address 2 : ntkrnlpa.exe+a2d8a
Stack Address 3 : ntkrnlpa.exe+31d5c
Computer Name :
Full Path : C:\Windows\Minidump\021116-21859-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 153.888
Dump File Time : 11.02.2016 10:13:08
==================================================
Variante 2:
==================================================
Dump File : 021116-19640-01.dmp
Crash Time : 11.02.2016 10:29:03
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0x00000098
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x828abd8a
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+40cbf
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.19135 (win7sp1_gdr.160121-1718)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+40cbf
Stack Address 1 : ntkrnlpa.exe+a2d8a
Stack Address 2 : ntkrnlpa.exe+31d5c
Stack Address 3 : ntkrnlpa.exe+28456f
Computer Name :
Full Path : C:\Windows\Minidump\021116-19640-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 154.368
Dump File Time : 11.02.2016 10:33:20
==================================================
Dump File : 021116-19640-01.dmp
Crash Time : 11.02.2016 10:29:03
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0x00000098
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x828abd8a
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+40cbf
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.19135 (win7sp1_gdr.160121-1718)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+40cbf
Stack Address 1 : ntkrnlpa.exe+a2d8a
Stack Address 2 : ntkrnlpa.exe+31d5c
Stack Address 3 : ntkrnlpa.exe+28456f
Computer Name :
Full Path : C:\Windows\Minidump\021116-19640-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 154.368
Dump File Time : 11.02.2016 10:33:20
==================================================
Variante 3:
==================================================
Dump File : 021116-24046-01.dmp
Crash Time : 11.02.2016 09:22:31
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0x00000028
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x828add8a
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+40cbf
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.19135 (win7sp1_gdr.160121-1718)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+40cbf
Stack Address 1 : ntkrnlpa.exe+a2d8a
Stack Address 2 : ntkrnlpa.exe+31d5c
Stack Address 3 : ntkrnlpa.exe+28456f
Computer Name :
Full Path : C:\Windows\Minidump\021116-24046-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 151.744
Dump File Time : 11.02.2016 09:24:25
==================================================
Dump File : 021116-24046-01.dmp
Crash Time : 11.02.2016 09:22:31
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0x00000028
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x828add8a
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+40cbf
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.19135 (win7sp1_gdr.160121-1718)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+40cbf
Stack Address 1 : ntkrnlpa.exe+a2d8a
Stack Address 2 : ntkrnlpa.exe+31d5c
Stack Address 3 : ntkrnlpa.exe+28456f
Computer Name :
Full Path : C:\Windows\Minidump\021116-24046-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 151.744
Dump File Time : 11.02.2016 09:24:25
==================================================
Ich hatte erst den GraKa Treiber in Verdacht und den noch einmal installiert, was beim zweiten Versuch auch klappte. Ich verwende Win 7 32bit (mit sp1) mit 4gb ram (3,25 verwendet), eine geForce 9500 GT und einen amdx64 dualcore prozessor.
Das win eigene ram test tool fand nichts und die festplatte ist laut crystaldiskinfo auch ok.
Kann jemand helfen? Schonmal danke im voraus
EDIT: Bisher traten die BSOD nur beim installieren von Programmen auf. nVidia, chrome usw. sfc /scannow fand auch nichts
EDIT2: hier der Report von WhoCrashed:
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 11.02.2016 09:29:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021116-19640-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x40CBF)
Bugcheck code: 0xA (0x98, 0x2, 0x1, 0xFFFFFFFF828ABD8A)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 Thu 11.02.2016 09:29:03 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x28B7)
Bugcheck code: 0xA (0x98, 0x2, 0x1, 0xFFFFFFFF828ABD8A)
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.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe IRQL_NOT_LESS_OR_EQUAL
On Thu 11.02.2016 09:11:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021116-21859-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E3C1)
Bugcheck code: 0xBE (0x75008C, 0x48166005, 0xFFFFFFFF943DD6F4, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntkrnlpa.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 Thu 11.02.2016 08:22:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021116-24046-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x40CBF)
Bugcheck code: 0xA (0x28, 0x2, 0x1, 0xFFFFFFFF828ADD8A)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 crash dumps have been found and analyzed. 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:
ntkrpamp.exe
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.
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.
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 11.02.2016 09:29:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021116-19640-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x40CBF)
Bugcheck code: 0xA (0x98, 0x2, 0x1, 0xFFFFFFFF828ABD8A)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 Thu 11.02.2016 09:29:03 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x28B7)
Bugcheck code: 0xA (0x98, 0x2, 0x1, 0xFFFFFFFF828ABD8A)
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.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe IRQL_NOT_LESS_OR_EQUAL
On Thu 11.02.2016 09:11:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021116-21859-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E3C1)
Bugcheck code: 0xBE (0x75008C, 0x48166005, 0xFFFFFFFF943DD6F4, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntkrnlpa.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 Thu 11.02.2016 08:22:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021116-24046-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x40CBF)
Bugcheck code: 0xA (0x28, 0x2, 0x1, 0xFFFFFFFF828ADD8A)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 crash dumps have been found and analyzed. 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:
ntkrpamp.exe
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.
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.
Verstehe ich das richtig, dass ein Treiber schuld ist? Die meisten hat Windows automatisch beim installieren erkannt. Netzwerkadapter habe ich über Win Update aktualisiert (Realtek PCIe GBE Family Controller) und nVidia den hier: 341.92-desktop-win8-win7-winvista-32bit-international
EDIT3:
habe mal die dumps angehängt. Mag sie bitte jemand debuggen? Bei mir klappt das nicht mit debugDiag2 analyse.
Anhänge
Zuletzt bearbeitet: