Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
Always post system specs, driver version et cetera when posting a "help" thread.
Have you checked your temps? What in-game settings are you using? Did you force "Nightmare?" Hard locking is typically a sign of resource allocation and assets being exceeded and causing a crtical fault. Do you have micro-stutter or mini freezes before it completely locks up? Have you tried a clean install in safe mode using DDU with Windows 10 automatic device installation disabled? There is a chance there are driver conflicts with old registry entries from previous versions.
Answer as many of those questions as you can, it will help a great deal in getting you on the right track.
EDIT: Also, have you changed any settings related to XMP profiles via your UEFI or Legacy BIOS recently? Any changes to your socket frequencies at all (overclock). Even if you have not, I suggest running memory test; this behavior can also be related to a bad DIMM module.
I actually experienced the exact same thing about an hour ago as I was pulling a Glory Kill on a Hell Knight. However I could use ctrl alt del and navigate the Windows taskmanager. Alt + F4 didn't work though. Coincidentlally I'm also running with a GTX 970. Didn't experience any sign of stress before the game froze, everything was running smooth on Ultra settings as always. Game is installed on an SSD. Haven't had a single issue with the game aside from this one incident.
Specs:
Windows 7 64-bit Home Premium
MSI GTX 970 OC 4GB
i5-6400 2.70Ghz
MSI B150 PC MATE mobo
8GB DDR4 Ram
Kingston V300 240GB SSD
Seagate Barracuda 2TB HDD
Enermax MaxPro 500W 80+ PSU
Latest Nvidia drivers.
Thank you for posting your specs.
How is your capacity on the SSD (Gb allocated & Gb free)? Do you have Windows utilizing auto-detection of Virtual Memory? DOOM actually utilizes a virtual texture page size which allocates resources between physical and virtual pools. You could be exceeding the load limit for your system specifications. 8Gb is pretty much the minimal of physical memory allocation space on a 64-bit operating system for gaming in 2016. I'm not saying that is the primary issue, it is just something to consider. Also, check your page file size.
Finally, if you could do me a favor, enter Resource Monitor, RAM tab, list the following: Hardware Reserved (if applicable), Free, Modified (if applicable) in that order on your response to this post please.
Thank you, and I will check your follow-up.
-re-enabled my pagefile and set to 8192
-sound options on 24 bit 48000 hz
-disabled the compass & other UI bloat
-video options to low where possible
-video set on borderless window
Steam launch options, i removed -USEALLAVAILABLECORES line
+com_skipIntroVideo 1 +menu_advanced_AllowAllSettings 1 +set m_smooth 0 +com_skipKeyPressOnLoadScreens 1
Those aren't really fixes. Turning settings down on "low" does effect performance and resource allocation, however that isn't really a fix...that's more or less common sense. I wager the hard-lock issue are due to either faulty hardware (possible frequencies UEFI/Legacy settings), or registry entry issues with the application's hexadecimals from previous versions.
The contribution is appreciated, so don't take offense, but those are mostly aesthetic and personal preferences. The issue these two users have is directly attributed by hardware configuration.
Also, I strongly advise against changing any entries such as -useallavailablecores, hyper-threading, core parking et cetera with DOOM; as the application utilizes all hardware cores/threaded cores automatically up to decacore (twenty thread count). If anything manipulating lower core detection will cause adverse effects in the texture streaming and physics processes. Trust me.
EDIT: In the kindest way possible, disregard candlestone's suggestions.
NOTE: Two the original poster, and David The Gnome, please first try and clean install from safe mode using the DDU utility. You can find the updated mirror here: http://www.guru3d.com/files-details/display-driver-uninstaller-download.html (v.16.1.0.1)
Once drivers are removed via the safe mode restart and Windows automated install for devices is restricted, install the latest WHQL NVIDIA driver from this mirror: http://www.guru3d.com/files-details/geforce-368-81-whql-driver-download.html (for applicable OS version).
EDIT 2: candlestone34, you should always allow Windows to designate your Virtual Memory pool; there is no benefit to custom Page File sizes, unless using very high physical memory, or NAS RAID 5 configurations. Don't fall victim to misinformation or BS articles from non-professional sources. There is nothing wrong with allowing Windows to manage Page File; as a matter of fact the dynamic nature is far more intelligent than specified numerical limitations. You can actually cause incorrect data streaming and detection with applications such as Catzilla (benchmark) & Futuremark software, which are designed for VM+Physical allocation. The more you know...
Windows 10 Pro
MSI GTX 1080 Gaming X
i7-4790k
Asus Z97I-PLUS
16GB DDR3 @ 2400MHz
Crucial BX100 500GB SSD
Seasonic platinum 660w
Latest drivers.
Doom is installed on the SSD, which is about about 45% full.
CPU and GPU temps always between 50-55.
Installed GTX 1080 with DDU.
No sign of stress or micro-stutters at all, running at capped 135FPS at 1080p at max settings with both nightmare options.
Game would freeze randomly with music still playing as mentioned. Just happened for the second time since yesterday when I started a new playthrough.
I did find a way to get out of it without forcing a shutdown though. If you Ctrl+Alt+Del you will have a black screen but still see the mouse cursor. If you hover around the center of the screen the cursor will change to a pointer indicating that you can click something. There are 5 options from top to bottom, the 3rd option in the middle is sign out. After clicking that you go to the lock screen and regain control, and then I restart anyway for good measure.
No issues with other games, Been playing DOOM since May but only Multiplayer/snapmap. Never crashed once in those modes. Not sure if this is a problem from a recent update, or if this has always been a campaign issue, as I have not played much of the campaign until yesterday.
There seems to be a few people with this problem, with different cards and different RAM entirely.
i7 4770k overcocked to 4.3 ghz
16 GB DDR3 RAM
780ti @ 1.1 ghz
Game is installed to my SSD Raid 0, 83 gigs free
Windows 10
Windows is managing my page file
No warning, microstutters or anything of that sort. In around 150 hours of playing, this is the first time I've encountered this bug.
On launch I had few issues outside CTDs, but with each patch and driver update there's totally new issues. For some reason these people keep coming on here and telling everyone it's their pcs when most people have no problems outside of Doom, and they're weirdly nice about it--which is fine and all, and in allot of cases probably true, but in this case I don't think so because my buddy still hasn't been able to play Doom since launch because of some crash Bethesda/ID can't figure out, and they're totally quiet about it. My guess is Vulkan or Denuvo bugs are causing these issues. I mean, I went from able to play this game fine with a couple CTDs here and there to now my PC totally crashing for no real reason, I've wasted hours upon hours monitoring my system thinking it was my pc.
Sorry to hear that. I was certain it was the game.
I should also mention I am playing on OpenGL. I tried Vulkan and I do get more FPS but for some reason it just isn't smooth. Very minor constant micro-stuttering.
And I think I actually remember getting one or two CTDs in multiplayer a few days after launch but they must have patched that. Although I would prefer CTDs now instead of these annoying AF freezes.
Refer to my post as a "wall of text," while using a program like Driver Fusion. Get lost chump. Leave PCs to those who know what they are doing.
That's similar for me, too. The CTDs are fixed but now my pc restarts lmao. It's very obvious these are issues with the game.
If that were the case everyone would encounter the same issues and a patch would be deployed. Are you certian you are not exceeding your hardware resoruces; e.g. VRAM/Physical memory allocation?
Typically CTDs come from faulty driver registry entries, or unstable hardware configuration. Have you run Prime95, MEMTest et cetera? Did you recently change any settings in your UEFI/Legacy BIOS? Did you try DDU for clean driver install with the option to remove Vulkan runtime API?