Lots of BSODs different processes RAM problems?


  1. Posts : 10
    Windows 7 Professional x64
       #1

    Lots of BSODs different processes RAM problems?


    Hi, My friend is having a lot of blue screens, so I thought I'd check them with windbg and I'm a newbie so I just looked at the processes, bucket ids and googled them to see if anyone else has the problems, I am now clueless because they all seem to be different and so I need an experts opinion. I have attached all of the minidumps, I can get him to run the system finder bit if you need.

    His specs are as follows:
    i5 4440
    8GB RAM
    Windows 7
    2TB HDD
    Palit GTX 750 Ti graphics card


    If you need any more info, please ask.
    Thanks!
    Last edited by andrew89898; 11 Jan 2015 at 08:22.
      My Computer


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

    Hi.

    Before suggesting anything, it will be better to see the required data as per BSOD posting instructions.

    Click on button below ....

    It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
    Screenshots and Files - Upload and Post in Seven Forums

    Also, it cannot be nullified that there is a high probability that the memory is failing, anyhow. So, 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 results. Further troubleshooting may be needed depending on the results.
    ___________________________________
    Code:
    BugCheck 1A, {41790, fffffa80062e1f10, ffff, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )
    
    Followup: MachineOwner
    ---------
    Code:
    BugCheck 3B, {c0000005, fffff800033f6123, fffff8800a332d60, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 )
    
    Followup: MachineOwner
    ---------
    Code:
    BugCheck 50, {fffff6bc5002c020, 0, fffff800032ea6d8, 5}
    
    
    Could not read faulting driver name
    Probably caused by : memory_corruption ( nt!MiLockProtoPoolPage+38 )
    
    Followup: MachineOwner
    ---------
      My Computer


 

  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 07:24.
Find Us