Windows 10: Random BSOD's every 45 min or so, usually while playing games

Yah okay that's what I thought. I watched the video but there was no new option highlighted so I just wanted to clarify, thanks!

Edit: in the video and post it says when you use the new option on the unallocated drive 4 partitions should show up. There are only two that show up for me. Systems reserved and primary. Is that a problem?

Edit 2: nevermind about the previous edit, I found out you're supposed to select boot from UEFI: USB D: after doing I got four partitions, Windows is installing right now

 

Well guys, you'll be dissapointed to know that it wasn't windows or a program because a clean windows install later and the BSOD's don't stop. After I clean installed I put on graphics drivers and such, programs and i reinstalled a game and skype along with my mail program (thunderbird), vlc and chrome. Even after all that the computer went and died again. No clue how it could get more depressing than this. I have the DM log attatched, but does this mean I have to get a new SSD? My HDD and other SATA devices were all unplugged for the duration I was using the PC up until the crash. I mean honestly, will new hardware fix this or am I just stuck in a perpetual loop of troubleshooting and constant disappointment. Student life is stressful as its sigh. Anyways DM log is attached, hope ya'll can find something helpful.

 

Please run the hard drive tests again, this time with HDTune





Diagnostics Test

HDD TEST


Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials...s-how-use.html



Note Do not run SeaTools on an SSD as the results will be invalid.



Run chkdsk http://www.sevenforums.com/tutorials...isk-check.html



Run HDTune to scan for errors, health and benchmark.
Let me know what the results are, prefered screenshots.


Code: FAULTY_HARDWARE_CORRUPTED_PAGE (12b) This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error. Arguments: Arg1: ffffffffc00002c4, virtual address mapping the corrupted page Arg2: 0000000000000473, physical page number Arg3: 000000eb0654eff0, zero Arg4: ffffd000249d6000, zero[/quote]

 

Hiya axe0, ill run those tests when I get home. Do I need to test my hdd also? I didn't have it plugged in at the time of the bsod.

 

Then there is not yet a reason to for scanning it *Wink

 

Heya guys, sorry for the delay. So long story, I ran chkdsk and it said C Drive was damage and needed to be repaired. So I attempted that and restarted like Windows asked. Lo and behold it started to BSOD as soon as C Drive was repaired. It went into startup repair after the 2nd BSOD so I decided to do what Essenbe suggested a while back when I was in the same situation. I reset windows and surprisingly this time it worked. After resetting windows the computer repaired C Drive. When I booted back in I ran chkdsk again just to make sure, and it had no errors. I ran HDTune just in case and as far as I can see the drive is healthy but here are the screenshots you asked for just in case.

Attachment 47965Attachment 47963Attachment 47964Attachment 47962Attachment 47961Attachment 47965Attachment 47963Attachment 47964Attachment 47962Attachment 47961
Attachment 47968Attachment 47969Attachment 47966Attachment 47967Attachment 47970
Attachment 47971

 

Welp, looks like a clean install and fixing the hard drive didn't do it. ANOTHER BSOD happened. That's just ****in' great. (Pardon my french). No but seriously this is the biggest source of stress for me right now. What the hell am I supposed to do to make this bullshit stop. I ran dskcheck again and it returned no errors. Before the BSOD i connected my old HDD and for 8 hours or so my computer ran fine. Got a memory management error. DM log is attatched. I really don't want to have to clean install and reinstall all my programs for the 15th time.

Edit: So I checked whocrashed and it said that the memory managment error is most likely a driver error, I decided to check all my devices for updates in device manager. Took a really long time but I managed to find one that needed to update. A screenshot of the update device screen is attatched. Not sure if it'l help but one can hope.

 

