Looking To Breathe Again, Stop Turning Blue

spencerplane · Jul 5, 2020

Hey,

New to the forums and like the subject title says I need help with BSODs. I was directed to this site by satrow in a reply to a post on AskWoody.

Here are the recommended answers:

· Windows 10 1909
· x64 (64-bit)
· Windows 10 1803
· I installed Windows 10 1909 using Windows Media Creation Tool.
· I got the laptop on June 4th, 2018
· March 8th, 2020 was the most recent install of the OS.

· CPU - Intel i7 8750H
· Video Card - NVIDIA GeForce GTX 1050Ti

· System Manufacturer - ASUS
· Exact model number - ASUS ROG Strix Scar Edition GL703GE

· Laptop or Desktop? Laptop

System memory is one 16GB DDR4-2666 SO-DIMM by Samsung.
System drive is an ADATA SX8200 Pro 512GB M.2 Nvme SSD I installed in March of 2019.
Storage drive is a Seagate FireCuda 1TB OEM.

The March install of Windows was an effort to stop a run of BSODs but I was just kidding myself. It was only a few days later - BSOD. A spate of the anoying buggers last month and now, games are crashing to desktop or freezing at the most unfortunate time. I used Windows Memory Diagnostic tool and a standard test came up clean but the extended test "hung" at 21% complete on pass 1 of 2 - - for more than 12 hours. Not sure if that is an acceptable amount of time but I stopped the test since the laptop is used regularly. The attached files include three blue screens from last month.

Thank you

MrPepka · Jul 5, 2020

Check in Windows Update if there any updates of system
However, there are many indications of corrupted RAM

x BlueRobot · Jul 5, 2020

I would suggest testing your RAM using MemTest - Test RAM with PassMark MemTest86

Patrick · Jul 5, 2020

Agreed w/ all.

Code:

1: kd> .bugcheck
Bugcheck code 000001C7
Arguments 00000000`00000000 ffffa208`bbb4a000 00000000`88bb107a 00000000`00252845

1st argument tells us that a chunk heap buffer (memory management) had an invalid hash. If a hash doesn't match, the system has to bugcheck to prevent overflow exploitation.

Code:

