Solved

Lots of BSODs with lots of different error types, I'm dumbfounded please help!

Hi there,

For about a week now, my computer has been plagued with various BSOD crashes. Most of them have been due to MEMORY_MANAGEMENT, but recently I've been getting many different errors, I'll post a screenshot of the error minidumps.

I have looked at all these errors individually, and tried their various fixes to no avail. The crashes mostly happen while I am playing PUBG or Divinity 2. Chrome tabs randomly crash and sometimes the system flickers.

I have tried using each of my 8GB sticks in different slots and individually, but the blue screens keep coming, but I have not received a MEMORY_MANAGEMENT error with just the one stick installed. I have tried the windows memory checker and a third party checker loaded onto a boot USB. I have completely re-installed windows, and wiped/cleaned the drives overnight.

I am almost certain that the RAM is somehow faulty, but both sticks?? If you require any more information, please ask, I really want to get to the source of this issue and replace whatever is faulty, thanks!

Error dumps:
https://www.dropbox.com/sh/ma422vlciy7nj2k/AAATGtQoSyFbyOlPkgQYzKd9a?dl=0

DXDIAG:
pastebin

Motherboard is: Asrock super alloy Z170 EXTREME6+
10 answers Last reply Best Answer
More about lots bsods lots error types dumbfounded
  1. the second last error caused Direct X to crash. I would do this and see if it helps: http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html

    as for the rest, have you ever run memtest86? run it on 1 stick at a time, any errors are too many. the only score you want is 0 errors. If you get any errors stick needs to be replaced. If you know 1 stick works, test it on other slots and see if they do as well.

    can you go to c:\windows\minidump and copy the contents to desktop
    Upload the copies from desktop to a file sharing site and share the link here
  2. Thank you very much for your reply :)

    I have uploaded my dump files to dropbox, here is the link

    I have tried a fresh install of my graphics drivers, but it blue-screened again during the install :(

    I used memtest86 on my RAM a while back, no errors were found. I have not tried with individual RAM modules though.

    Cheers for all your help :)
  3. Looks like either a problem with the RAM or hard drive.

    Run chkdsk /r in admin powershell or command prompt on ALL partitions.
    After chkdsk is finished, post the log
    https://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html
  4. Looks good, errors fixed.

    Let us know if you keep getting BSODs.
  5. Lmao, as I was writing my reply, my Chrome tab stopped working/crashed, so here I go again.

    I was just playing some PUBG and managed to have one game with no issues, the next game, I was riding on a bike as a passenger and my PC BSOD'd. It seems nothing has worked :(

    Here is the link to all my .dmp files that I am collecting

    The error was SYSTEM_THREAD_EXCEPTION_NOT_HANDLED and was caused by dxgmms2.sys.

    This problem is completely erratic, it generally only happens while or after I finish playing PUBG or Divinity: Original Sin 2. I played Divinity for 5 hours a few nights ago with no crashes whatsoever, the next day, within one hour of gameplay I get a BSOD. Normally after the first one occurs and I try to resume gameplay, they keep coming with increased frequency.

    I can play games such as Supreme Commander for hours on end with no crashes, I can browse the web with little crashing, although Chrome acts up a bit sometimes. That is what bugs me as this came out of the blue, everything was fine, and then *poof*.

    Thank you everyone for your help :)
  6. Direct X again... when you fixed graphics card drivers before, where did you get the drivers from? If you are trying nvidia ones. run windows update instead and let windows find drivers. It might make a difference (this assumes you have an nvidia card, if AMD, the same applies)
  7. Best answer
    looks like you have two GPU tweak tools installed, I would remove them both and see if your problem goes away. looks like
    690b33e1-0462-4e84-9bea-c7552b45432a.sys

    will not pass driver verification testing. (I would remove it as a likely cause of corruption)

    remove iomap64.sys ( GPU Tweak tool)
    C:\Windows\system32\drivers\IOMap64.sys Fri Apr 28 03:02:15 2017
    http://www.carrona.org/drivers/driver.php?id=IOMap64.sys

    remove:
    C:\Program Files (x86)\ASUS\GPU TweakII\690b33e1-0462-4e84-9bea-c7552b45432a.sys

    I looked at the most current bugcheck, the stack was corrupted from some user mode service and the process was terminated and the system bugchecked.

    looking now to see if I can find the cause.

    you might want to do a Malwarebytes scan, then run powershell as an admin and run
    dism.exe /online /cleanup-image /restorehealth

    I am having the debugger check for corrupted windows files now.

    you should change your memory dump type to kernel, reboot and provide the kernel memory dump for the next time this happens.
    you might even run verifier.exe
    ie start cmd.exe or powershell as an admin then run
    verifier.exe /standard /all

    and reboot. this will check for common problems in device drivers and will make debugging a kernel memory dump much easier.

    be sure you have applied all of the windows updates and motherboard updates.
    common for motherboard audio driver to corrupt the stack.
    (in case your virus scan/ Malwarebytes scan does not turn up anything)
  8. johnbl said:
    I looked at the most current bugcheck, the stack was corrupted from some user mode service and the process was terminated and the system bugchecked.

    The stack is not corrupted. As you say the it's from usermode, because a minidump and kernel dump won't provide usermode data we can't look at those calls.

    Unless there is a driver present from a developer that doesn't know anything about driver development, there is no reason to use driver verifier.
    This bugcheck is usually caused by faulty hardware (hdd and ram mostly) or by malware attempting to modify a critical file of Windows.
  9. I would expect verifier to flag problems in
    690b33e1-0462-4e84-9bea-c7552b45432a.sys
    --------------

    frames 0c, 0f and 14 looked wrong to me. ie corrupted.

    7: kd>
    # RetAddr : Call Site
    00 fffff800`e9967091 : nt!KeBugCheckEx
    01 fffff800`e98a4025 : nt!PspCatchCriticalBreak+0xc9
    02 fffff800`e97811f6 : nt!PspTerminateAllThreads+0x122d29
    03 fffff800`e9780fb7 : nt!PspTerminateProcess+0xde
    04 fffff800`e93fe413 : nt!NtTerminateProcess+0xa7
    05 00007ffc`157b5924 : nt!KiSystemServiceCopyEnd+0x13
    06 00007ffc`15815d3f : 0x00007ffc`157b5924
    07 00690057`005c0074 : 0x00007ffc`15815d3f
    08 00007ffc`15846598 : 0x00690057`005c0074
    09 00000069`590ffad0 : 0x00007ffc`15846598
    0a 00790072`006f006d : 0x00000069`590ffad0
    0b 00000000`0000000a : 0x00790072`006f006d
    0c 00007ffc`157bcfbe : 0xa
    0d 00007ffc`15846598 : 0x00007ffc`157bcfbe
    0e 00000000`00000005 : 0x00007ffc`15846598
    0f 0065004d`00730073 : 0x5
    10 00790072`006f006d : 0x0065004d`00730073
    11 00670061`00690044 : 0x00790072`006f006d
    12 00740073`006f006e : 0x00670061`00690044
    13 00000000`00041989 : 0x00740073`006f006e
    14 00007ffc`157a6466 : 0x41989
    15 00000000`00000000 : 0x00007ffc`157a6466

    axe0axe0 said:
    johnbl said:
    I looked at the most current bugcheck, the stack was corrupted from some user mode service and the process was terminated and the system bugchecked.

    The stack is not corrupted. As you say the it's from usermode, because a minidump and kernel dump won't provide usermode data we can't look at those calls.

    Unless there is a driver present from a developer that doesn't know anything about driver development, there is no reason to use driver verifier.
    This bugcheck is usually caused by faulty hardware (hdd and ram mostly) or by malware attempting to modify a critical file of Windows.
Ask a new question

Read More

RAM Blue Screen Hardware Problem Motherboards Memory Management