7 Days to Die BSODs my PC. SOLVED!!

[Bam4000]

Whenever I launch the game it just crashes my PC and gives me a different error every time.
First it was kernel mode heap corruption then irql not less or equal and after that reference by pointer.

I reinstalled my graphics driver and reinstalled the game.
I tried taking a look into the minidump folder but the website you use to look at the crash logs got shut down.

Specs:

Computer Information:
Manufacturer: ASUS
Model: System Product Name
Form Factor: Desktop
No Touch Input Detected

Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 5 3600X 6-Core Processor
CPU Family: 0x17
CPU Model: 0x71
CPU Stepping: 0x0
CPU Type: 0x0
Speed: 3793 Mhz
12 logical processors
6 physical processors
HyperThreading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported

Operating System Version:
Windows 11 (64 bit)
NTFS: Supported
Crypto Provider Codes: Supported 311 0x0 0x0 0x0

Video Card:
Driver: Radeon RX 5500 XT
DirectX Driver Name: aticfx32.dll
Driver Version: 30.0.21023.1015
DirectX Driver Version: 30.0.21023.1015
Driver Date: 6 22 2022
OpenGL Version: 4.6
Desktop Color Depth: 32 bits per pixel
Monitor Refresh Rate: 59 Hz
DirectX Card: Radeon RX 5500 XT
VendorID: 0x1002
DeviceID: 0x7340
Revision: 0xc5
Number of Monitors: 1
Number of Logical Video Cards: 1
No SLI or Crossfire Detected
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 1920 x 1080
Primary Display Size: 20.91" x 11.73" (23.94" diag)
53.1cm x 29.8cm (60.8cm diag)
Primary Bus Type Not Detected
Primary VRAM Not Detected
Supported MSAA Modes: 2x 4x 8x

Sound card:
Audio device: Lautsprecher (High Definition A

Memory:
RAM: 16283 MB

VR Hardware:
VR Headset: None detected

Miscellaneous:
UI Language: English
Media Type: Undetermined
Total Hard Disk Space Available: 2145513 MB
Largest Free Hard Disk Block: 866903 MB
OS Install Date: Jul 01 2022
Game Controller: None detected

Storage:
Disk serial number hash: f22a0226
Number of SSDs: 1
SSD sizes: 250G
Number of HDDs: 1
HDD sizes: 2000G



Please help

[Mardoin69]

Sounds more like a Windows and / or BIOS configuration problem or possible faulty hardware. BSOD are almost ALWAYS a problem with the PC....not the apps on them....aside from Windows. First thing to try is open command prompt. R-click it and choose 'Run as administrator.' Now at the command line, type: SFC /SCANNOW hit enter and wait. It'll try an fix any windows system file errors it finds.

Aside from this, let's be sure you have a clean install of the game...as described in the pinned '...troubleshooting' thread.....and, you used the launcher tools to clear old Registry data. You should have used the launcher tools to clean off old data from your client whenever you re-install the game or update to different versions.
Here's how;
First, backup your save and map files if you intend on resuming a previous game session. Then;
Run 7d2d launcher.exe, switch to 'tools' tab, click 'Clean' and select all the options to clean. Switch back to main tab, disable EAC--if not needed--and Anaylitics then, select 'Run and save settings.' Next, at game's main menu--options, optimize your video settings. See this thread for pointers on that;

https://steamcommunity.com/app/251570/discussions/1/3190241086281294394/

*Note* Most rigs meeting minimum specs should have very little fps issues with the Medium preset w/exception of reflections settings which need to be at Low or even off for best results. Shadow distance at Med. and dynamic mesh, occlusion, possibly Dynamic music, all disabled.

Close out game. Copy your save and map files back to appropriate user folders. Re-launch game and continue your game.
Optionally, create a new map then exit the game so RAM is flushed. Then, launch and start a new game using your new RWG map.

Also, be sure you don't have some old mods left in a 'mods' folder either in Steam's 7d2d directory and / or user's \Appdata\Roaming\ 7d2d folder. If so, delete the files inside the 'mods' folder(s) or move them temporarily.

It's also a good idea to create an exception in your Anti-Virus app for the 7d2d.exe, 7d2dlauncher.exe, and EAC.exe--if playing MP. This will avoid possible 'False positives' and keep it from halting them to check each time you run them.

Having done all that.....if your system still crashes when trying to launch this game, you should run a Memory test to see if you have some faulty RAM. Look online and get Mem Test app or start up the system using the Windows Install disk and use Windows Memtest option. Personally, I find the one you can download is much easier.

[SuperMeatBag]

In addition to the excellent advice above, does the Windows Event Viewer have anything to say? It may not as it can't log an event once frozen, but it might point you in the right direction.

[Bam4000]

Thanks for all the advice! At first i will go and try to run the SFC /SCANNOW command and see if it finds something.

[Bam4000]

It found no issues with windows. Please god dont say my RAM is faulty and i need to replace it. I really dont have the money for it.

[SuperMeatBag]

Just to clarify here, when you say it "crashes" the PC, is it hanging ie it stops responding? Or giving a BSOD and rebooting? Some googling of the errors you mentioned indicate many possible problems, some hardware-related and some software. Most replies talk about new drivers not working correctly/not installing correctly, wrong PCI lane being chosen (very unlikely but I mention it for completeness' sake). Also for trouble-shooting purposes, is the PC able to play other games or perform high stress tasks? Has the PC been able to play 7DTD before or until recently?

[SiEgE]

Originally posted by Bam4000 2.0:

...

Disable EAC, and if that doesn't help - fix your hardware.

BSODs are impossible to be caused by software(games, applications, websites and etc.), except drivers and OS itself.
If you have incompatible/damaged drivers, or your OS is having issues(damaged/corrupted files), then you can have BSODs.

So, answering your main question: No, 7DTD cannot cause you to BSOD.

[Bam4000]

I mean whenever I start the game is BSODs and gives me an error. Its always different but they still have one thing in common that is that they all have something to do with drivers it seems.

But I reinstalled my drivers many times now so what could I do to fix it? Is windows being an idiot again and installing alongside my real drivers some other dumb microsoft drivers i dont know.

[SuperMeatBag]

Originally posted by SuperMeatBag:

Also for trouble-shooting purposes, is the PC able to play other games or perform high stress tasks? Has the PC been able to play 7DTD before or until recently?

I'll quote myself to re-ask these questions, it would help to narrow down the problem greatly. 7DTD works hardware very hard but if all your games do the same thing, that would point to driver and/or OS problems. I'd recommend also using DisplayDriverUninstaller to do a totally clean install of your GPU drivers, remnants are often left behind which can cause conflicts, and they aren't helpful.

[Bam4000]

Well it could handle Cyberpunk 77 so...

[Bam4000]

And no I just bought 7DTD and have never played it before.

[SiEgE]

Originally posted by Bam4000 2.0:

I mean whenever I start the game is BSODs and gives me an error. Its always different but they still have one thing in common that is that they all have something to do with drivers it seems.

But I reinstalled my drivers many times now so what could I do to fix it? Is windows being an idiot again and installing alongside my real drivers some other dumb microsoft drivers i dont know.

When it goes BSoD, it usually displays the type of issue you had. Some kind of code, or code name that targets at the fault. If it doesn't - you can always check your Event Viewer and see what kind of BSoD that was and what was the reason.

[Bam4000]

First it was "kernel mode heap corruption" then "irql not less or equal" and after that "reference by pointer." As I said in the original post.

[Bam4000]

I looked in event viewer and the 4 critical errors show up.

Protokollname: System
Quelle: Microsoft-Windows-Kernel-Power
Datum: 07.07.2022 15:18:43
Ereignis-ID: 41
Aufgabenkategorie:(63)
Ebene: Kritisch
Schlüsselwörter:(70368744177664),(2)
Benutzer: SYSTEM
Computer: DESKTOP-NUAK9VR
Beschreibung:
Das System wurde neu gestartet, ohne dass es zuvor ordnungsgemäß heruntergefahren wurde. Dieser Fehler kann auftreten, wenn das System nicht mehr reagiert hat oder abgestürzt ist oder die Stromzufuhr unerwartet unterbrochen wurde.
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
<EventID>41</EventID>
<Version>9</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2022-07-07T13:18:43.6899533Z" />
<EventRecordID>3207</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>DESKTOP-NUAK9VR</Computer>
<Security ID: "I dont wanna show this" />
</System>
<EventData>
<Data Name="BugcheckCode">10</Data>
<Data Name="BugcheckParameter1">0x7fffffff0000</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">0</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">0</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
<Data Name="BugcheckInfoFromEFI">true</Data>
<Data Name="CheckpointStatus">0</Data>
<Data Name="CsEntryScenarioInstanceIdV2">0</Data>
<Data Name="LongPowerButtonPressDetected">false</Data>
<Data Name="LidReliability">false</Data>
<Data Name="InputSuppressionState">0</Data>
<Data Name="PowerButtonSuppressionState">0</Data>
<Data Name="LidState">3</Data>
</EventData>
</Event>

The first error says this

[Bam4000]

The one i send was the second

[Bam4000]

I reinstalled my drivers with DDU and all but it still crashes.