Ernstige fout PC sluit af en start opnieuw op

Status
Niet open voor verdere reacties.

snarf54

Verenigingslid
Lid geworden
2 aug 2004
Berichten
896
Heb W10 Home op een zelfbouw Azerty i5 PC
Van tijd tot tijd ernstige fout blauw scherm pc sluit af en start opnieuw op.
Vaak als deze is achtergebleven met een aantal progamma's / pagina's open.

Met 8 GB intern en OS op SSD 500 GB zou dat toch geen probleem mogen zijn.

Snel foto gemaakt helaas niet de gehele tekst erop gekomen.
Sluit deze wel bij.

Is er ergens een log waarin ik deze fout kan terug vinden ?

Wellicht zijn er ook helpmijers die aan de fout al zien wat het probleem wellicht zou kunnen zijn.
 

Bijlagen

  • Foutmelding restart.JPG
    Foutmelding restart.JPG
    37,1 KB · Weergaven: 112
Naast dat je plaatje erg onscherp is laat deze ook niet de error code zien. En daar gaat het nu net om bij het achterhalen van een oorzaak.
 
Videokaartdriver via apparaatbeheer deïnstalleren en rebooten, windows zelf de driver laten installeren.

Was het een upgrade of een verse W10 installatie?
 
Clean install door Azerty van W10.
Uit een andere topic Wincrash gehaald.

report

On Sat 14-11-2015 12:44:17 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xFDE0B)
Bugcheck code: 0x7E (0xFFFFFFFFC000001D, 0xFFFFF800388FDE0B, 0xFFFFD00055334608, 0xFFFFD00055333E20)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 355.98
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 355.98
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 355.98 , NVIDIA Corporation).
Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED


Huidige driver 355.98
Volgens NVidia nieuwste 358.91

Al eens eerder NVidia driver verwijderd en die van Microsoft genomen maar dat gaf meer crashes.

Nu (net weer) alleen melding dat de beelschermadapter niet werkt maar alles blijft wel functioneren.
Nieuwste van Nvdia proberen ?

Is een GTX750 Ti.

ps foutmelding niet scherp maar was nog maar 15 sec en moest phone nog pakken/app starten...
 
Laatst bewerkt:
Gedaan en met progje Wncrash kan ik dan direct de fout ontdekken (en posten)
 
Na update driver nog geen "crash" gehad. Wie weet is deze dan beter versie 358.91. Zie nu wel dat er een nieuwere is 359.00. Ik wacht er nog even mee.
 
Nieuwe drivers kunnen aan de laatste hardware (lees grafische kaart) wat toevoegen maar maar aan oudere niet en als het werkt, afblijven
 
Te vroeg enthousiast geworden.
Vandaag zelfs 2 x crash.
Onderstaand rapport.
Nu niet specifiek verwezen naar de Nvidia video driver...

Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: H81M-S2H, Gigabyte Technology Co., Ltd.
CPU: GenuineIntel Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8483483648 bytes total


Code:
________________________________________
Crash Dump Analysis 
________________________________________

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Mon 30-11-2015 19:27:59 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\113015-4703-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF8D, 0x2, 0xFFFFF800E6C2FEA0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 Mon 30-11-2015 19:27:59 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: 0x50 (0xFFFFFFFFFFFFFF8D, 0x2, 0xFFFFF800E6C2FEA0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 Mon 30-11-2015 18:32:23 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\113015-5375-01.dmp
This was probably caused by the following module: mcupdate.sys (mcupdate+0x1035) 
Bugcheck code: 0xD1 (0x20, 0xFF, 0x0, 0xFFFFF801A8F71035)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: mcupdate.sys . 
Google query: mcupdate.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Thu 26-11-2015 19:36:04 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112615-4718-01.dmp
This was probably caused by the following module: mcupdate_genuineintel.dll (mcupdate_GenuineIntel!UpdateRegistry+0x6F) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8011F81A06F, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\mcupdate_genuineintel.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Intel Microcode Update Library
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 that cannot be identified at this time. 



On Sun 15-11-2015 19:10:55 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111515-6437-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xEB53F) 
Bugcheck code: 0xD1 (0x10B, 0x2, 0x1, 0xFFFFF800AD9BB53F)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 358.91 
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 358.91 
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 358.91 , NVIDIA Corporation). 
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
 
Laatst bewerkt door een moderator:
Memtest loopt (staat op USB) maar draait nu al 12 uur. Is dat gebruikelijk ? Nog geen errors gevonden maar loopt nog...
 
