Random BSOD problems in the past 2 days. Random errors at random times

Page 3 of 4 FirstFirst 1234 LastLast

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

    JacobT said:
    I moved my video card over to the second slot.
    OK, let us know how it is running now.
      My Computer


  2. Posts : 16
    Windows 7 Home Premium 64 bit
    Thread Starter
       #22

    No such luck. 2 crashes last night before i went to bed, but these don't seem to point at my graphics card this time, or at least It doesn't look like it. It's not the same driver as the video crashes. Going to run memtest again after i finish uploading this SF file.
      My Computer


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

    Arc said:
    A summery of what we have done so far:

    • Driver Verifier did not catch anything.
    • Memtest is fine.
    • Furmark is fine.
    • Prime95 is fine.
    • Power supply is enough.
    • Not overheating.

    But the hardware issue is there.
    The hardware issue continues. This time it added some other thing up, that is Ntfs.sys; the storage driver.

    Do some Disc checks.

    1. Re-seat the sata and power.

      Also change the sata cable, apply the cable in another unused port on the motherboard.
    2. Run chkdsk /f/r, following the option two of the tutorial Disk Check
    3. Seatool for dos: SeaTools for DOS and Windows - How to Use
      ** Note that your Storage controller is AHCI. So follow the information about AHCI before starting the test.

    Some ataport.sys issues are also there. Alongwith many a things, it may be a rootkit infection. Scan the system for possible virus infection with the following programs.


    Let us know the results. Probably we will be able to take the final decision seeing the results.

    ______________________________________________________________________________________
    Code:
    BugCheck A, {f4, 2, 1, fffff800030d2f74}
    
    Probably caused by : hardware ( dxgmms1!VidSchiFreeQueuePacket+a4 )
    
    Followup: MachineOwner
    ---------------------------------------------------------------------------
    BugCheck 24, {1904fb, fffff88003ae2ec8, fffff88003ae2720, fffff8800130dee3}
    
    Probably caused by : Ntfs.sys ( Ntfs!NtfsAddDelWindow+6f )
    
    Followup: MachineOwner
    ---------
      My Computer


  4. Posts : 16
    Windows 7 Home Premium 64 bit
    Thread Starter
       #24

    I will be sure to check all that once I get back up and running. Strangely enough I started memtest again for the 3rd time since this started happening and it found 2 errors almost immediately even though the previous 2 times it came up with nothing. I managed to squeeze all 4 of my RAM sticks out, and I'm testing them all 1 by one. If nothing shows on any stick then I guess one of the slots is bad even though it showed no errors before.
      My Computer


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

    Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

    Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

    How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
    How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

    No code has to be inserted here.
    It is a RAM, a bad RAM.

    But if you have got a result like that:

    No code has to be inserted here.
    It is a motherboard issue. The particular slot is bad.

    Another point: sometimes some boards fail to work with all the DIMM slots are occupied. Have one more test. Use two RAM modules only and let the computer run.
      My Computer


  6. Posts : 16
    Windows 7 Home Premium 64 bit
    Thread Starter
       #26

    I tested each stick individually for 10 passes. All 4 sticks reported no errors after 10 passess of memtest. Now I'm going to run 10 tests with a stick on the other 3 slots.
      My Computer


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

    I would suggest you to use two RAM sticks only, for a test. Use two sticks and let the computer run for a few time and observe if it is causing BSODs there or not.
      My Computer


  8. Posts : 16
    Windows 7 Home Premium 64 bit
    Thread Starter
       #28

    Okay so where I'm at so far. I have tested all 4 sticks of RAM individually for 10 passes each (about 4 and a half hours for each one. it took forever) I also tested the two end slots. The two closest to the CPU are the ones under the heatsink, and are a bit awkward to get to without removing it. I'm running right now with 2 RAM sticks in the two end slots since I know for now that is good. I did the full disk check and repair using the CMD that took about 2 hours, but no errors. I have also ran the Sea tools program for what I'm able to test with it and also no errors on that. I also scanned my computer using one of the anti-rootkit programs you listed above, and that also came back with no threats found. I'm going to run this computer as normal for awhile on the 4GB on RAM I have installed right now to see if it's stable. If I get no BSOD I'll assume one of the other 2 RAM slots is bad and run memtest on them to find out which/if are both of them are bad.
      My Computer


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

    Usually if the RAM slots are too near to the heatsink, it causes issues when those slots are occupied.
      My Computer


  10. Posts : 13
    Windows 7 Professional 32 bit
       #30

    Random BSODs


    Am new here. And I too am suffering from random BSODs.
    Had faulty RAMs, and have replaced them. And still BSOD
    I seriously need help guys.
      My Computer


 
Page 3 of 4 FirstFirst 1234 LastLast

  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 09:45.
Find Us