BSOD IRQL not less or equal

[jayarte]

Hello,

My OS is Win 7 64 bit OEM, and the PC came with minor overclock already from cyberpower.com. I've had the pc for 18 days, and had maybe 3-4 bsod previous to the one today (sorry can't rem the error message with those). Today altered the overclock settings in bios, and got the bsod again (info attached) when playing Lord of the Rings Online. Previous bsod's happened not when gaming.

Checked drivers and all are up to date. Ran deep scan with avast free, no malware was detected.

Thanks in advance for any advice anyone can offer.

 

[wish]

Hi,
Nothing much info in single dump so it'll much better if you follow this instruction:
Blue Screen of Death (BSOD) Posting Instructions

Anyway your dump has bugcheck 0xA = IRQL_NOT_LESS_OR_EQUAL could be caused by driver or RAM.

Start troubleshooting by removing Avast and replace it with MSE.
http://www.microsoft.com/security_essentials/

Then update these drivers:

yk62x64.sys  Mon Sep 28 01:19:31 2009 --> [URL="http://www.marvell.com/support.html"]Marvel Yukon Ethernet driver[/URL]
copperhd.sys Tue May 23 20:51:13 [COLOR=Red]2006[/COLOR] --> [URL="http://www.razersupport.com/index.php?_m=downloads&_a=view"]Razer Diamondback[/URL]

Log:

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {11, d, 1, fffff80002cc4694}

