Question Windows 10 BSOD from attempting to launch TF2 after crash.

cph30075

Reputable
Apr 25, 2015
42
0
4,530
0
I occasionaly get a BSOD, but I'm done dealing with these. Temps are fine, no thermal throttling or that jazz. Running a Ryzen 1700x @ stock (3.4Ghz), 32GB DDR4 RAM, EVGA FTW2 GTX 1080 @ stock. The Ryzen is water cooled by an NZXT 280mm cooler, runs at 34C idle. GPU runs at 60C idle. I'll attach the BSOD viewer logs. Thanks for any help.
Here's the BSOD .dmp file below:
https://pastebin.com/GzU5tdWQ
 

cph30075

Reputable
Apr 25, 2015
42
0
4,530
0
Hi, please upload the actual minidump located here:
C:\WINDOWS\Minidump\060819-13546-01.dmp
to a file sharing site such as Google Drive or OneDrive (there are others too).
The file isn't there; folder is empty. It also no longer shows up on BSODview so I don't know where it could have gone besides a timed cleanup. I don't have any cleanup programs installed so my guess is Windows deleted it automatically.

EDIT: With that said I assume I'll have to wait until I get another BSOD, correct?
 

cph30075

Reputable
Apr 25, 2015
42
0
4,530
0
Hi, yes. Wait until you have another crash. Be sure minidumps (Small Memory Dumps) are enabled.
https://www.tenforums.com/tutorials/5560-configure-windows-10-create-minidump-bsod.html

Right after a crash go ahead a make a copy of the dump file just in case it gets deleted from it's original location.

You may need to copy the minidump file to your desktop (or documents) before it will upload properly.
I checked that already. I definately do have minidumps enabled, but I guess windows deletes them after a restart or a day. Would using driver verifier do anything?
 

gardenman

Admirable
Herald
@Colif asked me to take a look at the dump file and he will reply later. I ran the dump file through the debugger and got the following information: https://pste.eu/p/KMv2.html

File information:071219-14156-01.dmp (Jul 12 2019 - 10:12:28)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:memory_corruption (Process: csrss.exe)
Uptime:0 Day(s), 14 Hour(s), 36 Min(s), and 16 Sec(s)

Comment: The overclocking driver "IOCBios2.sys" was found on your system. (Intel Extreme Tuning Utility)

BIOS information was not included in the dump file. This can sometimes mean an outdated BIOS is being used.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 

cph30075

Reputable
Apr 25, 2015
42
0
4,530
0
Any news yet? I'm thinking it might be because I'm using Ryzen, I used to use an Intel chip so I'm the remnant XTU files are causing something but I don't know for sure.
 

Colif

Titan
Moderator
Normally I look at older drivers as potential causes of errors, figuring newer ones are more likely to have been written to work with win 10

  1. Jul 26 2008 - OpenHardwareMonitorLib.sys - Open Hardware Monitor driver http://openhardwaremonitor.org/
  2. Aug 22 2012 - AsIO.sys - ASUS Input Output driver http://www.asus.com/
  3. Sep 12 2012 - btwsecfl.sys - Broadcom Bluetooth IT Manager Filter driver (Broadcom Corporation)
  4. Feb 28 2013 - npf.sys - NetGroup Packet Filter driver, a component of WinPCap by Riverbed
  5. Jun 22 2016 - btwusb.sys - Bluetooth USB Device driver (Broadcom Corporation)
1 should be okay, I often see it
2 leads me to think you have an Asus motherboard
3 & 4 seem to old for the hardware you are using, I have seen 4 before, just can't remember where. wireshark?

what motherboard are you using? what bluetooth adapter?

dump is unable to identify the name of driver that caused this. csrss.exe = client services, its part of windows your user runs in.
 

ASK THE COMMUNITY

TRENDING THREADS