IRQL_NOT_LESS_OR_EQUAL Crash

[ProbleMatic]

Event[652]: Log Name: System Source: Application Popup Date: 2011-05-23T13:13:43.000 Event ID: 26 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: user-PC Description: Application popup: chrome.exe - Application Error : The instruction at 0x76ed2776 referenced memory at 0x003a0008. The memory could not be written. Click on OK to terminate the program

remember that from the 1st post? Is it just an appcrash and nothing more?


Far as memory goes, all RAM slots are occupied.

 

[ProbleMatic]

So far, I'm running great.

 

[Dave76]

Which brand RAM card in which slot?


If Chrome is running with no issues it's ok.
It updates regularly, so the issue is probably fixed.

 

[ProbleMatic]

Mixed ram brands in both slot groups. PNY is silver, and SpecTek is the normal green stick.

 

[Dave76]

Go to your BIOS and tell us what the CPU(CPU Vcore), RAM (DRAM Voltage) and North Bridge or NB (MCH Core) voltages are.
The timings from your CPUZ snips look ok for now, with these voltages we can give a recommendation for a bump.


D/L your motherboard manual if you don't have it.
GA-EP45-UD3L

Your PNY RAM is in slots DDR2_1 and DDR2_3
Your SpecTek is in slots DDR2_2 and DDR2_4

These are in the correct slots for dual channel.

From your motherboard manual.

2. When enabling Dual Channel mode with two or four memory modules, it is recommended that
memory of the same capacity, brand, speed, and chips be used and installed in the same
colored DDR2 sockets for optimum performance.

 

[ProbleMatic]

I've gone pretty much all day without crashing so far. I think things are going to be ok. Thanks for the help, in the future, I will repost if any crash occurs. Cheers! Thanks for the Mobo pdf manual.

 

[Dave76]

We can check those RAM and NB settings, they will likely cause more issues, best to give them a little adjustment now.

Your choice, let me know if you want to continue or if you have any questions.

 

[ProbleMatic]

OK, so maybe I spoke too soon. It crashed on me with the IRQL error again, but, I installed a motherboard program onto my pc, could that have made it crash? it was called EasyTune, allows me to tweak the boards settings with software. I matched the ram up, so now, both ram sticks are the same for both slots. See what that does for me. Attachment below, just did this.

 

[Dave76]

Post the crash files.

According to your motherboard manual you had the RAM in the correct slots the first time, you need to change it back.
What you have just done will likely cause more problems.

Uninstall the Gigabyte EasyTune, it is known to cause crashes.
This is not a reliable way to OC your system, these programs always overvolt everything, causing heat issues.
If you want to overclock your system, first of all wait until the cause of your crashes is found, secondly take a little time to read and understand the OC'ing methods. You can easily OC with minimal voltage and better results doing it manually through the BIOS.

 

[ProbleMatic]

Just captured a bunch of screens with easy tune, and just experimented for a second. So, the correct way was the previous RAM configuration? I will switch back then. Below are screens from easytune, with the voltage, like you were asking.

I will repost the crash files. creating a new report right now. Will oust EasyTune too.

 

[ProbleMatic]

Here's the new report.

 

[Dave76]

Go to your BIOS and increase the MCH Core voltage to 1.2v.


CPU - Stress Test with Prime95
Run Prime95 torture test.
First open Real Temp to monitor CPU temperatures, don't go over 76°C.
Open Prime95 and stop the test if it is running, in Advanced tab select 'Round off checking', in the Options tab select 'Torture Test...', in the window that opens select 'Blend', after 'Number of torture test threads to run' enter 4, then click OK to start the test.

Run the test for two hours.

Intel® Core™2 Quad Processor Q9550

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000007a83, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
 bit 0 : value 0 = read operation, 1 = write operation
 bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002abb943, address which referenced memory
Debugging Details:
------------------
 
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc10e0
 0000000000007a83 
