1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Windows Vista 0x0000007F BSOD

Discussion in 'Legacy Windows' started by spike99, 2008/03/28.

  1. 2008/03/28
    spike99

    spike99 Inactive Thread Starter

    Joined:
    2008/01/07
    Messages:
    33
    Likes Received:
    0
    Hi,

    Last night I bougth a new thermal paste (OCZ Freeze) and wanted to see if it made any difference in terms of temperature... so I ran some stability tests with Everest (before & after). I usually run stability test for ~ 10mins but in one of the runs I noticed a "hardware error" displayed in Everest. I restarted PC and ran stability test with no issues.

    After i stopped stability test I received a klif.sys BSOD. I looked around and this appears to be related to Kapersky (I currently have Kapersky).

    To experiment, I booted into "safe mode" and within 2 mins, PC rebooted without giving any error messages. My PC has a history of reseting BIOS settings so I wanted to take pics of BIOS settings just in case. When i went to BIOS, screen would freeze less than 1 minute and I was no longer able to navigate thru BIOS settings... I would repeatedly restart PC to get additional screens but PC still froze while in BIOS settings.

    I gave it a rest and this morning i let PC boot to windows and within 2 mins, i got a BSOD but with a different error. This time I got 0x0000007F.

    I currently overclock my PC from 3GHz to 3.66GHz. I was reading around and this seems to indicate a bad memory module (I have 2 sticks of 2GB of RAM)or motherboard problem.

    If the problem is either RAM or MOBO.... What should i be doing to check which one is the problem ?

    Any other suggestions, would be appreciated...

    Thanks in advance.
     
  2. 2008/03/28
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Run with one RAM module - switch it around the slots and test - repeat for other module. This will show if it is a specific RAM module or a dud slot on the mobo. Then run as a pair and switch between pairs of slots.

    I would be very inclined to dump the overclocking until you have this issue resolved.
     

  3. to hide this advert.

  4. 2008/03/30
    spike99

    spike99 Inactive Thread Starter

    Joined:
    2008/01/07
    Messages:
    33
    Likes Received:
    0
    Hi Pete,

    Yes, I tested each RAM module on and tested. One RAM gave over 2,000 errors and the other gave over 7,000 errors running Memtest+86 v2.01.

    I tested 1 RAM on each slot and it appears that I have a bad/dud slot on the MOBO.

    Currently in the process of RMA'ing MOBO & memory sticks... argh!!

    What is odd to me is to have both RMA sticks going bad at the same time...that seems a bit odd to me...
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.