Thinkpads Forum

Posted: **Sun Jul 29, 2012 3:23 pm**

Problem signature:
  Problem Event Name:	BlueScreen
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	1033

Additional information about the problem:
  BCCode:	a
  BCP1:	0000000000000000
  BCP2:	0000000000000002
  BCP3:	0000000000000000
  BCP4:	FFFFF80003096442
  OS Version:	6_1_7601
  Service Pack:	1_0
  Product:	256_1

Files that help describe the problem:
  C:\Windows\Minidump\072912-31012-01.dmp
  C:\Users\HYX\AppData\Local\Temp\WER-80839-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Neither one of the files that "help describe the problem" are accessible.

Posted: **Sun Jul 29, 2012 3:50 pm**

Check the related Event Log entry. Also the minidump file should be there. You can use BlueScreenView to display content of the minidump report.

The error code indicates Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL It is not easy to track it

Usually it is related to a hardware problem or buggy device driver. The information from minidump file could help to find failing device driver file and its related hardware/software component.

Have you updated BIOS or device driver or antivirus software recently ?

Posted: **Sun Jul 29, 2012 4:03 pm**

Thanks, I didn't do any recent updates. The only thing I installed was Adobe Elements, which I uninstalled few days later.
This happened while I was trying to watch Comedians in Cars first video and trying to view the source in Firefox 14.

I was going to take a snapshot of the BSOD but it didn't wait too long for me, just restarted.

I will try the viewer thanks for the suggestion, but I am hoping this was an isolated incident, since it is not something that's easy to track or pinpoint with the info MS has given in the message.

Posted: **Sun Jul 29, 2012 4:11 pm**

It might be related to outdated video driver. The recent version is here http://support.lenovo.com/en_US/downloa ... D=DS014907

But again, by inspecting the minidump file (it might require elevated privilege to access it) you can get more information.

Posted: **Mon Jul 30, 2012 10:39 am**

Thanks puppy, here is the result of bluescreenview

I will take a look at the driver update (I think I should run thinkvantage to see if there are other updates as well)

Posted: **Wed Oct 03, 2012 10:43 pm**

Another one today...

Code: Select all

Problem signature:
  Problem Event Name:	BlueScreen
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	1033

Additional information about the problem:
  BCCode:	a
  BCP1:	0000000000000000
  BCP2:	0000000000000002
  BCP3:	0000000000000000
  BCP4:	FFFFF80003087442
  OS Version:	6_1_7601
  Service Pack:	1_0
  Product:	256_1

Files that help describe the problem:
  C:\Windows\Minidump\100312-26020-01.dmp
  C:\Users\HYX\AppData\Local\Temp\WER-360799-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Posted: **Thu Oct 04, 2012 4:53 am**

I believe IRQL_NOT_LESS_OR_EQUAL is generally a driver bug. In your case it mentions ntoskernel.exe.

I see here where faulty RAM was the issue:
http://www.pchelpforum.com/xf/threads/b ... xe.102480/

Personally, in the past I have had bad device drivers cause this issue. Have you updated any device drivers recently?

A Microsoft MVP also stated that rootkits and malware could cause this issue.
http://answers.microsoft.com/en-us/wind ... ee58619b10

Posted: **Thu Oct 04, 2012 10:26 am**

Thanks for the suggestion, yes I updated some of the drivers after the first occurrence (above) but I may check again to see if there is any other driver updates that may fix this issue.
I don't believe it is the ram, if it was it should occur a lot more often, and I don't see any other problems during daily work.

After my last update, there are mainly only optional updates left, I wonder if any one of them should be applied.
In the meantime, I will make sure to run malwarebytes to search for some rootkit, etc. Thanks for the suggestion, I just couldn't trust any of the ones out there claim to search for malware/etc.. without modifying or digging itself deep in registry..

Posted: **Thu Oct 04, 2012 10:55 am**

I searched my old posts and found it was the Nero InCD packet writing driver software that caused this IRQL_NOT_LESS_OR_EQUAL message on a desktop PC I had back in 2005. Uninstalling that driver software fixed the issue permanently for me.

Nevertheless, a number of people report that faulty RAM can cause this as well. You might want to run memtest to rule that out.

FWIW, I also have a X220 that I fully updated on 9/18/12. No BSOD here. Note: I don't use or have the fingerprint reader software installed. Likewise I don't have Access Connections installed.

EDIT: I didn't install the Lenovo Solutions Center when offered either (I think that's what it was called).

Posted: **Thu Oct 04, 2012 11:28 am**

