Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD - KMODE Exception 0x1e ffffff'c....

01 May 2014   #1
mos3110

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

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.


My System SpecsSystem Spec
.
02 May 2014   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Hi mos3110.

The output of WhoCrashed or BSview is not very trustworthy. Specially when it contradicts with your physical finding.
Quote:
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:

testSlot1Slot2
RAM1ErrorError
RAM2GoodGood
It is a RAM, a bad RAM.

But if you have got a result like that:

testSlot1Slot2
RAM1ErrorGood
RAM2ErrorGood
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.
_________________________________________
Code:
BugCheck 1E, {ffffffffc0000005, fffff800030ef1e0, 0, ffffffffffffffff}

Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+150 )

Followup: MachineOwner
---------
Code:
BugCheck 24, {1904fb, fffff88007f7def8, fffff88007f7d750, fffff800030f1150}

Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )

Followup: MachineOwner
---------
My System SpecsSystem Spec
02 May 2014   #3
mos3110

32
 
 

Thank you Arc - I have replaced the ram - it now appears OK!
My System SpecsSystem Spec
.

02 May 2014   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

My System SpecsSystem Spec
Reply

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




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD from System Service Exception and KMode Exception Not Handled
For a long time now i have been getting BSOD's, pretty much all of the time from System Service Exception and KMode Exception Not Handled. Sometimes the PC never gets to the BSOD and just freezes up and restarts. This happens at any time whether im doing nothing or on the internet, sometimes it...
BSOD Help and Support
BSOD, Memory Management + Kmode Exception Not Handled
Hi guys. Recently I have been getting a few BSODs. I have attached the requested .zip file of the most recent crashes (some previous ones have been wiped for disk clean-ups and reformatting etc.). Thanks in advance for any help. The only things I can think of that made the problem happen are the...
BSOD Help and Support
BSOD - Kmode exception and System Service exception
Hi Guys, I'm a composer working on a deadline and have started to experience quite intermittent BSOD's. It appears to happen at higher system loads. I'm reasonably experienced in building custom machines (this is my third on), and so far have never experienced issues with them. This current...
BSOD Help and Support
BSOD IRQL Not Less or Equal, KMode Exception Not Handled, Service Exce
Hey, I keep getting BSOD every few hours randomly. I've tried updating drivers, removing AVG, Registry cleaners, MemTest64, and Seagate drive test. Here are my dump files. I'm just stuck and need some help. Any ideas will be much appreciated. Thanks, Mugsy420
BSOD Help and Support
Random BSOD, errors IRQL not less or equal/KMODE exception not handled
Hi all, the last month has been a real nightmare: I started getting BSODs practically out of the blue and it's happening more and more often. I can't recall installing anything particular at the time (I use the PC mostly to work and navigate the web), and I haven't changed any piece of hardware,...
BSOD Help and Support
BSOD: kmode exception not handled
I have been trying to find an answer to this issue. I've started having a lot of BSOD errors this past week and can't seem to diagnose the issue. I've updated video drivers, updated my BIOS, un-installed and re-installed programs. I'm wondering if anyone can spot my issue in these files. Windows...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 07:26.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App