Random BSOD--Several different codes back to back. New computer.


  1. Posts : 3
    Windows 7 64 Bit
       #1

    Random BSOD--Several different codes back to back. New computer.


    Computer seems stable and then will randomly BSOD-- Doesnt seem to be consistent with what im doing. A few of the BSOD's came after a 'error memory reference line' or something like that.

    Computer is new, I installed drivers with supplied disks from motherboard manufacturer (asus). At first I thought it was the memory because Id read people having issues running 1866mhz ram with their Asus 990FX sabertooth, so I let it 'auto clock' and it chose 1333, But im still getting BSOD after that, tried adjusting voltage with no success either.

    Please help, its very frustrating.. If I need to reinstall windows that is not an issue, I just need to stop the blue screens.
      My Computer


  2. Posts : 2,014
    Windows 7 Professional 64bit
       #2

    Hi,


    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 19, {3, fffff88006dfb570, fffff88006df9170, fffff88006dfb570}
    Probably caused by : Pool_Corruption
    STOP 0x00000019: BAD_POOL_HEADER
    Usual causes: Device driver
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 3B, {c0000005, fffff80002d12dac, fffff8800b8a6dc0, 0}
    Probably caused by : memory_corruption
    STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
    Usual causes: System service, Device driver, graphics driver, ?memory

    fffff880`0b8a6978 fffff880`01035f29Unable to load image \SystemRoot\system32\drivers\mfehidk.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for mfehidk.sys
    *** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
    mfehidk+0x35f29
    Related to: McAfee Host Intrusion Detection Link Driver
    Please uninstall MCafee as it is one cause of your crashes.

    As an alternative install Microsoft Security Essentials.
    Recommended from a strict BSOD perspective, compatibility & stability
    compared to other antiviruses/internet security software.

    Microsoft Security Essentials - Microsoft Windows

    Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

    https://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

    Run SFC to check the integrity of all Windows 7 system files:

    Click on the Start > Type in search cmd
    Right click cmd at top and Run as Administrator
    Type SFC /scannow at the prompt (note the space between SFC and /scannow)

    https://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

    Also please ensure all Windows Updates are installed.

    Post back any results/observations and/or a new crash dump if you experience another crash.

    cheers
    Dave
      My Computer


  3. Posts : 3
    Windows 7 64 Bit
    Thread Starter
       #3

    Noticed that when the computer boots, the Wifi card that I let windows install takes longer than anything else, just sitting there, and then it goes. Its the only thing that lags on the system when I boot it.

    sfc /scannow didnt find any integrity violations. Ill run memtest next. Thanks for the help, I uninstalled mcaffee, if we cant fix the issues I will just reformat the computer--Its only irritating because I hardly had anything installed when the BSOD started (within the first 30 minutes) so its hard to tell whether it was software or not.
      My Computer


  4. Posts : 2,014
    Windows 7 Professional 64bit
       #4

    Thanks for the feedback.
    Mcafee drivers definately contributed to one of your crashes

    And probable memory issues could explain the BSOD after 30 mins.

    Lets see how you get on with memtest

    cheers

    Dave
      My Computer


  5. Posts : 3
    Windows 7 64 Bit
    Thread Starter
       #5

    Memtest confirms its bad Ram. Ill be RMA'ing through newegg. Thanks for the help!
      My Computer


  6. Posts : 2,014
    Windows 7 Professional 64bit
       #6

    No problem, glad to help.
    Please mark this thread as solved if you feel it has been.

    cheers

    Dave
      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 04:22.
Find Us