Ransom BSOD's for no apparent reason/each one is different

Page 4 of 4 FirstFirst ... 234

  1. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #31

    Right, I need to know exactly how many different drivers (and what versions) you've tried for the GPU. It's possible the GPU itself is faulty, we'll get to stress testing it after you let me know which driver versions you've tried.
    To be brutally honest April it could be down to the card overheating, that rig isn't exactly a beastly gaming spec.

    As for the bug you have I have no idea whatsoever. My advice there would be to back up all of your files to an external drive and perform a clean installation of Windows. I wouldn't waste the money upgrading when you don't need to.
      My Computer


  2. Posts : 34
    Windows 7 Home Premium 64bit OEM
    Thread Starter
       #32

    Ugh sounds about right. Every GPU I've bought in the last few years from EVGA goes bad usually right before the warranty expires, which is in about a month and a half on this one. It's not overheating. Ran tests via EVGA utilities, and it passes all stress tests with flying colors. Temp avg is 41 degrees C and never goes above 68 degrees C. I've used all the drivers going from the ones released back in Feb when this started up until the most recent Beta ones, same issue. More BSOD's again, returning now to the original ones, and crashed last night when it was idle again with the original BSOD's we started with in Feb.. Was afraid you'd say that, since with my other vid cards as I said the same thing happened right before they went out *Sigh* Had no issues w/running games at Ultra period. Never have. Even when I was running it w/a GTX 460 SE, until it also went bad. Seems now hardware is created to last just long enough to go out of warranty LOL! When I worked for IBM we'd make jokes about certain depts we supported coming up on the end of their laptop warranties and how we'd be getting calls soon and have to tell them all "So Sorry, Out of Warranty Now" *Sigh* Attaching latest BSOD's just for giggles!!!
      My Computer


  3. Posts : 34
    Windows 7 Home Premium 64bit OEM
    Thread Starter
       #33

    TYVM again Boozad for all your help <3 My concern w/backing up everything atm is the image is corrupt, the files are showing eg for size etc. So if I just simply 'Back them up' and then return them after a fresh install, the files may no longer be any good or completely corrupted and the court case ones and of course I would lose the programs which together were much more expensive than the upgrade to Ultimate. Thus why I was considering the upgrade opposed to the fresh install. Since they will NOT give me new licenses on these programs 'Yet Again'.
      My Computer


  4. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #34

    You shouldn't need new licenses for programs, you should be able to reinstall any programs you've bought on any new install. You own that license and you just need to re-use the product key. I'm not convinced it's your files that are corrupt either, I'm pretty sure it's your OS although I've no way of proving that. Even if it was the case of your files being corrupt they'd still be present if you upgraded to Ultimate so either way the result would be the same.
      My Computer


  5. Posts : 34
    Windows 7 Home Premium 64bit OEM
    Thread Starter
       #35

    Unfortunately that was not the case after I lost my 3 HDD's on the PSU install. Had to contact 3 program manufacturers due to the error (Your 1 license has already been used, purchase another license) etc. And sorry I said it incorrectly. What I meant is I believe the O/S is corrupt and thought perhaps by upgrading the O/S it would over write the corrupted files and save my programs etc. Any thoughts on the most recent BSOD's? And does it still appear to you the GPU is bad? I can try a 550Ti I have floating around here somewhere and see what happens. Just been doing really rough lately and eek on working on PC's when on chemo since they cause mini seizures! Which is why Hubby did the PSU thing before (Really crappy PSU now sometimes wonder if 'That's' the problem, though voltages look fine, temps look fine, stress tests on GPU and temps on GPU look fine. Just Ugh. LOL! Was wondering if the corrupted O/S could be causing 'All of the issues'...
      My Computer


  6. Posts : 34
    Windows 7 Home Premium 64bit OEM
    Thread Starter
       #36

    Ok am pretty convinced the issue is a corrupt O/S so backed up everything 'Important' said heck w/it to the programs and going to do a full clean install after formatting the HDD. The BSOD's are just 'Too Random' and new profiles are corrupt and only one profile has the 'eg' bug which all points to a corrupt O/S as opposed to all the drivers that were fine suddenly going 'Bad' along w/the numerous O/S BSOD's *Sigh* Tried another GPU same issue. Think I've exhausted every other resource, but if something screams out at you in the latest batch of BSOD's please let me know before I start the Fun Fun process.. Esp with having to copy back over all my game saves, reinstall programs etc >< which will be about a 2 day marathon considering all the junk I have LOL! TYVM again Boozad appreciate you taking the time w/me!
      My Computer


  7. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #37

    Hi Apryldaun.

    Your latest BSODs are all different.
    Code:
    BugCheck D1, {fffff9808d980e60, 2, 0, fffff88010dc92cd}
    
    Probably caused by : L1E60x64.sys ( L1E60x64+72cd )
    -----------------------------------------------------------
    BugCheck D5, {fffff98016aaef10, 0, fffff880043cf750, 0}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+6dc )
    -----------------------------------------------------------
    BugCheck D1, {fffff3000cd0c660, 2, 1, fffff88010d4a782}
    
    Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c0 )
    -----------------------------------------------------------
    BugCheck 1A, {8885, fffffa8001160fd0, fffffa800115e000, 605}
    
    Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+115 )
    -----------------------------------------------------------
    BugCheck 3B, {c000001d, fffff800036e5125, fffff8800add2840, 0}
    
    Probably caused by : hardware ( nt!MiCompleteProtoPteFault+235 )
    -----------------------------------------------------------
    BugCheck D1, {6a, 2, 0, fffff88010236c02}
    
    Probably caused by : nvlddmkm.sys ( nvlddmkm+1b6c02 )
    Another note, the computer/motherboard is somehow old.
    Code:
    BiosVersion = 2103   
    BiosReleaseDate = 04/27/2009
    In this situation, this randomness can be associated with hardware.

    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.

    If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Stress test the CPU.
    Hardware - Stress Test With Prime95

    Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

    Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
    eXtreme Power Supply Calculator
    Also let us know the wattage of the PSU.

    Let us know the results.
      My Computer


 
Page 4 of 4 FirstFirst ... 234

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

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