Random BSOD and restarts on clean windows 10 installation when idle

jcoozy · 07 Jan 2017

Hi,

I have just built a PC for a friend (specs in signature). MemTest86 passes all tests (including extended tests overnight) with zero errors. Windows 10 pro installed onto clean, unpartitioned SSD. No overclocks in place, all hardware in auto configuration). Intel desktop utilities showing temps stable when running prime95 and all temp sensors on green.

No games or other apps installed apart from Chrome, battle.net (client only) steam (Client only) and burn test / diagnostics (e.g. CPU-Z).

Only additional hardware apart from MB is an Nvidia 1050 video card (a low power card drawing power from PCI-e bus only) and a MediaTek USB wifi adaptor (windows installed a WHQL driver for this.)

BSOD and re-starts happened at the following times:

1) PC idling, no inputs, sudden restart
2) Starting a download in Steam whilst downloading WOW in battle.net

There have been 2 other re-starts which appeared to result in no dump files

I am posting the dumps here. Would really like an idea what is going on.

Ztruker · 08 Jan 2017

Your running with mixed RAM:

Code:

[Memory Device (Type 17) - Length 28 - Handle 002bh]
  Physical Memory Array Handle  0028h
  Memory Error Info Handle      002ch
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          4096MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                DIMM 3
  Bank Locator                  CHANNEL A DIMM 0
  Memory Type                   18h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         1333MHz
  Manufacturer                  Undefined       
  Serial Number                           
  Asset Tag Number                             
  Part Number                   ST51264BA1339.16FK

[Memory Device (Type 17) - Length 28 - Handle 0031h]
  Physical Memory Array Handle  0028h
  Memory Error Info Handle      0032h
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          4096MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                DIMM 4
  Bank Locator                  CHANNEL B DIMM 0
  Memory Type                   18h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         1333MHz
  Manufacturer                  Undefined       
  Serial Number                           
  Asset Tag Number                             
  Part Number                   RMR1870EC58E9F1333

May not be a problem but has some times caused BSODs and other failures. I recommend removing one of them and runnin gwith 4GB as a test. If no problem then get a DIMM thgat matches what is installed or replace both with a matched set of 8GB DIMMs perhaps.

All the dumps are identical:

Code:

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: a3a025e43168b81b, Reserved
Arg2: b3b7326a83e9d0a5, 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

Nothing else of use in the dumps.

You can try removing the Nvidia card and using the onboard Intel HD for awhile, see if that makes a difference.

Your board is old and no longer supported by Intel, though it should be okay with Windows 10.