BSOD IRQL_NOT_LESS_OR_EQUAL while playing SW:TOR and idling

[writhziden]

Alright, the blue screen .dmp files are pretty general and are hard to narrow down the problem. I'll have to ask some questions to determine how to proceed from here.

Are you running a laptop or a desktop?
Is this a pre-built machine from a vendor (HP, DELL, SONY, LENOVO, ETC.), or was it custom built?
Have you added any hardware to the machine recently that may have been added around the time the problems started?
Are you overclocking any hardware?

 

[XplicitMind]

Okay this is a custom built desktop PC that was made about 1 year ago. I've just recently started getting BSOD messages about 1-2 months ago but then was kind of dealt with by cleaning out my computer. About 3 weeks ago, I started getting more and more BSOD messages that had to deal with memory corruption and all that stuff but I did what I was told and nothing came up as an error. So I did a fresh install about 2-3 weeks ago and got a couple of BSOD messages after the fresh install but then after that I was free from BSOD until the day I made this thread. No new hardware was installed at all during that whole time. Nothing is overclocked, BIOS values are at default.

I've tried placing RAM sticks in different slots, made sure the temps are acceptable and not overheating. At times I would be able to play a game without BSOD but then afterwards it would BSOD a couple of times the next day.

I just noticed that in my event viewer, I get an error saying "Session "Microsoft Security Essentials OOBE" stopped due to the following error: 0xC000000D". I've just done what they said to get rid of this error. Could this have anything to do with my BSOD even though my dmp files don't specify it?

 

[writhziden]

Did you do any registry cleaning between the time you did a clean install and the BSODs started?

 

[XplicitMind]

Did you do any registry cleaning between the time you did a clean install and the BSODs started?

Yes I have with CCleaner. Not with the RegUtility program.

 

[writhziden]

Did you do any registry cleaning between the time you did a clean install and the BSODs started?

Yes I have with CCleaner. Not with the RegUtility program.

It's possible the registry has been compromised and is causing your crashes. Normally, CCleaner is safe to use, but it does cause problems on some systems. I used it once on a system and the system would not even boot into Windows other than in Safe Mode. I had to restore the registry from the backup I made before using CCleaner. Over the past year, I've learned to avoid any registry tools and rely strictly on manual cleaning when actual problems pop up.

If you encounter registry errors in the future (which are uncommon in 7), please visit these forums and ask for help and instructions in fixing them rather than relying on an automated tool to do the work for you. There is too much risk with automated registry tools.

As to your current problem, disable Verifier and run through any Win7 Basic Troubleshooting Steps that you have not yet tried.

 

[writhziden]

If you are concerned about any possible hardware problems, check Hardware Diags for diagnostic tools for basic hardware.

 

[XplicitMind]

Alright I will look into this.

In your opinion, do you think I should do another fresh install or would a repair install work just the same?

 

[writhziden]

Alright I will look into this.

In your opinion, do you think I should do another fresh install or would a repair install work just the same?

A fresh install guarantees any system/registry corruption is a thing of the past. A repair install may fix the problem, but is not guaranteed. The repair install is usually suggested first as it re-installs Windows system files and fixes most issues without sacrificing user files and programs. It is really up to you which to do. Typically, we recommend a repair install first, and then if that does not resolve problems, we will recommend a clean install as a last resort. If problems persist after a clean install before any user programs are installed, the problem can be narrowed down to hardware.

 

[XplicitMind]

Alright I will try the repair install first and see if I get any BSOD messages, I won't use any registry cleaners this time around. haha

 

[writhziden]

Alright I will try the repair install first and see if I get any BSOD messages, I won't use any registry cleaners this time around. haha

Sounds good. Post back how things go. Best wishes.

 

[Dave76]

Can you post your System Specs?

This is likely a hardware issue, specifically RAM, we need to know what components you have.
Use these links to find your system specs.
Speccy Free System information Utility

System Info - See Your System Specs

D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

This information will help us analyze your system.

Did you run memtest86+ for a full 7 passes, best to run overnight.
This is recommended over Windows memtest, it will find errors more reliably, it runs without the OS.
RAM - Test with Memtest86+
Run this with both RAM cards installed.

Any RAM test can pass with no errors several times and then will show errors on a subsequent test.
This is just the nature of electronics.