CURRENT_IRQL:  2
FAULTING_IP: 
nt!MiResolveTransitionFault+4a3
fffff800`02abb943 f6819000000004  test    byte ptr [rcx+90h],4
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
[COLOR=red]BUGCHECK_STR:  0xA[/COLOR]
[COLOR=red]PROCESS_NAME:  Azureus.exe[/COLOR]
TRAP_FRAME:  fffff8800c17e4d0 -- (.trap 0xfffff8800c17e4d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=000000000ab48000
rdx=fffff98049578000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a804a0 rsp=fffff8800c17e668 rbp=fffffa8008913480
 r8=0000000000004000  r9=0000000000000200 r10=fffff780c0000488
r11=000000000ab48000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!memcpy+0xb0:
fffff800`02a804a0 488b040a        mov     rax,qword ptr [rdx+rcx] ds:fffff980`540c0000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002a88c69 to fffff80002a89700
STACK_TEXT:  
fffff880`0c17de58 fffff800`02a88c69 : 00000000`0000000a 00000000`00007a83 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0c17de60 fffff800`02a878e0 : fffffa80`0b8aa110 00000000`00000001 fffffa80`08240b70 fffffa80`07ad5040 : nt!KiBugCheckDispatch+0x69
fffff880`0c17dfa0 fffff800`02abb943 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0c17e130 fffff800`02aafe59 : 00000000`00000000 00000000`07a128c6 fffffa80`08240b70 fffff800`02c15e00 : nt!MiResolveTransitionFault+0x4a3
fffff880`0c17e1c0 fffff800`02aa55be : 00000000`00000000 fffff980`540c0000 fffff6fc`c02a0600 fffff800`02c15e00 : nt!MiResolveProtoPteFault+0x419
fffff880`0c17e260 fffff800`02aa3cf1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDispatchFault+0x1de
fffff880`0c17e370 fffff800`02a877ee : 00000000`00000000 00000000`00004000 00000000`00004000 00000000`00004000 : nt!MmAccessFault+0x8f1
fffff880`0c17e4d0 fffff800`02a804a0 : fffff800`02da5b81 00000000`00004000 00000000`00000000 fffffa80`0b800ae0 : nt!KiPageFault+0x16e
fffff880`0c17e668 fffff800`02da5b81 : 00000000`00004000 00000000`00000000 fffffa80`0b800ae0 00000000`00004000 : nt!memcpy+0xb0
fffff880`0c17e670 fffff800`02da5702 : 00000000`055c0000 00000000`0ab48000 00000000`00004000 00000000`00004000 : nt!CcCopyBytesToUserBuffer+0x41
fffff880`0c17e6b0 fffff880`012e6c48 : fffff880`00000000 00000000`00000005 fffffa80`00004000 fffffa80`00004001 : nt!CcCopyRead+0x1a2
fffff880`0c17e770 fffff880`010d80c8 : fffffa80`08913480 fffffa80`0b800a78 fffff880`0c17e9d0 fffffa80`08913401 : Ntfs!NtfsCopyReadA+0x1a8
fffff880`0c17e940 fffff880`010dbc2a : fffff880`0c17ea10 00000000`0ab48003 00000000`0ab48000 fffffa80`08913400 : fltmgr!FltpPerformFastIoCall+0x88
fffff880`0c17e9a0 fffff880`010f95f0 : fffffa80`08913480 00000000`00000000 fffff880`0c17eb00 00000000`00004000 : fltmgr!FltpPassThroughFastIo+0xda
fffff880`0c17e9e0 fffff800`02da5ff9 : fffffa80`08913480 fffffa80`00000001 fffffa80`06a13c90 fffffa80`08913480 : fltmgr!FltpFastIoRead+0x1d0
fffff880`0c17ea80 fffff800`02a88953 : 00000000`00001358 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x417
fffff880`0c17eb70 00000000`753d2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0901f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x753d2dd9
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!MiResolveTransitionFault+4a3
fffff800`02abb943 f6819000000004  test    byte ptr [rcx+90h],4
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  nt!MiResolveTransitionFault+4a3
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd34
IMAGE_NAME:  [COLOR=red]memory_corruption[/COLOR]
FAILURE_BUCKET_ID:  X64_0xA_nt!MiResolveTransitionFault+4a3
BUCKET_ID:  X64_0xA_nt!MiResolveTransitionFault+4a3
Followup: MachineOwner
---------

The process Azureus belongs to the software Azureus or Azureus Vuze or BitTyrant by Aelitis or Azureus, Inc or Azureus Inc or Vuze Inc.

Any malware can be named anything - so you should check where the files of the running processes are located on your disk. If a "non-Microsoft" .exe file is located in the C:\Windows or C:\Windows\System32 folder, then there is a high risk for a virus, spyware, trojan or worm infection!

Uninstall the bittorrent app for testing purposes. You can re-install after the cause is found.​

Old drivers can cause crashes, check for new drivers or look for a new program, if this is for hardware and a 2009 or newer driver can't be found, then uninstall for testing purposes.
​

usbVM31b usbVM31b.sys Mon Sep 19 14:57:34 2005

http://www.vimicro.com/english/product/pc003.htm​

 

[ProbleMatic]

Looking at the program right now, I just took a screenshot of my systems temp as of this moment, checks out OK:

 

[ProbleMatic]

i'll run the above test above tomorrow morning, i have to work tonight @ 10. i won't be able to monitor it while at work.

 

[ProbleMatic]

and I use Vuze a lot, it doesn't give me any problems...as far as I know..

 

[Dave76]

Were the above temps during the Prime95 torture test?
If those temps are at system idle, then you have a problem.

Uninstall Vuze, for testing purposes, it was indicated as the cause of your last crash.
You can re-install it later, or another bittorrent app, you have to eliminate the possible causes as we find them.

Let me know the answer to the above question, if you are having high CPU temps, this will need to be addressed first.

 

[ProbleMatic]

Alright, as far the CPU temps, yes, those are the system idle temps. I haven't yet ran Prime95, but I am right now. What would I need to do about those pretty high temps? Would I need some kind of cooling put in? Do you still want me to change the voltage in the system bios to 1.2? It was hot out yesterday, around 77 degrees. Hot in my room too. Does that matter? I just removed Vuze now. Any torrent programs other than Vuze that you would recommend?

 

[Dave76]

If you idle temps are in the 50-60°C range then don't run prime95.

Your idle temp should be around 35°C, 40°C max.

Check if you CPU cooler is tight, it should not move or be able to twist it.
It will likely have four push pins, check that they haven't come loose.
Make sure the CPU cooler fan is rotating.

77°F = 25°C, that is not hot enough to affect the CPU idle temps.