Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Vista 64 bit IRQL_NOT_LESS_OR_EQUAL Crashes


  • Please log in to reply

#1
pilkman

pilkman

    New Member

  • Member
  • Pip
  • 4 posts
Hi,
For about the past two or three weeks, my computer has been experiencing a serious problem. When I start it up, it boots up normally, but then maybe 3-10 minutes later it crashes. For a while, the screen would just lock up and the mouse, keyboard, etc. would become totally unresponsive, forcing me to hard reboot. Lately, though, it actually crashes to the blue screen of death with error message IRQL_NOT_LESS_OR_EQUAL.

If the computer goes more than 10 minutes or so without crashing, it does not crash for the rest of the day. (That is to say, it crashes shortly after booting or not at all.)

The computer usually only crashes on a cold boot. Once I restart it, it typically is OK (though on one occasion it continued to crash even after the initial reboot--it took four restarts to get it to work on that occasion).

Occasionally the computer won't crash even on its initial cold boot.

I've used MSConfig to disable all startup processes, but this has not stopped the crashing (though this change did coincide with the change in the crash going from lockup to blue screen).

The specific error code is STOP 0x0000000A followed by a list of hexadecimal numbers in parentheses. I wrote down those numbers. Is there some way to figure out what devices/programs/etc to which they correspond?

I know that this error comes from Windows trying to access forbidden memory, but I can't figure out whether it is a hardware failure, a bad device driver, a corrupted program, or something else entirely that is to blame. I hope the specifics of my problem can help you narrow it down for me.

Thanks so much!
  • 0

Advertisements


#2
Brother Bill

Brother Bill

    Member

  • Member
  • PipPip
  • 31 posts
My first instinct would be a memory issue. Microsoft has a download called Windows Memory Diagnostics useful for testing RAM on your computer for errors. You might check it out. Other than that, it could be an issue with your CPU, but I'd check the memory first.

Windows Memory Diagnostic
  • 0

#3
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Download BlueScreenView (in Zip file)
No installation required.
Unzip downloaded file and double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.
  • 0

#4
pilkman

pilkman

    New Member

  • Topic Starter
  • Member
  • Pip
  • 4 posts
Ok, here is my bluescreenview text file.

==================================================
Dump File : Mini062510-01.dmp
Crash Time : 6/25/2010 4:26:46 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000095
Parameter 2 : 00000000`0000000c
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`020aff5d
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a4d0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\Mini062510-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini080309-01.dmp
Crash Time : 8/3/2009 10:59:01 PM
Bug Check String :
Bug Check Code : 0x00000101
Parameter 1 : 00000000`00000031
Parameter 2 : 00000000`00000000
Parameter 3 : fffffa60`019d8180
Parameter 4 : 00000000`00000003
Caused By Driver : hal.dll
Caused By Address : hal.dll+2d460
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\Mini080309-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6001
==================================================
  • 0

#5
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Well, I can see only one crash from two days ago (6/25/2010). The other one is from a year ago.
We can't judge anything from one BSOD.
  • 0

#6
pilkman

pilkman

    New Member

  • Topic Starter
  • Member
  • Pip
  • 4 posts
Yeah, the problem is that most of the crashes don't make it to the blue screen. The computer just locks up. Of the two times where I got the blue screen (the two most recent crashes) it only succeeded in making a crash dump once. The second time it just locked up on the blue screen and I had to hard reboot it.

I tried booting up in safe mode today, and it didn't crash, so I really think it's some corrupted driver rather than a hardware failure. My computer didn't come with a Vista CD, but I have a restore CD (made shortly after the computer was purchased). Can I use that to check the harddrive for errors? Does running such a check carry any risk of data loss?

Thanks for the help so far.
  • 0

#7
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Go Start>Run ("Start Search" in Vista/7), type in:
sfc /scannow
Click OK (hold CTRL, and SHIFT, hit Enter in Vista/7).
Have Windows CD/DVD handy (with Vista/7, most likely, you won't need it).
If System File Checker (sfc) will find any errors, it may ask you for the CD/DVD (rarely in Vista/7 case).
  • 0

#8
shirishkale

shirishkale

    New Member

  • Member
  • Pip
  • 1 posts
I have a similar issue and after downloading minidumps only things I notice is that all the parameters are same in the BSOD file.
But the drivers and bug check code are separate. What does that mean?

Attached Files

  • Attached File  BSOD.txt   5.95KB   94 downloads

  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP