You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so , join our community today!

If you have any problems with the registration process or your account login, please contact us.

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffffa6000a0e248, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffffa6000a0e248, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

Your reads indicate memory corruption in the pagefile, and this is most
frequently used during more memory intensive operations. There are a number
of possible causes here. First, since the pagefile uses the hard drive for
memory storage, the problem may originate in drive corruption. You can both
a) run a drive diagnostic to ensure it's functioning correctly and b) delete
the existing pagefile and have it rebuilt. To do the latter, you must
disable paging temporarily and reboot, the restart it and reboot.

It's also possible that one of the programs you are regularly using is
causing the issue. This includes not only the applications you run, but
background stuff like real-time antivirus and antispyware scanners, and any
other program that autoloads at boot time. You'd have to selectively disable
these to see when the unwanted behavior stops. A good way to quickly tell if
this is the issue is to boot to safe mode and run some applications to see
if you can recreate the problem.

http://support.microsoft.com/kb/275678
This is typically the result of a new driver. You state you have loaded
three: External HDD, Nvidia, and Creative.
Try uninstalling or disable the External HDD from Device Manager and rolling
back Nvidia and Creative (one at a time.)

The bugcheck found in that full kernel dump is 0x0000001e
(0xffffffffc0000005, 0xfffffa6000a0e248, 0x0, 0xffffffffffffffff),
listing a probable cause of -"unknown image"- (the driver name could not
be read)and occured while svchost.exe was running.

0x0000001e = 0x1e = *KMODE_EXCEPTION_NOT_HANDLED* and indicates that a
kernel-mode app generated an exception not caught by the error handler.
The exception here can be found by looking at the first parameter (1st #
inside the parenthesis) = 0xffffffffc0000005 - which tells us that a
memory access violation occurred. Parm #4 is the memory address of the
object that the "unknown image" attempted to access. That doesn't do us
any good here even w/ a full kernel dump to work with because parm 4 is
all high-values and not a valid memory address.

Just to note, I did not find any reference in the dbug log to the
infamous *IRQL_NOT_LESS_OR_EQUAL*, which is a bugcheck 0x0000000a (0xa).
Did you have a 0xa BSOD in addition to this 0x1e crash? If so when?

A look at the right side of the stack text tells us that the Microsoft
module *nt *and *fltmgr *were

::I hear what you are saying about the NVIDIA drivers - I have seen
quite a few roll back the updates. But I found more here than just a
possible NVIDIA connection. D::::uring the 8 day period from Oct 17 –
Oct 25 your system had at least 26 BSODs and 14 app crashes. Only a few
of the BSOD buchecks were visible to me in WERCON – ::

::*0xa* = IRQL_NOT_LESS_OR_EQUAL = a kernel mode driver accessed paged
memory when it should not have. 9/10 times I see this w/ 1st parm
(inside parenthesis) = 0xc0000005 – a memory violation by a driver.::

::*0x3b* = SYSTEM_SERVICE_EXCEPTION = an exception happened while the
app was transitioning into kernel code territory. NVIDIA would certainly
fit nicely into this one during a GUI crossing. ::

::*0x127* = PAGE_NOT_ZERO = a page (virtual RAM) should have been
zeroed out but was not. This could be caused by a kernel driver
modifying a page after freeing it ::

::*0x50* = PAGE_FAULT_IN_NONPAGED_AREA = invalid system memory was
referenced. Usually this is seen after the installation of a faulty
hardware, after a program install of system service or HDD corruption –
would be good to run *chkdsk /r *here.::

::The first two were executing when you ran the driver query and have
timestamps of May 2008; the last is listed as disabled and has a time
stamp of November 2006. I have seen numerous BSODs caused by COMODO and
I believe it may turn out to be the cause of the 0xc..5 app crashes. ::

::Then re-boot to allow repairs to take place that need the HDD
dismounted. You should also look at the Event Viewer logs and WERCON
(START | type wercon). COMODO could have been responsible for the
various bugcheks, but usually when I see such a variety there is a
hardware issue. In addition to running chkdsk, run memtest. I noticed
there was no WERCON hisory before Oct 17 - did you delete it or was this
a fresh Vista install? The latter would be a preferred remedy here
now.::

::They both appear to be Ethernet. The NVIDIA as you can see is recent
and the Intel is Aug 2007. That should have an update should you want it
-::
'_::http://www.intel.com/support/network/sb/cs-023752.htm::_'
(http://www.intel.com/support/network/sb/cs-023752.htm)

::But why both? Don’t they perform the same function?::

::Please run a Vista health report – but it must be saved in *HTML*
format (web page) to be of any use to me - and it must be run from an
*elevated *admin cmd prompt - bring one up and type:::

::*perfmon /report*::

::It will take ~ 60 seconds. Zip up the HTML file and attach to your
next post. I would appreciate knowing the outcome of the COMODO removal
& SFC. ::

Thanks for the info regarding the COMODO app. Ironically, I've not
actually had a single BSOD instance for over 2 weeks since I rolled back
the NVIDIA drivers. In my experience of Windows, most issues seem to
stem from incompability problems between graphics and soundcards and/or
MS drivers.

I installed a new update of COMODO a few days ago, and [touch wood], it
seems stable.

I ran a memory test and chkdsk /f a number of times when the BSOD was
ocurring often and didn't have any reported problems with either.

If COMODO is working for you - that's OK. It is just that I have seen
COMODO case many problems in Vista. I still am concerned that you have
KIS installed as well. I believe COMODO &/or Kaspersky firewall related
to all of the 0xc...5 exceptions (memory access violation) causing app
crashes (these are not BSODs).

Running *sfc /scannow* can't hurt here and may be of some help.

You can pass on the performance report for now.

For info, I am a Moderator of Microsoft Support at another forum (I
write for several) and have > 5,000 postings in one alone, most dealing
with BSODs in the Vista Forum. This is where I have obtained the
knowledge about COMODO and KIS re: 0xc..5 exceptions.