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
estrella
Lid
Berichten: 4
Lid geworden op: 03 jul 2011 11:39

Hallo,

al enige tijd hebben wij last van een BlueScreen. Hierdoor blijft de computer uitvallen.

Eerder hadden we dit bericht al geplaatst met de hijackThis logjes maar het heeft niets met maleware te maken
Ik hoop dat iemand ons hier kan helpen. Alvast vriendelijk bedankt!

Om het probleem te verhelpen hebben we geprobeerd de drivers opnieuw te instaleren, de computer diverse malen geformateerd en gisteren hebben we Windows 7 erop gezet. (voorheen draaiden we op XP)

Jammer genoeg is het probleem nog steeds daar.

Hieronder een logje van de foutmelding Blue Screen.

Alvast bedankt voor jullie hulp.

FOUTMELDING BlueScreen
Probleemhandtekening:
Gebeurtenisnaam van probleem: BlueScreen
Versie van besturingssysteem: 6.1.7600.2.0.0.256.1
Landinstelling-id: 1043

Aanvullende informatie over dit probleem:
BCCode: d1
BCP1: 00000000
BCP2: 00000002
BCP3: 00000000
BCP4: 914C0B83
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Bestanden die helpen bij het beschrijven van het probleem:
C:\Windows\Minidump\070311-35187-01.dmp
C:\Users\woonkamer\AppData\Local\Temp\WER-69546-0.sysdata.xml

Lees de onlineprivacyverklaring:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0413

Als de onlineprivacyverklaring niet beschikbaar is, lees dan onze offlineprivacyverklaring:
C:\Windows\system32\nl-NL\erofflps.txt
Gebruikersavatar
Abraham54
Collega Helper
Berichten: 2755
Lid geworden op: 15 feb 2010 21:00
Contacteer: Website

Hoi estrella, laten we kijken of er meer duidelijkheid te krijgen is wat betreft de BSOD's.

WhoCrashed introductie

WhoCrashed beschrijving

Download de free home edition van WhoCrashed naar je bureaublad via klik hier Afbeelding en installeer het tool via klikken/dubbelklikken op "whocrashedSetup.exe"

Nadat 'WhoCrashed' is opgestart, klik je op de "Analyze" knop.

Selekteer nu de inhoud van het venster, kopieer dit en post het resultaat in je volgende post.
Domheid is ook een gave God's, maar men mag haar niet misbruiken.
Gebruikersavatar
estrella
Lid
Berichten: 4
Lid geworden op: 03 jul 2011 11:39

Hierbij de resultaten van de WhoCrashed analyse:


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: WOONKAMER-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Celeron(R) CPU 2.53GHz Intel586, level: 15
1 logical processors, active mask: 1
RAM: 1072226304 total
VM: 2147352576, free: 1957699584



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 5-7-2011 18:00:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070511-46906-01.dmp
This was probably caused by the following module: avgtdix.sys (avgtdix+0x4DA9)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF98A9EC82, 0xFFFFFFFF98F73858, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\avgtdix.sys
product: AVG Internet Security
company: AVG Technologies CZ, s.r.o.
description: AVG Network connection watcher
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.
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: avgtdix.sys (AVG Network connection watcher, AVG Technologies CZ, s.r.o.).
Google query: avgtdix.sys AVG Technologies CZ, s.r.o. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M




On Sun 3-7-2011 15:46:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070311-71890-01.dmp
This was probably caused by the following module: avgtdix.sys (avgtdix+0x4DA9)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8E274BA1, 0xFFFFFFFF901D385C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\avgtdix.sys
product: AVG Internet Security
company: AVG Technologies CZ, s.r.o.
description: AVG Network connection watcher
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.
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: avgtdix.sys (AVG Network connection watcher, AVG Technologies CZ, s.r.o.).
Google query: avgtdix.sys AVG Technologies CZ, s.r.o. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M




On Sun 3-7-2011 10:34:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070311-36656-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x462828)
Bugcheck code: 0xD1 (0xFFFFFFFFDB33D0FF, 0x7, 0x1, 0xFFFFFFFF91484828)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 185.93
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 185.93
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.
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 185.93 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL




On Sat 2-7-2011 22:32:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070311-35187-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x484B83)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFFFFF914C0B83)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 185.93
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 185.93
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.
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 185.93 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL




On Sat 2-7-2011 20:55:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070211-42687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD1574)
Bugcheck code: 0x4E (0x9A, 0x34162, 0x3, 0x0)
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 which cannot be identified at this time.


On Sat 2-7-2011 20:44:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070211-49578-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC0823)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF93E00823, 0xFFFFFFFF9B651B84, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: Multi-User Win32-stuurprogramma
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 2-7-2011 20:38:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070211-48125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x38B5B)
Bugcheck code: 0xA (0xDA572F4, 0x2, 0x1, 0xFFFFFFFF828D2E0A)
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
--------------------------------------------------------------------------------

7 crash dumps have been found and analyzed. 4 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 185.93 , NVIDIA Corporation)

avgtdix.sys (AVG Network connection watcher, AVG Technologies CZ, s.r.o.)

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 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
Abraham54
Collega Helper
Berichten: 2755
Lid geworden op: 15 feb 2010 21:00
Contacteer: Website

Heb jij soms nog een antivirusprogramma in jouw PC?

En ook: download de nieuwste drivers voor jouw videokaart en deïnstalleer eerst de oude versie, eer je de nieuwe versie installeert.
Domheid is ook een gave God's, maar men mag haar niet misbruiken.
Gebruikersavatar
estrella
Lid
Berichten: 4
Lid geworden op: 03 jul 2011 11:39

We hebben de gratis versie van AVG op de computer staan. Verder geen andere antivirus programma's.

Ik heb net even gekeken naar de nieuwste versies van de videokaart en het systeem zegt dat ik de nieuwste versie erop heb staan. Toch eraf gooien en opnieuw erop zetten?
Gebruikersavatar
Abraham54
Collega Helper
Berichten: 2755
Lid geworden op: 15 feb 2010 21:00
Contacteer: Website

Ik adviseer je AVG in ieder geval te verwijderen en weer te installeren.
Desnoods ga je over op een ander gratis AV-programma (Avast 6\2011 Free is momenteel het allerbeste alternatief wat betreft gratis AV-programma's).

En ja, net zoals AVG vermoedelijk licht beschadigd is, kan dat zelfde ook gelden voor de videokaartdrivers.

AVG Removal tool: http://www.avg.com/nl-nl/36
Domheid is ook een gave God's, maar men mag haar niet misbruiken.
Gebruikersavatar
estrella
Lid
Berichten: 4
Lid geworden op: 03 jul 2011 11:39

hallo,

we hebben de 2 geupdate en het lijkt erop dat alles nu goed werkt.
We kijken het nog even aan, maar hij loopt nu al 3 dagen goed. :-)
Thanks voor het advies!

Groetjes,

Estrella

Terug naar “Blauwe schermen en opstartproblemen”