Last crash was STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005100, The subtype of the bugcheck.
Arg2: fffff6fd4001c0a0
Arg3: 0000000000000001
Arg4: 000000000732d963

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_5100

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME: firefox.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880080b04a0 -- (.trap 0xfffff880080b04a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000071784460 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=00000000770e6882 rsp=00000000005bac00 rbp=00000000005bac3c
 r8=000000000000002b  r9=00000000770bfada r10=0000000000000000
r11=0000000000200246 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac pe nc
0023:770e6882 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ae5957 to fffff80002a8bc40

STACK_TEXT:  
fffff880`080afdb8 fffff800`02ae5957 : 00000000`0000001a 00000000`00005100 fffff6fd`4001c0a0 00000000`00000001 : nt!KeBugCheckEx
fffff880`080afdc0 fffff800`02bb7b5e : 00000000`00000001 fffff880`080aff40 fffff6fd`4001c0a0 fffff880`080affa0 : nt! ?? ::FNODOBFM::`string'+0xaf37
fffff880`080afed0 fffff800`02aac760 : 00000000`00001000 fffff800`02c16340 00000000`00000000 00000000`00002001 : nt!MiAllocatePoolPages+0x4de
fffff880`080b0010 fffff800`02bba90e : 00000000`00000000 00000000`00000020 fffff680`00000000 00000000`00001000 : nt!ExpAllocateBigPool+0xb0
fffff880`080b0100 fffff800`02b8cdc4 : fffff700`01080000 00000000`00001000 00000000`00000000 fffff8a0`02834c68 : nt!ExAllocatePoolWithTag+0x82e
fffff880`080b01f0 fffff800`02b8cf96 : 00000000`00000000 fffffa80`07719060 fffff680`0038bc21 00000000`00000000 : nt!MiAllocateAccessLog+0xb4
fffff880`080b0220 fffff800`02afd7ff : 00000003`00000000 00000000`00000000 fffff880`080b02e0 fffffa80`07719060 : nt!MiLogPageAccess+0x46
fffff880`080b0270 fffff800`02a9a02a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x38a04
fffff880`080b0340 fffff800`02a89d6e : 00000000`00000000 00000000`71784464 00000000`00002801 00000000`00300570 : nt!MmAccessFault+0x146a
fffff880`080b04a0 00000000`770e6882 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`005bac00 fffff800`02a83210 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x770e6882
fffff880`080b0880 fffff900`c0808450 : fffff880`080b08f0 fffff880`080b0b68 fffff880`080b0a00 fffff880`080b08c8 : nt!KiCallUserMode
fffff880`080b0888 fffff880`080b08f0 : fffff880`080b0b68 fffff880`080b0a00 fffff880`080b08c8 fffff880`080b0db0 : 0xfffff900`c0808450
fffff880`080b0890 fffff880`080b0b68 : fffff880`080b0a00 fffff880`080b08c8 fffff880`080b0db0 00000000`00000000 : 0xfffff880`080b08f0
fffff880`080b0898 fffff880`080b0a00 : fffff880`080b08c8 fffff880`080b0db0 00000000`00000000 00000000`00000000 : 0xfffff880`080b0b68
fffff880`080b08a0 fffff880`080b08c8 : fffff880`080b0db0 00000000`00000000 00000000`00000000 40830000`00000000 : 0xfffff880`080b0a00
fffff880`080b08a8 fffff880`080b0db0 : 00000000`00000000 00000000`00000000 40830000`00000000 00000000`00000000 : 0xfffff880`080b08c8
fffff880`080b08b0 00000000`00000000 : 00000000`00000000 40830000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`080b0db0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+af37
fffff800`02ae5957 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+af37

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1a_5100_nt!_??_::FNODOBFM::_string_+af37

BUCKET_ID:  X64_0x1a_5100_nt!_??_::FNODOBFM::_string_+af37

Followup: MachineOwner
---------

This is an out of date driver for Asus PCProbe Utility.
Uninstall the ASUS utilities for testing purposes, these are known to cause system crashes.

AsIO     AsIO.sys     Mon Apr 06 15:21:08 2009

From the Event App dumps:

There are several of these.

Event[25]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2012-01-08T23:53:11.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RyRichJ-PC
  Description: 
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: [COLOR="red"]Regutility.exe[/COLOR]
P2: 4.1.1.8
P3: 2a425e19
P4: KERNELBASE.dll
P5: 6.1.7601.17651
P6: 4e211319
P7: 0eedfade
P8: 0000b9bc
P9: 
P10: 

Attached files:
C:\Users\RyRichJ\AppData\Local\Temp\WER4B9F.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Regutility.exe_8d866312baecec5be67c375136f718ed3937ebb_0c2b4f95

Analysis symbol: 
Rechecking for solution: 0
Report Id: d3c64cd2-3a7d-11e1-98c7-485b39c633e8
Report Status: 1

Please verify that Regutility has been uninstalled.

Memory corruption.

Event[58]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2012-01-08T23:19:21.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RyRichJ-PC
  Description: 
Fault bucket X64_MEMORY_CORRUPTION_ONE_BIT, type 0
Event Name: BlueScreen
Response: http://wer.microsoft.com/responses/resredir.aspx?sid=603&Bucket=X64_MEMORY_CORRUPTION_ONE_BIT&ID=8712bb3f-e690-4869-a5d6-94f8edfaa0e7
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
C:\Windows\Minidump\010812-17050-01.dmp
C:\Users\RyRichJ\AppData\Local\Temp\WER-24804-0.sysdata.xml
C:\Users\RyRichJ\AppData\Local\Temp\WER9BC1.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_090703c7

Analysis symbol: X64_MEMORY_CORRUPTION_ONE_BIT
Rechecking for solution: 0
Report Id: 010812-17050-01
Report Status: 0

Event[158]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2012-01-08T21:34:23.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RyRichJ-PC
  Description: 
Fault bucket X64_MEMORY_CORRUPTION_STRIDE, type 0
Event Name: BlueScreen
Response: http://wer.microsoft.com/responses/resredir.aspx?sid=603&Bucket=X64_MEMORY_CORRUPTION_STRIDE&ID=12f1de1f-7a76-47c0-a93a-4f455fadbf73
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
C:\Windows\Minidump\010812-14164-01.dmp
C:\Users\RyRichJ\AppData\Local\Temp\WER-21840-0.sysdata.xml
C:\Users\RyRichJ\AppData\Local\Temp\WER8A44.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_08e50740

Analysis symbol: X64_MEMORY_CORRUPTION_STRIDE
Rechecking for solution: 0
Report Id: 010812-14164-01
Report Status: 0

Event[389]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2012-01-08T12:24:50.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RyRichJ-PC
  Description: 
Fault bucket X64_0xA_nt!MiUnlinkFreeOrZeroedPage+181, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
C:\Windows\Minidump\010812-20077-01.dmp
C:\Users\RyRichJ\AppData\Local\Temp\WER-28532-0.sysdata.xml
C:\Users\RyRichJ\AppData\Local\Temp\WER8600.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0984be7d

Analysis symbol: X64_0xA_nt!MiUnlinkFreeOrZeroedPage+181
Rechecking for solution: 0
Report Id: 010812-20077-01
Report Status: 0

Skype is also reported crashing.


System Event logs:

Event[25]:
  Log Name: System
  Source: Microsoft Antimalware
  Date: 2012-01-09T00:06:46.000
  Event ID: 3002
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RyRichJ-PC
  Description: 
Microsoft Antimalware Real-Time Protection feature has encountered an error and failed.
 	Feature: Behavior Monitoring
 	Error Code: 0x80004005
 	Error description: Unspecified error 
 	Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection.

Check for updates for MSE on Windows Update.
Install and run full scan from MSE.


Most of this information leads me to suspect your RAM.
Post the CPUZ info requested above,

 

[XplicitMind]

Hey there again. After a week since the repair install, I've gotten a couple of BSOD while playing SW:TOR and I think once idling. I haven't touched my registry at all, just let it go with the flow. I hope these minidumps can tell you something. I currently placed on order to upgrade my RAM so in a few days I can test that out.

Thanks.

 

[writhziden]

These were memory related, so the RAM may help. Let us know how the new RAM holds up in the system. Best wishes it resolves the crashes!

 

[XplicitMind]

A quick question, can overheating be a factor as well? I have posted a image of my idle cpu/gpu temps. Usually when I game, my GPU averages around 80-90C and one time even surpassing 100C while my CPU usually goes around 55C to 62C at most.

If this is a problem, how should I go about this? I have 1 140mm front panel intake, 1 120mm top panel exhaust, 1 80mm back exhaust and 1 80mm side panel intake.

Since it's been a year since I set my HSF, I would assume that the thermal paste would disappear, should I reapply more thermal paste or do you think I should go and buy a different heat sink? Same goes for my GPU, should I reapply thermal paste on that too, my GPU being about 3 years old.

 

[writhziden]

A quick question, can overheating be a factor as well? I have posted a image of my idle cpu/gpu temps. Usually when I game, my GPU averages around 80-90C and one time even surpassing 100C while my CPU usually goes around 55C to 62C at most.

If this is a problem, how should I go about this? I have 1 140mm front panel intake, 1 120mm top panel exhaust, 1 80mm back exhaust and 1 80mm side panel intake.

Since it's been a year since I set my HSF, I would assume that the thermal paste would disappear, should I reapply more thermal paste or do you think I should go and buy a different heat sink? Same goes for my GPU, should I reapply thermal paste on that too, my GPU being about 3 years old.

100C is very high for an nVidia card. My AMD card gets over 90C, but from the research I have done, that is normal for that particular card. From the research I've read on nVidia cards, I believe nVidia cards are supposed to run between 80-85C max.

Here is what the maximum is for your card:

Thermal and Power Specs:
Maximum GPU Temperature (in C) 105 C

From GeForce 9600 GT

I guess 100C isn't above the max, but it is definitely getting dangerously close to the max and may cause prolonged issues if it continues to run that hot. Have you tried blowing the dust out of it?

That card typically runs at 41-73C, see Power, Temperature, And Noise Benchmarks : GeForce 9600 GT/GTS 250/GTX 260 Non-Reference Roundup

 

[XplicitMind]

Yes I research the same stuff but did wonder what was the normal rage of it either at idle or at max load. I've blew out as much dust as possible, with compressed air, without taking the cover off of it. Should I take it off and blow it out some more?

 

[writhziden]

Yes I research the same stuff but did wonder what was the normal rage of it either at idle or at max load. I've blew out as much dust as possible, with compressed air, without taking the cover off of it. Should I take it off and blow it out some more?

To remove dust, follow the following general procedure.

1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Remove the casing for a desktop, or remove any screwed on panels and disc drives for laptops.
5. Blow out the dust inside by using a can of compressed air or a low pressure compressor. You will want to put the computer on a desk or table so you can maintain the can in an upright position if using a can of air. Blow into all crevices on the motherboard, heat sinks, cards, modules, etc. for a desktop. Blow into vents, opened panels, disc drive areas, USB ports, and the keyboard if it is a laptop. You may also want to blow inside the disc drive by replacing the drive to the laptop, starting the computer, opening the drive, and then turning off the computer and removing all power as described above including the 30 second power button step. For a desktop, you may also want to blow inside the disc drive by starting the computer, opening the drive, and then turning off the computer and removing all power as described above including the 30 second power button step.
6. Replace casing for the desktop. Replace panels and disc drive (if you have not already done so) for the laptop.
7. Plug power supplies in. AC adapter for the desktop. Battery and then AC Adapter for the laptop.
8. Start the computer and see if performance is better.

For the graphics card, you want to blow into the fan as much as possible to get all the grit out. The fan gets very clogged with dust. Just blowing in the vents of the casing (not removing the cover/case of the desktop tower) is not enough. Make sure opening up the case will not void any warranty first.

 

[XplicitMind]

I believe my warranty is up for this card. RMA requires original receipt of purchase which I don't have so I don't have to worry about voiding any warranties. Alright I'll try to open up the casing of the card and blow as much as I can.

I'll see if it help with the temperature.

How about concerning thermal paste for my heat sink? Doesn't seem like my CPU is overheating or is it? Especially at idle.

 

[writhziden]

I believe my warranty is up for this card. RMA requires original receipt of purchase which I don't have so I don't have to worry about voiding any warranties. Alright I'll try to open up the casing of the card and blow as much as I can.

I'll see if it help with the temperature.

How about concerning thermal paste for my heat sink? Doesn't seem like my CPU is overheating or is it? Especially at idle.

You do not have to open up the casing of the card. I meant that you should open up the casing of the desktop tower, not the card. And the warranty warning was more for computers that are under warranty through a vendor like Dell, HP, Sony, Lenovo, etc. They sometimes put a sticker on the case so if it is broken to access the internals, the warranty is void because they assume a person would only do such a thing to replace components.

 

[XplicitMind]

You do not have to open up the casing of the card. I meant that you should open up the casing of the desktop tower, not the card. And the warranty warning was more for computers that are under warranty through a vendor like Dell, HP, Sony, Lenovo, etc.

Oh no, this is a custom built PC.