BSOD While doing anything (at least 6 different ones)


  1. Posts : 1
    Windows 7 Home Premium 64bit
       #1

    BSOD While doing anything (at least 6 different ones)


    For a long time I have gotten Blue Screens and it has been hard for me to pinpoint the problem on my own and it has finally got to me enough to post about it. I got one making this post the first time and one playing league earlier this morning. Nothing in particular seems to set them off. Hopefully you guys can help me out here.

    Attachment 355533
      My Computer


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

    Hi RShoua.

    Uninstall McAfee security scan plus. It is one thing you have got unintentionally, and it is problematic. Be careful while updating flash player, dont install it back.

    Stress test the Graphics Card using Furmark.Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

    Test your RAM modules for possible errors. Run memtest86+ for at least 8 consecutive passes.

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

    Let us know the result.
    __________________________________
    Code:
    BugCheck 10E, {1f, fffff8a00d3b9e50, 0, eb86a}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148 )
    
    Followup: MachineOwner
    ---------
    Code:
    BugCheck DE, {2, fffff8a00c301a48, fffffaa00cb01a49, 11664b8c6}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c8e1 )
    
    Followup: MachineOwner
    ---------
    Code:
    BugCheck 3B, {c0000005, fffff80002facde3, fffff88008c04a20, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 )
    
    Followup: MachineOwner
    ---------
    Code:
    BugCheck 50, {fffff6fcd00f4b38, 0, fffff80002eb154b, 2}
    
    
    Could not read faulting driver name
    Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 )
    
    Followup: MachineOwner
    ---------
      My Computer


 

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 15:35.
Find Us