[Solormos]

Hello.

I was happily playing WoW, but then suddenly ''BOOM'' the blue screen of death popped to my screen. This isn't the first time, and before I was too lazy to ask help for this.

And yes, I've been searching the forums, internet for a solution, but I can't find a working solution.

Shortly, it happens randomly.

Long version; This has happened about 20 - 30 times so far, I've been experiencing this for months. This usually happens 1 - 8 times per week. Sometimes it doesn't come at all for a few days, or even weeks. Sometimes it comes when the computer has been on for a few hours, then sometimes not at all. So, I'm getting sick of this.

It says:
IRQL_NOT_LESS_OR_EQUAL

Bla bla bla (Text)

Stop: 0x0000000A, (0x00000000070AC00, 0x00000002, 0x00000001, 0x00000000059B85E

Btw, this may be abit incorrect because I memorized it, so there might be 1 - 2 too much 0's.

So, what could be causing this?
Any help is appreciated.

Thank you in advance.

Edited by Solormos, 25 October 2009 - 04:45 AM.

[Advertisements]

Hello Solormos.... Welcome to GeeksToGo,

I'm sorry to hear about your issue. We will try to help you resolve this as soon as possible.
Please understand we are all volunteers and we are not here all the time. Sometimes it may be a extended amount of time to get back to you. If it has been more then 3 days please shoot me a PM and I will try to get back to you quickly then.

• Please download the Event Viewer Tool by Vino Rosso VEW and save it to your Desktop:
• Double-click VEW.exe
• Under 'Select log to query', select (as appropriate):
  
  • Application
  • System
• Under 'Select type to list', select (as appropriate):
  
  • Error
  • Information
  • Warning

Then use the 'Date of events' or 'Number of events' as follows:

Either:

• Click the radio button for 'Number of events'
  Type 3 in the 1 to 20 box (or any number from 1 to 20)
  Then click the Run button.
  Notepad will open with the output log.
  
  
• Click the radio button for 'Date of events'
  In the From: boxes type today's date (presuming the crash happened today) 13 07 2009
  In the To: boxes type today's date (presuming the crash happened today) 13 07 2009
  Then click the Run button.
  Notepad will open with the output log.

Please post the Output log in your next reply





Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply



Download and install Free Everest Home Edition
Open it.
1: In left pane expand Computer folder.
2: Click once on Summary
3: In upper menu, go Report
4: And then to Quick Report-Summary
5: Save it in text file, and paste it in your next post.
Click the + by computer, click on Sensor. Get a screenshot and post it so I can check your temps and voltages...

DO NOT INCLUDE ANYTHING UNDER THE LINE THAT SAYS "DEBUG- PCI"

[rshaffer61]

Hello Solormos.... Welcome to GeeksToGo,

I'm sorry to hear about your issue. We will try to help you resolve this as soon as possible.
Please understand we are all volunteers and we are not here all the time. Sometimes it may be a extended amount of time to get back to you. If it has been more then 3 days please shoot me a PM and I will try to get back to you quickly then.

• Please download the Event Viewer Tool by Vino Rosso VEW and save it to your Desktop:
• Double-click VEW.exe
• Under 'Select log to query', select (as appropriate):
  
  • Application
  • System
• Under 'Select type to list', select (as appropriate):
  
  • Error
  • Information
  • Warning

Then use the 'Date of events' or 'Number of events' as follows:

Either:

• Click the radio button for 'Number of events'
  Type 3 in the 1 to 20 box (or any number from 1 to 20)
  Then click the Run button.
  Notepad will open with the output log.
  
  
• Click the radio button for 'Date of events'
  In the From: boxes type today's date (presuming the crash happened today) 13 07 2009
  In the To: boxes type today's date (presuming the crash happened today) 13 07 2009
  Then click the Run button.
  Notepad will open with the output log.

Please post the Output log in your next reply





Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply



Download and install Free Everest Home Edition
Open it.
1: In left pane expand Computer folder.
2: Click once on Summary
3: In upper menu, go Report
4: And then to Quick Report-Summary
5: Save it in text file, and paste it in your next post.
Click the + by computer, click on Sensor. Get a screenshot and post it so I can check your temps and voltages...

DO NOT INCLUDE ANYTHING UNDER THE LINE THAT SAYS "DEBUG- PCI"

[Solormos]

Hey, and thank you very much for your reply.


When I try to run the VEW, I get the following error ''VEW has not been coded for your language [Finnish]''
So, should I change my computer language for a while? Or what should I do?






WhoCrashed:

On Sun 25.10.2009 9:28:58 your computer crashed
This was likely caused by the following module: tukernel.exe
Bugcheck code: 0xA (0x8070AC00, 0x2, 0x1, 0x8059B85E)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\tukernel.exe
product: Microsoft® Windows® -käyttöjärjestelmä
company: Microsoft Corporation
description: NT Ydin & Järjestelmä
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

-------------------------------------------------------------------------------------------------------------------------------------------
Sensor:

And sorry, it's crappy quality.

Attached Files

•  Summary.txt   4.07KB   111 downloads

Edited by Solormos, 25 October 2009 - 08:14 AM.

[rshaffer61]

Please follow the steps below to enter the Event Viewer program in XP. This will give me more information into what is causing your issue.

Go to
Start and then click on Run
Type in eventvwr.msc and press Enter
On left side click on Applications On right side look for any RED X about the time of a incident
On left side click on System. On right side look for any Red X about the same time of a incident
Also look for any yellow exclamation mark at the same time in either of the above
If you find any double click on one at a time and take a screenshot.
To take a screenshot click on your Print Screen on your keyboard. It is normally the key above your number pad between the F12 key and the Scroll Lock key
Now go to Start
All Programs
Accessories
Paint
In the empty white area click and hold the CTRL key and then click the V
Go to the File option at the top and click on Save as
Save as file type JPEG and save it to your Desktop

Include as a attachment in your next reply

[Solormos]

Here they are. The text is in finnish, though.

Attached Thumbnails

• 

Attached Images

• 

[Solormos]

Here's the 3rd.

Attached Thumbnails

• 

[rshaffer61]

Go to
Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Let me know if this fixes the problem

[rshaffer61]

When done with the above then do the following.


If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-2.11.iso.zip file.
3. Inside, you'll find memtest86+-2.11.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate memtest86+-2.11.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run.

The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

[Solormos]

Go to
Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y

Sorry for taking so long. Work takes most of my time.

If it doesn't ask to do it in the next bootup, instead it puts up a black, small window (The same as if you would reboot check) is it okay? Or is better to do it on next reboot? I'm asking because it's a very fast, snd small check, it only takes about 1 - 2 minutes.

Btw, if I try starting computer with one RAM stick at a time, how do I know if my RAM is bad/broken etc.? What signs shoud I expect?

Edited by Solormos, 27 October 2009 - 02:04 PM.

[rshaffer61]

The time to run the program will vary depending on
Capacity of drive
Problems it may or may not encounter.

Try doing it this way.

How To Run Chkdsk /r from Recovery Console:


How to run checkdisk from recovery console (Windows xp). (Courtesy dsenette)

• Insert the Windows XP startup disk into the floppy disk drive, or insert the Windows XP CD-ROM into the CD-ROM drive, and then restart the computer.
  Note:Click to select any options that are required to start the computer from the CD-ROM drive if you are prompted to do so.
• When the "Welcome to Setup" screen appears, press R to start the Recovery Console.
  Note:If you have a dual-boot or multiple-boot computer, select the installation that you want to access from the Recovery Console.
• When you are prompted to do so, type the Administrator password. If the administrator password is blank, just press ENTER.
• At the Recovery Console command prompt, type the following then press Enter:
  

  chkdsk /r

• Allow this to run UNDISTURBED until completed (45 min or so)
• Report any errors

[Solormos]

Ehm, my bad. I accidentally typed Chkdsk, not Chkdsk /r
So it was a completly different check. Sorry.

Will do it right now.

Btw, if I try starting computer with one RAM stick at a time, how do I know if my RAM is bad/broken etc.? What signs shoud I expect?

Edited by Solormos, 27 October 2009 - 02:58 PM.

[rshaffer61]

Memory errors can show a lot of different ways.
This is why we use the programs we do to find out if the problem is with all the memory or with just one stick of the memory..
There could be a completely bad module or just one chip bad.
Memory can't be written, programs not responding correctly, IRQ errors
These are just a few of the issues that could arise from a faulty memory.

[Solormos]

Alright.

Thank you for your help.

Now I'll just have to wait and see if it worked, or not. I'll let you know today, or whenever it comes.

If this doesn't work, I'll try to boot up my computer with one RAM stick at a time.

Until then!

[Solormos]

Hey, it's me again.
So far It hasn't been showing up. So I suppose I just have to do that check every week in order to use my computer normally.

Thank you for you help, I really appreciate it.

[rshaffer61]

You are very welcome and please let us know how it all is working.
We will continue to monitor this topic for a while.