[Win10 x64] Critical Structure Corruption

LeoBloom · Mar 19, 2016

Hello, and thanks in advance for help. PERFMON System Health Report will not complete after hours of running. Is this normal?

· OS - Windows 10, insider build 11099
· x64
· Windows 10
· full retail version
· ~1 year hardware (custom built)
· ~ half a year old OS install

· i5-4690
· GTX 970
· MB GIGABYTE|GA-H97-GAMING 3 H97 ATX
· PSU EVGA|750W 120-G1-0750-XR RT

Desktop

Jared · Mar 19, 2016

re: BSOD Critical Structure Corruption - Windows 10 x64

Code:

0: kd> .bugcheck
Bugcheck code 00000109
Arguments a3a01f59`8f73c5e5 b3b72bdf`e1f16721 fffff803`b2817c14 00000000`00000001


0: kd> !chkimg -lo 50 -d !nt
    fffff803b2817c54 - nt! ?? ::FNODOBFM::`string'+40034


nt!MiInvalidateCollidedIos

It would appear that there was a bit flip in an address, resulting in memory corruption.
This is only a minidump, so I cannot look further into what exactly happened, but it looks like an IO failed because of the bitflip, possibly a hash function.

The cause is almost certainly failing RAM, so I suggest running Memtest86+ overnight to confirm it.

LeoBloom · Mar 20, 2016

re: BSOD Critical Structure Corruption - Windows 10 x64

I ran Memtest86+ overnight for 9 hours. It stated 8 Passes and 0 Errors. Is there a better way to access further information into the crash?

Jared · Mar 22, 2016

re: BSOD Critical Structure Corruption - Windows 10 x64

Can we get the Kernel memory dump from C:\Windows\MEMORY.dmp ?
Upload it to a file sharing site and paste the download link here.

LeoBloom · Mar 22, 2016

re: BSOD Critical Structure Corruption - Windows 10 x64

memory.dmp

MEMORY.DMP - Google Drive

invalid · Mar 23, 2016

re: BSOD Critical Structure Corruption - Windows 10 x64

Have not had time to get to this today but a first guess would be this....

Code:

           FriendlyName: Logitech QuickCam S5500
               Location: n/a
           SymbolicLink: [URL="file:///?\usb#vid_046d&pid_09a1&mi_00#7&12e6e5da&0&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\{bbefb6c7-2fc4-4139-bb8b-a58bba724083"]\\?\usb#vid_046d&pid_09a1&mi_00#7&12e6e5da&0&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\{bbefb6c7-2fc4-4139-bb8b-a58bba724083[/URL]}
           Manufacturer: Logitech
             HardwareID: USB\VID_046D&PID_09A1&REV_0008&MI_00,USB\VID_046D&PID_09A1&MI_00
             DriverDesc: Logitech QuickCam S5500
         DriverProvider: Logitech
          DriverVersion: 12.10.1110.0
      DriverDateEnglish: 10/7/2009 00:00:00
    DriverDateLocalized: 10/7/2009 12:00:00 AM
                Service: LVUVC64
                  Class: Image
          DevNodeStatus: 180200A[DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
            ContainerId: {14F990AE-9D84-5038-864F-56758647F615}
            ProblemCode: No Problem
  BusReportedDeviceDesc: n/a
                 Parent: USB\VID_046D&PID_09A1\B5471720
      DriverProblemDesc: n/a
           UpperFilters: n/a
           LowerFilters: n/a
                  Stack: \Driver\ksthunk,\Driver\LVUVC64,\Driver\usbccgp
      ContainerCategory: Imaging.Webcam

LeoBloom · Mar 26, 2016

Re: BSOD Critical Structure Corruption - Windows 10 x64

Is there a crash associated with this driver, or are you pointing it out because it is from 2009? I ask because I am not really looking to get a new webcam so I want to make sure if the crash is in fact due to the driver

invalid · Mar 28, 2016

Re: BSOD Critical Structure Corruption - Windows 10 x64

LeoBloom said:
Is there a crash associated with this driver, or are you pointing it out because it is from 2009? I ask because I am not really looking to get a new webcam so I want to make sure if the crash is in fact due to the driver

Hey Leo,

There was not much going on in that memory.dmp you provided.

Code:

BugCheck D1, {ffffcf8054cf8fc0, 2, 1, fffff8018e00f82b}
Probably caused by : USBXHCI.SYS ( USBXHCI!memcpy+2b )
Followup:     MachineOwner

 # Child-SP          RetAddr           Call Site
00 fffff802`c44c34b8 fffff802`c2947e29 nt!KeBugCheckEx
01 fffff802`c44c34c0 fffff802`c29465c7 nt!KiBugCheckDispatch+0x69
02 fffff802`c44c3600 fffff801`8e00f82b nt!KiPageFault+0x247
03 fffff802`c44c3798 fffff801`8e00db02 [COLOR=#ff0000]USBXHCI!memcpy+0x2b[/COLOR]
04 fffff802`c44c37a0 fffff801`8e00a3c9 [COLOR=#ff0000]USBXHCI!Control_ProcessTransferEventWithED1+0x212[/COLOR]
05 fffff802`c44c3830 fffff802`c2862df9 [COLOR=#ff0000]USBXHCI!Interrupter_WdfEvtInterruptDpc+0x759[/COLOR]
06 fffff802`c44c3920 fffff802`c2862687 nt!KiExecuteAllDpcs+0x289
07 fffff802`c44c3a70 fffff802`c293ffda nt!KiRetireDpcList+0xe7
08 fffff802`c44c3c60 00000000`00000000 nt!KiIdleLoop+0x5a

At a glance it looks to be doing something USB related right? XHCI crash.

Digging deeper we can look at other threads on the system

Code:

0: kd> !thread ffffe001cd3f5040
THREAD ffffe001cd3f5040  Cid 0004.00f8  Teb: 0000000000000000 Win32Thread: 0000000000000000 WAIT: (Executive) KernelMode Non-Alertable
    ffffd00020b9bdb0  NotificationEvent
IRP List:
   [COLOR=#ff0000] ffffe001ce52b720: [/COLOR](0006,06b8) Flags: 00060000  Mdl: 00000000
Not impersonating
DeviceMap                 ffffc0002b2180a0
Owning Process            ffffe001cba64700       Image:         System
Attached Process          N/A            Image:         N/A
Wait Start TickCount      412            Ticks: 0
Context Switch Count      990            IdealProcessor: 1             
UserTime                  00:00:00.000
KernelTime                00:00:00.250
Win32 Start Address nt!ExpWorkerThread (0xfffff802c284f100)
Stack Init ffffd00020b9cc90 Current ffffd00020b9b930
Base ffffd00020b9d000 Limit ffffd00020b97000 Call 0
Priority 13 BasePriority 12 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for lvuvc64.sys - 

Child-SP          RetAddr           : Args to Child                                                           : Call Site
ffffd000`20b9b970 fffff802`c2868fcf : 00000000`00000000 ffffe001`cd3f5140 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x76
ffffd000`20b9bab0 fffff802`c2868aa3 : ffffe001`cd3f5040 ffffe001`cd3f5180 fffff6fb`74000828 fffff6fb`00000000 : nt!KiSwapThread+0x15f
ffffd000`20b9bb70 fffff802`c2868727 : ffffe001`00000000 fffff802`c2eba1e5 ffffe001`000000b4 00000000`00000000 : nt!KiCommitThreadWait+0x153
ffffd000`20b9bc10 fffff802`c2eca2ea : ffffd000`20b9bdb0 00000000`00000000 ffffd000`20b9be00 ffffe001`00000002 : nt!KeWaitForSingleObject+0x387
ffffd000`20b9bcc0 fffff802`c2ec9876 : ffffd000`20b9bdb0 ffffe001`ce52b720 beeffeed`01233210 00000000`00000103 : nt!ViKeWaitForSingleObjectCommon+0x92
ffffd000`20b9bd10 fffff801`8ef4dfef : ffffd000`20b9bdb0 ffffe001`ce52b720 ffffe001`ce4e5738 00000000`00000c00 : nt!VerifierKeWaitForSingleObject+0x1e
ffffd000`20b9bd50 fffff801`8ef4e981 : ffffffff`fd050f80 ffffcf80`55ec2f60 ffffe001`ce4f8c00 00000000`0000000c : [COLOR=#ff0000]lvuvc64!calloc+0x2d6a3[/COLOR]
ffffd000`20b9be30 fffff801`8ef4ed4a : 00000000`c0000001 beeffeed`01233210 ffffcf80`55ebef01 fffff801`8f50b9a0 : lv[COLOR=#ff0000]uvc64!calloc+0x2e035[/COLOR]
ffffd000`20b9beb0 fffff801`8ef4cc2f : fffff801`00000005 00000000`c0000001 ffff32dc`fb7841a4 00000000`00000000 : [COLOR=#ff0000]lvuvc64!calloc+0x2e3fe[/COLOR]
ffffd000`20b9bf60 fffff801`8ef5ee30 : ffffcf80`54cf8f00 fffff801`8b055c88 00000000`00000000 00000000`00000000 : [COLOR=#ff0000]lvuvc64!calloc+0x2c2e3[/COLOR]
ffffd000`20b9bfb0 fffff801`8ef757d5 : 00000000`c0000001 fffff801`8ef612e2 ffffcf80`55ebefe0 ffffcf80`54cf8f80 : [COLOR=#ff0000]lvuvc64!calloc+0x3e4e4[/COLOR]
ffffd000`20b9bfe0 fffff801`8ef739d4 : 00000000`00000001 ffffcf80`55ebefe0 ffffcf80`54cf6ea0 00000000`00000002 : [COLOR=#ff0000]lvuvc64!cvSetErrMode+0x21cd[/COLOR]
ffffd000`20b9c040 fffff801`8ef748c3 : 00000000`00000000 00000000`00000002 ffffcf80`55ebcfe8 ffffffff`800004bc : [COLOR=#ff0000]lvuvc64!cvSetErrMode+0x3cc[/COLOR]
ffffd000`20b9c0c0 fffff801`8ef36475 : ffffcf80`55ebcfe0 00000000`00000000 00000000`00000000 ffffe001`ce4f6040 : [COLOR=#ff0000]lvuvc64!cvSetErrMode+0x12bb[/COLOR]
ffffd000`20b9c130 fffff801`8ef37e43 : ffffe001`ce4f6001 ffffe001`ce4f6000 beeffeed`01233210 00000000`00000000 : [COLOR=#ff0000]lvuvc64!calloc+0x15b29[/COLOR]
ffffd000`20b9c1c0 fffff801`8ef38239 : ffffe001`00000001 fffff801`8f000003 ffffe001`ce4f6040 00000000`00000000 : [COLOR=#ff0000]lvuvc64!calloc+0x174f7[/COLOR]
ffffd000`20b9c260 fffff801`8ef205f1 : ffffe001`ce4e5738 ffffe001`ce526180 ffffe001`ce4f6040 00000000`00000000 : [COLOR=#ff0000]lvuvc64!calloc+0x178ed[/COLOR]
ffffd000`20b9c2f0 fffff801`8ed8b568 : ffffe001`ce4e5670 ffffe001`ce4e5738 ffffd000`20b9c530 ffffc000`2bbdf800 : [COLOR=#ff0000]lvuvc64+0x5f1[/COLOR]
ffffd000`20b9c320 fffff801`8ed82334 : ffffe001`ce526180 ffffe001`ce4e5b20 ffffe001`ce4e5670 fffff802`c2c0580a : ks!CKsDevice::PnpStart+0x8794
ffffd000`20b9c370 fffff801`8ef616c4 : ffffe001`ce526180 ffffe001`ce5267f0 ffffd000`20b9c590 ffff32dc`fb783cd4 : ks!CKsDevice::DispatchPnp+0x104
ffffd000`20b9c3e0 fffff801`8b05e030 : fffff801`8ef61618 ffffd000`20b9c440 ffffe001`ce4e5b20 ffffe001`ce526180 : [COLOR=#ff0000]lvuvc64!calloc+0x40d78[/COLOR]
ffffd000`20b9c410 fffff802`c2eb7eb6 : ffffe001`ce526180 ffffe001`ce4e5b20 00000000`00000000 ffffd000`00000086 : VerifierExt!xdv_IRP_MJ_PNP_wrapper+0xe0
ffffd000`20b9c470 fffff802`c2858ff2 : ffffe001`ce526180 ffffd000`20b9c540 ffffe001`ce526838 ffffe001`ce4aa640 : nt!IovCallDriver+0x252
ffffd000`20b9c4b0 fffff801`8cd514b1 : 00000000`00000017 fffff802`00000003 fffff802`c2822700 fffff802`c2c2013a : nt!IofCallDriver+0x72
ffffd000`20b9c4f0 fffff802`c2eb7eb6 : ffffe001`ce526180 ffffe001`ce4e6060 00000000`00000000 ffffe001`ce4a4580 : ksthunk!CKernelFilterDevice::DispatchIrp+0xf9
ffffd000`20b9c550 fffff802`c2858ff2 : ffffe001`ce526180 ffffd000`20b9c6b0 ffffe001`ce4e6060 ffffe001`ce4a4580 : nt!IovCallDriver+0x252
ffffd000`20b9c590 fffff802`c2c201e9 : ffffe001`ce4e3060 ffffd000`20b9c6b0 ffffe001`ce4e6060 ffffe001`ce4e3060 : nt!IofCallDriver+0x72
ffffd000`20b9c5d0 fffff802`c2822c68 : ffffe001`ce4e3060 00000000`00000000 ffffe001`ce5268e0 00000000`00000000 : nt!PnpAsynchronousCall+0xe5
ffffd000`20b9c610 fffff802`c2822790 : 00000000`00000000 ffffe001`ce4e3060 fffff802`c28227c4 fffff802`c28227c4 : nt!PnpSendIrp+0x54
ffffd000`20b9c680 fffff802`c2c1f4f7 : ffffe001`ce4e2880 ffffe001`ce5268e0 00000000`00000000 00000000`00000000 : nt!PnpStartDevice+0x88
ffffd000`20b9c710 fffff802`c2c1f153 : ffffe001`ce4e2880 ffffd000`20b9c8e0 00000000`00000000 ffffe001`ce4e2880 : nt!PnpStartDeviceNode+0xdb
ffffd000`20b9c7a0 fffff802`c2c08162 : ffffe001`ce4e2880 00000000`00000001 00000000`00000001 ffffe001`cbba3d30 : nt!PipProcessStartPhase1+0x53
ffffd000`20b9c7e0 fffff802`c2bfe745 : ffffe001`ce3effb0 ffffd000`20b9cb19 ffffe001`ce322490 00000000`00000000 : nt!PipProcessDevNodeTree+0x402
ffffd000`20b9ca60 fffff802`c28eb802 : 00000001`00000003 00000000`00000000 00000000`00000000 00000000`32706e50 : nt!PiProcessReenumeration+0xa1
ffffd000`20b9cab0 fffff802`c284f1e9 : ffffe001`cd3f5040 fffff802`c2af8dc0 fffff802`c2b97340 ffffe001`cdd3d8e8 : nt!PnpDeviceActionWorker+0x166
ffffd000`20b9cb80 fffff802`c2807d85 : 00000005`bd9bbfff 00000000`00000080 ffffe001`cba64700 ffffe001`cd3f5040 : nt!ExpWorkerThread+0xe9
ffffd000`20b9cc10 fffff802`c2942366 : ffffd000`251ce180 ffffe001`cd3f5040 fffff802`c2807d44 00000000`00000000 : nt!PspSystemThreadStartup+0x41
ffffd000`20b9cc60 00000000`00000000 : ffffd000`20b9d000 ffffd000`20b97000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
0: kd> !irp ffffe001ce52b720
Irp is active with 20 stacks 17 is current (= 0xffffe001ce52bc70)
 No Mdl: No System Buffer: Thread ffffe001cd3f5040:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    
   Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    
   Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    
   Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    
   Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    
   Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    
   Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    
   Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    
   Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    
   Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    
   Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    
   Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    
   Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    
   Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    
   Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    
   Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    
   Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_INTERNAL_DEVICE_CONTROL(f), N/A(0)]
            0  1 ffffe001ce3551f0 00000000 00000000-00000000    [COLOR=#ff0000]pending[/COLOR]
    [COLOR=#ff0000]    \Driver\USBXHCI[/COLOR]
   Args: ffffcf8055ec2f60 00000000 00220003 ffffe001ce4e14e0
 [IRP_MJ_INTERNAL_DEVICE_CONTROL(f), N/A(0)]
            0 e0 ffffe001ce3fae20 00000000 00000000-00000000    
        [COLOR=#ff0000]\Driver\USBXHCI[/COLOR]
   Args: ffffcf8055ec2f60 00000000 00220003 ffffe001ce4e14e0
 [IRP_MJ_INTERNAL_DEVICE_CONTROL(f), N/A(0)]
            0 e1 ffffe001ce3fae20 00000000 00000000-00000000    [COLOR=#ff0000]pending[/COLOR]
       [COLOR=#ff0000] \Driver\USBXHCI[/COLOR]
   Args: ffffcf8055ec2f60 00000000 00220003 ffffe001ce4e14e0
 [IRP_MJ_INTERNAL_DEVICE_CONTROL(f), N/A(0)]
            0 e0 ffffe001ce4c0380 00000000 fffff8018ef6284c-ffffd00020b9bdb0 Success Error Cancel 
       Page 104099 not present in the dump file. Type ".hh dbgerr004" for details
*** ERROR: Module load completed but symbols could not be loaded for ctxusbm.sys
[COLOR=#ff0000] \Driver\USBHUB3 lvuvc64!calloc[/COLOR]
   Args: ffffcf8055ec2f60 00000000 00220003 ffffe001ce4e14e0

Lets take a look at the memory referenced

Code:

Arg1: ffffcf8054cf8fc0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8018e00f82b, address which referenced memory

0: kd> !pte ffffcf8054cf8fc0
                                           VA ffffcf8054cf8fc0
PXE at FFFFF6FB7DBEDCF8    PPE at FFFFF6FB7DB9F008    PDE at FFFFF6FB73E01530    PTE at FFFFF6E7C02A67C0
contains 0000000004D18863  contains 0000000100017863  contains 0000000100131863  contains 800000010A7B9882
pfn 4d18      ---DA--KWEV  pfn 100017    ---DA--KWEV  pfn 100131    ---DA--KWEV  [COLOR=#ff0000]not valid[/COLOR]
                                                                                  Transition: 10a7b9
                                                                                  Protect: 4 - ReadWrite

0: kd> !pool ffffcf80`54cf8fc0 
Pool page ffffcf8054cf8fc0 region is [COLOR=#ff0000]Special pool[/COLOR]
ffffcf8054cf8000: Unable to get nt!_POOL_HEADER

ffffcf80`54cf7fc0  ???????? ???????? ???????? ????????  ????????????????
ffffcf80`54cf7fd0  ???????? ???????? ???????? ????????  ????????????????
ffffcf80`54cf7fe0  ???????? ???????? ???????? ????????  ????????????????
ffffcf80`54cf7ff0  ???????? ???????? ???????? ????????  ????????????????
ffffcf80`54cf8000  009dc080 6d61434c 00000000 00000000  ....[COLOR=#ff0000]LCam[/COLOR]........
ffffcf80`54cf8010  ce4e8b40 ffffe001 9d9d9d9d 9d9d9d9d  @.N.............
ffffcf80`54cf8020  9d9d9d9d 9d9d9d9d 9d9d9d9d 9d9d9d9d  ................
ffffcf80`54cf8030  9d9d9d9d 9d9d9d9d 9d9d9d9d 9d9d9d9d  ................

So lets see what modules should be using this pool tag.

Code:

!for_each_module ".echo @#ModuleName; s-a @#Base @#End \"LCam\""
..
[COLOR=#ff0000]lvuvc64[/COLOR]
fffff801`8ef61002  4c 43 61 6d 48 89 7c 24-20 ff 15 4f 7f 4e 00 66  LCamH.|$ ..O.N.f
fffff801`8ef6102b  4c 43 61 6d 48 89 7c 24-20 ff 15 8e 7e 4e 00 83  LCamH.|$ ...~N..
fffff801`8ef61212  4c 43 61 6d 8b ce ff 15-2a 7e 4e 00 48 8b d8 49  LCam....*~N.H..I
fffff801`8ef92a17  4c 43 61 6d ff 15 27 66-4b 00 33 d2 48 8b c8 48  LCam..'fK.3.H..H
fffff801`8f50afa8  4c 43 61 6d 20 00 00 00-88 92 eb c2 02 f8 ff ff  LCam ...........
fffff801`8f50b028  4c 43 61 6d 40 00 00 00-88 92 eb c2 02 f8 ff ff  LCam@...........
fffff801`8f50b0a8  4c 43 61 6d 60 00 00 00-88 92 eb c2 02 f8 ff ff  LCam`...........
fffff801`8f50b128  4c 43 61 6d 80 00 00 00-88 92 eb c2 02 f8 ff ff  LCam............
fffff801`8f50b1a8  4c 43 61 6d a0 00 00 00-88 92 eb c2 02 f8 ff ff  LCam............
fffff801`8f50b228  4c 43 61 6d c0 00 00 00-88 92 eb c2 02 f8 ff ff  LCam............
fffff801`8f50b2a8  4c 43 61 6d e0 00 00 00-88 92 eb c2 02 f8 ff ff  LCam............
fffff801`8f50b328  4c 43 61 6d 00 01 00 00-88 92 eb c2 02 f8 ff ff  LCam............
fffff801`8f50b3a8  4c 43 61 6d 20 01 00 00-88 92 eb c2 02 f8 ff ff  LCam ...........
fffff801`8f50b428  4c 43 61 6d 40 01 00 00-88 92 eb c2 02 f8 ff ff  LCam@...........
fffff801`8f50b4a8  4c 43 61 6d 20 00 00 00-88 92 eb c2 02 f8 ff ff  LCam ...........
fffff801`8f50b528  4c 43 61 6d 40 00 00 00-88 92 eb c2 02 f8 ff ff  LCam@...........
fffff801`8f50b5a8  4c 43 61 6d 60 00 00 00-88 92 eb c2 02 f8 ff ff  LCam`...........
fffff801`8f50b628  4c 43 61 6d 80 00 00 00-88 92 eb c2 02 f8 ff ff  LCam............
fffff801`8f50b6a8  4c 43 61 6d a0 00 00 00-88 92 eb c2 02 f8 ff ff  LCam............
fffff801`8f50b728  4c 43 61 6d c0 00 00 00-88 92 eb c2 02 f8 ff ff  LCam............
fffff801`8f50b7a8  4c 43 61 6d e0 00 00 00-88 92 eb c2 02 f8 ff ff  LCam............
fffff801`8f50b828  4c 43 61 6d 00 01 00 00-88 92 eb c2 02 f8 ff ff  LCam............
fffff801`8f50b8a8  4c 43 61 6d 20 01 00 00-88 92 eb c2 02 f8 ff ff  LCam ...........
fffff801`8f50b928  4c 43 61 6d 40 01 00 00-88 92 eb c2 02 f8 ff ff  LCam@...........
..
[COLOR=#ff0000]lvrs64[/COLOR]
fffff801`8f570593  4c 43 61 6d 49 8b d5 33-c9 4c 89 30 4c 89 70 08  LCamI..3.L.0L.p.
fffff801`8f5705fd  4c 43 61 6d 49 8b d5 33-c9 44 89 70 10 44 89 70  LCamI..3.D.p.D.p
fffff801`8f573caa  4c 43 61 6d ff 15 64 8f-03 00 48 8b d8 48 85 db  LCam..d...H..H..
fffff801`8f57840f  4c 43 61 6d 48 89 74 24-20 ff 15 2a 48 03 00 66  LCamH.t$ ..*H..f
fffff801`8f578438  4c 43 61 6d 48 89 74 24-20 ff 15 11 48 03 00 83  LCamH.t$ ...H...
fffff801`8f5b60e8  4c 43 61 6d 20 00 00 00-88 92 eb c2 02 f8 ff ff  LCam ...........
fffff801`8f5b6168  4c 43 61 6d 40 00 00 00-88 92 eb c2 02 f8 ff ff  LCam@...........
fffff801`8f5b61e8  4c 43 61 6d 60 00 00 00-88 92 eb c2 02 f8 ff ff  LCam`...........
fffff801`8f5b6268  4c 43 61 6d 80 00 00 00-88 92 eb c2 02 f8 ff ff  LCam............
fffff801`8f5b62e8  4c 43 61 6d a0 00 00 00-88 92 eb c2 02 f8 ff ff  LCam............
fffff801`8f5b6368  4c 43 61 6d c0 00 00 00-88 92 eb c2 02 f8 ff ff  LCam............
fffff801`8f5b63e8  4c 43 61 6d e0 00 00 00-88 92 eb c2 02 f8 ff ff  LCam............
fffff801`8f5b6468  4c 43 61 6d 00 01 00 00-88 92 eb c2 02 f8 ff ff  LCam............
fffff801`8f5b64e8  4c 43 61 6d 20 01 00 00-88 92 eb c2 02 f8 ff ff  LCam ...........
fffff801`8f5b6568  4c 43 61 6d 40 01 00 00-88 92 eb c2 02 f8 ff ff  LCam@...........
fffff801`8f5b66a8  4c 43 61 6d 20 00 00 00-88 92 eb c2 02 f8 ff ff  LCam ...........
fffff801`8f5b6728  4c 43 61 6d 40 00 00 00-88 92 eb c2 02 f8 ff ff  LCam@...........
fffff801`8f5b67a8  4c 43 61 6d 60 00 00 00-88 92 eb c2 02 f8 ff ff  LCam`...........
fffff801`8f5b6828  4c 43 61 6d 80 00 00 00-88 92 eb c2 02 f8 ff ff  LCam............
fffff801`8f5b68a8  4c 43 61 6d a0 00 00 00-88 92 eb c2 02 f8 ff ff  LCam............
fffff801`8f5b6928  4c 43 61 6d c0 00 00 00-88 92 eb c2 02 f8 ff ff  LCam............
fffff801`8f5b69a8  4c 43 61 6d e0 00 00 00-88 92 eb c2 02 f8 ff ff  LCam............
fffff801`8f5b6a28  4c 43 61 6d 00 01 00 00-88 92 eb c2 02 f8 ff ff  LCam............
fffff801`8f5b6aa8  4c 43 61 6d 20 01 00 00-88 92 eb c2 02 f8 ff ff  LCam ...........
fffff801`8f5b6b28  4c 43 61 6d 40 01 00 00-88 92 eb c2 02 f8 ff ff  LCam@...........
..

That is the reasoning behind why I mentioned that device. Should be simple enough to disconnect it and remove any software related to it and see if it resolved the problem.

Jared · Mar 29, 2016

Re: BSOD Critical Structure Corruption - Windows 10 x64

What appears to have happened, from the best I can do with this dump file given it is still only a Kernel dump, is that an IRP was sent from the Logitech Webcam down the driver stack of the USB parent driver, and then the USB 3.0 host controller. The IRP was changing the power state of this device, and incurred a page fault at Dispatch IRQL, a big no no.

Code:

0: kd> !irp ffffe001ce52b720
Irp is active with 20 stacks 17 is current (= 0xffffe001ce52bc70)
 No Mdl: No System Buffer: Thread ffffe001cd3f5040:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_INTERNAL_DEVICE_CONTROL(f), N/A(0)]                                      //IRP is pending here
            0  1 ffffe001ce3551f0 00000000 00000000-00000000    pending
	       \Driver\USBXHCI
			Args: ffffcf8055ec2f60 00000000 00220003 ffffe001ce4e14e0
 [IRP_MJ_INTERNAL_DEVICE_CONTROL(f), N/A(0)]
            0 e0 ffffe001ce3fae20 00000000 00000000-00000000    
	       \Driver\USBXHCI
			Args: ffffcf8055ec2f60 00000000 00220003 ffffe001ce4e14e0
 [IRP_MJ_INTERNAL_DEVICE_CONTROL(f), N/A(0)]
            0 e1 ffffe001ce3fae20 00000000 00000000-00000000    pending
	       \Driver\USBXHCI
			Args: ffffcf8055ec2f60 00000000 00220003 ffffe001ce4e14e0
 [IRP_MJ_INTERNAL_DEVICE_CONTROL(f), N/A(0)]
            0 e0 ffffe001ce4c0380 00000000 fffff8018ef6284c-ffffd00020b9bdb0 Success Error Cancel 
	      Page 104099 not present in the dump file. Type ".hh dbgerr004" for details
 \Driver\USBHUB3	lvuvc64!calloc
			Args: ffffcf8055ec2f60 00000000 00220003 ffffe001ce4e14e0

0: kd> !devstack ffffe001ce4e5b20
  !DevObj           !DrvObj            !DevExt           ObjectName
  ffffe001ce4e6060  \Driver\ksthunk    ffffe001ce4e61b0  00000049
> ffffe001ce4e5b20  \Driver\LVUVC64    ffffe001ce4e5c90  
  ffffe001ce4e3060  \Driver\usbccgp    ffffe001ce4e31b0  00000047
!DevNode ffffe001ce4e2880 :
  DeviceInst is "USB\VID_046D&PID_09A1&MI_00\7&12e6e5da&0&0000"
  ServiceName is "LVUVC64" // Logitech USB camera

0: kd> !devstack ffffe001ce4c0380
  !DevObj           !DrvObj            !DevExt           ObjectName
  ffffe001ce4cb060  \Driver\usbccgp    ffffe001ce4cb1b0  00000046
> ffffe001ce4c0380  \Driver\USBHUB3    ffffe001ce4bf850  USBPDO-9
!DevNode ffffe001ce4c4010 :
  DeviceInst is "USB\VID_046D&PID_09A1\B5471720"
  ServiceName is "usbccgp" //USB generic parent driver

0: kd> !drvobj \Driver\USBHUB3 //USB 3.0 hub driver object
Driver object (ffffe001ce776ac0) is for:
 \Driver\USBHUB3
Driver Extension List: (id , addr)
(fffff8018b13e0b0 ffffe001cf247150)  
Device Object list:
ffffe001ce530060  ffffe001ce52b060  ffffe001ce4c6e20  ffffe001ce4c0380
ffffe001ce4bee20  ffffe001ce422310  ffffe001ceed5cb0  ffffe001ceec5d50
ffffe001ceed6060  ffffe001cf3eba00  //All the attached devices, including the USB 3.0 Host Controller

//Memory referenced

0: kd> !pte ffffcf8054cf8fc0
                                           VA ffffcf8054cf8fc0
PXE at FFFFF6FB7DBEDCF8    PPE at FFFFF6FB7DB9F008    PDE at FFFFF6FB73E01530    PTE at FFFFF6E7C02A67C0
contains 0000000004D18863  contains 0000000100017863  contains 0000000100131863  contains 800000010A7B9882
pfn 4d18      ---DA--KWEV  pfn 100017    ---DA--KWEV  pfn 100131    ---DA--KWEV  not valid
                                                                                  Transition: 10a7b9 //Transition page, meaning it is still valid, but paged out from the working set
                                                                                  Protect: 4 - ReadWrite

0: kd> !pfn 10a7b9
    PFN 0010A7B9 at address FFFFFA80031F72B0
    flink       0010B6B3  blink / share count 000034BE  pteaddress FFFFF6E7C02A67C0
nt!_MMPFNENTRY type not found
    reference count 0000    used entry count  0000      NonCached color 0   Priority 0
    restore pte 00000080  containing page        100131  nt!_MMPFNENTRY type not found //Not exactly helpful

0: kd> knL
  *** Stack trace for last set context - .thread/.cxr resets it
 # Child-SP          RetAddr           Call Site
00 ffffd000`20b9b970 fffff802`c2868fcf nt!KiSwapContext+0x76
01 ffffd000`20b9bab0 fffff802`c2868aa3 nt!KiSwapThread+0x15f
02 ffffd000`20b9bb70 fffff802`c2868727 nt!KiCommitThreadWait+0x153
03 ffffd000`20b9bc10 fffff802`c2eca2ea nt!KeWaitForSingleObject+0x387
04 ffffd000`20b9bcc0 fffff802`c2ec9876 nt!ViKeWaitForSingleObjectCommon+0x92
05 ffffd000`20b9bd10 fffff801`8ef4dfef nt!VerifierKeWaitForSingleObject+0x1e
06 ffffd000`20b9bd50 fffff801`8ef4e981 lvuvc64!calloc+0x2d6a3
07 ffffd000`20b9be30 fffff801`8ef4ed4a lvuvc64!calloc+0x2e035
08 ffffd000`20b9beb0 fffff801`8ef4cc2f lvuvc64!calloc+0x2e3fe
09 ffffd000`20b9bf60 fffff801`8ef5ee30 lvuvc64!calloc+0x2c2e3
0a ffffd000`20b9bfb0 fffff801`8ef757d5 lvuvc64!calloc+0x3e4e4
0b ffffd000`20b9bfe0 fffff801`8ef739d4 lvuvc64!cvSetErrMode+0x21cd
0c ffffd000`20b9c040 fffff801`8ef748c3 lvuvc64!cvSetErrMode+0x3cc
0d ffffd000`20b9c0c0 fffff801`8ef36475 lvuvc64!cvSetErrMode+0x12bb
0e ffffd000`20b9c130 fffff801`8ef37e43 lvuvc64!calloc+0x15b29
0f ffffd000`20b9c1c0 fffff801`8ef38239 lvuvc64!calloc+0x174f7
10 ffffd000`20b9c260 fffff801`8ef205f1 lvuvc64!calloc+0x178ed
11 ffffd000`20b9c2f0 fffff801`8ed8b568 lvuvc64+0x5f1
Page 102418 not present in the dump file. Type ".hh dbgerr004" for details
12 ffffd000`20b9c320 fffff801`8ed82334 ks!CKsDevice::PnpStart+0x8794
Page 102418 not present in the dump file. Type ".hh dbgerr004" for details
Page 10248f not present in the dump file. Type ".hh dbgerr004" for details
13 ffffd000`20b9c370 fffff801`8ef616c4 ks!CKsDevice::DispatchPnp+0x104
Page 10248f not present in the dump file. Type ".hh dbgerr004" for details
14 ffffd000`20b9c3e0 fffff801`8b05e030 lvuvc64!calloc+0x40d78
15 ffffd000`20b9c410 fffff802`c2eb7eb6 VerifierExt!xdv_IRP_MJ_PNP_wrapper+0xe0
16 ffffd000`20b9c470 fffff802`c2858ff2 nt!IovCallDriver+0x252
17 ffffd000`20b9c4b0 fffff801`8cd514b1 nt!IofCallDriver+0x72
18 ffffd000`20b9c4f0 fffff802`c2eb7eb6 ksthunk!CKernelFilterDevice::DispatchIrp+0xf9
19 ffffd000`20b9c550 fffff802`c2858ff2 nt!IovCallDriver+0x252
1a ffffd000`20b9c590 fffff802`c2c201e9 nt!IofCallDriver+0x72
1b ffffd000`20b9c5d0 fffff802`c2822c68 nt!PnpAsynchronousCall+0xe5
1c ffffd000`20b9c610 fffff802`c2822790 nt!PnpSendIrp+0x54
1d ffffd000`20b9c680 fffff802`c2c1f4f7 nt!PnpStartDevice+0x88
1e ffffd000`20b9c710 fffff802`c2c1f153 nt!PnpStartDeviceNode+0xdb
1f ffffd000`20b9c7a0 fffff802`c2c08162 nt!PipProcessStartPhase1+0x53
20 ffffd000`20b9c7e0 fffff802`c2bfe745 nt!PipProcessDevNodeTree+0x402
21 ffffd000`20b9ca60 fffff802`c28eb802 nt!PiProcessReenumeration+0xa1
22 ffffd000`20b9cab0 fffff802`c284f1e9 nt!PnpDeviceActionWorker+0x166
23 ffffd000`20b9cb80 fffff802`c2807d85 nt!ExpWorkerThread+0xe9
24 ffffd000`20b9cc10 fffff802`c2942366 nt!PspSystemThreadStartup+0x41
25 ffffd000`20b9cc60 00000000`00000000 nt!KiStartSystemThread+0x16


Irp worker threads (PopIrpThreadList - fffff802c2add0c0)
  THREAD: ffffe001cbb05040 (static)
  THREAD: ffffe001cbb04040 (static)


//The thread we saw was indeed an IRP worker thread.

0: kd> !podev ffffe001ce4e5b20
Device object is for:
  DriverObject ce4db930
Current Irp 00000000 RefCount 0 Type 0000002f AttachedDev ffffe001ce4e6060 DevFlags 00002000  DO_POWER_PAGABLE //IRP flag indicating the device is pagable
Device queue is not busy.
Device Object Extension: ffffe001ce4e5c98:
PowerFlags: 00000000 =>SystemState=0 DeviceState=0
Dope: 00000000:

The device tried to access pagable memory at IRQL 2.
Pretty common bug for a driver to not take into account interrupt levels properly.

jcgriff2 · Mar 29, 2016

Re: BSOD Critical Structure Corruption - Windows 10 x64

This driver? --> Driver Reference Table - USBXHCI.sys

Jared · Mar 29, 2016

Re: BSOD Critical Structure Corruption - Windows 10 x64

That's the USB 3.0 Host Controller.
The IRP passed from the Logitech driver is at fault, not the host controller.

RepairandRestore · Mar 29, 2016

Re: BSOD Critical Structure Corruption - Windows 10 x64

Sorry to intrude =)

Recently I faced such problem the solution I applied was to use was removing all conflicts drivers with this tool which is integrated in Windows and is called a "Verifier" .

Here is the procedure.

PLEASE WAIT THE FEEDBACK FROM THE OTHER MEMBERS WORKING ON THIS ISSUE BEFORE YOU APPLY THE PROCEDURE.

this was worked for similar problem but still in your case the solution might be different this is just a suggestion.

Many thanks,
Andy

jcgriff2 · Mar 29, 2016

Re: BSOD Critical Structure Corruption - Windows 10 x64

RepairandRestore said:
Sorry to intrude =)

Recently I faced such problem the solution I applied was to use was removing all conflicts drivers with this tool which is integrated in Windows and is called a "Verifier" .

Here is the procedure.

Driver Verifier doesn't fix anything on its own. It subjects 3rd party drivers to a variety of stresses and tests to find improper behavior.

https://www.sysnative.com/forums/bs...er-bsod-related-windows-10-8-1-8-7-vista.html

Regards. . .

jcgriff2

Jared · Mar 29, 2016

Re: BSOD Critical Structure Corruption - Windows 10 x64

RepairandRestore said:
Sorry to intrude =)

Recently I faced such problem the solution I applied was to use was removing all conflicts drivers with this tool which is integrated in Windows and is called a "Verifier" .

Here is the procedure.

PLEASE WAIT THE FEEDBACK FROM THE OTHER MEMBERS WORKING ON THIS ISSUE BEFORE YOU APPLY THE PROCEDURE.

this was worked for similar problem but still in your case the solution might be different this is just a suggestion.

Many thanks,
Andy

What exactly was your problem?
Driver Verifier doesn't resolve anything, but alters the way drivers behave by implementing more checks to their functions.
You probably hid a race condition, which isn't unusual for Driver Verifier to do.

RepairandRestore · Mar 29, 2016

Re: BSOD Critical Structure Corruption - Windows 10 x64

Jared said:
RepairandRestore said:

Sorry to intrude =)

Recently I faced such problem the solution I applied was to use was removing all conflicts drivers with this tool which is integrated in Windows and is called a "Verifier" .

Here is the procedure.

PLEASE WAIT THE FEEDBACK FROM THE OTHER MEMBERS WORKING ON THIS ISSUE BEFORE YOU APPLY THE PROCEDURE.

this was worked for similar problem but still in your case the solution might be different this is just a suggestion.

Many thanks,
Andy

Click to expand...

What exactly was your problem?
Driver Verifier doesn't resolve anything, but alters the way drivers behave by implementing more checks to their functions.
You probably hid a race condition, which isn't unusual for Driver Verifier to do.

Not really maybe sound strange but after Verifier and System Restore most of blue screen issues was resolved. (when drivers conflict cause blue screens)

https://support.microsoft.com/en-us/kb/244617

The Driver Verifier tool that is included in every version of Windows since Windows 2000 is used to detect and troubleshoot many driver issues that are known to cause system corruption, failures, or other unpredictable behavior. This article describes how to use Driver Verifier to isolate and troubleshoot a driver in the system.

I must disagree is not resolving anything =)

Jared · Mar 29, 2016

Re: BSOD Critical Structure Corruption - Windows 10 x64

RepairandRestore said:
Jared said:

RepairandRestore said:

Sorry to intrude =)

Recently I faced such problem the solution I applied was to use was removing all conflicts drivers with this tool which is integrated in Windows and is called a "Verifier" .

Here is the procedure.

PLEASE WAIT THE FEEDBACK FROM THE OTHER MEMBERS WORKING ON THIS ISSUE BEFORE YOU APPLY THE PROCEDURE.

this was worked for similar problem but still in your case the solution might be different this is just a suggestion.

Many thanks,
Andy

Click to expand...

What exactly was your problem?
Driver Verifier doesn't resolve anything, but alters the way drivers behave by implementing more checks to their functions.
You probably hid a race condition, which isn't unusual for Driver Verifier to do.

Click to expand...

Not really maybe sound strange but after Verifier and System Restore most of blue screen issues was resolved.

https://support.microsoft.com/en-us/kb/244617

[FONT=Segoe UI, Segoe UI Web, Segoe UI Symbol, Helvetica Neue, BBAlpha Sans, S60 Sans, Arial, sans-serif]The Driver Verifier tool that is included in every version of Windows since Windows 2000 is used to detect and troubleshoot many driver issues that are known to cause system corruption, failures, or other unpredictable behavior. This article describes how to use Driver Verifier to isolate and troubleshoot a driver in the system. [/FONT]

[FONT=Segoe UI, Segoe UI Web, Segoe UI Symbol, Helvetica Neue, BBAlpha Sans, S60 Sans, Arial, sans-serif]I must disagree is not resolving anything =) [/FONT]

It helps you find the problem, it doesn't resolve it for you.
You misunderstand the purpose of the tool.
You are wrong.

The system restore will have resolved your issue.
Please keep this topic away from this thread as it is solely for helping the OP.
If you wish to discuss this further, either PM me, or start your own thread.
Thanks.

RepairandRestore · Mar 29, 2016

Re: BSOD Critical Structure Corruption - Windows 10 x64

Jared said:
RepairandRestore said:

Jared said:

RepairandRestore said:

Sorry to intrude =)

Recently I faced such problem the solution I applied was to use was removing all conflicts drivers with this tool which is integrated in Windows and is called a "Verifier" .

Here is the procedure.

PLEASE WAIT THE FEEDBACK FROM THE OTHER MEMBERS WORKING ON THIS ISSUE BEFORE YOU APPLY THE PROCEDURE.

this was worked for similar problem but still in your case the solution might be different this is just a suggestion.

Many thanks,
Andy

Click to expand...

What exactly was your problem?
Driver Verifier doesn't resolve anything, but alters the way drivers behave by implementing more checks to their functions.
You probably hid a race condition, which isn't unusual for Driver Verifier to do.

Click to expand...

Not really maybe sound strange but after Verifier and System Restore most of blue screen issues was resolved.

https://support.microsoft.com/en-us/kb/244617

The Driver Verifier tool that is included in every version of Windows since Windows 2000 is used to detect and troubleshoot many driver issues that are known to cause system corruption, failures, or other unpredictable behavior. This article describes how to use Driver Verifier to isolate and troubleshoot a driver in the system.

I must disagree is not resolving anything =)

Click to expand...

It helps you find the problem, it doesn't resolve it for you.
You misunderstand the purpose of the tool.
You are wrong.

The system restore will have resolved your issue.
Please keep this topic away from this thread as it is solely for helping the OP.
If you wish to discuss this further, either PM me, or start your own thread.
Thanks.

Please accept my apologies

BenjiYoda · Feb 9, 2017

Re: BSOD Critical Structure Corruption - Windows 10 x64

I'm having this same problem. My computer is stuck running the perfmon... What should I send?

xilolee · Feb 10, 2017

Re: BSOD Critical Structure Corruption - Windows 10 x64

Hi BenjiYoda. :)

Please open your own topic.

We usually need the bsodcollectionapp logs and all the details about your machine (see below). Nonetheless, a piriform speccy snapshot is always welcome.
Check Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 & Vista (click).

Please provide answers for (answer the best that you can):
- System Manufacturer?
- Laptop or Desktop?
- Exact model number (if laptop, check label on bottom)
- OS ? (Windows 10, 8.1, 8, 7, Vista)
- x86 (32bit) or x64 (64bit)?
- Service pack?
- What was original installed OS on system?
- Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
- Age of system? (hardware)
- Age of OS installation?
- Have you re-installed the OS?
- CPU
- RAM (brand, model, which slots are you using?)
- Video Card
- MotherBoard - (if NOT a laptop)
- Power Supply - brand & wattage (if laptop, skip this one)
- What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth)
- Are you using proxy, vpn, ipfilters or similar software?
- Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software)
- Are you currently under/overclocking? Are there overclocking software installed on your system?

[Win10 x64] Critical Structure Corruption

LeoBloom

New member

Attachments

Jared

Sysnative Staff, BSOD Kernel Dump Expert

LeoBloom

New member

Jared

Sysnative Staff, BSOD Kernel Dump Expert

LeoBloom

New member

invalid

Member

LeoBloom

New member

invalid

Member

Jared

Sysnative Staff, BSOD Kernel Dump Expert

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Jared

Sysnative Staff, BSOD Kernel Dump Expert

RepairandRestore

Well-known member

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Jared

Sysnative Staff, BSOD Kernel Dump Expert

RepairandRestore

Well-known member

Jared

Sysnative Staff, BSOD Kernel Dump Expert

RepairandRestore

Well-known member

BenjiYoda

Member

xilolee

Moderator

[Win10 x64] Critical Structure Corruption

New member

Attachments

Sysnative Staff, BSOD Kernel Dump Expert

New member

Sysnative Staff, BSOD Kernel Dump Expert

New member

Member

New member

Member

Sysnative Staff, BSOD Kernel Dump Expert

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Sysnative Staff, BSOD Kernel Dump Expert

Well-known member

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Sysnative Staff, BSOD Kernel Dump Expert

Well-known member

Sysnative Staff, BSOD Kernel Dump Expert

Well-known member

Member

Moderator

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)