Windows 10: Windows 10- BSOD- CRITICAL_STRUCTURE_CORRUPTION

I am having BSOD every 40 minutes or so on Windows 10. But there seems to be no BSOD when I switch to another microsoft account.

:)

 

CRITICAL_STRUCTURE_CORRUPTION BSOD error message on Windows 10.

Original title: BSOD CRITICAL_STRUCTURE_CORRUPTION on Windows 10?

Hello. Recently, I've met many BSOD with message: CRITICAL_STRUCTURE_CORRUPTION. I don't know which caused it. Here is the dump file:
http://1drv.ms/1NjuKAV

 

Critical_Structure_Corruption Crash

Hi

Since of late I have had some BSOD crashes due to Critical_Structure_Corruption.

I have a MiniDump. How do I send it.

Best regards

 

সায়ন্তন, your issue looks like to be a driver related issue. May be, this account uses any program/software that is calling it.
Code: BugCheck 109, {a3a01f5903acea67, b3b72bdf562da510, 1, 18} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner ---------[/quote] 18 is the type of corrupted region, that is .....
Code: 18 : Kernel notification callout modification[/quote] The description is ....
Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_STRUCTURE_CORRUPTION (109) This bugcheck is generated when the kernel detects that critical kernel code or data have been corrupted. There are generally three causes for a corruption: 1) A driver has inadvertently or deliberately modified critical kernel code or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx 2) A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was booted. Normal breakpoints, "bp", can only be set if the debugger is attached at boot time. Hardware breakpoints, "ba", can be set at any time. 3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.[/quote] But we cannot find any failing driver, even in the deepest seh.

Let us enable Driver Verifier to monitor the drivers. Driver Verifier - Enable and DisableRun Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.



Information Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.


Warning Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.


Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

P.S. Following different suggestions from multiple forums will not be a good idea. If I have been in place of you, I would have choose either place to continue with.

 

I am going on vacation so I will post the results as soon as I get back. Thank you for your support.

 

So, I ran the driver verifier and I got BSOD again. Here is the dump file:-
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

 

Disable Driver verifier.
Update the vJoy driver from here: Download

Let us know how it goes.
_____________________________________________________________
Code: BugCheck C9, {23b, fffff800977b24d0, ffffe00044570510, 0} Probably caused by : vjoy.sys Followup: MachineOwner -------------------------------------------------------------------- Image name: vjoy.sys Timestamp: Tue Mar 19 23:46:09 2013 (5148AB69)[/quote] That is a continuing issue, we failed to trace it last time.

 

Okay, I updated the vJoy driver and BSOD occurred immediately after the restart. But since then, no BSOD till now. It's been just over an hour since the last BSOD.

 

No more BSOD. I think it is solved. Thanks a lot.

 

Good news.
Still, monitor the system. If it causes any further trouble, let us know.

 

Well I uninstalled vJoy because it wasn't working properly with the new driver. But BSOD again after 2 hours. Here's the dump file:-
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

 

Two very well known BSOD causers are present in your system.

► qmudisk tencent QMUdisk \??\c:\program files (x86)\tencent\qqpcmgr\10.8.16208.227\qmudisk64.sys
It is ....

Uninstall it. It is a virus class element.

► nvstreamkms NvStreamKms \??\c:\program files\nvidia corporation\nvstreamsrv\nvstreamkms.sys
It causes BSOD very frequently. To deal with it, you need perform a driver only clean install of the nvidia display driver.

See how it goes. Report us for any further BSOD, following the Blue Screen of Death (BSOD) Posting Instructions .

 

I could not find - Start Menu\Programs\腾讯软件. So I couldn't uninstall it.
I have installed the latest driver for nvidia (i.e Version 364.72) after the last BSOD, so should I uninstall it?

 

Read the entire I posted about it. Some of the descriptions will be found at least.
You cannot leave it in your PC, because it will be harmful to you. It is a potential spyware, that gives some other person access to your computer. If you cannot find it at all, you have to do a clean reinstall of windows in order to get rid of it.

It is not about a driver package installation but driver only installation. Have you done it already as I suggested?
If yes, skip it. If no, do it.

 

I was able to uninstall that tencent spyware.
No BSOD for 4 hours now. But I will keep you updated for any further BSODs.