New
#41
If it doesn't crash in Safe Mode, then it's usually just a driver issue, however, looking at the most recent bugcheck it seem that the working set free list is corrupt is most likely caused by hardware.
Code:BugCheck 1A, {5003, c0802000, 6c1, 6c3d80} Probably caused by : memory_corruption ( nt!MiAllocateWsle+6f )With the second bit flag set with the extension, the free WSLEs shoud also be displayed, but since this data structure has become corrupt then this data may not be displayed.Code:0: kd> !wsle 2 Working Set @ c0802000 FirstFree 6c1 FirstDynamic 6 LastEntry 701 NextSlot 6 LastInitialized 8bd NonDirect 1f4 HashTable 0 HashTableSize 0 Reading the WSLE data .....Unable to get Wsle table block - address c0803108 - count 512 - page 0x100
Code:0: kd> dt nt!_MMWSLE c0802000 +0x000 u1 : <unnamed-tag>Interestingly, the trap frame which was caused because of an invalid assembly instruction. The call stack doesn't reveal much, because the instruction was possibly made in User-Mode.Code:0: kd> .trap a75d2d34 ErrCode = 00000006 eax=01470020 ebx=01470020 ecx=000037f1 edx=0000004c esi=76dbeef7 edi=014a1fa0 eip=76f19c9c esp=00f0f194 ebp=00f0f198 iopl=0 nv up ei pl nz na po nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010202 001b:76f19c9c ?? ???
We could try running Driver Verifier again, but with the Special Pool option enabled too. Select Individual Settings, and enable all the options, apart from Low Resources Simulation.
Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:
InformationAdditional Help - Using Driver Verifier to identify issues with Drivers