Custom built PC BSOD playing Outlast and other games

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 7 Ultimate 64 Bit
       #1

    Custom built PC BSOD playing Outlast and other games


    I had BSOD problems this summer (was running 4 sticks of ram, 2 Patriot and 2 Kingston). They went almost completely away when I took out the Patriot sticks and a PCI to USB adapter that seemed to be sitting in the slot crooked when the support screw was all the way in. BSOD's started recurring when I attempted to play Outlast, eventually leading to me being unable to go more than a few minutes without one.
      My Computer


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

    Hello rjcooley.

    How old the Western Digital SiliconEdge BlueSSD is?
    Make it sure that it is running with the up-to-date firmware. WD Support / Installation / SSD / WD SiliconEdge Blue
    Also, it is almost full .... which is enough to make it crash to BSOD.

    No code has to be inserted here.

    Salvage some space. At first, disable hibernate.

    The latest version of the display driver is buggy in cases. Install the 314.22 WHQL only.

    • Uninstall All nvidia items in Control Panel > Programs and features
      • 3D Vision Control Driver
      • 3D Vision Driver
      • Graphics Driver
      • HD Audio Driver
      • PhysX
      • nvidia Update

      (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
    • Now follow Drivers - Clean Left over Files after Uninstalling
    • Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:


    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.

    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Is the computer running hot? Let us see. Upload a snapshot Using Speccy.


    Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
    eXtreme Power Supply Calculator
    Also let us know the wattage of the PSU.

    Let us know the results.
      My Computer


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

    How old the Western Digital SiliconEdge BlueSSD is?
    3 years or so. I bought it almost a year ago from someone who said he'd built it 2 years prior. I cleared space so there's about 15 GB free now, and that site indicated that there were no available downloads for the SSD.

    The latest version of the display driver is buggy in cases. Install the 314.22 WHQL only.
    I uninstalled all the NVIDIA things you listed. Not sure how to tell if I'm using the chipset drivers. I then tried installing the 314.22 WHQL driver and got this error: "NVIDIA Installer cannot continue. The graphics driver could not find compatible graphics hardware."

    I will run memtest when I have more time as well. FurMark gives me the error "Could not initialize ZoomGPU. FurMark startup failed. Bye!" I imagine it might have something to do with the lack of video drivers, but I'm not sure.
      My Computer


  4. Posts : 7
    Windows 7 Ultimate 64 Bit
    Thread Starter
       #4

    Oh, and eXtreme Power Supply Calculator suggests at least 609W for the power supply. Mine is 850.
      My Computer


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

    Hmm ... 314.22 WHQL does not support Geforce GTX 780. I did not notice it earlier, my bad. You get the 320.49 version back, and wait for another driver update. Nothing more to do there.

    Furmark does not work in absence of a display driver. Try it again after installing the driver back.

    The power supply is enough. Nothing to be worried about it.

    Its good that you salvaged some free space. Definitely it will make some good behavior there. Now test how it is running, and let us know :)
      My Computer


  6. Posts : 7
    Windows 7 Ultimate 64 Bit
    Thread Starter
       #6

    So I ran into more BSOD's for a while and ended up removing my GPU and all but 1 stick of RAM. That seemed to be working, and seemed to be continuing to work when I put in another stick of RAM and the GPU, but after leaving my computer idling for a while, I returned to find another BSOD had occurred. I ran memtest86+ for 10 passes with the 2 Kingston memory sticks in and got 0 errors, and I ran FurMark and attached my results for that as well as another zip file containing more BSOD minidump data.
      My Computer


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

    Oh, and I reinstalled Windows 7 before the most recent BSOD's.
      My Computer


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

    Arc said:
    Hello rjcooley.

    How old the Western Digital SiliconEdge BlueSSD is?
    Make it sure that it is running with the up-to-date firmware. WD Support / Installation / SSD / WD SiliconEdge Blue
    Also, it is almost full .... which is enough to make it crash to BSOD.
    You say there is no firmware updates over 3 years? That is bad.

    As a test, try installing Windows in another HDD, say the 1 TB seagate. There is a lot of free space on the D drive. Cut 100 GBs out and install Windows there ..... to test how it goes on there.

    I am suspecting the SSD is failing.

    But if you want to do what I suggest and you dont have proper idea about what exactly is to do ... let us know. We can assist you in the process.
    ___________________________________________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 34, {50853, fffff8800314c5f8, fffff8800314be50, fffff80002ed4470}
    
    Probably caused by : memory_corruption ( nt!MmCheckCachedPageStates+3f0 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    CACHE_MANAGER (34)
        See the comment for FAT_FILE_SYSTEM (0x23)
    Arguments:
    Arg1: 0000000000050853
    Arg2: fffff8800314c5f8
    Arg3: fffff8800314be50
    Arg4: fffff80002ed4470
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_RECORD:  fffff8800314c5f8 -- (.exr 0xfffff8800314c5f8)
    ExceptionAddress: fffff80002ed4470 (nt!MmCheckCachedPageStates+0x00000000000003f0)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 000063e000016c91
    Attempt to read from address 000063e000016c91
    
    CONTEXT:  fffff8800314be50 -- (.cxr 0xfffff8800314be50)
    rax=63e000016c914900 rbx=000063e000016c91 rcx=ffffffffffffffff
    rdx=0000000000000011 rsi=fffff6fcc008b600 rdi=0000000000000001
    rip=fffff80002ed4470 rsp=fffff8800314c830 rbp=fffff8800314c880
     r8=0000000000000000  r9=fffffa8006031c80 r10=0000000000000000
    r11=0000000000000000 r12=000063e000016c91 r13=0000000000000000
    r14=fffff6fcc008b7f8 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    nt!MmCheckCachedPageStates+0x3f0:
    fffff800`02ed4470 498b1c24        mov     rbx,qword ptr [r12] ds:002b:000063e0`00016c91=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  000063e000016c91
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f6100
    GetUlongFromAddress: unable to read from fffff800030f61c0
     000063e000016c91 Nonpaged pool
    
    FOLLOWUP_IP: 
    nt!MmCheckCachedPageStates+3f0
    fffff800`02ed4470 498b1c24        mov     rbx,qword ptr [r12]
    
    FAULTING_IP: 
    nt!MmCheckCachedPageStates+3f0
    fffff800`02ed4470 498b1c24        mov     rbx,qword ptr [r12]
    
    BUGCHECK_STR:  0x34
    
    LAST_CONTROL_TRANSFER:  from fffff80002eacf1e to fffff80002ed4470
    
    STACK_TEXT:  
    fffff880`0314c830 fffff800`02eacf1e : fffff980`116c0000 00000000`00040000 fffffa80`00000000 fffffa80`10055801 : nt!MmCheckCachedPageStates+0x3f0
    fffff880`0314c9e0 fffff800`031267c1 : fffff880`00000000 00000000`c00000d8 fffffa80`10055860 fffffa80`0c364e00 : nt!CcFetchDataForRead+0x10e
    fffff880`0314ca40 fffff800`02e6bda8 : fffffa80`10055860 00000000`03200000 00000000`00040000 fffffa80`067fa040 : nt!CcMapAndCopyFromCache+0xc5
    fffff880`0314cad0 fffff800`02f03b4e : fffffa80`10055860 fffffa80`067fa000 fffff880`00000005 fffff880`04343734 : nt!CcPerformReadAhead+0x3b8
    fffff880`0314cc00 fffff800`02ec8251 : fffffa80`0671b530 fffff800`031b6d01 fffff800`030c58d0 fffffa80`00000000 : nt!CcWorkerThread+0x21e
    fffff880`0314ccb0 fffff800`0315cede : 00000000`00000000 fffffa80`067fa040 00000000`00000080 fffffa80`0670a040 : nt!ExpWorkerThread+0x111
    fffff880`0314cd40 fffff800`02eaf906 : fffff880`03088180 fffffa80`067fa040 fffff880`03093040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`0314cd80 00000000`00000000 : fffff880`0314d000 fffff880`03147000 fffff880`0314c6e0 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!MmCheckCachedPageStates+3f0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6
    
    STACK_COMMAND:  .cxr 0xfffff8800314be50 ; kb
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x34_nt!MmCheckCachedPageStates+3f0
    
    BUCKET_ID:  X64_0x34_nt!MmCheckCachedPageStates+3f0
    
    Followup: MachineOwner
    ---------
      My Computer


  9. Posts : 7
    Windows 7 Ultimate 64 Bit
    Thread Starter
       #9

    No good. I installed Windows 7 on the HDD and removed the SSD. I ended up with another BSOD (PFN_LIST_CORRUPT) while downloading updates for windows and a game through Steam.
      My Computer


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


 
Page 1 of 2 12 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 10:09.
Find Us