KMODE_EXCEPTION_NOT_HANDLED Error Code 0x0000001e

Hello.

This is the first time in two years time that I've received a BSOD. I woke up this morning, turned on my PC as usual, the OS reached the start-up picture (the one with a date and time on it), and it then spew the BSOD out on me.

1. Nothing is over-clocked. Everything is working on its default stock speeds (CPU, RAM, GPU).

2. I'm ruling out overheating cause the PC was less than a minute on till the BSOD appeared.

3. All of the possible OS updates have been installed via Windows Update. No changes in the OS's settings have been made in months as well.

4. All of the software I use (including drivers) is stable (not alpha, beta, so on...) and up-to-date. The OS is also an RTM release.

The only changes I've made in the past 7 days are as follows:

a) Uninstalled Opera 12.15 and installed its new version - v15. Highly doubt it has anything to do with this.

b) Reinstalled Daemon Tools LITE (+sptd v1.83). The version I had was 4.47.1-0333 and the disc-soft's main site had 4.47.1-0335.

c) Upgraded to a new graphics card - GTX780. The card, as stated above, is working on its default settings. Using the 320.49 WHQL drivers with it.

Bluescreen viewer gives out the following information: KMODE_EXCEPTION_NOT_HANDLED and 0x0000001e. It says the error was caused by the ACPI.sys driver at crash address ntoskrnl.exe+5a440.

Any help would be extremely appreciated.

ACPI.sys is related to power management. So, you just installed a new graphics card; yes? Can you current PSU handle the new power requirements? Specs say the minimum PSU recommendation is 600 watts for the GTX 780. Also, did you connect the 8 pin and 6 pin supplementary power connectors (information obtained from specs)?

Seems like your Razer keyboard driver is the cause, check for an update:

Probably caused by : Lycosa.sys ( Lycosa+132d )

fffff880`06830000 fffff880`0683e000 Lycosa Thu Feb 28 05:50:03 2013 (512EE1FB)

Also uninstall Daemon tools and the sptd-driver (download the installation program and use it to uninstall the driver).

JustATest said:

ACPI.sys is related to power management. So, you just installed a new graphics card; yes? Can you current PSU handle the new power requirements? Specs say the minimum PSU recommendation is 600 watts for the GTX 780. Also, did you connect the 8 pin and 6 pin supplementary power connectors (information obtained from specs)?

Click to expand...

My PSU is Cooler Master Silent Pro Gold 800W. I think it should be enough. And, yes, the additional power connectors are plugged-in as well.

Tobias said:

Seems like your Razer keyboard driver is the cause, check for an update:

Probably caused by : Lycosa.sys ( Lycosa+132d )

fffff880`06830000 fffff880`0683e000 Lycosa Thu Feb 28 05:50:03 2013 (512EE1FB)

Also uninstall Daemon tools and the sptd-driver (download the installation program and use it to uninstall the driver).

Click to expand...

The current Razer Lycosa driver I'm using is 3.03 for Windows 8 (downloaded from their official page; it's also the latest driver). And I've had it installed since I installed Windows a few months ago. Seems a little strange that it could've caused a problem just now.
How did you find out it was exactly this driver?

While you are waiting for Tobias to respond, I examined your dump file using WhoCrashed and it couldn't come up with anything specific other than it is most likely a software driver. However, maybe your Event Viewer logs might give some additional insight or have you been there already?

Unfortunately, Event Viewer doesn't list anything additional/specific that the other apps aren't able to.

It's funny how I try to keep my Windows installation clean and tidy, and yet problems still occur. I try not to overclock, I install only stable/final programs and certified drivers, don't EVER use any cleaning software in the face, for instance, Driver Sweeper, CCleaner, TuneUp Utilities, and so on, I try to stay out of Windows' way as much as possible by not tinkering too much or at all with its settings. I never thought I'd see the bloody BSOD again, but alas...

bastuna said:

Unfortunately, Event Viewer doesn't list anything additional/specific that the other apps aren't able to.

It's funny how I try to keep my Windows installation clean and tidy, and yet problems still occur. I try not to overclock, I install only stable/final programs and certified drivers, don't EVER use any cleaning software in the face, for instance, Driver Sweeper, CCleaner, TuneUp Utilities, and so on, I try to stay out of Windows' way as much as possible by not tinkering too much or at all with its settings. I never thought I'd see the bloody BSOD again, but alas...

Click to expand...

