Another BSOD only on Cold Boot login (brand new PC)

Hello guys, another BSOD that happens only on boot!

I've just built a new computer, all parts are brand new.

I was having some BSOD during the boot. Then I turned off the Fast Boot option and I didn't get this BSOD anymore.

On the other hand, now I'm still facing a BSOD after logging Windows. The MEMORY_MANAGEMENT error happens only in a cold boot, a few minutes after logging in (I don't need to run anything special, just opening a Chrome browser and voi lá). After rebooting it works perfectly. Also, when it crashes, it stucks at 0%, so, I don't have a log to help understand the issue.

The tests I already did:

- Memtest86: ran twice, each of them 4 passes, and no issues were found. The free version doesn't allow me to run 8 passes as most people suggest. I tried to run Memtest86+, but my BIOS is UEFI, and I couldn't boot it.

- GPU stress test: ran FurMark (for about an hour) and Heaven Benchmark (both simple and heavy tests). None of them found issues. Also, my GPU is up-to-date with latest driver.

- HDD test: ran SeaTools on both disks and no issue was found.

- CPU: I'm running Prime95 heavy tests right now (for about 1.30h). No problems so far. How many hours should it run?

- Motherboard: updated BIOS and drivers to the last version (april/19). Problem was happening before BIOS update, and continues to happen after update.

- WiFi adapter: I started the computer without the WIFI adapter, just to make sure it wasn't faulty, but I still got the BSOD.

- Startup apps: I removed all non-windows apps on startup. Also didn't fix the problem.

I ran out of options. Can anybody help me isolate the issue, please? I still have a few days to return the faulty piece, but I

------
Spec:

AMD Ryzen 7 2700X
ZOTAC Gaming GeForce RTX 2060 Twin Fan Graphic Cards
GIGABYTE X470 AORUS Ultra Gaming
Corsair CP-9020122-NA CX Series 650 Watt 80 Plus Bronze Certified Non-Modular Power Supply
Corsair Vengeance LPX 16GB (2 X 8GB) DDR4 3000 (PC4-24000) C16 1.35V
SSD HP EX920 M.2 512GB PCIe 3.0 x4 NVMe 3D TLC NAND (for system and applications)
Seagate BarraCuda ST3000DM007 3TB 256MB Cache SATA 6.0Gb/s 3.5"
WISE TIGER Wifi Adapter Ac 600Mbps

- - - Updated - - -

I was checking again the Event View, and it says that the

Event is 41
BugcheckCode is 26 (0x1a)
BugcheckParameter1 is 0x41792 ("A corrupted PTE has been detected. Parameter 2 contains the address of the PTE. Parameters 3/4 contain the low/high parts of the PTE.").
BugcheckParameter2 0x0
BugcheckParameter3 0x0
BugcheckParameter4 0x0

I've already enabled the driver check profile, but I'm running the PC after the BSOD (so, no errors after the cold boot). Maybe tomorrow morning, when I turn on the PC again, I will have the driver test result?

Hi skimi,

Welcome to the BSOD forum.

1) The logs were in a foreign language.
Change the default language to English so the logs can be scanned and read.

Add, Remove, and Change Display Language in Windows 10 | Tutorials

2) There were no mini dump files collected.

3) Windows driver verifier is still on.
Turn off the tool.
Enable and Disable Driver Verifier in Windows 10 | Tutorials

4) Download and install: Everything
voidtools

5) Use Everything to search for: PoW32kWatchdog-20190424-2157.dmp

6) Zip the file and post a share link into the thread using one drive, drop box, or google drive.

Code:

Name                             LastWriteTime       Size (MB)
----                             -------------       ---------
PoW32kWatchdog-20190424-2157.dmp 24/04/2019 21:57:11   1570,11

7) If there are any spontaneous BSOD:
a) immediately run the BETA log collector and upload the results into the thread
b) search for: c:\windows\memory.dmp > if the file size is < 1.5 GB the zip and post a seprate share link into the thread



8) Open administrative command prompt and type or copy and paste:
9) sfc /scannow
10) dism /online /cleanup-image /restorehealth
11) chkdsk /scan
12) wmic recoveros set autoreboot = false
13) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

14) Make sure that there is no over clocking while troubleshooting.

15) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

Hi zbook, thanks for your time.

1) Switched to English and attached a new scan.

2) Yes, no minidumps were found in folder. Should I have it? The BSOD is stuck at 0% all the time, so I wasn't created.

3) I had turned on to try to test drivers. But I've turned off again.

4-6) Done. The PoW32kWatchdog-20190424-2157.dmp is at https://drive.google.com/open?id=1z6...-kLyuCZnZAY4At

I believe this dump was generated during a startup BSOD, before I turned Fast Boot off. Maybe it gives some clue on how to fix that issue, but I don't think it's related to the BSOD after login.

7.a) OK, will do that. Tomorrow morning, when PC is cold again, I should be able to see the BSOD again.

7.b) I had a MEMORY.dmp, but I think Windows got rid of it. I analyzed with WinDbg, and it was related to the start BSOD, that would happen the first time I booted the PC - same behavior as now, with the computer working fine after reboot.

8-13)

Microsoft Windows [Version 10.0.17763.475]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.475

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
498432 file records processed.
File verification completed.
9775 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
435 reparse records processed.
670134 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
435 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
85852 data files processed.
CHKDSK is verifying Usn Journal...
38797056 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

499476479 KB total disk space.
82850584 KB in 402510 files.
230032 KB in 85853 indexes.
0 KB in bad sectors.
621151 KB in use by the system.
65536 KB occupied by the log file.
415774712 KB available on disk.

4096 bytes in each allocation unit.
124869119 total allocation units on disk.
103943678 allocation units available on disk.

C:\Windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP-SBSREE1\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk1\\Partition4"'
Property(s) update successful.

C:\Windows\system32>


14) Didn't configured any overclock.

15.a)

Attachment 232576

15.b)

Attachment 232577

___

Thanks again.

In general new computers should not have BSOD.
If possible the computer should be returned with a RMA.

The logs displayed multiple different types of bugchecks:

7E
A
A0
1A
50

Otherwise the logs were unremarkable.
The windows failed fast startup was last displayed on 4/30.

Hardware problems can be the cause of multiple types of bugchecks.

Tests can be performed for CPU, GPU, RAM and Drive.
There are no direct tests for Motherboard and PSU.

There were no misbehaving drivers seen in the kernel dump debugging.

Windows driver verifier can be restarted with these customized settings:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

If there are no BSOD then hardware can be tested.
This may repeat tests that were already performed.

Hi skimi, this sounds like a duplicate of a problem I hadde untill yesterday. It was a case of faulty RAM. I borrowed two new sticks from a friend and now all is good.

BSOD on cold boot only - Windows 10 Forums

Hey guys,

Quick update. I bought another pair of memories and since yesterday I didn't have any issues. Did cold boot three times, as I was doing before. I hope it keeps like that.

Thanks for all the help so far.