ntoskrnl.exe probleem, hangende pc, blauw scherm

[Arion Rufus]

Hallo,
Ik heb het volgende systeem;

Gigabyte ga-ep45-ud3r
4GB (2x2GB) Kingston ValueRam 800MHz
Core 2 Duo E8200
1TB hitachi deskstar (64mb cache)
Sapphire Radeon 4850 - 1GB
Coolermaster 520W Modular
windows 7 Ultimate x64

Nu loopt dit systeem soms random vast.
Ik verdacht eerst de harde schijf omdat deze begon te tikken. WD HD Tooltjes laten lopen, maar geen fouten.
Toch even andere HD erin en de oude nu als extern, geen effect.
-memtest gedaan, geen fouten. Kan ik nogmaals doen?
-benchmark test, 'Furmark' voor de videokaart zonder problemen.

Nu heb ik een logje;
On Sun 12-6-2011 8:49:20 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x888A, 0xFFFFF8A00782D5D0, 0x4615151665750627, 0xFFFFFA8000400020)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\061211-15319-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.


On Wed 8-6-2011 13:07:45 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xC2 (0x7, 0x1097, 0x0, 0xFFFFFA8005C17910)
Error: BAD_POOL_CALLER
Dump file: C:\Windows\Minidump\060811-15210-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.


On Tue 7-6-2011 8:49:39 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x8886, 0xFFFFFA80003BD3F0, 0xFFFFFA8000400050, 0x500)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\060711-16536-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.


On Sun 5-6-2011 14:58:55 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\060511-13462-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.


On Wed 25-5-2011 12:13:33 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\052511-13650-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.


On Tue 24-5-2011 11:39:33 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0xD1 (0xFFFFF8800133CC7C, 0x2, 0x8, 0xFFFFF8800133CC7C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\052411-15459-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.


On Mon 23-5-2011 5:49:03 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x8886, 0xFFFFFA8001C16850, 0xFFFFFA8000400050, 0x200)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\052311-18345-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.


On Sat 21-5-2011 11:00:18 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\052111-16130-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.


On Wed 18-5-2011 10:56:48 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x403, 0xFFFFF680000399E8, 0xC360000015557835, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\051811-18439-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.


On Sun 15-5-2011 17:35:16 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x8886, 0xFFFFFA80003FF510, 0xFFFFFA8000400050, 0x500)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\051511-14398-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.


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

10 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.

Het is steeds (behalve 1 keer) ntoskrnl.exe
Wat is er kapot?
Alvast hartelijke dank!

[Anoniem: 302635]

je weet dat je ntoskrnl.exe ook gewoon op google kan zoeken he.. http://www.google.nl/sear...341276l0l0l0l0l0l0l0l0l0l vind ik zo al genoeg hits.

ik heb even gekeken en ik vond dit als eerste mischien heb je er iets
Op deze pagina vind ik de volgende oplossing:

To restore this file follow the below steps.

1- Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.
2 - Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
3 - In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
4 - Select the operating system you wish to fix, and then enter the administrator password.
5 - Type expand d:\i386\ntoskrnl.ex_ c:\windows\system32
6 - You will then be prompted if you wish to overwrite the file type Y and press enter to overwrite the file.
7 - Type exit to reboot the computer.

[Voor 58% gewijzigd door Anoniem: 302635 op 14-06-2011 23:39]

[Zorian]

Ook al vind ie nu geen fouten, ik zou de schijf goed in de gaten blijven houden. Tikkende geluiden luiden (meestal) het einde van de schijf in.

[Arion Rufus]

@banaan en Xereon
Ik heb er een nieuwe windows 7 installatie opgezet, dus ik neem aan dat dit dan ook het ntoskrnl.exe zou vervangen, aangezien er ook een nieuwe harde schijf in zit.
Maar wat kan het probleem dan zijn.
bedankt!

---> toch nog volledige memtest x86 uitvoeren lijkt me?

[Voor 11% gewijzigd door Arion Rufus op 15-06-2011 09:33]

[Soundstorm2010]

Ik denk dat je misschien een Verkeerde Win7 hebt gedownload/gekopieerd.

Mijn sug = Download een Nieuwe Win7 (zonder of met SP1)
Brand op nieuw, installeer op nieuw.

Ik heb ook win7 x64 en nog nooit problemen.

MeMtest86x kun je altijd draaien (laat hem de hele nacht lopen)
Geen problemen ?

Probeer eens bankje voor bankje te wisselen.

1. als je 4 slots hebt. begin bij 1, en eindig dan bij 4 (met 1 geheugen bankje dan)(laat memtest altijd lopen)
2. Probleem blijft voordoen, probeer eens andere geheugen.

3. Je kunt als uiteindelijk nog 1 ding proberen, en dat is XP installeren.
4. Kijk of je daar problemen mee hebt of niet\

Suc6

[Starke]

Arion Rufus schreef op dinsdag 14 juni 2011 @ 23:20:
<snip>
Nu loopt dit systeem soms random vast.
<snip>

Loopt het systeem echt random vast, is het niet bij 1 bepaald programma wat je (normaal) hebt kunnen laten lopen maar met bijvoorbeeld een driver update blue screens geeft?

Analyseer je dmp's is met meuk: BlueScreenView 1.31 om te kijken wat er als crashende driver(s) aangegeven worden, misschien dat dit meer opheldering geeft.

Ik heb hetzelfde maar alleen met 1 game die ik speel (moet nog proberen met videokaart driver downgrade).

[Arion Rufus]

Memtest laten lopen, 24 uur, geen errors, maarja dat zegt ook nog niet alles

@Starke
Het systeem loopt inderdaad random vast, geen specifieke programma's.

Ik kan eigenlijk niets anders bedenken dan het geheugen..