Solved BSOD - KMODE Exception 0x1e ffffff'c....

[mos3110]

Hi everyone I am getting random BSOD's

Here are some of the whocrashed it and bluescreen view summaries - I have also attached the dmp files

I also have 300 something errors in the memtest too.

The bluescreenview summary of dump files show a range of problems all with ntoskrnl - vwifibus, parport, netbios.sys dump_pciidex
==================================================
Dump File : 050214-21481-01.dmp
Crash Time : 2/05/2014 11:38:09 AM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`030ef1e0
Parameter 3 : 00000000`00000000
Parameter 4 : ffffffff`ffffffff
Caused By Driver : dump_pciidex.sys
Caused By Address : dump_pciidex.sys+2eaa150
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\050214-21481-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 288,872
Dump File Time : 2/05/2014 11:39:30 AM
==================================================

==================================================
Dump File : 050214-20108-01.dmp
Crash Time : 2/05/2014 11:10:28 AM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`030a4150
Parameter 3 : 00000000`00000000
Parameter 4 : ffffffff`ffffffff
Caused By Driver : parport.sys
Caused By Address : parport.sys+3266700
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\050214-20108-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 288,872
Dump File Time : 2/05/2014 11:11:30 AM
==================================================



On Fri 2/05/2014 1:38:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050214-21481-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030EF1E0, 0x0, 0xFFFFFFFFFFFFFFFF)
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 that cannot be identified at this time.



On Fri 2/05/2014 1:10:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050214-20108-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030A4150, 0x0, 0xFFFFFFFFFFFFFFFF)
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 that cannot be identified at this time.



On Fri 2/05/2014 1:01:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050214-22136-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030E81E0, 0x0, 0xFFFFFFFFFFFFFFFF)
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 that cannot be identified at this time.



On Fri 2/05/2014 12:53:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050214-21949-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4211)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88007F7DEF8, 0xFFFFF88007F7D750, 0xFFFFF800030F1150)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 Fri 2/05/2014 12:41:26 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050214-23852-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003100150, 0x0, 0xFFFFFFFFFFFFFFFF)
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 that cannot be identified at this time.

 

[Arc]

Hi mos3110.

The output of WhoCrashed or BSview is not very trustworthy. Specially when it contradicts with your physical finding.

I also have 300 something errors in the memtest too.

So RAM is failing. One single error is enough to decide that memory is failing.

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

When the bad RAM is detected, replace it with one that is of same specs of the existing one. Or you may change the entire RAM kit too.
_________________________________________

BugCheck 1E, {ffffffffc0000005, fffff800030ef1e0, 0, ffffffffffffffff}

[COLOR=Red]Probably caused by : memory_corruption[/COLOR] ( nt!MiReplenishPageSlist+150 )

Followup: MachineOwner
---------

BugCheck 24, {1904fb, fffff88007f7def8, fffff88007f7d750, fffff800030f1150}

[COLOR=Red]Probably caused by : memory_corruption[/COLOR] ( nt!MiReplenishPageSlist+c0 )

Followup: MachineOwner
---------

 

[mos3110]

Thank you Arc - I have replaced the ram - it now appears OK!

 

[Arc]