[SOLVED] BSOD, no dump file

[Whaddap]

Hi. I recently purchased a HP Pavillion 27 all in one pc.
It crashes at random occasions, BSOD with UNEXPECTED_STORE_EXCEPTION or CRITICAL_PROCESS_DIED
It does not write a dump file. Configured Pagefile size bigger than total memory. I can crash manually and write a dumpfile using WhoCrashed.
Windows has all updates, nvidia graphics card has most recent drivers. I disabled fast boot. I disabled all non microsoft startup items and services.
I removed all attached USB devices. Bluetooth adapter for keyboard+mouse are still in use.
I tried to narrow down the situation when it happens, at first i assumed it would be related to specific programs.
Therefore changed the antivirus from bitdefender to avast and the browser from chrome to firefox.
No change in behaviour, even crashes when only firefox is running and playing youtube music.
Some days i dont have a single crash, some days i have 10+
I dont see the pattern.
Any help welcome
System information:
OS Name Microsoft Windows 10 Home
Version 10.0.18362 Build 18362
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-JJ2MPGD
System Manufacturer HP
System Model HP Pavilion All-in-One 27-xa0xxx
System Type x64-based PC
System SKU 5ES82EA#ABD
Processor Intel(R) Core(TM) i7-8700T CPU @ 2.40GHz, 2400 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Version/Date AMI F.10, 01/11/2018
SMBIOS Version 3.2
Embedded Controller Version 25.20
BIOS Mode UEFI
BaseBoard Manufacturer HP
BaseBoard Product 84EE
BaseBoard Version 1100
Platform Role Desktop
Secure Boot State On
PCR7 Configuration Elevation Required to View
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume2
Locale United Kingdom
Hardware Abstraction Layer Version = "10.0.18362.145"
Username DESKTOP-JJ2MPGD\max
Time Zone W. Europe Summer Time
Installed Physical Memory (RAM) 16,0 GB
Total Physical Memory 15,8 GB
Available Physical Memory 11,6 GB
Total Virtual Memory 18,7 GB
Available Virtual Memory 13,5 GB
Page File Space 2,88 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualisation-based security Not enabled
Device Encryption Support Elevation Required to View
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualisation Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes

Relevant eventlog entries are only
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ID 41
The previous system shutdown at 10:48:55 on ‎07/‎06/‎2019 was unexpected. ID 6008
Dump file creation failed due to error during dump creation. ID 161

 

[Whaddap]

i hate to be right.. a diskpart, list drives in the repair commandline lists C: as RAW filesystem.. something killed the content of the SSD..

 

[Whaddap]

https://imgur.com/a/9UVSn9S

 

[Colif]

really, a raw partition... on a brand new ssd? Its not normal for a brand new ssd to get something like that, itts essentially a blank partition, something has decided C drive didn't need windows on it

Do you have another PC? I would make memtest86 up on a USB and test your ram. Bad ram can corrupt all. Its the only thing we haven't tested. can't test motherboard or PSU, so running out of choices

 

[Whaddap]

i do, just not sure if i can find a working usb 🙃 the two memory tests that i did (windows memory diagnostics and the HP system test one, which did run for 4-5 hours and tested all 16 gigs) didn't find any memory issues.

should i try with memtest86 as well?

 

[Whaddap]

i think the controller of the disks or that part on the Mainboard killed the disk.. will probably leave it in this state overnight to double-check with HP if i should use the reset installation or not

 

[Colif]

contact HP, see what they suggest. I don't know what the HP tester does with regard to ram.

two ssd going bad is really bad news. something inside PC is killing parts.

 

[Whaddap]

local laws say if they can not repair it within a 'reasonable time span', which is up for interpretation but 6 weeks should be good, they have to replace or refund.. 2 weeks in.. let's see 😁

 

[Colif]

It was new and has never really worked, you deserve better.

 

[Whaddap]

not at HP apparently.. but the support tries their best, to be fair, it's a hard case without any dumpfile.. the repair team is to blame for not properly testing if it works after the SSD replacement.. wouldn't been hard to power it on, install updates and let it run for a day to see if it crashes