Uiteindelijk toch maarr gestopt.
19 passes en geen errors.
Dus daar zit het zeer waarschijnlijk niet.
 
Weer een crash

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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 5-12-2015 08:19:30 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\120515-4640-01.dmp
This was probably caused by the following module: netio.sys (NETIO!IndexHashAdd+0x3C)
Bugcheck code: 0x19 (0x3, 0xFFFFE0006DE48180, 0xFFFFE0006DE48182, 0xFFFFE0006DE48180)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 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 Sat 5-12-2015 08:19:30 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: netio.sys (NETIO!IndexHashAdd+0x3C)
Bugcheck code: 0x19 (0x3, 0xFFFFE0006DE48180, 0xFFFFE0006DE48182, 0xFFFFE0006DE48180)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 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.

Heb wel nieuwste Nvidia driver geinstalleerd.

Wel weer een andere melding.
 
Moet zo weg dus kijk later vandaag even naar de link
Inmiddels weer een crash

On Sat 5-12-2015 10:56:09 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\120515-4562-01.dmp
This was probably caused by the following module: mcupdate_genuineintel.dll (mcupdate_GenuineIntel!UpdateRegistry+0x52)
Bugcheck code: 0xFC (0xFFFFD00012F5094C, 0x8000000001100121, 0xFFFFD0002C8756A0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\mcupdate_genuineintel.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Intel Microcode Update Library
Bug check description: This indicates that an attempt was made to execute non-executable memory.
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. There is a possibility this problem was caused by a virus or other malware.
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 Sat 5-12-2015 10:56:09 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: mcupdate_genuineintel.dll (mcupdate_GenuineIntel!UpdateRegistry+0x52)
Bugcheck code: 0xFC (0xFFFFD00012F5094C, 0x8000000001100121, 0xFFFFD0002C8756A0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\mcupdate_genuineintel.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Intel Microcode Update Library
Bug check description: This indicates that an attempt was made to execute non-executable memory.
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. There is a possibility this problem was caused by a virus or other malware.
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.
 
Hier de bios versie
Zie F2 dus dat zou up to date zijn. Right ?

Fabrikant Gigabyte Technology Co. Ltd.
Model H81M-S2H (SOCKET 0)
Versie x.x
Chipsetfabrikant Intel
Chipsetmodel Haswell
Chipset-herziening 06
Southbridgefabrikant Intel
Southbridge-model H81
Southbridge-herziening C2
Systeemtemperatuur 28 °C
BIOS
Merk American Megatrends Inc.
Versie F2
Datum 11-8-2015

Nieuwe drivers
Hmm misschien beetje boven mijn pet.
Bijgaand schermpint.
Welke zou ik al eerste proberen?
Geen ervaring wijst dit zichzelf na het downloaden ?
 

Bijlagen

  • Drivers Gigabyte.jpg
    Drivers Gigabyte.jpg
    82,1 KB · Weergaven: 66
Laatst bewerkt door een moderator:
Enige update is de HD Graphics driver. Zie bijlage.
Maar dat is toch voor de built in grafische kaart die niet gebruikt wordt omdat de Nvidia GTX 750 Ti erin zit ?
Driver GTX 750 ongewijzigd. Deze opnieuw installeren ?

Hoppa nieuwe crash weer andere meldingen....

Code:
[I]On Sat 5-12-2015 21:32:01 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\120515-4796-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpMcUpdatePostUpdate+0x1F) 
Bugcheck code: 0xF7 (0x2800874B8804, 0x87F828BF884, 0xFFFFF7807D74077B, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that a driver has overrun a stack-based buffer.
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 Sat 5-12-2015 21:32:01 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalpMcUpdatePostUpdate+0x1F) 
Bugcheck code: 0xF7 (0x2800874B8804, 0x87F828BF884, 0xFFFFF7807D74077B, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that a driver has overrun a stack-based buffer.
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. [/I]
Is het heel gek om voortestellen de NVIDIA GTX 750 Ti via Apparaatbeheer uit te schakelen en de standard video van de Intel processor te gebuiken ? Wel € 150 weg gegooid natuurlijk ?

Moet ik dan monitor HDMI kabel ook anders aansluiten ?
Pff word er wel beetje hopeloos van..
 

Bijlagen

  • Intel HD Graphics update driver.JPG
    Intel HD Graphics update driver.JPG
    17,4 KB · Weergaven: 55
Laatst bewerkt door een moderator:
Status
Niet open voor verdere reacties.
Terug
Bovenaan Onderaan