BSOD, ntoskrnl.exe, memory_management seemingly at random.

KitsuneSidhe · 16 May 2013

Hi there,
Sooo after more than a month without my desktop (truly a nightmarish experience) I finally got all of the parts I needed (or thought I needed, then actually needed) to fix it. So happy was I when it loaded up and I could start updating and reinstalling my old stuff... and then the bluescreens began.

It started first when I was doing Windows Updates and I ended up having to do all of the updates either one at a time or in small chunks, otherwise they'd get corrupted and wouldn't install correctly. Which is what I was figuring the issue was at first, but for the last week it's been bluescreening, seemingly at random.

I've run memtest and SFC which both came back clean (even let memtest run for 10 hours or so). I did the driver verifier, which crashed with an issue about my keyboard driver, so I updated that (and every other one I could think of) and it's still doing it. So far the two common bug check strings in BlueScreenView have been: Memory_management and IRQL_NOT_LESS_OR_EQUAL... But I suppose you'll have seen that after checking the uploaded stuff, huh? ^^;;

Thank you in advance for your help.

Northernsoul55 · 17 May 2013

Hi,

From your logs:

Code:

 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41790, fffffa8001285fb0, ffff, 0}
Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )

Code:

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

Code:

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

Please remove Avira AV from your system, as an alternative use:

Microsoft Security Essentials.
Recommended from a strict BSOD perspective, compatibility & stability
compared to other antiviruses/internet security software.

Microsoft Security Essentials Download

Note

Once downloaded, update and run a full system scan

---------------------------------------------------------------------------------------------

Please take memtest again following these instructions:
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

https://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Tip

Run these tests overnight and pay particular attention to Part 3

Problem devices:

Code:

 
Universal Serial Bus(USB)Controller PCI\VEN_1B21&DEV_1042&SUBSYS
The drivers for this device are not installed.

Please navigate to:
Go to Control Panel > select icon view> click on the "Device Manager".
In the Device Manager window, find the item/items labeled "Universal Serial Bus controllers." Expand.
Do any of these have a yellow sysmol/triangle next to it?
If so attempt to update/install driver.

This may be the keyboard driver you reffered to, is this the latest version?:
Driver: Lycosa.sys
Timestamp: Wed Sep 30 05:45:50 2009
Refers to: Razer Lycosa/Razer Tarantula Keyboard Driver. Older versions have BSOD issues with Win7

Razer Support

Turn off USB Suspension:

USB Selective Suspend - Turn On or Off

Post back any result/observations
cheers
Dave

KitsuneSidhe · 26 May 2013

Thanks for the help. ^_^

I've dropped Avira for MSE and ran a full system scan, which turned up nothing. BSOD still persisted.
I found a newer driver for my keyboard, BSOD still persisted.
I found the driver in question for the USB controller and it seemed to work, the system went three days without a BSOD, and then it did again.
I ran the Memtest as instructed and no errors came up, and the BSOD persisted.

Since then I've turned Driver verifier back on and the BSOD hasn't happened in the last couple of days. However, my secondary hard drive also isn't showing up, so I'm wondering if that might be the cause. It was formatted on a different motherboard (a non-UEFI one). So I'm wondering if I should turn driver verifier off and see if it'll bring my secondary drive back up so I can format it and see if that helps, or just remove it entirely.

Northernsoul55 · 27 May 2013

Hi,

Okay sounds good, Yes turn verifier off and see the situation with the HDD.

If once verifier confirmed off, and HDD recognised then perhaps it may be best to test the drive:

Please download

Seagate Tools and post back any results,

cheers

Dave

Northernsoul55 · 27 May 2013

Your post attachments are not showing?

KitsuneSidhe · 04 Jun 2013

Alrighty, I stopped running Driver Verifier to see if that'd help. The small drive came back for a couple of times before it stopped showing up, again. Bluescreens continued a few days later, so I took it out entirely. Surprisingly I was able to play a game that I was unable to before, but today it bluescreened again with the usual IRQL stuff (specifically it happened a few minutes after coming back from the system being asleep).

Attached a new run of the SF tools thing. Wondering if I'm going to have to completely reinstall Windows.

Thank you again for the help. ^_^

KitsuneSidhe · 10 Jun 2013

There've been a few more BSODs since the last update, including two within the same hour today. One of them was while I was just browsing the net, and the other happened while installing Windows Updates.

I've attached the latest SFC zip.

Any other ideas? Or should I just break down and try reinstalling windows entirely?

Thanks in advance. ^_^

Northernsoul55 · 12 Jun 2013

Hi,
This driver is still not been updated and may be causing issues?

Code:

 
Driver: Lycosa.sys
Timestamp: Wed Sep 30 05:45:50 2009
Refers to: Razer Lycosa/Razer Tarantula Keyboard Driver. Older versions have BSOD issues with Windows 7

Razer Support

Cheers

Dave

KitsuneSidhe · 12 Jun 2013

Northernsoul55 said:

Hi,
This driver is still not been updated and may be causing issues?

Code:

 
Driver: Lycosa.sys
Timestamp: Wed Sep 30 05:45:50 2009
Refers to: Razer Lycosa/Razer Tarantula Keyboard Driver. Older versions have BSOD issues with Windows 7

Razer Support

Cheers

Dave

I've tried to do it before, and I tried it again. Installing the 3.02 driver doesn't seem to change anything in the device manager or the driver list though. We'll see if it works though, so here's hoping. ^_^

KitsuneSidhe · 13 Jun 2013

Alrighty. I attempted to update the Lycosa Driver. Even using the most recent Windows 7 version (3.02) off their website, it's still giving me a BSOD, and I'm not even sure if it's properly updating the drivers anyway. At least in the Device Manager they're the same as they used to be, and I've tried to manually uninstall the drivers, reinstall in safe mode so Windows doesn't auto-install, etc.

I'll probably try to get a spare keyboard from a friend of mine and see if that fixes it. This keyboard never gave me any issues in my previous run with Windows 7 though.

I've added the SF files again. ^_^