Help! CRITICAL_STRUCTURE_CORRUPTION BSOD

bala89

Commendable
Aug 1, 2016
6
0
1,510
My system crashes with BSOD saying CRITICAL_STRUCTURE_CORRUPTION
- Lenovo m91 with i7 2600, 12 GB ram, 2GB and GT 730
- Windows 10 full install in PNY 240 GB SSD
- have office 2016, EndNote, google drive and Adobe reader - nothing more
- MemTest86+ = pass, no errors.
- intel processor diagnostic tool = pass
- whochrashed:

crash dump file: C:\Windows\Minidump\073116-4609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x109 (0xA3A01F5925961771, 0xB3B72BDF7817BFBA, 0x1A0, 0x7)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


Please help
 
Solution
Hello... THX again... Ok both of these are Windows OS components having problems.

#1 there is problem with the administrator settings or ownership of the clsid and appid listed... locate the name of the APP. http://www.sevenforums.com/general-discussion/28840-event-id-10016-dcom-permissions-error.html
#2 the service Control manager is starting/stopping 'Sync host" OneSyncSvc http://servicedefaults.com/10/onesyncsvc/

I would suggest always logging in an administrator, when installing new APPs that need online communications, so as to have these settings/permissions auto configured in the future.

Do you have this computer connected to other computers/WAN/office?
Hello... APPs Calls can cause them... and OS Calls can cause them... and hardware can cause them... We need to fix/look at them in that order first.

1) Do you have any RED or Yellow marks in your Control panel-Device manager?
2) kernel 41 errors mean the OS was not properly shut down... either by You OR the hardware.

Here is the Windows event debug screen.

You NEED to be logged on as administrator to the OS...

let's see what the OS is reporting as the error... Right click computer-manage-System Tools-Event Viewer-Windows Logs-System. Click on the "RED" errors, for more information, General/Details... and files/drivers/Apps, comments/suggestions/information associated with them B )

Expanding Window panes and Posting screen images from here will help me, help you faster... But copy and posting text will work too B )
 

bala89

Commendable
Aug 1, 2016
6
0
1,510
From EventViewer:
1. The computer has rebooted from a bugcheck. The bugcheck was: 0x00000109 (0xa3a01f58b3c8b71f, 0xb3b72bdf06498718, 0x00000000000001a0, 0x0000000000000007). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 51f191a6-1cce-42a0-9887-a423241405ee.

2. Idle power management features on processor 0 in group 0 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware.

Others: https://drive.google.com/open?id=0BwhJI880WFGBaDUwZ0w0Y0RScVE
 
Hello... "Idle power management features on processor 0 in group 0 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware." this suggests a Bio's update to your MB, have you checked your Systems maker website, for a Newer MB Bio's Version, than the one you have installed now, listed in your BIO's screen?
 

bala89

Commendable
Aug 1, 2016
6
0
1,510
Updated BIOS, still the problem persists :(

On Tue 8/2/2016 3:49:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080116-4093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x109 (0xA3A00F58B478D6A5, 0xB3B71BDF06F9A69E, 0x1A0, 0x7)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Matched error in event viewer:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000109 (0xa3a00f58b478d6a5, 0xb3b71bdf06f9a69e, 0x00000000000001a0, 0x0000000000000007). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 1770cab5-b3c7-4a21-a8b8-6ef4d7e6ac99.
 

bala89

Commendable
Aug 1, 2016
6
0
1,510
Hi Ironsounds,

I snapped CPU-Z mainboard with Lenovo support/drivers side by side. Both showing same BIOS version...

Thank you for your prompt help!

open

https://drive.google.com/open?id=0BwhJI880WFGBdjRTZFRGc2N6OFk

 
Hello... THX... I meant from here...
Right click computer-manage-System Tools-Event Viewer-Windows Logs-System. Click on the "RED" errors, for more information, General/Details... and files/drivers/Apps, comments/suggestions/information associated with them B )

Expanding Window panes and Posting screen images from here will help me, help you faster... But copy and posting text will work too B )
 
Hello... Thx... that's better... move the Windows panes in the future for complete sentences and information... Your My eyes here B )

Well lets start with giving me a closer/Full view and "detail" of the DistributedC... and Service Cont... errors, lets see what APP is making these BAD calls. Ok ?
 

bala89

Commendable
Aug 1, 2016
6
0
1,510


Here you go:
https://drive.google.com/open?id=0BwhJI880WFGBN2ZtZmVtTmlYV0E
https://drive.google.com/open?id=0BwhJI880WFGBd0Z0Rnl5VmNzUk0

https://drive.google.com/open?id=0BwhJI880WFGBYW5OazRvWk5PcTQ
https://drive.google.com/open?id=0BwhJI880WFGBRnBJUEl6RHpSRjQ

Thank you

 
Hello... THX again... Ok both of these are Windows OS components having problems.

#1 there is problem with the administrator settings or ownership of the clsid and appid listed... locate the name of the APP. http://www.sevenforums.com/general-discussion/28840-event-id-10016-dcom-permissions-error.html
#2 the service Control manager is starting/stopping 'Sync host" OneSyncSvc http://servicedefaults.com/10/onesyncsvc/

I would suggest always logging in an administrator, when installing new APPs that need online communications, so as to have these settings/permissions auto configured in the future.

Do you have this computer connected to other computers/WAN/office?
 
Solution