Probably caused by : ntkrnlmp.exe ( nt!KiCancelTimer+28 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 0000000000000011, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000001, 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: fffff80002cc4694, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef50e0
 0000000000000011 

CURRENT_IRQL:  d

FAULTING_IP: 
nt!KiCancelTimer+28
fffff800`02cc4694 f00fba2b07      lock bts dword ptr [rbx],7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002ffd7f0 -- (.trap 0xfffff88002ffd7f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002ffd9b8 rbx=0000000000000000 rcx=0000000000000011
rdx=00000000000126d9 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cc4694 rsp=fffff88002ffd980 rbp=0000000000000001
 r8=0000000000015eee  r9=0000000000000000 r10=0000000000000e81
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KiCancelTimer+0x28:
fffff800`02cc4694 f00fba2b07      lock bts dword ptr [rbx],7 ds:2711:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cbcca9 to fffff80002cbd740

STACK_TEXT:  
fffff880`02ffd6a8 fffff800`02cbcca9 : 00000000`0000000a 00000000`00000011 00000000`0000000d 00000000`00000001 : nt!KeBugCheckEx
fffff880`02ffd6b0 fffff800`02cbb920 : 00000000`00000000 00000000`00000011 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02ffd7f0 fffff800`02cc4694 : 00000000`00000001 fffffa80`075997c0 00000000`00000000 00001f80`01000d81 : nt!KiPageFault+0x260
fffff880`02ffd980 f7fffffa`fc324d43 : fffff880`02fd5180 00000000`00000001 fffff880`02fe00c0 00000000`00000000 : nt!KiCancelTimer+0x28
fffff880`02ffd9c0 fffff880`02fd5180 : 00000000`00000001 fffff880`02fe00c0 00000000`00000000 00000000`00000010 : 0xf7fffffa`fc324d43
fffff880`02ffd9c8 00000000`00000001 : fffff880`02fe00c0 00000000`00000000 00000000`00000010 00000000`00000000 : 0xfffff880`02fd5180
fffff880`02ffd9d0 fffff880`02fe00c0 : 00000000`00000000 00000000`00000010 00000000`00000000 00000000`00000000 : 0x1
fffff880`02ffd9d8 00000000`00000000 : 00000000`00000010 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`02fe00c0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiCancelTimer+28
fffff800`02cc4694 f00fba2b07      lock bts dword ptr [rbx],7

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiCancelTimer+28

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0xA_nt!KiCancelTimer+28

BUCKET_ID:  X64_0xA_nt!KiCancelTimer+28

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

 

[jayarte]

Sorry about that, I followed the instructions but uploaded the wrong file.

 

[wish]

Hi jayarte no problem about that,
Hmm still the same dump as before, so follow the suggestion above.
Make sure to do the update and see how is it goes. If still get BSOD then attach the new files here.

 

[jayarte]

I decided to update the drivers first and try for a few days until/if I get another bsod, then uninstall Avast so it might be easier to see which, if any, was the cause of the crash.

Thanks for the help, wish, much appreciated.

 

[jayarte]

Another bsod

I've had another bsod, this time whilst browsing only (using firefox). I hope I've been more successful this time in gathering the data and uploading it.

I've also attached 3 cpuz screens to show cpu overclock and memory timings because I think the latter are wrong but don't have a clue how to adjust them correctly, plus SIW screens to give more detailed info on memory.

Please let me know if you need any more data, and thanks once again for any help anyone can offer.

Actually I'll post the cpu and siw screens in the post below, because for some reason I can't upload them to this post.

 

[jayarte]

more info

Forgot to say I have uninstalled Avast and installed MSE and the bsod happened a couple of days after that.

The slight overclock which the pc came with also caused bsod, but I reckon it's prob because I haven't got the correct overclock for this system yet. I'm a bit of a noob when it comes to overclocking and I tend to copy settings people post on forums. I know that's not the best way, but my illness makes it hard for me to concentrate, so fiddling around with settings and testing is just beyond my reach, unfortunately. I prefer to get some settings someone has tried and then tweak them until they are right for my pc set-up, but I feel out of my depth with this new cpu.

Screens of cpuz and siw attached for further info.

 

[wish]

Hi again,
Yes, I see you have update the drivers and the 2 new dmp files have IRQL_NOT_LESS_OR_EQUAL (0xa) and DRIVER_IRQL_NOT_LESS_OR_EQUAL (0xd1) bugcheck.
Usual caused by driver and RAM but your overclock system is most likely the caused.

Honestly I don't have much experience with hardware stuff, so I'll search help for you.
The only things that I can suggest is : could you adjust the CPU clock into default clocks?
Default Frequency = 2800 Mhz
Your current Frequency = 3800 Mhz
Overclock Ratio = 1.35

 

[Wishmaster]

A 1000Mhz overclock on that Cpu (about 35-36% OC) is a bit more than a mild OC.

What Im curious about is the vcore seems quite low for 3.8Ghz.


If it were me, being as the PC is new, take it back and make them replace or fix it.


However, if you want to try and resolve the issue yourself:

My guess is its just unstable.
You can try running Prime95 and see what happens.
Chances are it will fail. But that will let you know its a hardware issue.


So to isolate it, the first thing I would do is go into the bios and reset to optimized deafults.

This should return everything to default speeds.


Next, test the hardware itself to be sure it is good.

Then, run Memtest86 to ensure memory is good.
If it checks good, boot to Windows and run Prime 95.

You want to be sure the hardware itself is good before attempting any OC.

 

[Hopalong X]

Jayarte

Have easy way to get rid of OC and back to default.

Do you have ASUS TurboV EVO installed on the PC?
Go to start> All Programs> Asus It should be listed there. Open it if it is.

Let me know.

Wishmaster I was typing when you posted. Leave it as is and run your test or get rid of OC? Your call.

TurboV is the software they use to OC with. It can be accessed easier than thru bios. In the picture they have his set on #3.
Set mine there and it goes to 3.8GHz.
Click the "0" and then click Apply then the system will auto reboot to default settings.
Bios is now reset to defaults also.
Software accessed Bios.

 

[Wishmaster]

Wishmaster I was typing when you posted.
Leave it as is and run your test or get rid of OC? Your call.

I agree. I would just get rid of the OC for the time being.

Running Prime as is will likely fail, pointing to a hardware problem as we already suspect.
Pinpointing the problem will require resetting defaults and testing to isoltae the culprit. So in a sense, its a bit pointless.

just my 2cents

 

[Hopalong X]

Wishmaster

I added to my last post.

 

[jayarte]

Thanks for the helpful suggestions. Yes, I could take it back to default settings, but I don't really want to just yet. This chip should easily overclock to 3.8MHz, although I am happy to settle for less (maybe around 3.4MHz). The part I am really unsure about is the memory timings: I just don't think they are right, but don't know enough to alter them.

I have looked at the turbov utility, and will use it if need be. At present, my best bet (maybe) is to post this info on the overclock forum where I got the settings I used, and ask for advice, particularly re memory timings for my brand of RAM. Or, I could leave the blck as it is, but set everything else back to auto, which is how it was when the pc arrived. As I said though, the overclock the pc arrived with also caused a couple of bsod's. Also forgot to say that the pc was tested for 48 hours before they sent it out.

Something I forgot to mention: I ran the windows memory diagnostic at extensive setting, including cache, for 7 passes and no faults were found. I realise memtest86 is probably better given that everyone recommends it, but I thought I might as well try the windows tool first.

Thanks again for all help and advice offered,

Regards,

Jay

 

[Wishmaster]

The only problem with plugging some one elses settings in, is what your experiencing now.
On top of which, you really have no idea what exactly is causing the instability.
It could be the Chip, RAM, voltages, heat .. just too many variables.

At this point you'd just be guessing, which makes it extremely difficult to diagnose.


Keep in mind, all HW is different.
So even if someone has the exact same setup as you do, results will vary. Some better, some worse.


Your best bet is start at stock speeds, test to make sure all is OK.
If it is start slowly.


Lower RAM speeds, see what the CPU is capable of, and where its limits are.
Then start working with RAM, timings, etc.

This way, when problems arise you know where to look.

The overclock you are asking for (3.8Ghz) plus, is not a mild OC.
A mild OC is 20% or less. Your asking 35% +

Is it capable? Probablly so.
But remember, even if 90% of those CPUs reach that speed or more, does not mean yours will.

This is not the type of thing you can just copy someone elses settings, plug them in and hope for the best.


Perhaps someone else will have something more positive to share.

 

[jayarte]

I know you are right, Wishmaster, I'm just trying to avoid the long slog. Probably there'll be no way round it in the end. I'll keep ya'll posted.

Thanks again for all the helpful advice, and I'm not just ignoring it, honestly, I'm just postponing the inevitable ^^

 

[Wishmaster]

I know you are right, Wishmaster, I'm just trying to avoid the long slog. Probably there'll be no way round it in the end. I'll keep ya'll posted.

Thanks again for all the helpful advice, and I'm not just ignoring it, honestly, I'm just postponing the inevitable ^^

Let us know what you find.
You very well may be able to work it out.

 

[jayarte]

Sorry for the delay in replying here. It took me a long, long time to realise that the bsod was caused by my Razer Coppherhead driver. I had enabled Win7 to automatically update all drivers and the driver for the mouse was actually incompatible. The only reason I finally realised was because I noticed that any time I unplugged and reinstalled the mouse usb, the system would crash. Obviously, that isn't something I do very often, so I hadn't connected the two.

I googled Razer mouse incompatibility Win 7 and it seemed lots of people had bsod's occurring from this. Reinstalled the driver from Razer's website (also unticked enable Win to auto update drivers), and the problem didn't reoccur.

My overclock was changed after much reading around and thinking through the relationship between the different factors, and now I have been stable at around 3.45 MHz (hyper threading disabled, and, after a period of testing without, power saving options enabled). DRAM timing is 9,9,9,24 as recommended by manufacturer (Mushkin). My pc has been running stable with this oc for a couple of months now.

Ai Overclock Tuner.....................[Manual]
CPU Ratio Setting......................[21.0]
Intel(r) SpeedStep(tm) Tech............[Enabled]
Xtreme Phase Full Power Mode...........[Enabled]
BCLK Frequency.........................[165]
PCIE Frequency.........................[100]
DRAM Frequency.........................[DDR3-1322MHz]
UCLK Frequency.........................[2646MHz]
QPI Link Data Rate.....................[Auto]

CPU Voltage Control....................[Manual]
CPU Voltage............................[1.19375]
CPU PLL Voltage........................[1.80]
QPI/DRAM Core Voltage..................[1.22500]
IOH Voltage............................[1.14]
IOH PCIE Voltage.......................[1.50]
ICH Voltage............................[1.20]
ICH PCIE Voltage.......................[1.50]
DRAM Bus Voltage.......................[1.50]
DRAM DATA REF Voltage on CHA...........[Auto]
DRAM CTRL REF Voltage on CHA...........[Auto]
DRAM DATA REF Voltage on CHB...........[Auto]
DRAM CTRL REF Voltage on CHB...........[Auto]
DRAM DATA REF Voltage on CHC...........[Auto]
DRAM CTRL REF Voltage on CHC...........[Auto]

Load-Line Calibration..................[Enabled]
CPU Differential Amplitude.............[800mV]
CPU Clock Skew.........................[Delay 300ps]
CPU Spread Spectrum....................[Disabled]
IOH Clock Skew.........................[Auto]
PCIE Spread Spectrum...................[Disabled]

C1E Support............................[Enabled]
Hardware Prefetcher....................[Enabled]
Adjacent Cache Line Prefetch...........[Enabled]
Intel(r) Virtualization Tech...........[Disabled]
CPU TM Function........................[Enabled]
Execute Disable Bit....................[Enabled]
Intel(r) HT Technology.................[Disabled]
Active Processor Cores.................[All]
A20M...................................[Disabled]
Intel(r) SpeedStep(tm) Tech............[Enabled]
Intel(r) C-STATE Tech..................[Enabled]
Thanks to everyone who offered advice, and sorry once again for the long delay in coming back to post.

 

[CarlTR6]

That is good news, Jay. Thank you for reporting back with your solutions. I am glad you are BSOD free.