BSOD - Critical Structure Corruption every 1st PC turn on - Win 10 - Urgent matter

[Alexe300]

Hey all !
I have a serious problem regarding my PC. Every time I power it on, it runs for a while and then BAM !!! BSOD - Critical Structure Corruption. If it restarts then I can run it for as long as I like w/o any problems what so ever. I tried every tip and trick from this forum including SFC.EXE, DISM.EXE, VERIFIER, MEMTEST86, changed RAM, changed GPU, changed HDD, reaplied thermal paste (altho VRM temp is on 70 idle - 90 load), tried 5 versions of WIN10. I'm getting out of options here and i hope it's not smt that could prematurely kill my PC. Pls help me, I need a solution !!!

PC Specs are:
MB - Intel DQ57TM (latest BIOS update)
CPU - i7 860 (no OC !) - Ninja Scythe 3 Cooler
RAM - Kingston Dual Channel 2x2GB 667 Mhz
GPU - Nvidia GT630
PSU - 450 W
SSD - Adata 128 GB


Minidump link - https://drive.google.com/file/d/0B1CHqxIlyUmueEwwWnFNVEQxY0E/view?usp=sharing

Thank you in advance and I hope i get an answer !

 

[Alexe300]

Pls guys ..I need a solution to this delicate situation that I am experiencing...TY

 

[gardenman]

Hi, I used WhoCrashed to get reports on 25 of your (26 I think) dump files. The vast majority of them were the CRITICAL_STRUCTURE_CORRUPTION error with the ntoskrnl.exe file. A couple were DRIVER_VERIFIER_DETECTED_VIOLATION errors with the ntoskrnl.exe file.

WhoCrashed Results:

Spoiler

On Sat 4/29/2017 1:28:12 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\042917-8437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x109 (0xA39FBF60ECAA051D, 0xB3B6CBE73F2B1A0F, 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.

On Tue 4/25/2017 1:29:35 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\042517-20734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0xC4 (0xF5, 0x0, 0xFFFFE484C36BEDC0, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver passed a NULL handle to ObReferenceObjectByHandle. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

In addition, I also ran 041417-10421-01.dmp through the Win10 Kit Debugger and got the following results:

Spoiler

Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\UserName\Desktop\Minidump\041417-10421-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
Machine Name:
Kernel base = 0xfffff803`90008000 PsLoadedModuleList = 0xfffff803`9030d060
Debug session time: Fri Apr 14 11:46:18.360 2017 (UTC - 4:00)
System Uptime: 4 days 21:11:20.561
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a00c6740989661, b3b718ed931a9417, 1a0, 7}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )


*******************************************************************************
* *
* 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.
Arguments:
Arg1: a3a00c6740989661, Reserved
Arg2: b3b718ed931a9417, Reserved
Arg3: 00000000000001a0, Failure type dependent information
Arg4: 0000000000000007, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
8 : Object type
9 : A processor IVT
a : Modification of a system service function
b : A generic session data region
c : Modification of a session function or .pdata
d : Modification of an import table
e : Modification of a session import table
f : Ps Win32 callout modification
10 : Debug switch routine modification
11 : IRP allocator modification
12 : Driver call dispatcher modification
13 : IRP completion dispatcher modification
14 : IRP deallocator modification
15 : A processor control register
16 : Critical floating point control register modification
17 : Local APIC modification
18 : Kernel notification callout modification
19 : Loaded module list modification
1a : Type 3 process list corruption
1b : Type 4 process list corruption
1c : Driver object corruption
1d : Executive callback object modification
1e : Modification of module padding
1f : Modification of a protected process
20 : A generic data region
21 : A page hash mismatch
22 : A session page hash mismatch
23 : Load config directory modification
24 : Inverted function table modification
25 : Session configuration modification
26 : An extended processor control register
27 : Type 1 pool corruption
28 : Type 2 pool corruption
29 : Type 3 pool corruption
101 : General pool corruption
102 : Modification of win32k.sys

Debugging Details:
------------------

DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.14393.447 (rs1_release_inmarket.161102-0100)
SYSTEM_MANUFACTURER: Viglen
SYSTEM_PRODUCT_NAME: DQ57TM
SYSTEM_VERSION: 70:71:BC:50:40:28
BIOS_VENDOR: Intel Corp.
BIOS_VERSION: TMIBX10H.86A.0050.2011.1207.1134
BIOS_DATE: 12/07/2011
BASEBOARD_MANUFACTURER: Intel Corporation
BASEBOARD_PRODUCT: DQ57TM
BASEBOARD_VERSION: AAE70931-402
DUMP_TYPE: 2
BUGCHECK_P1: a3a00c6740989661
BUGCHECK_P2: b3b718ed931a9417
BUGCHECK_P3: 1a0
BUGCHECK_P4: 7
PG_MISMATCH: 40000
CPU_COUNT: 8
CPU_MHZ: ae9
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 1e
CPU_STEPPING: 5
CPU_MICROCODE: 6,1e,5,0 (F,M,S,R) SIG: 7'00000000 (cache) 7'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: BAD_STACK_0x109
BUGCHECK_STR: 0x109
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: UserName-PC
ANALYSIS_SESSION_TIME: 05-18-2017 15:08:03.0944
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 81a83ae0317433a47fcc36991983df3b6e638b71
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6e16edd8c7dd677734fdbcd2397a2e35e9fae964
THREAD_SHA1_HASH_MOD: 76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: BAD_STACK_0x109
PRIMARY_PROBLEM_CLASS: BAD_STACK
FAILURE_BUCKET_ID: BAD_STACK_0x109
TARGET_TIME: 2017-04-14T15:46:18.000Z
OSBUILD: 14393
OSSERVICEPACK: 447
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-11-02 06:17:03
BUILDDATESTAMP_STR: 161102-0100
BUILDLAB_STR: rs1_release_inmarket
BUILDOSVER_STR: 10.0.14393.447
ANALYSIS_SESSION_ELAPSED_TIME: 130b
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:bad_stack_0x109
FAILURE_ID_HASH: {b4d7023a-05c3-49b2-3ea4-6240fe57d90e}

I'm no expert on crash dumps or hardware. I can say that when the crash dumps point to ntoskrnl.exe it is difficult to track down what is going on. If they pointed to say "nvidia.sys", then we would know it was a Nvidia driver causing the problem. I would recommended to do hardware tests, but it seems you have already done this. It seems the only thing you haven't changed is the motherboard.

I can't help you much more than that. Maybe someone else will come along with more info and more help. Good luck.

 

[Alexe300]

Thank you for your time ! actually I forgot to specify that I've also changed the MB. From what's being described in the minidumps, it seems that the same thing is causing the BSOD. The only component I haven't changed is the CPU, but I ran a couple of tests (Prime, Intel CPU Utility) on it and they all came out OK. Please dont let it be the CPU. It's hard to get another one with 1156 socket. Still waiting for other opinions...

 

[gardenman]

I guess know you have to reinstall Windows when you change the motherboard. If you don't, the drivers from the old motherboard are still installed and will cause problems.

Have you tried booting up into [Safe Mode] and see if you have any crashes? If the crashes happen often, and right after boot and not when loading games or things like that, then you should test it out in safe mode to see if you have problems. If it normally happens when gaming, then don't try gaming in safe mode. If you don't have crashes in safe mode doing the things that would normally cause a crash, then its one of the drivers that Windows is loading in normal mode that is causing the crash, OR, a program causing the crash (and we might be able to figure out which one, driver or software anyway).

Any additional ideas from anyone else appreciated.