nt!_HEAP
   +0x000 Segment          : _HEAP_SEGMENT
   +0x000 Entry            : _HEAP_ENTRY
   +0x010 SegmentSignature : 0xcd5
   +0x014 SegmentFlags     : 0
   +0x018 SegmentListEntry : _LIST_ENTRY [ 0x000011dd`077aaef9 - 0x077aaf17`c8ff90b1 ]
   +0x028 Heap             : 0xf341f423`000011ce _HEAP
   +0x030 BaseAddress      : 0x000011ce`077aaf34 Void
   +0x038 NumberOfPages    : 0xf9964084
   +0x040 FirstEntry       : 0x0f9e661a`000011b7 _HEAP_ENTRY
   +0x048 LastValidEntry   : 0x000011f1`077aaf6d _HEAP_ENTRY
   +0x050 NumberOfUnCommittedPages : 0x4a287250
   +0x054 NumberOfUnCommittedRanges : 0x77affff
   +0x058 SegmentAllocatorBackTraceIndex : 0x27e
   +0x05a Reserved         : 0
   +0x060 UCRSegmentList   : _LIST_ENTRY [ 0x0000125a`077aafb5 - 0x077aafdb`89588f37 ]
   +0x070 Flags            : 0x128b
   +0x074 ForceFlags       : 0xdad86cd9
   +0x078 CompatibilityFlags : 0x77ab004
   +0x07c EncodeFlagMask   : 0x12c5
   +0x080 Encoding         : _HEAP_ENTRY
   +0x090 Interceptor      : 0x77ab05b
   +0x094 VirtualMemoryThreshold : 0x129d
   +0x098 Signature        : 0xffc20e81
   +0x0a0 SegmentReserve   : 0xbd4c29c6`00001198
   +0x0a8 SegmentCommit    : 0x000011d1`077ab09f
   +0x0b0 DeCommitFreeBlockThreshold : 0x077ab0bd`2d84ecec
   +0x0b8 DeCommitTotalFreeThreshold : 0xce27f4da`00001162
   +0x0c0 TotalFreeSize    : 0x0000117a`077ab0d4
   +0x0c8 MaximumAllocationSize : 0x06bbb1cb`a4e118ce
   +0x0d0 ProcessHeapsListIndex : 0x1a52
   +0x0d2 HeaderValidateLength : 0
   +0x0d8 HeaderValidateCopy : 0x0000149c`06bbb181 Void
   +0x0e0 NextAvailableTagIndex : 0xa546
   +0x0e2 MaximumTagIndex  : 0xbef0
   +0x0e8 TagEntries       : 0x344b1455`00001558 _HEAP_TAG_ENTRY
   +0x0f0 UCRList          : _LIST_ENTRY [ 0x00001515`06bbb0d9 - 0x06bbb099`c4eabd55 ]
   +0x100 AlignRound       : 0x6b928342`000013f2
   +0x108 AlignMask        : 0x00001218`06bbb077
   +0x110 VirtualAllocdBlocks : _LIST_ENTRY [ 0x06bbb039`c8731a59 - 0x3e308269`000013de ]
   +0x120 SegmentList      : _LIST_ENTRY [ 0x000013b4`06bbaffd - 0x06bbafa5`bc47f685 ]
   +0x130 AllocatorBackTraceIndex : 0x1575
   +0x134 NonDedicatedListLength : 0x7a927ae0
   +0x138 BlocksIndex      : 0x0000150d`06bbaf54 Void
   +0x140 UCRIndex         : 0x077ab242`1daf9ded Void
   +0x148 PseudoTagEntries : 0xbc775e8b`0000120b _HEAP_PSEUDO_TAG_ENTRY
   +0x150 FreeLists        : _LIST_ENTRY [ 0x000014fa`077ab263 - 0x077ab2b3`f9f5de65 ]
   +0x160 LockVariable     : 0x5336afe3`000014ae _HEAP_LOCK
   +0x168 CommitRoutine    : 0x0000150a`077ab2fe     long  +150a077ab2fe
   +0x170 StackTraceInitVar : _RTL_RUN_ONCE
   +0x178 CommitLimitData  : _RTL_HEAP_MEMORY_LIMIT_DATA
   +0x198 FrontEndHeap     : 0x0000151d`06bbae1f Void
   +0x1a0 FrontHeapLockCount : 0xe69e
   +0x1a2 FrontEndHeapType : 0x88 ''
   +0x1a3 RequestedFrontEndHeapType : 0x1d ''
   +0x1a8 FrontEndHeapUsageData : 0xd9681200`00001546  "--- memory read error at address 0xd9681200`00001546 ---"
   +0x1b0 FrontEndHeapMaximumIndex : 0xad8a
   +0x1b2 FrontEndHeapStatusBitmap : [129]  "???"
   +0x238 Counters         : _HEAP_COUNTERS
   +0x2b0 TuningParameters : _HEAP_TUNING_PARAMETERS

There was a memory read error at 0x1a8.

Given that your system locked up when running memory test(s), it's more than likely faulty RAM.

spencerplane · Jul 6, 2020

Well, I got a copy of MemTest86-Pro and ran it for 12 passes and each passed with no errors. Weird.

xilolee · Jul 7, 2020

Please read CAREFULLY the following instructions:

