Solved BSOD ntoskrnl.exe+26ee0 ntoskrnl.exe+7cc40

[postal]

Hi, I've been having this BSOD appear very randomly.

IRQL_NOT_LESS_OR_EQUAL 0x0000000a
(all reports in .rar file)

Sometimes within 1 hour, other times as long as 24hrs+. I've got my BIOS/Drivers up to date for my CPU, Graphics Card, and Motherboard. I've rigorously tested my memory and have never had any issues arise.

It has occurred during
3d gaming,
when the system has been idle,
also when browsing with firefox or ie.

Any help at all would be appreciated, I've struggled with this BSOD for years I would love to finally find whats causing it.

Thank you.

 

[zigzag3143]

Hi, I've been having this BSOD appear very randomly.

IRQL_NOT_LESS_OR_EQUAL 0x0000000a
(all reports in .rar file)

Sometimes within 1 hour, other times as long as 24hrs+. I've got my BIOS/Drivers up to date for my CPU, Graphics Card, and Motherboard. I've rigorously tested my memory and have never had any issues arise.

It has occurred during
3d gaming,
when the system has been idle,
also when browsing with firefox or ie.

Any help at all would be appreciated, I've struggled with this BSOD for years I would love to finally find whats causing it.

Thank you.

First lets start with asacpi.sys yours dated 2005


1-ASACPI.SYS

The pre 2009 version of this driver is a known BSOD cause.

Please visit this link: ASUS teK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.SYS file is date stamped from 2009 or 2010 (NOT 2005).

 

[postal]

Thank you for the quick reply zigzag3143.
I have done exactly as you posted and the file is now dated 2009.
I will continue to test to see if this fix's it.

Thanks again

 

[zigzag3143]

Thank you for the quick reply zigzag3143.
I have done exactly as you posted and the file is now dated 2009.
I will continue to test to see if this fix's it.

Thanks again

My pleasure and good luck

 

[postal]

Well its been about 2 days straight and no bsod whatsoever!
I can't believe it was as simple as a ATK0110 driver that was causing it.

What does the driver control that would cause a bsod every few hours?
I no longer use any asus monitoring/overclocking software so I'm clueless.

But thank you ever so much, You truly are a guru zigzag3143

 

[postal]

Damn, I spoke to soon
I managed to last 48hrs on with no BSOD but just before got the +26ee0 one again.

I did do a system clean up just before this happened so I've attached fresh error reports in this post.

The crash happened while system idling with only steam in background.

If anyone has any more ideas I'd really appreciate it.

 

[zigzag3143]

Damn, I spoke to soon
I managed to last 48hrs on with no BSOD but just before got the +26ee0 one again.

I did do a system clean up just before this happened so I've attached fresh error reports in this post.

The crash happened while system idling with only steam in background.

If anyone has any more ideas I'd really appreciate it.

I would start here it is Related to RTCore64.sys MSI Afterburner from Micro-Star Int'l Co. Ltd. I would update it or remove it if possible.

If you are overclocking stop

 

[postal]

Ok, I've de-tuned my PC to stock standards. = 2.6ghz cpu / and 765mhz gfx.

I followed your link, but it is the same version I am currently using MSI Afterburner 2.1.0 (latest according to official site) Can I update just the RTCore64.sys from somewhere?

I switched from asus smart doc to MSI Afterburner because the MSI one actually loads my settings on start and the features work correctly. If you can recommend a better software I would try it
I would like to try to keep it as without it I can't overclock my Graphics card.

Thank you kindly for your suggestion, I will continue testing at stock speeds to show my overclock isn't to blame.

(EDIT) Just found another dump file created last night which includes ndis.sys+bf0eb ... Thats to do with my NIC's right? does that change anything?

 

[zigzag3143]

Given the Ndis reference I assume you are using either Blue screen view, or who crashed. Both of which have a tendency to give erroneous results when there is no clear driver and blame it on an OS file.

Was this one after being set to default?.

 

[postal]

Correct, BlueScreenView I'm using.
And sorry should have posted, this was still on OC settings.

I just started reading up on Atheros LAN drivers having a BSOD effect and thought this maybe relative. (my onboard is Atheros F1 Gigabit PHY)

Anyway, I'll keep waiting for the BSOD while my system is stock to see if it is that.

Thank you

 

[zigzag3143]

Correct, BlueScreenView I'm using.
And sorry should have posted, this was still on OC settings.

I just started reading up on Atheros LAN drivers having a BSOD effect and thought this maybe relative. (my onboard is Atheros F1 Gigabit PHY)

Anyway, I'll keep waiting for the BSOD while my system is stock to see if it is that.

Thank you

My pleasure and good luck

 

[stefanalexej]

Hello to all
I have the Same Problem,
and my english is not the best
i will try to do my best and i hope that you can help me

If you need more information i will do my best to deliver this
My pc seller has no Idea and i have some new rams since yesterday
Same Problem
If i make to many things FF and Fifa this bluescreen comes

Thank you very much for your help

Stefan

 

[postal]

SOLVED

Well been a few weeks and no BSOD, so safe to say my OC settings where wrong.
Stefan, if your Overclocking then try turning it off or the other solutions already discussed in this thread.

to ZigZag3143 Thanks heaps mate, I believe overall it was a combination of the outdated file and my bad oc settings. I can't believe I missed that, appreciate all your help!

Thank you.

 

[stefanalexej]

Now i made it right --> Attached

Win7 home Premium Version 6.1

What you mean bei OC ?
I have no Overclocking i think

Thank you very much for helping...
now i have all options ...
and i Have no OC seen in Bios