This doesn't look like a driver issue to me, but more like a GPU issue
Code: FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0[/quote] Code: 1: kd> k Child-SP RetAddr Call Site ffffd000`249b8d48 fffff802`10800ef8 nt!KeBugCheckEx ffffd000`249b8d50 fffff802`106b03d4 nt! ?? ::FNODOBFM::`string'+0x20df8 ffffd000`249b8f50 fffff802`1072f6e5 nt!MiDeleteVad+0x394 ffffd000`249b9080 fffff802`10a98255 nt!MiFreeVadRange+0x4d ffffd000`249b90c0 fffff802`107dbb63 nt!NtFreeVirtualMemory+0x415 ffffd000`249b9210 fffff802`107d4360 nt!KiSystemServiceCopyEnd+0x13 ffffd000`249b93a8 fffff802`03d34c97 nt!KiServiceLinkage ffffd000`249b93b0 fffff802`03ce0936 dxgmms2!VIDMM_RECYCLE_BLOCK::~VIDMM_RECYCLE_BLOCK+0x53 ffffd000`249b9400 fffff802`03d36951 dxgmms2!VIDMM_RECYCLE_BLOCK::`scalar deleting destructor'+0xe ffffd000`249b9430 fffff802`03d3880e dxgmms2!VIDMM_RECYCLE_HEAP_MGR:estroyRange+0x4d ffffd000`249b9460 fffff802`03d18ab8 dxgmms2!VIDMM_RECYCLE_MULTIRANGE::MergeSubrangesWherePossible+0xc2 ffffd000`249b9490 fffff802`03cd4e54 dxgmms2!VIDMM_RECYCLE_HEAP_MGR::~VIDMM_RECYCLE_HEAP_MGR+0x12758 ffffd000`249b9500 fffff802`03d05e1d dxgmms2!VIDMM_RECYCLE_HEAP_MGR::`vector deleting destructor'+0x14 ffffd000`249b9530 fffff802`03cd4d82 dxgmms2!VIDMM_PROCESS::~VIDMM_PROCESS+0xfd ffffd000`249b9560 fffff802`0230c206 dxgmms2!VidMmTerminateProcess+0x12 ffffd000`249b9590 fffff802`0230a7c6 dxgkrnl!VidMmTerminateProcessX+0x7a ffffd000`249b95c0 fffff802`0232c7d9 dxgkrnl!DXGPROCESS:estroy+0xb6 ffffd000`249b9690 fffff960`941e324c dxgkrnl!DxgkProcessCallout+0x159 ffffd000`249b96f0 fffff960`93edd3ff win32kbase!GdiProcessCallout+0x8c ffffd000`249b9770 fffff802`10b20c82 win32kfull!W32pProcessCallout+0xbf ffffd000`249b97a0 fffff802`10b2139f nt!PsInvokeWin32Callout+0x42 ffffd000`249b97e0 fffff802`10ba1c88 nt!PspExitThread+0x66f ffffd000`249b98e0 fffff802`10ba1c6f nt!PsExitCurrentUserThread+0x18 ffffd000`249b9910 fffff802`106c4e12 nt!KiSchedulerApcTerminate+0x1f ffffd000`249b9940 fffff802`107d4800 nt!KiDeliverApc+0x2f2 ffffd000`249b99c0 fffff802`107dbc0a nt!KiInitiateUserApc+0x70 ffffd000`249b9b00 00007fff`8162353a nt!KiSystemServiceExit+0x9f 00000040`0dddf718 00000000`00000000 0x00007fff`8162353a[/quote] Note the temps of the GPU when idle and under load and post them.





Diagnostic test

GPU TEST


Run Furmark tutorial



Note Run Furmark for around 30 minutes



Warning Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if temperatures rise too high

 

Hiya Axe0, that's a shame. Well the gpu idles around 24-29 degrees. I ran furmark like you said, in the first minute or so the temps climbed rapidly to 75 degrees and that was the max. For the rest of the test it never dropped from 74 and never went past 75. It went fairly smoothly, average fps was 24, no artifacts that I could see. I know there's supposed to be a data log but I don't know where it's stored.

 

Don't know if thread has gone dead but I crashed while I was afk. In WhoCrashed it says AVG was the cause, here's the dump log, I uninstalled avg.

 

The thread hasn't gone dead, @axe0 is very busy and is in a different time zone. But uninstalling AVG is a good decision. Maybe that will give you better results.

 

I see, don't mean to be pushy, there were a couple windows updates I did, not too sure if that would help with driver issues but perhaps? Anyways thanks for the reply.

 

I'm sorry for the delay Azazrael.

Currently I am extremely busy with everything.
I am not sure how much time I would need to get passed everything, but I promise I will help a.s.a.p. if nobody else has passed me.

 

Windows updates can help with driver updates as well as stability. Have you had any BSODs since uninstalling AVG?

 

No no it's not a problem, I understand, and heck its not like I'm paying you guys for the help. I really appreciate your help and Essenbe's. In reply to your question essenbe, I haven't, then again I've gone 2+ days without a BSOD happening. I uninstalled AVG around this time yesterday, since then I haven't had a BSOD.