EVGA

New Build Problem with Drivers

Author
RobbieB
New Member
  • Total Posts : 8
  • Reward points : 0
  • Joined: 2015/04/28 14:06:37
  • Status: offline
  • Ribbons : 0
2015/04/28 14:29:08 (permalink)
Please help, I need someone smarter than me!
 
I just recently constructed a custom build, below are the specs:
 
EVGA Z97 Classified w/ i7-4790K @ 4.0 GHz
WD20EZRX 2T HDD, Samsung 840 EVO 500GB SSD, HyperX Fury 2x8 GB RAM  
EVGA GeForce GTX 750
Win7/64 Professional

The short version is, I'm having some blue screen problems and have narrowed my troubleshooting to the drivers.  I need help on how and which drivers to update.  Almost all of my drivers are provided by Microsoft and are standard dated to 6/21/06.  I'm no expert, but pretty sure 9 year old drivers can't be right, and I don't necessarily want Microsoft generic drivers.  I was planning on just going through the whole device manager list and one by one trying to update them all (and of course the windows auto search for updates is useless).  The drivers I feel like are the highest priority are my Chipset drivers (I found 8 with varying titles after Intel(R) 9 Series Chipset Family).  The Chipset Family SMBus Host Controller is the only one I could update, I assume from the Intel Chipset Update Utility I downloaded, but what about the rest?  And there are a ton more important sounding devices in the System Devices category of the Device Driver.
 
Im trying to figure out which devices actually matter, and where I can find the drivers so I can manually update them.  Any pointers would be greatly appreciated!
#1