I totally agree with your logic and advice to stay away from those cleaners. Anyway, is this problem repeatable or was this just a one-time shot? If repeatable, and you don't know where to go next, I would try a different driver version on that new card. Sometimes the latest is not always the greatest. Good luck.

This is the first BSOD I have received in two years. The last one was when I was on Windows 7 in July/August of 2011, I think. And I haven't gotten another one since morning. It's been a one-time 'experience' so far. I hope it stays that way!

Checked my HDD's SMART with 3 different programs (AIDA64, HDTune and HD Sentinel) - all is OK. Did an Error Scan with HDTune. - nothing out of the ordinary. HD Sentinel reports the drive as being in perfect condition.

Will check my RAM later with Memtest via a bootable USB flash drive.

Wow! Only one BSOD and you are on it like a buzzard on roadkill! Just kidding because I would probably react just like you. Good luck!

Well, I can safely exclude any problems with the RAM as well since it completed over 3 hours of testing with Memtest86 with no errors. I'm now almost sure it was a software problem.

What exactly does the ACPI.sys driver do?

ACPI info: Advanced Configuration and Power Interface - Wikipedia, the free encyclopedia

The STOP 0x1E error is one of the more complicated BSOD's to troubleshoot as it can be caused by either hardware or software. Here's a list of "Usual Causes" from this webpage of mine: BSOD Index - STOP 0x1E

Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

Click to expand...

Just a few things about BSOD's:

One BSOD isn't usually anything to worry about. The old BSOD screens used to state this, but it was done away with in Win8.
If they repeat, then start to worry about them.

BSOD's are caused by:
- 3rd party drivers (non-Windows) over 90% of the time
- hardware/incompatibility less than 10% of the time
- Windows drivers less than 1% of the time (this presumes that Windows is fully updated)

In general that's also the order that we troubleshoot them in.

IME known problem drivers are responsible for at least 75% of the 3rd party driver crashes (the 90%). This is hard to estimate as there's generally no solid proof of a particular driver causing a BSOD. Here's a page with the known BSOD causing drivers that I know of: Driver Reference Table - Common BSOD related drivers

One reason that a problem driver may not show in a memory dump:

- the problem driver writes to a memory space that's owned by another driver
- the problem driver then exits
- the other driver looks at the memory space that was written to and doesn't find what was supposed to be there.
- the other driver panics because of this and throws a BSOD (and creates a memory dump).
- as the problem driver has already exited, there's no evidence of it in the memory dump

Click to expand...

One of the most common problem drivers that I've seen is sptd.sys - the pass through driver used in Daemon Tools. Removing it is the first step in any attempt to stop them. Unfortunately, since this is your only BSOD, there's not telling if it's been fixed or not.

IMO, I'd let it go for now. If it recurs, then post the subsequent memory dump files so we can start examining it in detail. There's no need to remove Daemon Tools at this point unless you're willing to leave it off permanently (I do suggest this, but it's your system - so only you can make that choice).

Good luck!

Did some hardware testing today.

Ran 3 hours and 15 minutes of AIDA64's stability stress test (CPU, FPU, cache, system memory) and everything was normal. CPU usage was always at 100% while the throttling levels were always at 0%. No errors, warnings, or any other unwanted or unexpected behavior.
Also ran a few tests with very GPU-intensive tests such as Unigine's Valley and Heaven benchmarks (with V-Sync on and off; all of them set at maximum settings). All was fine and dandy (the same situation with all of the games I've played so far right after buying my new GPU - TWD: 400 days, Mortal Kombat and DARK, and a few other small ones) .

So, I don't think it was anything hardware-related.

Will remove Lycosa's driver (don't know why I insist on having this particular driver installed even though I've never used its settings and capabilities) and DT Lite with its SPTD driver. I know Win8 has a built-in module for mounting ISO's but it doesn't recognize .bin and .cue files. These files are the single and only reason that make me keep using DT Lite, but since I continue on bumping into these file formats less often than normal, I'll stick to using Win8's mounting functions.

Thanks for your reply, usasma. Learnt a thing or two from your post, and I think I'll learn quite a lot more from your website. I've been on the clear so far and no other misbehavior has been witnessed; REALLY hope it was the pesky Lycosa driver that acted as the main culprit (I used Osronline.com's testing environment, Whocrashed and Debugging Tools for Windows; they also listed Lycosa.sys as a potential candidate for all this trouble - same with Tobias' suggestion).