Solved Bsod. Irql_not_less_or_equal

[Yeoman]

Okidoke. If I don't have any for BSOD's for a week, that would be a very positive sign. Although in that case, I'd be quite puzzled over what actually fixed the BSOD (though I find that is often the case with BSODs, that you can never quite pinpoint the fix).

Thanks for your help, and fingers crossed.

 

[x BlueRobot]

Your welcome and hopefully no BSODs will happen, sometimes it's the smallest things that can be the solution

 

[Yeoman]

I had another bluescreen only last night. I had just clicked the shut down button on the desktop, then a second later; bluescreen.

I've uploaded the BSOD in question, if it's helpful.

 

[Yeoman]

Just had a further two blue-screens this morning, they do seem to arrive like buses, both times they occurred whilst I was browsing the internet.

I just looked again in device manager, there are no little warning symbols or anything, to suggest something is without a driver. :/

When I had BSOD's previously, it was the result of me having all my drivers for the wrong motherboard (I had P8P67, I should have had P8P67 REV 3.1 - the page wasn't showing in the list, so I was none the wiser for ages), last time the FIX, seemed to be just installing the USB3 driver from the disk. This time I'm 100% certain all drivers are correct. I did chipset, lan, usb, audio, GPU and then blutooth off of my mobo disk. And ofc the marvell controller, to see if that stopped the bsods.

Should I upload the last two BSOD's as well? Also, could I try disconnecting the sata/power connectors from my storage hard drive, and leave it a week or so to see if it has an affect?

 

[x BlueRobot]

[COLOR="Red"]BugCheck A[/COLOR], {ffffffffffffffff, 2, 1, fffff8000e2c79b2}

Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )

Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

Use the Windows Upgrade Advisor to check for any compability issuses with drivers, hardware and programs:

• Windows 7 Upgrade Advisor - Download - Microsoft Windows

Delete/Recreate the Pagefile

1. Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
2. Click on the Advanced tab
3. Click on the Performance Settings button
4. Click on the Advanced tab
5. Click on the Virtual Memory Change button
6. Uncheck the "Automatically manage paging file size for all drives" box (it's the default)
7. If the above box isn't checked, then make a note of what the paging file settings are
8. Click on the "No paging file" radio button, then click on "Set"
9. Answer Yes to the confirmation dialog that pops up.
10. Click on OK 3 times (to close all the Windows)
11. Reboot the system (this will delete the paging file)
12. Once Windows starts, go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
13. Click on the Advanced tab
14. Click on the Performance Settings button
15. Click on the Advanced tab
16. Click on the Virtual Memory Change button
17. Place a checkmark in the "Automatically manage paging file size for all drives" box (it's the default)
18. If the above box wasn't checked at first, then re-enter the paging file settings that you noted in Step 7
19. Click on "Set" (it'll be greyed out if you checked the box 2 steps earlier
20. Click on OK 3 times (to close all the Windows)
21. Reboot the system (this will recreate the paging file)

Please upload the other dumps too.

 

[Yeoman]

Since my last post, it's turned to three BSOD's. I've uploaded them.

I've also uploaded the results from the win 7 update program. I passed all the system requirements, and all my programs were compatible bar 1.

I've also deleted and recreated the page file. I hope I've done it right, after rebooting, and opening sysdm.cpl for the second time, I clicked the round button for 'system managed size', then clicked the set button, then I checked the 'automatically manage paging..' box. I assume that's correct, since that was the opposite of what I did first time around.

Also, my D and E drives were already set to not have paging files, I'm assuming this is normal?

 

[Yeoman]

I've already downloaded a more 'compatible' version of winrar x64, I assume installing it won't do any harm? At least it will please Windows Upgrade assistant.

 

[x BlueRobot]

Yes, usually only the drive/partition in which you installed Windows upon has a paging file yet, and least it rules out the possiblity of the WinRAR program not being compatible for some reason, even though I've never come across it causing problems.

Here's the dump with the best information so far:

[COLOR="Red"]BugCheck A[/COLOR], {ffffffffffffffff, 2, 1, fffff8000e5089b2}

Probably caused by : [COLOR="red"]win32k.sys[/COLOR] ( win32k!SURFACE::bDeleteSurface+3c8 )

Win32k.sys is a Windows driver which I believe handles system services, Windows drivers are usually not the true cause of the crash though.

You could try another run of Driver Verifier to see if the drivers are completely fine with Windows after all the updates:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

:info: Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

The system will act more 'laggy' and slow with Driver Verifier enabled.

Have you installed all the latest Windows Updates?

Start rb: > Type: Windows Update > Scan for Updates > Install Updates (Important and Optional)

 

[Yeoman]

Okidoke. Thank you. I'll make sure I'm up to date then try with driver verifier.

 

[x BlueRobot]

Your welcome, and please post back your results.

 

[Yeoman]

I ran driver verifier for about 8 hours yesterday (I think I'm meant to leave my pc on for the whole 24 hours?), but, I turned it off when I went to bed, I'll leave it on all day today and tonight. So far I haven't had any BSODs. Although, when trying to start steam (which caused a BSOD the previous time I ran driver verifier), my machine seems to freeze, and I have to restart, but I get no BSOD.

Since I haven't encountered a BSOD whilst gaming (outside of driver verifier), perhaps that's just as well that I wait to see if I get one through browsing or whilst on the desktop.

I'll keep you updated if there are any other developments.

 

[x BlueRobot]

Run Driver Verifier for 24 hours, and it will slow down your computer, which may explain the why it seems to freeze when you went on Steam. Thanks for the update, and least you haven't had a BSOD so far.

 

[Yeoman]

Okay. I've ran driver verifier for about over 40 hours in total. So about 8+20+16. It hasn't ran for 24 hours in one go, not sure if that's a problem. But it has ran for at least 40 hours overall.

No bluescreens sadly. I was hoping I would experience some so that it might hone down on the issue. And the things which produced BSOD's last time running verifier haven't caused any this time (such as opening steam, I mentioned it froze instead).

So, not sure if its good news or bad news. Since obviously the problem isn't fixed, considering the 3 BSOD's on Wednesday.

 

[x BlueRobot]

Have you checked for all the latest Windows Updates? You could check for all the latest drivers for all the possible hardware installed.

 

[Yeoman]

All my drivers are up to date. And I've installed all possible windows updates.

Should I try scanning with a Seatools variant that works with windows? See if that brings anything up, since the DOS version wasn't detecting my hard drives?

 

[x BlueRobot]

Yes, since we, actually haven't even tried to use the Windows version yet.

 

[Yeoman]

Okay. I installed seatools for windows, though to do that I had to first download and install some kind of .netframework 4.0 or something like that. Which I believe I've heard of before.

Seatools for windows has a number of basic tests, but I ran a 'smart check' and 'long generic' test, the latter taking 4hrs and 7.5hrs for my 1TB and 2TB respectively.

Both drives passed both tests.
Not sure to try other tests or explore 'advanced' options.

 

[x BlueRobot]

Try the tests designed for your drives by Western Digital, just to confirm the results.

The link and steps can be found here:

• Hard Drive Diagnostic Procedure

The basic tests should be fine.

 

[Yeoman]

I already ran the WD data life guard program on my drives from within windows. I did the extended test on both drives, and it said they both passed. Would you like me to run them again?

 

[x BlueRobot]

I would just leave it then, and see what happens, your hard-drives seem to be in good condition.