Windows 10: Critical_structure_corruption bsod

I have this configuration:

MB:Asus M2n-e
CPU: Amd 9650 2.3ghz no overclock
Ram: corsair 4gb 1066 (working 800mhz)
HDD: WD velociraptor 250gb 10000rpm (win 10 64 bit) + 1tb caviar black + 1tb caviar black sata II
psu: 650W high power sirtec
VGA: evga gtx 460 sc factory default
creative x-fi pci ex
intel gigabit card CT
1 dvdrw lg
Windows 10 64bit build 10.0.10586.11 (th2_release.151112-1900)

I have tested the ram with mem test no errors 100 %
no virus scan with kaspersky internet security and Malwarebytes Anti-Malware
HDD disks are 100 % healthy and no errors
also tested the videocard no crash

I have this BSOD
CRITICAL_STRUCTURE_CORRUPTION

I've attached print screen of the bsod




:)

 

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

 

You are required to remove every bypass/crack on your system before we proceed.

Counterfeit programs causes the system to behave in unexpected ways what makes troubleshooting unreliable.
For this reason we won't try it and will not give support until all the bypasses have been removed.
Note, this does NOT mean the bypasses are causing the crash.

Forum rules

Code: 127.0.0.1 lmlicenses.wip4.adobe.com 127.0.0.1 lm.licenses.adobe.com 127.0.0.1 na1r.services.adobe.com 127.0.0.1 hlrcv.stage.adobe.com 127.0.0.1 practivate.adobe.com 127.0.0.1 activate.adobe.com 127.0.0.1 activate-sea.adobe.com 127.0.0.1 activate-sjc0.adobe.com 127.0.0.1 practivate.adobe.com 127.0.0.1 ereg.adobe.com 127.0.0.1 activate.wip3.adobe.com 127.0.0.1 wip3.adobe.com 127.0.0.1 3dns-3.adobe.com 127.0.0.1 3dns-2.adobe.com 127.0.0.1 adobe-dns.adobe.com 127.0.0.1 adobe-dns-2.adobe.com 127.0.0.1 adobe-dns-3.adobe.com 127.0.0.1 ereg.wip3.adobe.com 127.0.0.1 wwis-dubc1-vip60.adobe.com[/quote]

 

Please run the dm log collector again, so nobody gets confused with this *Smile

 

done but today I did delete also the dumb bsod file(the 500MB) but you can find it in the other upload thank you

 

If you are using a program like Ccleaner please stop using it while troubleshooting.
This because programs like Ccleaner remove dump files that are needed to troubleshoot.
Or configure Ccleaner to not remove dump files:




The single dump from your first upload doesn't contain anything useful.
Code: Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/quote] Following a generic and specific usual cause, please enable driver verifier to find any problematic driver.
Read the instructions carefully!





Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

when I will have a blue screen I will post it again but that dump that you read does not have a little bit of information ??

 

That is what I said,

 

yes but the bluescrrenview say caused by ntoskrnl.exe is this fake or what ??

 

No, the ntoskrnl.exe file is the last file to blame.
If everything else cannot be blamed this file is blamed.
However, this Windows file is used in the boot process, if it is the cause then you would have much more problems.
Also, Windows drivers are rarely the real cause, in almost every case you can assume it is not the real cause.

 

but from your experience what do you think that could be the problem of this structure_critical thing ???

 

It is easier to say that, with description from your side of what happens and what you are doing *Smile

 

I've had started using driver verify and will test for 48h........anyway my pc run 24/7 days hope to find the bluescreen.......but if a driver fails driver verify will show me the bug ????

 

It depends on what error code and if a driver is shown.