15 Replies Related Threads

    CptSpig
    SSC Member
    • Total Posts : 736
    • Reward points : 0
    • Joined: 2011/11/21 11:12:11
    • Location: Sunny California
    • Status: offline
    • Ribbons : 1
    Re: New Build Problem with Drivers 2015/04/28 14:47:13 (permalink)
    Here you will find the latest drivers for your board. http://www.evga.com/support/download/default.aspx




     
    #2
    bcavnaugh
    The Crunchinator
    • Total Posts : 38977
    • Reward points : 0
    • Joined: 2012/09/18 17:31:18
    • Location: USA Affiliate E5L3CTGE12 Associate 9E88QK5L7811G3H
    • Status: online
    • Ribbons : 282
    Re: New Build Problem with Drivers 2015/04/28 14:49:51 (permalink)
    I would start with the Base Drivers that come on the DVD that came with your Motherboard.

    Associate Code: 9E88QK5L7811G3H


     
    #3
    Sajin
    EVGA Forum Moderator
    • Total Posts : 49165
    • Reward points : 0
    • Joined: 2010/06/07 21:11:51
    • Location: Texas, USA.
    • Status: online
    • Ribbons : 199
    Re: New Build Problem with Drivers 2015/04/28 15:06:27 (permalink)
    RobbieB
    Please help, I need someone smarter than me!
     
    I just recently constructed a custom build, below are the specs:
     
    EVGA Z97 Classified w/ i7-4790K @ 4.0 GHz
    WD20EZRX 2T HDD, Samsung 840 EVO 500GB SSD, HyperX Fury 2x8 GB RAM  
    EVGA GeForce GTX 750
    Win7/64 Professional

    The short version is, I'm having some blue screen problems and have narrowed my troubleshooting to the drivers.  I need help on how and which drivers to update.  Almost all of my drivers are provided by Microsoft and are standard dated to 6/21/06.  I'm no expert, but pretty sure 9 year old drivers can't be right, and I don't necessarily want Microsoft generic drivers.  I was planning on just going through the whole device manager list and one by one trying to update them all (and of course the windows auto search for updates is useless).  The drivers I feel like are the highest priority are my Chipset drivers (I found 8 with varying titles after Intel(R) 9 Series Chipset Family).  The Chipset Family SMBus Host Controller is the only one I could update, I assume from the Intel Chipset Update Utility I downloaded, but what about the rest?  And there are a ton more important sounding devices in the System Devices category of the Device Driver.
     
    Im trying to figure out which devices actually matter, and where I can find the drivers so I can manually update them.  Any pointers would be greatly appreciated!


    What are the BSOD codes?
     
    CptSpig
    Here you will find the latest drivers for your board. http://www.evga.com/support/download/default.aspx


    This is a good place to start. To get the very latest drivers go to www.station-drivers.com 
    #4
    RobbieB
    New Member
    • Total Posts : 8
    • Reward points : 0
    • Joined: 2015/04/28 14:06:37
    • Status: offline
    • Ribbons : 0
    Re: New Build Problem with Drivers 2015/04/28 15:18:45 (permalink)
    Thanks for the replies.  I tried the chipset drivers from the EVGA site, but if it did anything, its not apparent in the device manager.  I had a similar experience loading the drivers off the MB software.  The load says it was successful, but when I look at my devices there isn't any evidence of an update.  
     
    The blue screens started from day 1, and and include, but are not limited to csrss.exe, winnit.exe., and the occassional memory corruption.  I did all the hardware tests I could get my hands on, MemTest 86+, Intel Burn Test, Performance Testing that came with my SSD, but nothing seems wrong with the hardware.  I also ran windows off both hard drives and got the same blue screens.  My only other thought was that the problem was my OS.  I originally booted the computer off of an upgrade version of windows 7 home premium, so maybe since it wasn't a full version there were issues?  But then I just recently bought and did a fresh install of professional and am having the same problems.  The drivers is the only other glaring piece of suspicious evidence I can find...
    #5
    Sajin
    EVGA Forum Moderator
    • Total Posts : 49165
    • Reward points : 0
    • Joined: 2010/06/07 21:11:51
    • Location: Texas, USA.
    • Status: online
    • Ribbons : 199
    Re: New Build Problem with Drivers 2015/04/28 16:06:15 (permalink)
    To help you with your BSOD you will need to post the BSOD codes or .dmp files. I believe it's normal for some of the Intel(R) 9 Series Chipset Family to be 6/21/06.
    #6
    RobbieB
    New Member
    • Total Posts : 8
    • Reward points : 0
    • Joined: 2015/04/28 14:06:37
    • Status: offline
    • Ribbons : 0
    Re: New Build Problem with Drivers 2015/04/28 16:22:03 (permalink)
    Yeah, I hear what you're saying about the chipset drivers, but ALL of my drivers?  
     
    You asked for it...
     
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa8012412b30, Terminating object
    Arg3: fffffa8012412e10, Process image file name
    Arg4: fffff80002fc0940, Explanatory message (ascii)
    Debugging Details:
    ------------------

    PROCESS_OBJECT: fffffa8012412b30
    IMAGE_NAME: csrss.exe
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    MODULE_NAME: csrss
    FAULTING_MODULE: 0000000000000000
    PROCESS_NAME: csrss.exe
    EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
    BUGCHECK_STR: 0xF4_IOERR
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    CURRENT_IRQL: 0
    STACK_TEXT:
    fffff880`02a71e38 fffff800`03050342 : 00000000`000000f4 00000000`00000003 fffffa80`12412b30 fffffa80`12412e10 : nt!KeBugCheckEx
    fffff880`02a71e40 fffff800`030065ab : ffffffff`ffffffff fffffa80`12b23060 fffffa80`12412b30 fffffa80`12412b30 : nt!PspCatchCriticalBreak+0x92
    fffff880`02a71e80 fffff800`02f740cc : ffffffff`ffffffff 00000000`00000001 fffffa80`12412b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x2a546
    fffff880`02a71ed0 fffff800`02cbbcd3 : fffffa80`12412b30 fffff800`c0000006 fffffa80`12b23060 00000000`006d0f80 : nt!NtTerminateProcess+0xf4
    fffff880`02a71f50 fffff800`02cb8290 : fffff800`02d3d519 fffff880`02a72a38 fffff880`02a72790 fffff880`02a72ae0 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`02a720e8 fffff800`02d3d519 : fffff880`02a72a38 fffff880`02a72790 fffff880`02a72ae0 00000000`006d1c90 : nt!KiServiceLinkage
    fffff880`02a720f0 fffff800`02cbc0c2 : fffff880`02a72a38 00000000`00013600 fffff880`02a72ae0 00000000`006d1768 : nt! ?? ::FNODOBFM::`string'+0x48554
    fffff880`02a72900 fffff800`02cbac3a : 00000000`00000000 000007fe`fd56d8c0 00000000`00000001 00000000`00013600 : nt!KiExceptionDispatch+0xc2
    fffff880`02a72ae0 00000000`77838fa2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
    00000000`006d16b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77838fa2

    STACK_COMMAND: kb
    FOLLOWUP_NAME: MachineOwner
    FAILURE_BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe
    BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe
    Followup: MachineOwner
    ---------
    2: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa8012412b30, Terminating object
    Arg3: fffffa8012412e10, Process image file name
    Arg4: fffff80002fc0940, Explanatory message (ascii)
    Debugging Details:
    ------------------

    PROCESS_OBJECT: fffffa8012412b30
    IMAGE_NAME: csrss.exe
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    MODULE_NAME: csrss
    FAULTING_MODULE: 0000000000000000
    PROCESS_NAME: csrss.exe
    EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
    BUGCHECK_STR: 0xF4_IOERR
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    CURRENT_IRQL: 0
    STACK_TEXT:
    fffff880`02a71e38 fffff800`03050342 : 00000000`000000f4 00000000`00000003 fffffa80`12412b30 fffffa80`12412e10 : nt!KeBugCheckEx
    fffff880`02a71e40 fffff800`030065ab : ffffffff`ffffffff fffffa80`12b23060 fffffa80`12412b30 fffffa80`12412b30 : nt!PspCatchCriticalBreak+0x92
    fffff880`02a71e80 fffff800`02f740cc : ffffffff`ffffffff 00000000`00000001 fffffa80`12412b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x2a546
    fffff880`02a71ed0 fffff800`02cbbcd3 : fffffa80`12412b30 fffff800`c0000006 fffffa80`12b23060 00000000`006d0f80 : nt!NtTerminateProcess+0xf4
    fffff880`02a71f50 fffff800`02cb8290 : fffff800`02d3d519 fffff880`02a72a38 fffff880`02a72790 fffff880`02a72ae0 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`02a720e8 fffff800`02d3d519 : fffff880`02a72a38 fffff880`02a72790 fffff880`02a72ae0 00000000`006d1c90 : nt!KiServiceLinkage
    fffff880`02a720f0 fffff800`02cbc0c2 : fffff880`02a72a38 00000000`00013600 fffff880`02a72ae0 00000000`006d1768 : nt! ?? ::FNODOBFM::`string'+0x48554
    fffff880`02a72900 fffff800`02cbac3a : 00000000`00000000 000007fe`fd56d8c0 00000000`00000001 00000000`00013600 : nt!KiExceptionDispatch+0xc2
    fffff880`02a72ae0 00000000`77838fa2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
    00000000`006d16b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77838fa2

    STACK_COMMAND: kb
    FOLLOWUP_NAME: MachineOwner
    FAILURE_BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe
    BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe
    Followup: MachineOwner
    ---------
    #7
    RobbieB
    New Member
    • Total Posts : 8
    • Reward points : 0
    • Joined: 2015/04/28 14:06:37
    • Status: offline
    • Ribbons : 0
    Re: New Build Problem with Drivers 2015/04/28 16:24:08 (permalink)
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck F4, {3, fffffa8012e54b30, fffffa8012e54e10, fffff80002fd0940}
    Probably caused by : wininit.exe
    Followup: MachineOwner
    ---------
    4: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa8012e54b30, Terminating object
    Arg3: fffffa8012e54e10, Process image file name
    Arg4: fffff80002fd0940, Explanatory message (ascii)
    Debugging Details:
    ------------------

    PROCESS_OBJECT: fffffa8012e54b30
    IMAGE_NAME: wininit.exe
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    MODULE_NAME: wininit
    FAULTING_MODULE: 0000000000000000
    PROCESS_NAME: wininit.exe
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    BUGCHECK_STR: 0xF4_C0000005
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    CURRENT_IRQL: 0
    STACK_TEXT:
    fffff880`0a11ce38 fffff800`03060342 : 00000000`000000f4 00000000`00000003 fffffa80`12e54b30 fffffa80`12e54e10 : nt!KeBugCheckEx
    fffff880`0a11ce40 fffff800`030165ab : ffffffff`ffffffff fffffa80`132dc060 fffffa80`12e54b30 fffffa80`12e54b30 : nt!PspCatchCriticalBreak+0x92
    fffff880`0a11ce80 fffff800`02f840cc : ffffffff`ffffffff 00000000`00000001 fffffa80`12e54b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x2a546
    fffff880`0a11ced0 fffff800`02ccbcd3 : fffffa80`12e54b30 fffff800`c0000005 fffffa80`132dc060 00000000`029505c0 : nt!NtTerminateProcess+0xf4
    fffff880`0a11cf50 fffff800`02cc8290 : fffff800`02d4d519 fffff880`0a11da38 fffff880`0a11d790 fffff880`0a11dae0 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`0a11d0e8 fffff800`02d4d519 : fffff880`0a11da38 fffff880`0a11d790 fffff880`0a11dae0 00000000`029520d0 : nt!KiServiceLinkage
    fffff880`0a11d0f0 fffff800`02ccc0c2 : fffff880`0a11da38 00000000`0000ec6c fffff880`0a11dae0 00000000`02951ba8 : nt! ?? ::FNODOBFM::`string'+0x48554
    fffff880`0a11d900 fffff800`02ccac3a : 00000000`00000001 00000000`02950cd8 00000000`00000001 00000000`0000ec6c : nt!KiExceptionDispatch+0xc2
    fffff880`0a11dae0 00000000`76d3883d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
    00000000`02950ce0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d3883d

    STACK_COMMAND: kb
    FOLLOWUP_NAME: MachineOwner
    FAILURE_BUCKET_ID: X64_0xF4_C0000005_IMAGE_wininit.exe
    BUCKET_ID: X64_0xF4_C0000005_IMAGE_wininit.exe
    Followup: MachineOwner
    ---------
    4: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa8012e54b30, Terminating object
    Arg3: fffffa8012e54e10, Process image file name
    Arg4: fffff80002fd0940, Explanatory message (ascii)
    Debugging Details:
    ------------------

    PROCESS_OBJECT: fffffa8012e54b30
    IMAGE_NAME: wininit.exe
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    MODULE_NAME: wininit
    FAULTING_MODULE: 0000000000000000
    PROCESS_NAME: wininit.exe
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    BUGCHECK_STR: 0xF4_C0000005
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    CURRENT_IRQL: 0
    STACK_TEXT:
    fffff880`0a11ce38 fffff800`03060342 : 00000000`000000f4 00000000`00000003 fffffa80`12e54b30 fffffa80`12e54e10 : nt!KeBugCheckEx
    fffff880`0a11ce40 fffff800`030165ab : ffffffff`ffffffff fffffa80`132dc060 fffffa80`12e54b30 fffffa80`12e54b30 : nt!PspCatchCriticalBreak+0x92
    fffff880`0a11ce80 fffff800`02f840cc : ffffffff`ffffffff 00000000`00000001 fffffa80`12e54b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x2a546
    fffff880`0a11ced0 fffff800`02ccbcd3 : fffffa80`12e54b30 fffff800`c0000005 fffffa80`132dc060 00000000`029505c0 : nt!NtTerminateProcess+0xf4
    fffff880`0a11cf50 fffff800`02cc8290 : fffff800`02d4d519 fffff880`0a11da38 fffff880`0a11d790 fffff880`0a11dae0 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`0a11d0e8 fffff800`02d4d519 : fffff880`0a11da38 fffff880`0a11d790 fffff880`0a11dae0 00000000`029520d0 : nt!KiServiceLinkage
    fffff880`0a11d0f0 fffff800`02ccc0c2 : fffff880`0a11da38 00000000`0000ec6c fffff880`0a11dae0 00000000`02951ba8 : nt! ?? ::FNODOBFM::`string'+0x48554
    fffff880`0a11d900 fffff800`02ccac3a : 00000000`00000001 00000000`02950cd8 00000000`00000001 00000000`0000ec6c : nt!KiExceptionDispatch+0xc2
    fffff880`0a11dae0 00000000`76d3883d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
    00000000`02950ce0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d3883d

    STACK_COMMAND: kb
    FOLLOWUP_NAME: MachineOwner
    FAILURE_BUCKET_ID: X64_0xF4_C0000005_IMAGE_wininit.exe
    BUCKET_ID: X64_0xF4_C0000005_IMAGE_wininit.exe
    Followup: MachineOwner
    ---------
     
     
     
     
    These are the only two I've gotten since the fresh install of 7 Professional on Saturday.  They also happen to be the most common ones I've gotten since building the rig.  
    #8
    Sajin
    EVGA Forum Moderator
    • Total Posts : 49165
    • Reward points : 0
    • Joined: 2010/06/07 21:11:51
    • Location: Texas, USA.
    • Status: online
    • Ribbons : 199
    Re: New Build Problem with Drivers 2015/04/28 16:50:20 (permalink)
    I doubt all your drivers are 6/21/06. Do the following for me...
     
    #1 Update your SSD firmware by downloading the latest version of the samsung magician software and running the firmware update.
    #2 Perform a clean boot of windows.
    #3 Report back if the BSOD is gone or not.
     
    post edited by Sajin - 2015/04/28 16:53:29
    #9
    RobbieB
    New Member
    • Total Posts : 8
    • Reward points : 0
    • Joined: 2015/04/28 14:06:37
    • Status: offline
    • Ribbons : 0
    Re: New Build Problem with Drivers 2015/04/28 17:09:17 (permalink)
    So I have checked the firmware using Samsung magician, and it has not required an update as long as I've owned the SSD. While fairly regular, the bsod are not predictable. Should I just clean boot and let it run and see if it happens?
    #10
    Sajin
    EVGA Forum Moderator
    • Total Posts : 49165
    • Reward points : 0
    • Joined: 2010/06/07 21:11:51
    • Location: Texas, USA.
    • Status: online
    • Ribbons : 199
    Re: New Build Problem with Drivers 2015/04/28 17:23:52 (permalink)
    RobbieB
    So I have checked the firmware using Samsung magician, and it has not required an update as long as I've owned the SSD. While fairly regular, the bsod are not predictable. Should I just clean boot and let it run and see if it happens?

    Yes.
    #11
    RobbieB
    New Member
    • Total Posts : 8
    • Reward points : 0
    • Joined: 2015/04/28 14:06:37
    • Status: offline
    • Ribbons : 0
    Re: New Build Problem with Drivers 2015/04/28 21:11:24 (permalink)
    OK!  I'll do that tomorrow and let you know how it goes!  Thanks for taking an interest!
    #12
    RobbieB
    New Member
    • Total Posts : 8
    • Reward points : 0
    • Joined: 2015/04/28 14:06:37
    • Status: offline
    • Ribbons : 0
    Re: New Build Problem with Drivers 2015/04/29 16:24:38 (permalink)
    So far everything has been smooth running with the clean boot, though that may just be a false negative because yesterday no BSOD occurred while operating under normal conditions.  What do you think it means if I dont get faults in clean boot, but do in a normal boot?  Are you brewing on some theories?
    #13
    Sajin
    EVGA Forum Moderator
    • Total Posts : 49165
    • Reward points : 0
    • Joined: 2010/06/07 21:11:51
    • Location: Texas, USA.
    • Status: online
    • Ribbons : 199
    Re: New Build Problem with Drivers 2015/04/29 17:56:05 (permalink)
    I'm thinking it's a software conflict/3rd party driver that may be causing the issue. Next we will check the drivers to see if they have an issue if you continue to BSOD while in clean boot.
    #14
    RobbieB
    New Member
    • Total Posts : 8
    • Reward points : 0
    • Joined: 2015/04/28 14:06:37
    • Status: offline
    • Ribbons : 0
    Re: New Build Problem with Drivers 2015/05/02 19:25:12 (permalink)
    So it has been several days since I started exclusively clean booting, and I've had zero BSODs.  I don't think I'll be 100% satisfied that it's fine in clean boot until I've left it that way for a couple of weeks, just because the faults that have been occurring are so unpredictable, but... I'm feeling pretty good about it.  What then is the problem if it's fine in clean boot?  Is it just one of the services that are currently showing as "stopped" in the system configuration (msconfig) window?  Do I just go through and allow them one by one?
    #15
    Sajin
    EVGA Forum Moderator
    • Total Posts : 49165
    • Reward points : 0
    • Joined: 2010/06/07 21:11:51
    • Location: Texas, USA.
    • Status: online
    • Ribbons : 199
    Re: New Build Problem with Drivers 2015/05/03 15:34:59 (permalink)
    RobbieB
    What then is the problem if it's fine in clean boot?  Is it just one of the services that are currently showing as "stopped" in the system configuration (msconfig) window?  Do I just go through and allow them one by one?

    Yes, that is exactly what you should do to figure out which one is causing the issue. I run my computer in clean boot 24/7 without any problems.
    #16
    Jump to:
  • Back to Mobile