Welkom op ons forum!

Heb je een computerprobleem of een algemene vraag? Registreer een account op het forum, wij helpen je dan graag verder om het probleem vakkundig op te lossen.

Gebruikersavatar
Marre
Lid
Berichten: 2
Lid geworden op: 15 aug 2011 00:03

Hallo, heb nu al even last van een BSOD meestal 1 keer per dag wanneer ik mijn laptop opstart of wanneer die lang dicht is maar stand by is.
Dit komt nadat ik een trojan had, AVG signaleerde pc viel uit en kon alleen terug naar fabrieksinstellingen. Ik herinstalleerde mijn laptop en alles ging goed de eerste keer tot ik al mijn (ongeveer) 100 windows update te verwerken kreeg toen die halverwege stopte omdat hij er eentje niet kon installeren krijg ik altijd een bsod als ik mijn pc opstart.

Ben al even op zoek op internet maar pc bleef werken nadat ik in veilige modus heb gestart dus heb ik er niet echt haast van gemaakt.

Via WhoCrashed ben ik dit te weten gekomen.
System Information (local)
--------------------------------------------------------------------------------

computer name: MARRE-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Pentium(R) Dual-Core CPU T4400 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4221542400 total
VM: 2147352576, free: 2002042880



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 14-8-2011 21:43:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081411-68453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002AA5047, 0x0, 0x7FFFFFA0000)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
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 which cannot be identified at this time.


On Sun 14-8-2011 21:43:22 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: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002AA5047, 0x0, 0x7FFFFFA0000)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 which cannot be identified at this time.


On Sun 14-8-2011 10:03:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081411-65863-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0x41, 0x2, 0x1, 0xFFFFF80002AC74D8)
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 which cannot be identified at this time.


On Sun 14-8-2011 9:57:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081411-38001-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002AA3047, 0x0, 0x7FFFFFA0000)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
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 which cannot be identified at this time.


On Sun 14-8-2011 9:50:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081411-38251-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF80002A784D8)
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 which cannot be identified at this time.


On Fri 12-8-2011 11:19:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081211-37611-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002A71047, 0x0, 0x7FFFFFA0000)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
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 which cannot be identified at this time.


On Fri 12-8-2011 3:02:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081211-43758-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002A71047, 0x0, 0x7FFFFFA0000)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
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 which cannot be identified at this time.


On Wed 10-8-2011 11:35:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081011-40185-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0x600DD, 0x2, 0x1, 0xFFFFF80002A628C5)
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 which cannot be identified at this time.



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

8 crash dumps have been found and analyzed.
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 actually 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.
Gebruikersavatar
swaken
Lid
Berichten: 88
Lid geworden op: 07 jan 2011 01:59

Beste Marre,
Best hier een bericht posten. De helpers zullen zullen het daar sneller vinden en je verder kunnen helpen.
http://www.hijackthis.nl/forum/viewforum.php?f=4
Wil je in het topic een verwijstopic plaatsen naar dit topic.
Als je probleem niet malware gerelateerd zal ik je achteraf hier dan trachten verder te helpen.

Groetjes
swaken
Degelijk en veilig computergebruik begint bij jezelf.
Gebruiker van Windows Vista, Ubuntu, PCLinuxOS
Gebruikersavatar
Marre
Lid
Berichten: 2
Lid geworden op: 15 aug 2011 00:03

Ok heb daar een nieuw topic gemaakt...

Terug naar “Blauwe schermen en opstartproblemen”