Windows 10: Random BSOD with memory_corruption which seems to be IRQ related

Hi,

For the last 2 months now I randomly get BSOD (with multiple types of failure) but most indicate memory_corruption.

I have tried to figure this out myself, but to no avail.

Can some possibly help me by checking the dump info?

Regards,


:)

 

IRQ conflict in Windows 10 but option to change interrupt grayed out

Ralf, thanks. See my response to MS, above. I've done endless, extensive testing of hardware and driver updating. The diagnostics and BSOD error messages suggest IRQ conflicts, memory conflicts, and driver issues, but I haven't figured out anything that
would be causing this. That's why the IRQ issue seemed to be worth exploring.

 

IRQ conflict in Windows 10 but option to change interrupt grayed out

Just by way of contrasting experience, I have had a computer where nearly every device was using the same IRQ and there were no IRQ conflict related BSODs. With virtually the whole range of IRQ's vacant and available to be used, neither the BIOS nor Windows
could ever be induced to change the IRQ assignments. That scenario seems to have been unique to that specific motherboard as others (same model, still on the shelf) that I checked all assigned IRQs normally. Anyhow I ran that computer for about 12 years in
that state, with Windows versions starting at XP Media Center Edition up through Windows 10, until a capacitor blew on the motherboard late last year.

Not that it cannot still happen but the last time I found hardware IRQ conflicts to be much of an issue was in pre-XP versions of Windows. These days I'd look for software or driver issues as likely causes, or defective hardware. Check that your graphics
card driver is either all from Nvidia or all from Microsoft update. Allowing the two sources to mix can cause the drivers to be corrupted. Software incompatibilities can also mimic hardware issues. One thing that can cause random BSODs is software that installs
or uses obsolete versions of DLL files. Some program or process causes an old DLL to be loaded, which stays loaded, and then at some random time later a different process makes a call to that DLL for a function that isn't supported in the old file version
and Windows does a face-plant.

 

Latest dump shows: lacuna64t.sys
Code: BugCheck 1E, {ffffffffc0000005, fffff80338c95ae2, ffffa1005e696e18, ffffa1005e696640} *** WARNING: Unable to verify timestamp for lacuna64t.sys *** ERROR: Module load completed but symbols could not be loaded for lacuna64t.sys Probably caused by : memory_corruption[/quote] This belongs to Dell: C:\Program Files (x86)\Dell SecureWorks\Red Cloak\lacuna64t.sys
I suggest uninstalling it unless you really need it. If you do then see if there is a newer verson available.

An earlier dump showed: jnprns.sys
Code: BugCheck D1, {8, 2, 0, fffff8048c764ae4} *** WARNING: Unable to verify timestamp for jnprns.sys *** ERROR: Module load completed but symbols could not be loaded for jnprns.sys Probably caused by : jnprns.sys ( jnprns+4ae4 )[/quote] This belongs to Juniper Network Service and is relatively old: 30/10/2014. Uninstall it. If you want to continue to use it, find a newer version to install.

 

Unfortunately I do need both installed and it seems I have the latest version of each.

What I have started to notice is that most crashed seem to happen when I click on a link in Outlook and it opens a new tab in Firefox.

What is wierd is that each crash seems to be slightly different as the last one was: Pool_corruption

 

You could try uninstalling them, rebooting then reinstalling them again, see if that helps.