Windows 10: Setting a World Record for Most BSoD's Within a Week (HELP)

Attachment 49840​

Updated: dumpfile - Attachment 49932
Hi everyone,

So, last week, I built this gaming PC with me installing windows 10 on it. Ever since I got it running and starting playing games such as fallout 4, my PC has picked up the hobby of crashing on me. I've had several different types of error codes over the past week such as CRITICAL_PROCESS_DIED, IRQL_NOT_LESS_OR_EQUAL, and MEMORY_MANAGEMENT. Before I went ahead and reset my PC recently, BlueScreenViewer picked up that my driver ntoskrnl.exe was causing majority of the BSoD's. I recently reset my PC so therefore those minidump files from before are now gone (I know. I shouldn't of. But maybe I'll get more BSoD's, which is a terrible thing to say, and will lead to more information about what's going on). But, I do have one file from when it crashed on me recently while playing fallout 4. I can browse the internet and do other non-gaming activity with ease. No crashes or anything. So, one would think that it might be my graphics card driver. I BlueScreenViewed my .dmp file and it revealed that the driver "dxgmms2.sys" (Which I believe is DirectX) caused the crash with the error code "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" I've ran SFC and it showed nothing. Also, ran memtest which also showed nothing. Beforehand, I thought it was the most recent windows updates that caused my PC to crash since I did at one point play Fallout 4 with no issues for about 4 hours until thenAttachment 49840 windows update practically forced the new updates on my computer. Which then led to a BSoD while playing the game. I've just been doing the guessing game for the past week and obviously it has a 0% successful rate. So, please, someone help me. This wasn't a cheap build and I'm trying to keep my self from getting stressed out from the fact that I built a busted expensive PC. I won't give up hope though. There is always a way to fix these issues. There has to be. Just a extremely difficult task. Again, HELP.

:)

 

E5 got dead within a week of purchase

Exactly the same thing happened to me!!!



Purchased my E5 on 25/10/10. Five days later, found it dead. I thought that I must have forgot to charge it overnight, so plugged it in for charging. 2 hours later, it woke up, only to die again in the evening.



Took it to the Nokia Care Center. Was told that this could be a software problem & I should deposit it for inspection!!! Damn!!! Didn't buy the brand new set only to get it inspected after 5 days of purchase!!!!!



To cut a long story short, got the damn thing back after 3 days.....had to reload my contact list, photos, other data etc. The phone worked fine for a week and this morning..Boom....!!!!!!!!!!!!!

Its dead again!!!!



What the@#%@??????



So much for connecting people, Nokia????



I want a replacement!!!!!!

 

E5 got dead within a week of purchase

i never had any problem wt my phone.the only problem i'm havin whch i knew it's common to other smartphones is,in some areas, network bars always go down reducing to one bar,and it pieces me off,and this lowers the speed of the internet connectivity.u
knw what i'm after for,is d speed of the internet connection.

 

Hi RyeFlex,

Welcome to the 10forums.

Many different errors are an indication of lower level problems with the system.
A quote of the usual causes by @usasma

I strongly suggest to run diagnostics test for your hardware.
Hardware Diagnostics

Below are shortened stacks about the GPU video memory and the hard drive.
This usually points to hardware problems.
Code: 1: kd> k Child-SP RetAddr Call Site ffffd001`0cef7d78 fffff800`881bf79d dxgmms2!VIDMM_PAGE_TABLE_BASE::IsResident ffffd001`0cef7d80 fffff800`881bf591 dxgmms2!VIDMM_PAGE_TABLE::EvictPageTable+0x15 ffffd001`0cef7dc0 fffff800`881c3dd4 dxgmms2!VIDMM_PAGE_DIRECTORY::EvictPageDirectory+0x14d ffffd001`0cef7eb0 fffff800`881c364c dxgmms2!VIDMM_PAGE_DIRECTORY::UncommitVirtualAddressRange+0x720 ffffd001`0cef8060 fffff800`881af509 dxgmms2!CVirtualAddressAllocator::UncommitVirtualAddressRange+0x78 ffffd001`0cef80d0 fffff800`881af6d8 dxgmms2!VIDMM_GLOBAL::MakeOneVirtualAddressRangeNotResident+0xfd ffffd001`0cef8560 fffff800`881cf528 dxgmms2!VIDMM_GLOBAL::MakeVirtualAddressRangeNotResident+0x50 ffffd001`0cef85a0 fffff800`8818fd25 dxgmms2!VIDMM_MEMORY_SEGMENT::EvictResource+0x10e8 ffffd001`0cef87a0 fffff800`8819531b dxgmms2!VIDMM_GLOBAL:rocessDeferredCommand+0x925 ffffd001`0cef8940 fffff800`88198ebd dxgmms2!VIDMM_WORKER_THREAD:rocessPendingTerminations+0xa3 ffffd001`0cef89f0 fffff802`67f626d8 dxgmms2!VIDMM_WORKER_THREAD::Run+0x9c1 ffffd001`0cef8b00 fffff802`67fced06 nt!PspSystemThreadStartup+0x58 ffffd001`0cef8b60 00000000`00000000 nt!KiStartSystemThread+0x16[/quote] Code: 3: kd> k Child-SP RetAddr Call Site ffffd000`22825b38 fffff803`751575a9 nt!KeBugCheckEx ffffd000`22825b40 fffff803`75155dc8 nt!KiBugCheckDispatch+0x69 ffffd000`22825c80 fffff803`75051d85 nt!KiPageFault+0x248 ffffd000`22825e10 fffff803`750dab50 nt!MiInsertPageInFreeOrZeroedList+0x265 ffffd000`22825ef0 fffff803`7501d925 nt!MiInsertLargePageInFreeOrZeroList+0xe0 ffffd000`22825f40 fffff803`7501d42a nt!MiGetFreeOrZeroPage+0x425 ffffd000`22825fc0 fffff803`75010aa1 nt!MiGetPage+0x7a ffffd000`22826030 fffff803`7500fc29 nt!MmCopyToCachedPage+0x8a1 ffffd000`228261f0 fffff803`750db61a nt!CcMapAndCopyInToCache+0x279 ffffd000`228262e0 fffff801`01808ce8 nt!CcCopyWriteEx+0x1ca ffffd000`22826380 fffff801`01807dc7 NTFS!NtfsCommonWrite+0xc88 ffffd000`22826620 fffff801`00bf51c4 NTFS!NtfsFsdWrite+0x1d7 ffffd000`228266e0 fffff801`00bf3a16 FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2a4 ffffd000`22826760 fffff803`7542072b FLTMGR!FltpDispatch+0xb6 ffffd000`228267c0 fffff803`7541f780 nt!IopSynchronousServiceTail+0x16b ffffd000`22826890 fffff803`75157263 nt!NtWriteFile+0x680 ffffd000`22826990 00007ffd`01fd35ca nt!KiSystemServiceCopyEnd+0x13 00000017`4155b9a8 00000000`00000000 0x00007ffd`01fd35ca[/quote]