Aww.. I love the fingerprint reader and I use the access connections on daily basis. I tried to find an alternative but it was the only solution that helps me switch profiles between office and work.
I will run memtest and report back. I use Cyberlink Power2Go which came with my external burner only when I need to burn something. So no Nero inCD here.

I must add that I started getting random Windows Explorer errors and fails, restarting windows explorer ..

Code: Select all

Log Name:      Application
Source:        Application Error
Date:          10/4/12 13:02:11
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HYX-2GO
Description:
Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d672ee4
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0x11f8
Faulting application start time: 0x01cda1e19c8eb5ac
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 3c659b4d-0e45-11e2-aae5-f0def16f009b
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-10-04T17:02:11.000000000Z" />
    <EventRecordID>26441</EventRecordID>
    <Channel>Application</Channel>
    <Computer>HYX-2GO</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Explorer.EXE</Data>
    <Data>6.1.7601.17567</Data>
    <Data>4d672ee4</Data>
    <Data>ntdll.dll</Data>
    <Data>6.1.7601.17725</Data>
    <Data>4ec4aa8e</Data>
    <Data>c0000374</Data>
    <Data>00000000000c40f2</Data>
    <Data>11f8</Data>
    <Data>01cda1e19c8eb5ac</Data>
    <Data>C:\Windows\Explorer.EXE</Data>
    <Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
    <Data>3c659b4d-0e45-11e2-aae5-f0def16f009b</Data>
  </EventData>
</Event>

Posted: **Fri Oct 05, 2012 2:35 am**

hyde wrote:Thanks, I didn't do any recent updates. The only thing I installed was Adobe Elements, which I uninstalled few days later.
This happened while I was trying to watch Comedians in Cars first video and trying to view the source in Firefox 14.

I was going to take a snapshot of the BSOD but it didn't wait too long for me, just restarted.

I will try the viewer thanks for the suggestion, but I am hoping this was an isolated incident, since it is not something that's easy to track or pinpoint with the info MS has given in the message.

FWIW: Adobe products can be intrusive and nearly impossible to really uninstall. So much so that even Adobe tacitly acknowledges this fact and offers "cleaners" to thoroughly remove and deregister components their customary uninstall mechanism misses.

Googling for "Adobe Cleaner" brings up a phone book of references from their own web site, like this one that may also apply to Premier Elements:

http://www.adobe.com/support/contact/cscleanertool.html

I've often used these silver bullet cleaners to flush Adobe products off before successfully reinstalling.

I'm glad you got your problem solved, but Adobe products can cause more problems than nosy in-laws.

Posted: **Fri Oct 05, 2012 3:33 am**

hyde wrote:I must add that I started getting random Windows Explorer errors and fails, restarting windows explorer ..

It is usually caused by a crappy shell extension (it is code that adds new items to Windows Explorer context menus) installed by a 3rdParty application.

Posted: **Sun Oct 07, 2012 1:05 pm**

I think the explorer problem is related to dropbox, because it only occurs when I browse to my documents folder.. I will check that later.
Regarding the blue screen, I ran memtest 86+ and first 7 test passed without any errors, I had to stop it because it was going for 2 hrs already, and it said passed without errors, but it just kept going.

Posted: **Sun Oct 07, 2012 2:33 pm**

hyde wrote:I ran memtest 86+ and first 7 test passed without any errors, I had to stop it because it was going for 2 hrs already, and it said passed without errors, but it just kept going.

It is not enough. RAM module errors are tricky. Keep it runnning for at least 16 hrs. For example I had a RAM module which had errors first ten minutes after power on the machine only (probably caused by temperature change progress). When I run the test lately it couldn't find the errors again.

While Memtest86+ is popular and excellent tool I'd recommend to try http://oca.microsoft.com/en/windiag.asp as well.

Thinkpads Forum

First BSOD in exactly 1 year since purchase

First BSOD in exactly 1 year since purchase

Re: First BSOD in exactly 1 year since purchase

Re: First BSOD in exactly 1 year since purchase

Re: First BSOD in exactly 1 year since purchase

Re: First BSOD in exactly 1 year since purchase

Re: First BSOD in exactly 1 year since purchase

Re: First BSOD in exactly 1 year since purchase

Re: First BSOD in exactly 1 year since purchase

Re: First BSOD in exactly 1 year since purchase

Re: First BSOD in exactly 1 year since purchase

Re: First BSOD in exactly 1 year since purchase

Re: First BSOD in exactly 1 year since purchase

Re: First BSOD in exactly 1 year since purchase

Re: First BSOD in exactly 1 year since purchase