New
#1
Multiple BSODs with ntoskrnl.exe as the culprit?
For a long time, I've been suffering from BSODs. Just yesterday I had two, one while browsing the web, and another while playing Medieval II: Total War. Here is the analysis from WhoCrashed:
-----
On Fri 16/04/2010 18:36:06 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\041610-19546-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 Fri 16/04/2010 17:52:06 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF800028A7786)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\041610-17596-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.
------
At first I thought installed Windows 7 wrongly (for some reason files were left over from my XP system, even though I had selected "Custom Install") and the local repair shop suggested reinstalling XP, then installing 7 again. They did so, and this time it was a clean install. The BSODs I was getting before were different however:
------
On Tue 06/04/2010 17:05:32 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x28, 0x2, 0x1, 0xFFFFF80002AC5517)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\040610-17238-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 04/04/2010 09:54:46 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x28, 0x2, 0x1, 0xFFFFF800028C2517)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\040410-19344-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 Fri 02/04/2010 20:28:44 your computer crashed
This was likely caused by the following module: dxgkrnl.sys
Bugcheck code: 0xA (0x28, 0x2, 0x1, 0xFFFFF80002876517)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\040210-17659-01.dmp
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 Fri 02/04/2010 15:20:39 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x28, 0x2, 0x1, 0xFFFFF80002879517)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\040210-17082-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.
------
(Stupidly I didn't back up the crash dump files themselves, so I'm afraid I can't attach them.)
Also previously, Windows Memory Diagnostic was telling me that there were errors with my memory. Now it's saying otherwise.
I've got a few things left to try; I haven't yet updated my audio drivers, so that'll be my next step I suppose, and I've read suggestions such as updating my chipset drivers and testing my HDD.
Still, if anyone could offer any help, I'd be very appreciative.
Quote