Create a restore point
Create a system image
(macrium reflect free is a good program, if you don't already have one... Make sure to create a recovery media - i.e., a CD or a USB stick with macrium installed - and test if it works and boot your machine/pc)
Backup your important files (the files you don't want to lose)
Read the guide about Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista (click).
Read some other tutorials/guides and WARNINGS on internet.
Download and unzip on your desktop the file I attached View attachment VERIFIER.zip (you should see the driverview folder, a .bat file and a .ps1 file) and then:
1. Open an elevated command prompt (right-click on windows start button, click command prompt (admin)
2. Type (copy/paste) in it:
  Code:
```
bcdedit /export c:\DEFAULT-BCDedit-SystemStoreContent
powershell -executionpolicy unrestricted "%userprofile%\desktop\EnableVerifier.ps1"
```
3. Press enter
4. The previous commands will modify your bcdedit settings, will set the necessary driver verifier settings, will reboot your PC in three minutes (but you can reboot it before).
  It will (more precisely):
  Read More:
  - export/save your current bcdedit system store content in c:\DEFAULT-BCDedit-SystemStoreContent
  - show the current bcdedit content in "BCDoriginal.txt" (in the folder Created-by-verifier-script on your desktop)
  - change the bcdedit {bootmgr} displaybootmenu setting from No to Yes
  - change the bcdedit {bootmgr} timeout setting to 30 seconds
  - change the bcdedit bootmenupolicy setting from standard to legacy
  - show the modified bcdedit content in "BCDmodified.txt" (in the folder Created-by-verifier-script on your desktop)
  - find non-microsoft drivers and set the necessary driver verifier settings
  - restart your PC after three minutes (you can abort this with "shutdown -a" in an elevated command prompt)
  - the boot menu should appear at every restart and it should allow you to select windows advanced boot options (SAFE MODE included).
  I've added the parameter /bootmode ResetOnUnusualShutdown.
  This should reset driver verifier settings, if they should cause a BSOD.
  It should appear something like:
  
  Code:
  
  Verifier Flags: 0x0002892b Standard Flags: [X] 0x00000001 Special pool. [X] 0x00000002 Force IRQL checking. [X] 0x00000008 Pool tracking. [ ] 0x00000010 I/O verification. [X] 0x00000020 Deadlock detection. [ ] 0x00000080 DMA checking. [X] 0x00000100 Security checks. [X] 0x00000800 Miscellaneous checks. [X] 0x00020000 DDI compliance checking. Additional Flags: [ ] 0x00000004 Randomized low resources simulation. [ ] 0x00000200 Force pending I/O requests. [ ] 0x00000400 IRP logging. [ ] 0x00002000 Invariant MDL checking for stack. [ ] 0x00004000 Invariant MDL checking for driver. [X] 0x00008000 Power framework delay fuzzing. [ ] 0x00010000 Port/miniport interface checking. [ ] 0x00040000 Systematic low resources simulation. [ ] 0x00080000 DDI compliance checking (additional). [ ] 0x00200000 NDIS/WIFI verification. [ ] 0x00800000 Kernel synchronization delay fuzzing. [ ] 0x01000000 VM switch verification. [ ] 0x02000000 Code integrity checks. [X] Indicates flag is enabled. Boot Mode: ResetOnUnusualShutdown Rules: All rules are using default settings Extensions: wdm: rules.default Verified Drivers: More data is available. The system reboot is required for the changes to take effect.
5. After the reboot, open a command prompt and check if verifier settings are enabled with this command
  Code:
```
verifier /querysettings
```
  If they are enabled, let verifier run from 24 to 72 hours.
  If they are not enabled, inform us.
  If you'll get a very fast BSOD after you logged into windows, or after some dozens (tenths?) of minutes, the option ResetOnUnusualShutdown should reset driver verifier settings (and should allow you to boot your machine in a normal state)... But if this won't happen, you'll need to go to safe mode to reset verifier settings. Once safe mode is available, from an elevated command prompt you'll type:
  Code:
```
verifier /reset
```
  Sometimes it is necessary to use a system restore point (or a system image).

Post here the new verifier dump; from an elevated command prompt, launch this command:

Code:

md "%userprofile%\desktop\minidump" && copy c:\windows\minidump "%userprofile%\desktop\minidump"

spencerplane · Jul 7, 2020

Hey xilolee, thanks for the reply. The time of one to three days for verifier - does that mean the system should not be used during the test? If so it might be one to two weeks before I can schedule that much down time.

xilolee · Jul 7, 2020

You can do it whenever you prefer, but I suspect it will produce the verifier bsod in less time than predicted.

spencerplane · Jul 10, 2020

So, more weirdness. I decided to do the verifier sooner rather than later. I let it run for 24 hours and no BSOD. I got the verifier.zip file and followed the instructions. Everything worked and the query came back A-OK. I guess we're done here? I did buy new ram and will install and test it.

spencerplane · Jul 11, 2020

It was suggested on a post over at AskWoody that I should let driver verifier run for 2 days. I got it re-enabled and we'll find out if a BSOD happens come Monday.

philc43 · Jul 11, 2020

spencerplane said:
It was suggested on a post over at AskWoody that I should let driver verifier run for 2 days. I got it re-enabled and we'll find out if a BSOD happens come Monday.

That is correct, I generally advise running for 48h with Driver Verifier, using your system as you normally would. You will most likely see a performance hit because of the significant activity from Driver Verifier testing the drivers in the background.

spencerplane · Jul 13, 2020

Monday has arrived and no BSOD. Maybe chalk up last month's issues to ghosts in the machine?

The laptop has two memory slots but only one populated. I bought a two stick replacement kit and will install one at a time and run memtest86+ on each.

Search

Search

Looking To Breathe Again, Stop Turning Blue

spencerplane

Member

Attachments

MrPepka

Sysnative Staff, BSOD Kernel Dump Senior Analyst

x BlueRobot

Administrator

Patrick

Sysnative Staff

spencerplane

Member

xilolee

Moderator

spencerplane

Member

xilolee

Moderator

spencerplane

Member

spencerplane

Member

philc43

BSOD Forum Moderator, BSOD Academy Instructor, BSOD Kernel Dump Expert

spencerplane

Member