Random BSOD

Page 4 of 7 FirstFirst ... 23456 ... LastLast

  1. Posts : 30
    Windows 7 Ultimate X64
    Thread Starter
       #31

    Thanks! Have not had to do such exhaustive testing before so a little anxious but rushing gets me nowhere!

    With post when I know more!
      My Computer


  2. Posts : 12,177
    Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
       #32

    Your CPUZ file and the MSinfo32 file are saying you only have 3 CPU cores.
    Go to Task Manager > Resource Monitor and check the CPU tab, make sure all four cores are recognized.

    It also shows your RAM running at 800MHz (actual 1600MHz), this is a known problem for AMD CPUs, set the RAM to run at maximum 667MHz (1333MHz).
    This has been known to stop AMD systems from constant BSoDs.
    Even though your RAM passed memtest86+, this may still be causing problems.
    Once the system is stable you can try and OC the RAM.
    If it's stable at 1333MHz then you know the cause.

    Also noticed the RAM has XMP settings, this is a feature for Intel system RAM, which may or may not run very well on an AMD system.
    We might need to come back to this later.

    If you want to change your BIOS from IDE to AHCI/RAID, it's best to do before you install the OS. There is a way to change it with the OS installed, best to leave this until the system is stable.

    Your first crash dump is Driver Verifier enabled, and blames RAM which may be a result of the RAM frequency issue.
    If you haven't already, disable Driver Verifier.
    Driver Verifier - Enable and Disable
    A PFN_LIST_CORRUPT (4e) is usually due to corrupt RAM, again the frequency issue.

    From first dump files posted:
    Code:
    STOP 0x0000004E: PFN_LIST_CORRUPT
    Usual causes:  Device driver, ?memory 
    Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+8d )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    IMAGE_NAME:  memory_corruption
    FAILURE_BUCKET_ID:  X64_0x4E_2_VRF_nt!MiUnlinkPageFromLockedList+8d
    --------------------------------------------------------------------------------------------------------------------------------
    STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,
    This is a very common bugcheck.
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0x7E
    FAILURE_BUCKET_ID:  X64_0x7E_VRF_nt!ExFreePoolWithTag+43
    --------------------------------------------------------------------------------------------------------------------------------
    Same as above, except:
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    --------------------------------------------------------------------------------------------------------------------------------
    STOP 0x000000C1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION 
    Usual causes:  Device driver, ?Memory
    Probably caused by : memory_corruption ( nt!MmFreeSpecialPool+374 )
    Special pool has detected memory corruption.  Typically the current thread's
    stack backtrace will reveal the guilty party.
    Arguments:
    Arg1: fffff98018c90ee0, address trying to free
    Arg2: fffff98018c90ff8, address where bits are corrupted
    Arg3: 0000000000f30118, (reserved)
    Arg4: 0000000000000024, caller is freeing an address where bytes after the end of the allocation have been overwritten
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    IMAGE_NAME:  memory_corruption
    Looks like a memory issue.

    Second dump files:
    Code:
    STOP 0x0000001A: MEMORY_MANAGEMENT
    Usual causes:  Device driver, memory, kernel
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  MsMpEng.exe
    FAILURE_BUCKET_ID:  X64_0x1a_5005_nt!_??_::FNODOBFM::_string_+20fc0
    Most important is to check the CPU core issue, this may be indicating an issue with the CPU, bent pins or faulty CPU.
    Next is change the RAM frequency to 1333MHz for testing.
    Download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
    For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
    How to Post a Screenshot in Seven Forums
    Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.
    Last edited by Dave76; 05 Nov 2012 at 04:47.
      My Computer


  3. Posts : 30
    Windows 7 Ultimate X64
    Thread Starter
       #33

    Dave76 said:
    Go to Task Manager > Resource Monitor and check the CPU tab, make sure all four cores are recognized.

    2nd core was turned off in BIOS. Resource monitor showing all 4 running.

    It also shows your RAM running at 800MHz (actual 1600MHz), this is a known problem for AMD CPUs, set the RAM to run at maximum 667MHz (1333MHz).
    This has been known to stop AMD systems from constant BSoDs.
    Even though your RAM passed memtest86+, this may still be causing problems.
    Once the system is stable you can try and OC the RAM.
    If it's stable at 1333MHz then you know the cause.

    Remembered reading about this when putting the system together and apparently forgot to change it. Thanks for pointing this out.

    Also noticed the RAM has XMP settings, this is a feature for Intel system RAM, which may or may not run very well on an AMD system.
    We might need to come back to this later.

    Will look in BIOS and turn it off when in there.

    If you want to change your BIOS from IDE to AHCI/RAID, it's best to do before you install the OS. There is a way to change it with the OS installed, best to leave this until the system is stable.

    Changed it in the BIOS before installing Windows on original build but gave me problems so went back to IDE. Found out a few months later that my HD was on it's way out and never went back to change. Not really concerned one way or another as I have noticed no major benefit to having AHCI on a single drive.

    Your first crash dump is Driver Verifier enabled, and blames RAM which may be a result of the RAM frequency issue.
    If you haven't already, disable Driver Verifier.

    Done.

    Most important is to check the CPU core issue, this may be indicating an issue with the CPU, bent pins or faulty CPU.

    Ran HotCPU tester PRO 2x's before coming on here looking for help. No issues were noted. CPU core "issue" has been fixed, as BIOS had 2nd core turned off.

    Next is change the RAM frequency to 1333MHz for testing.

    Done.

    Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

    Only one I changed is the RAM - set at 1.5v. Do not see anything that says CPU or CPU integrated memory controller, with regards to voltages. Is it under another name?
    Response in blue.
    Last edited by mp1cass0; 06 Nov 2012 at 12:23.
      My Computer


  4. Posts : 30
    Windows 7 Ultimate X64
    Thread Starter
       #34

    Update - did a diskpart/cleanall, eliminated all partitions, installed Windows, installed all drivers via Windows, except my network drivers (from MB CD and checked for update once online). Installed Abobe Reader, Java, MSE, and Malwarebytes, all listed on "Clean Install - Factory OEM". According to Windows Update, all files have been installed.

    Question - I have an Epson Artisan 837 printer that I use for work (I work from home). Installed via Windows update but then clicked on "update drivers" from Start menu link (downloaded from Epson). Should I use System Restore and go back to a time before that? to make sure nothing other than Windows "approved" drivers were installed? Or see how things go, keeping it in the back of my head?
      My Computer


  5. Posts : 6,458
    x64 (6.3.9600) Win8.1 Pro & soon dual boot x64 (6.1.7601) Win7_SP1 HomePrem
       #35

    I wouldn't worry about the printer driver.
    Run your machine as normal and focus on the BSOD- report any new occurrences
      My Computer


  6. Posts : 10,994
    Win 7 Pro 64-bit
       #36

    Slartybart said:
    I wouldn't worry about the printer driver.
    Run your machine as normal and focus on the BSOD- report any new occurrences

    ^^^What Bill said. :)
      My Computer

  7.    #37

    Just guard both places in msconfig per the tutorial to make sure nothing Epson sneaks in, unless you need scan function to show up on your desktop when you initiate it on printer. In that case if it doesn't I would test enable each Epson listing in msconfig. If that doesn't suffice you may need to do a Custom install of latest Printer software package leaving out all the unneeded (shopping, update) choices.
      My Computer


  8. Posts : 30
    Windows 7 Ultimate X64
    Thread Starter
       #38

    This is what my msconfig looks like for startup.
      My Computer

  9.    #39

    Very clean. My compliments.

    You didn't say if your Epson requires a scan initiated on the printer to show up on PC desktop. If not you likely don't need that listing unless you lose some other functionality without it.

    How about a screenie of Services tab after Hiding All MS Services? You're on a roll.
      My Computer


  10. Posts : 30
    Windows 7 Ultimate X64
    Thread Starter
       #40

    Not at home at the moment but it was only 2. AMD external events utility and Adobe Acrobat updater. Went into Adobe Acrobat reader, turned off automatic updates, and disabled AMD through services.

    I usually initiate scan from printer so will switch Epson to manual and see how if that works.
      My Computer


 
Page 4 of 7 FirstFirst ... 23456 ... 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 12:33.
Find Us