How do you personalize, *I had a BSOD?* Cause that's what happened.


  1. Posts : 73
    Windows 10 Pro
       #1

    How do you personalize, *I had a BSOD?* Cause that's what happened.


    After some confusion about this section last time, I'm pretty sure that blue screen that came up and said AHHHHH YOU DIED!!!!!! (well it didn't say that, I translated), was a BSOD.

    My computer crashes regularly, and since I am about to build a new one, I upped the voltages on my 4 cores a little (trying to stop the non bsod crashes). It seems to have worked, been a few day, then this BSOD while I was playing WOT and listening to SPOTIFY (that's usually what I'm doing when my computer crashes because that is what I mostly do lol).

    Given that it's been a couple or three days of continuous use since I upped the voltages (still in the green zone, before they were the lowest voltage in the green that was *stable*) it seems like that wouldn't be the cause, but it IS the only thing recently that has been changed. I also suspect some audio problems as well but don't know where that factors in. Anyway, here is the file;


    Attachment 118622
      My Computer


  2. Posts : 1,656
    Windows 10 Pro x64
       #2

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {ffff81fc82bd4ca8, 2, 0, fffff800b2f30272}
    
    *** WARNING: Unable to verify checksum for win32k.sys
    Probably caused by : memory_corruption
    
    Followup:     memory_corruption
    ---------
    Run a minimum of 8 passes of MemTest86+
    MemTest86+ - Test RAM
      My Computers


  3. Posts : 73
    Windows 10 Pro
    Thread Starter
       #3

    While I guess smoking a computer WILL prevent anymore BSOD's, or anything other than a blank black screen, it wasn't quite the solution I was looking for. I guess I am now out of time on my build research......... but hey, I can devote all my time on it now. I mean I already put the fire out on this one so other than taking a sledge to the hard drive this one requires no more time.

    While technicslly *solved*, i just can't make myself hit the solved button on something that torched my rig. But thanks for the try lol
      My Computer


  4. Posts : 1,656
    Windows 10 Pro x64
       #4

    Are you implying running MemTest86+ would somehow destroy the computer?
      My Computers


  5. Posts : 73
    Windows 10 Pro
    Thread Starter
       #5

    Golden said:
    Are you implying running MemTest86+ would somehow destroy the computer?
    I'm not implying anything, I think I was quite clear lol. I watched it happen. I ran MEMtesat and stuff started blowing up....... figuratively. This thing was old and on it's last legs so Memtest DID in fact kill it much like a marathon would kill a lifelong smoker with lung cancer.

    SO if you try to give him mouth to mouth when he collapses and his lungs explode.........

    I could have counted beeps and looked up post codes and whatnot to figure out EXACTLY what died first, but why waste the time of the person helping me (you). If I could keep this on life support, great, but since it can't, I'll pull out what can be used, trash the rest and go on. I'm typing this on a new computer already as I'm setting it up. I typed the last on a phone this morning to update you and hopefully give you a laugh. Maybe a visual of a cartoon dude with a blowed up computer in his face with his hair all frazzled and stuff......

    Anyway, thanks for the help. And despite the joke, I think we CAN call this solved.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 13:27.
Find Us




Windows 10 Forums