Soon as they patched Sunday, my pc started BSOD over and over. Yall ran another patch later that day, no more BSOD. Roll to today, patched earlier today, BSOD over and over. Patched again later, BSOD slowed down but didn’t stop until I uninstalled the whole …
1 Like
is there a possibility that something is malfunctioning on your pc? just saw your other post from September
what are your specs?
1 Like
Its an Alienware Aurora R16 , new , that from August was an older PC
Processor Intel(R) Core™ i9-14900KF, 3200 Mhz, 24 Core(s), 32 Logical Processor(s)
Nvidia RTX 4080 Super
I did just uninstall the game and the desktop app , and the BSOD just stopped
3 Likes
googled it, damn that thing looks hot! im jealous ^^
my pc for sure is a lot worse ^^
1 Like
Probably an overheating issue. The Aurora configurations are so mind-boggling bad for cooling.
They leave very little room for hot air to escape.
2 Likes
when i purchase a new pc, ill for sure ask the forums. Thats something id never know. i just saw that pc and was like: uuuuuuh pretty~! 
Yep, have a look at Gamer Nexus on YT and his video review of the Aurora. They legit cram everything into the case.
1 Like
My wife bought it for me, Its awsome
1 Like
Ah so this current gen seems to be a lot more open space wise. Completely different case.
Seems Dell do learn.
1 Like
Im runnig throught logs, No overheating, im not overclocked
i had a friend build my pc from parts, and yea, since budget was a thing that was her first advice - get a big case! we can save money on quite some parts, but the case is one of the most important parts ^^
Its not typical for a game to give you repeated BSOD. Thats going to be a hardware issue most likely. What are the stop codes you are getting with the BSOD?
1 Like
arent there error codes on bsod?
Faulting application name: Battle.net.exe, version: 2.37.0.15084, time stamp: 0x6722a18a
Faulting module name: libcef.dll, version: 108.0.0.0, time stamp: 0x63976dec
Exception code: 0xc0000005
Fault offset: 0x031bc56a
Faulting process id: 0x0x5634
Faulting application start time: 0x0x1DB2FEC527C0773
Faulting application path: C:\Program Files (x86)\Battle.net\Battle.net.exe
Faulting module path: C:\Program Files (x86)\Battle.net\Battle.net.15084\libcef.dll
Report Id: 2e06a380-89ca-4e90-8eea-d06e874627d0
Faulting package full name:
Faulting package-relative application ID:
There are hundreds of them… jeez
1 Like
hope the forum tech masterminds can help bud!
consider it a bump for visability 
1 Like
They are generic, IRQ faults
What does your event viewer say? What code?
Given it’s a BSOD it’ll be a critical error.
Starting to think it may be the HDD failing, but the smart doesn’t show an issue. nvme, and ssd, slowing stop working over time, and fail randomly like this and progressively worse ( I work in IT) . Problem is, that since i uninstalled , the BSOD stopped, … Coincidence?
1 Like
you installed d4 on hdd? just saying, min requirement is ssd.
doesnt explain bsod of course, but yea.
1 Like
These are from event viewer. What are your BSOD stopcodes? You should read your DMP files with either Bluescreenview or WINDBG. Or write down the stop codes of the BSOD. Event viewer only helps so much with BSOD. Eventviewer doesn’t always show what caused BSOD.
2 Likes