New
#11
Run for awhile as you have it setup now, without the Microsoft basic display adapter, see what happens.
Try another display with HDMI/DVI/VGA if you have more problems. Best not to change more than one thing at a time.
Run for awhile as you have it setup now, without the Microsoft basic display adapter, see what happens.
Try another display with HDMI/DVI/VGA if you have more problems. Best not to change more than one thing at a time.
Awesome!
Thanks so much for the help. I'll keep this post updated if anything else occurs.
- - - Updated - - -
Quick update:
I had one system crash after hours of idle when I started the program "Steam". I haven't had a crash since then but I haven't really had a chance to mess around with it over the past couple of days. I ran that batch file several times and didn't get any errors or anything out of the ordinary.
I'm going to switch to a different display today, although I had problems on my previous GPU with two different monitors, so I'm not sure if I should still try this step. (?)
I disabled auto restart and will get a V2 log as soon as it crashes this time.
Meanwhile, find my new V2 log attached. It may not have any new info.
Thanks for the help!
Attachment 242335
P.s. What are the odds my PCI slot is bad?
No mini dump in the zip. Event viewer log does indicate a BSOD on the 3rd:
Attachment 242342
but C:\Windows\memory.dmp is no longer available either.
No idea about the PCI slot. Probably about the same odds as the mother board being bad I guess.
Maybe time to consider doing a Repair Install. Even though this will supposedly not mess with your files I would do an image backup first:
Repair Install Windows 10 with an In-place Upgrade
The first thing you need to do is backup your current install. The best way to do this is to use Macrium Reflect Free to make an image backup to an external hard drive. If you don't have an external hard drive now is a good time to get one as regular backup should be a part of your normal process. You can get a 1TB external hard drive for $60 (less if on sale).
Last edited by Ztruker; 05 Aug 2019 at 18:37.
Just saw your post about minidump. Hopefully this V2 log has it. I just booted up about 2 minutes ago from a crash. It just went to black screen and turned off when i pressed the power button.
I'll do the restart that you suggested as well.
Thanks for the help!
Attachment 242350
- - - Updated - - -
Never mind. I just checked the minudump in the V2 log and it doesn't exist. I'll look into that.
I think the system is crashing (restarting) before the mini dump or memory dump can be created.
Nothing in the Event Viewer log indicates what the actual cause of the fail is.Code:Event[422]: Log Name: System Source: User32 Date: 2019-08-05T16:30:08.790 Event ID: 1074 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: S-1-5-21-1742859438-2548898130-462100011-1001 User Name: AWESOME-BUBBLES\Jason and Kristin Computer: Awesome-Bubbles Description: The process C:\Windows\System32\RuntimeBroker.exe (AWESOME-BUBBLES) has initiated the restart of computer AWESOME-BUBBLES on behalf of user AWESOME-BUBBLES\Jason and Kristin for the following reason: Other (Unplanned) Reason Code: 0x0 Shutdown Type: restart Comment: Event[510]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2019-08-05T16:39:23.799 Event ID: 20 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Awesome-Bubbles Description: The last shutdown's success status was false. The last boot's success status was true. Event[527]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2019-08-05T16:39:26.904 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Awesome-Bubbles Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Alright,
Came back to update after a couple weeks of troubleshooting.
The problem was extremely simple (if its fixed and not just lurking on me).
First I tried all the above steps. I finally broke down and ordered a new MOBO and processor thinking that surely that was the last items I could replace. I got them and couldn't even get the system stable enough to boot half the time.
Put the old stuff back in. At this point I'm certain that its something with the GPU or the PSU, and if that doesn't fix it I'm getting rid of my PC (haha). So I did something I should have done in the very beginning: I ordered a new GPU riser cable. The way my PC is set up, I have to have a riser cable for the GPU since it sits behind the MOBO. Lo, and behold, I have went 3 days crash free.
Boy do I feel like a dummy. I should've done the cheapest fix first.
Anyways, thanks for all the help. I now know I have a lot more resources when troubleshooting in the future.
TLDR: GPU riser cable was bad. Replacing it fixed the problem.
EDIT* my case was still under warranty so I got the riser cable for free. Didn't even cost me anything to fix.