Windows 8 and 8.1 Forums


Various BSODs in Past Two Days

  1. #41


    The profile was actually set on the high performance one. I changed it to Normal, then ran Prime95 again and this time I got 4 errors:
    "FATAL ERROR: Rounding was 0.5, expected less than 0.4
    FATAL ERROR: Rounding was 0.4982910156, expected less than 0.4" (x2)

    Searching online seems to be pointing to increasing CPU/Memory voltage. My CPU core voltages are currently at 1.325V and the NB VID is at 1.150V. My CPU is rated at 1.0V-1.475V. Would you suggest increasing voltage? Do these results indicate that the problem is most likely with my CPU and not my GPUs?

      My System SpecsSystem Spec

  2. #42


    Posts : 5,139
    Win8.1Pro - Finally!!!


    A while back (around 9 months ago or so) I noticed a few BSOD's due to automated overclocking utilities in the BIOS. It didn't last long, so I forgot about it (and don't normally caution people about it). I'd suggest disabling the auto-overclock feature to see if that helps.

    Also, try this free memory test: Memory Diagnostics
      My System SpecsSystem Spec

  3. #43


    I ran a few passes of memtest86+ a few months ago with no errors, but I'll try it again tonight. I'll let you know if it results in an error. Also, I got another BSOD:

    Code:
    ********************************************************************************                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck 1E, {ffffffffc0000005, fffff8012491d982, 0, 39}
    
    
    Probably caused by : ntkrnlmp.exe ( nt!PpmIdleExecuteTransition+361 )
    
    
    Followup: MachineOwner
    ---------
    
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8012491d982, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000039, Parameter 1 of the exception
    
    
    Debugging Details:
    ------------------
    
    
    
    
    READ_ADDRESS:  0000000000000039 
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    
    FAULTING_IP: 
    nt!PpmIdleExecuteTransition+361
    fffff801`2491d982 c5              ???
    
    
    EXCEPTION_PARAMETER2:  0000000000000039
    
    
    BUGCHECK_STR:  0x1E_c0000005_R
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  0
    
    
    TAG_NOT_DEFINED_c000000f:  FFFFF88002A8DFB0
    
    
    EXCEPTION_RECORD:  fffffa800f3862e0 -- (.exr 0xfffffa800f3862e0)
    ExceptionAddress: 0000000000000000
       ExceptionCode: 0d162090
      ExceptionFlags: fffffa80
    NumberParameters: 487472
       Parameter[0]: 0000000000000000
       Parameter[1]: 000000080000003a
       Parameter[2]: 0000000000000000
       Parameter[3]: 0000000000000000
       Parameter[4]: 0000000004000000
       Parameter[5]: fffffa800f434080
       Parameter[6]: fffff8a000371010
       Parameter[7]: fffffffffffffffc
       Parameter[8]: fffffa800f434018
       Parameter[9]: fffffa801041a3e0
       Parameter[10]: fffffa800d145241
       Parameter[11]: 0000000077061001
       Parameter[12]: 69646d4d02050009
       Parameter[13]: 0000000000000000
       Parameter[14]: 0000000000000000
    
    
    TRAP_FRAME:  fffff88002a86828 -- (.trap 0xfffff88002a86828)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff88002a5d180 rbx=0000000000000000 rcx=fffffa800f0e9ac0
    rdx=fffff801249510e4 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff9800a952eb8 rsp=fffff80124827dd4 rbp=0000000000000039
     r8=fffff88002a5d180  r9=0000000000000002 r10=0000000000000001
    r11=fffffa800f7160f8 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=2         ov dn ei pl nz na pe nc
    ffff:2eb8 ??              ???
    Resetting default scope
    
    
    LAST_CONTROL_TRANSFER:  from fffff801249e6df2 to fffff801248ef340
    
    
    STACK_TEXT:  
    fffff880`02a85888 fffff801`249e6df2 : 00000000`0000001e ffffffff`c0000005 fffff801`2491d982 00000000`00000000 : nt!KeBugCheckEx
    fffff880`02a85890 fffff801`2494f8ad : fffffa80`0ef69380 fffff880`01608a76 fffff801`24b83ee4 fffff880`01cf5a64 : nt!KiFatalExceptionHandler+0x22
    fffff880`02a858d0 fffff801`24951633 : 00000000`00000000 fffff880`02a81000 fffff801`24b859e4 fffff880`02a87000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`02a85900 fffff801`2496dabe : fffff880`02a86808 fffff880`02a86540 fffff880`02a86808 00000000`00000000 : nt!RtlDispatchException+0x44b
    fffff880`02a86010 fffff801`248ee742 : fffffa80`0f3862e0 00000000`00000039 fffff880`02a86828 0000016e`6a74e729 : nt!KiDispatchException+0x455
    fffff880`02a866d0 fffff801`248eceba : 00000000`00000000 fffffa80`0f7162e8 00000000`00000000 fffff880`02a868b0 : nt!KiExceptionDispatch+0xc2
    fffff880`02a868b0 fffff801`2491d982 : fffff880`00000001 fffffa80`0f7162e8 fffffa80`0f716010 00000000`00000000 : nt!KiPageFault+0x23a
    fffff880`02a86a40 fffff801`2491c4c0 : 00000000`00000000 00000000`005b9aa7 fffff880`02a86ca8 fffff880`02a86cb0 : nt!PpmIdleExecuteTransition+0x361
    fffff880`02a86c60 fffff801`2491a64c : fffff880`02a5d180 fffff880`02a5d180 00000000`00000000 fffff880`02a68ec0 : nt!PoIdle+0x1e0
    fffff880`02a86da0 00000000`00000000 : fffff880`02a87000 fffff880`02a81000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    nt!PpmIdleExecuteTransition+361
    fffff801`2491d982 c5              ???
    
    
    SYMBOL_STACK_INDEX:  7
    
    
    SYMBOL_NAME:  nt!PpmIdleExecuteTransition+361
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: nt
    
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  50ab0e64
    
    
    BUCKET_ID_FUNC_OFFSET:  361
    
    
    FAILURE_BUCKET_ID:  0x1E_c0000005_R_VRF_nt!PpmIdleExecuteTransition
    
    
    BUCKET_ID:  0x1E_c0000005_R_VRF_nt!PpmIdleExecuteTransition
    
    
    Followup: MachineOwner
    ---------

      My System SpecsSystem Spec

  4. #44


    I ran memtest again and didn't get any errors. Is there anything else you would do at this point? Also, another BSOD:

    Code:
    ********************************************************************************                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck 139, {3, fffff8801c5696d0, fffff8801c569628, 0}
    
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+1aa )
    
    
    Followup: MachineOwner
    ---------
    
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    KERNEL_SECURITY_CHECK_FAILURE (139)
    A kernel component has corrupted a critical data structure.  The corruption
    could potentially allow a malicious user to gain control of this machine.
    Arguments:
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: fffff8801c5696d0, Address of the trap frame for the exception that caused the bugcheck
    Arg3: fffff8801c569628, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    
    
    Debugging Details:
    ------------------
    
    
    
    
    TRAP_FRAME:  fffff8801c5696d0 -- (.trap 0xfffff8801c5696d0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa8013cfc080 rbx=0000000000000000 rcx=0000000000000003
    rdx=fffff8a01255d760 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88005ba37de rsp=fffff8801c569860 rbp=0000000000000004
     r8=fffffa8013a6c900  r9=0000000000000001 r10=0000000000000003
    r11=fffffa800f0c0400 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe cy
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x1aa:
    fffff880`05ba37de cd29            int     29h
    Resetting default scope
    
    
    EXCEPTION_RECORD:  fffff8801c569628 -- (.exr 0xfffff8801c569628)
    ExceptionAddress: fffff88005ba37de (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x00000000000001aa)
       ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
      ExceptionFlags: 00000001
    NumberParameters: 1
       Parameter[0]: 0000000000000003
    
    
    DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
    
    
    BUGCHECK_STR:  0x139
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  0
    
    
    ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
    
    
    EXCEPTION_PARAMETER1:  0000000000000003
    
    
    LAST_CONTROL_TRANSFER:  from fffff802406f3669 to fffff802406f4340
    
    
    STACK_TEXT:  
    fffff880`1c5693a8 fffff802`406f3669 : 00000000`00000139 00000000`00000003 fffff880`1c5696d0 fffff880`1c569628 : nt!KeBugCheckEx
    fffff880`1c5693b0 fffff802`406f3990 : fffffa80`0f93a500 fffff880`1c569640 fffffa80`0d16a850 00000000`00da7a64 : nt!KiBugCheckDispatch+0x69
    fffff880`1c5694f0 fffff802`406f2bf4 : 00000000`002aec0f fffff880`05ba6104 00000000`002aec0f fffffa80`0d16b240 : nt!KiFastFailDispatch+0xd0
    fffff880`1c5696d0 fffff880`05ba37de : 00000000`00000000 fffff8a0`13fc5a48 fffffa80`13d448f0 fffff8a0`13fc5a48 : nt!KiRaiseSecurityCheckFailure+0xf4
    fffff880`1c569860 fffff880`05ba0b61 : 00000000`00000000 fffff880`1c5699a0 fffff8a0`188f1530 fffffa80`13d3d330 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x1aa
    fffff880`1c5698a0 fffff880`05bbbe02 : fffffa80`0f0c0400 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x1659
    fffff880`1c569b10 fffff880`05bbbb25 : 00000000`00000000 fffff880`00000000 fffff780`00000320 fffff802`00000e80 : dxgmms1!VidSchiSubmitRenderCommand+0x1f6
    fffff880`1c569ce0 fffff880`05bbb662 : fffffa80`138c8630 fffffa80`14344e00 fffffa80`10f87010 fffffa80`0f0c0400 : dxgmms1!VidSchiSubmitQueueCommand+0x51
    fffff880`1c569d10 fffff802`4069b551 : fffffa80`0f1f0080 fffffa80`0f0c0400 fffff802`409c9880 00000000`0b1be8b0 : dxgmms1!VidSchiWorkerThread+0xe6
    fffff880`1c569d50 fffff802`406d9dd6 : fffff802`4096f180 fffffa80`0f1f0080 fffff802`409c9880 fffffa80`0d040680 : nt!PspSystemThreadStartup+0x59
    fffff880`1c569da0 00000000`00000000 : fffff880`1c56a000 fffff880`1c564000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+1aa
    fffff880`05ba37de cd29            int     29h
    
    
    SYMBOL_STACK_INDEX:  4
    
    
    SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+1aa
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: dxgmms1
    
    
    IMAGE_NAME:  dxgmms1.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  505ab2a9
    
    
    BUCKET_ID_FUNC_OFFSET:  1aa
    
    
    FAILURE_BUCKET_ID:  0x139_3_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission
    
    
    BUCKET_ID:  0x139_3_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission
    
    
    Followup: MachineOwner
    ---------
      My System SpecsSystem Spec

  5. #45


    Posts : 5,139
    Win8.1Pro - Finally!!!


    If no errors in Memtest, then run CPU stress tests from here: Additional Hardware Diagnostics

    Bugchecks are looking like hardware. Please run Driver Verifier according to the instructions in order to be sure: Driver Verifier Settings

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Thu Jan 10 21:09:57.664 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\011013-15054-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 2:32:26.393
    Probably caused by :dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+1aa )
    BugCheck 139, {3, fffff8801c5696d0, fffff8801c569628, 0}
    BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)
    Arguments: 
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: fffff8801c5696d0, Address of the trap frame for the exception that caused the bugcheck
    Arg3: fffff8801c569628, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    BUGCHECK_STR:  0x139
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x139_3_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission
      BIOS Version                  1604
      BIOS Release Date             10/16/2012
      Manufacturer                  To be filled by O.E.M.
      Product Name                  To be filled by O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Jan  9 15:20:59.191 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\010913-20560-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:1 days 19:42:54.687
    Probably caused by :ntkrnlmp.exe ( nt!PpmIdleExecuteTransition+361 )
    BugCheck 1E, {ffffffffc0000005, fffff8012491d982, 0, 39}
    BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8012491d982, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000039, Parameter 1 of the exception
    BUGCHECK_STR:  0x1E_c0000005_R
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x1E_c0000005_R_VRF_nt!PpmIdleExecuteTransition
      BIOS Version                  1604
      BIOS Release Date             10/16/2012
      Manufacturer                  To be filled by O.E.M.
      Product Name                  To be filled by O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Thu Jan 10 21:09:57.664 2013 (UTC - 5:00)**************************
    vmci.sys                    Mon Apr 30 21:14:27 2012 (4F9F38F3)
    vsock.sys                   Mon Apr 30 21:15:24 2012 (4F9F392C)
    Rt630x64.sys                Tue Jun 12 09:37:53 2012 (4FD74631)
    amd_sata.sys                Tue Jun 12 10:24:37 2012 (4FD75125)
    amd_xata.sys                Tue Jun 12 10:24:45 2012 (4FD7512D)
    VMNET.SYS                   Sun Jul  8 03:58:34 2012 (4FF93DAA)
    vmnetadapter.sys            Sun Jul  8 03:58:35 2012 (4FF93DAB)
    vmnetbridge.sys             Sun Jul  8 03:59:19 2012 (4FF93DD7)
    xusb22.sys                  Wed Jul 25 22:26:57 2012 (5010AAF1)
    hcmon.sys                   Wed Aug  1 20:10:29 2012 (5019C575)
    RTKVHD64.sys                Tue Aug  7 06:49:39 2012 (5020F2C3)
    vmnetuserif.sys             Wed Aug 15 16:31:54 2012 (502C073A)
    vmx86.sys                   Wed Aug 15 18:05:11 2012 (502C1D17)
    LEqdUsb.Sys                 Tue Sep 18 05:26:44 2012 (50583E54)
    LHidEqd.Sys                 Tue Sep 18 05:26:46 2012 (50583E56)
    LHidFilt.Sys                Tue Sep 18 05:26:53 2012 (50583E5D)
    LMouFilt.Sys                Tue Sep 18 05:26:58 2012 (50583E62)
    atikmpag.sys                Thu Sep 27 21:12:52 2012 (5064F994)
    atikmdag.sys                Thu Sep 27 22:14:57 2012 (50650821)
    HWiNFO64A.SYS               Wed Nov 14 06:15:59 2012 (50A37D6F)
    
    http://www.carrona.org/drivers/driver.php?id=vmci.sys
    http://www.carrona.org/drivers/driver.php?id=vsock.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
    http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
    http://www.carrona.org/drivers/driver.php?id=VMNET.SYS
    http://www.carrona.org/drivers/driver.php?id=vmnetadapter.sys
    http://www.carrona.org/drivers/driver.php?id=vmnetbridge.sys
    xusb22.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=hcmon.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=vmnetuserif.sys
    http://www.carrona.org/drivers/driver.php?id=vmx86.sys
    http://www.carrona.org/drivers/driver.php?id=LEqdUsb.Sys
    http://www.carrona.org/drivers/driver.php?id=LHidEqd.Sys
    http://www.carrona.org/drivers/driver.php?id=LHidFilt.Sys
    http://www.carrona.org/drivers/driver.php?id=LMouFilt.Sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS
      My System SpecsSystem Spec

  6. #46


    Tropical Island Pair a Dice
    Posts : 3,030
    Windows 8.1 Pro x64/ Windows 7 Ult x64


    How many passes of memtest86+ did you run?
    The test requires a minimum of 7 full passes, this may take several hours depending on the amount of RAM you have, best to let it run overnight. First run with all RAM cards installed, let us know the results.
    RAM - Test with Memtest86+

    Overclocking utilities always use poor settings, these are not recommended.
    Disable all overclocking, re-set your EFI BIOS to Optimized Defaults.

    Once your system is stable you can find a good OC guide and OC again, if you want.

    Please fill in your system specs, links to Newegg are not a good way to let us know your hardware, too much work.
    Use this program Speccy Free System information Utility

    In your previous post of your UEFI page, the voltages are not very good, What PSU do you have, give as much info as possible.

    For some more information, can you 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 Upload and Post a Screenshot and File in Eight Forums

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

  7. #47


    Memtest86+:
    I ran this overnight, but I didn't take notice of the number of passes, so I ran it again last night. No errors both times. It looks like it only got through 3 passes (does the 7 pass minimum need to be all at once?):

    Attachment 14687

    Speccy:
    Attached are my SF Dumps and Speccy exports ("Snapshot" and output as text).

    BIOS:
    The first screenshot I posted of BIOS was just a generic screen to show what I was talking about. I did not take it. Today, I took pics of all possibly relevant BIOS screens and included links (they were too large to include them in the attachment). Here is the main BIOS screen:

    Attachment 14688

    See the screenshots for voltages and other information. I did notice that my RAM timings and latency are not set at what my RAM is rated at (which is 10-10-10-30, latency 10). Should I manually set it to those?


    Screenshots:
    Screens 1-12-13 - Imgur
      My System SpecsSystem Spec

  8. #48


    I just tried setting my RAM to 10-10-10-30 and I got BSODs within 5 min of turning on the computer. So, I set the timings to Auto, set Memory Frequency to Auto, and set AI Overclock Tuner to Auto. After that, I ran Prime95 for about 15 min and didn't get any errors, which is the best it has been so far. I am still curios why the Auto settings set my RAM to different timings and a lower frequency. I did read that for my RAM: "To reach rated memory speed... manual BIOS tuning is required". Should I try setting it to what its rated at again? In the meantime I'll do more stress tests and report back if there are errors.


    Also, I now realize I could have taken screenshots with F12 *facepalm*
      My System SpecsSystem Spec

  9. #49


    Tropical Island Pair a Dice
    Posts : 3,030
    Windows 8.1 Pro x64/ Windows 7 Ult x64


    You need to to run 7 full consecutive passes, each pass runs different tests.

    Fill in your system specs in the lower left corner of your posts.
    This way we can see them without having to search the internet, or download files. Then everybody can see them, and I don't have to search or download them again if I post here. It makes it easier for everyone trying to help you.
    Be sure to fill in information about your PSU.

    Don't change the RAM settings until I can see more infor, like requested above and below.

    Can you post this information?
    For some more information, can you 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 Upload and Post a Screenshot and File in Eight Forums
    No further crash files then what usasma posted above.
    I'll help your through his suggestions.
    Run memtest86+ for 7 full passes.
    If it passes, run hard drive diagnostics on all your hard drives, use the manufacturers diagnostic utilities from their site.
    If you fill in your System Specs, I can help you with the correct tools.
    After those tests are done we can run a CPU stability test.
    Last edited by Dave76; 13 Jan 2013 at 01:31.
      My System SpecsSystem Spec

  10. #50


    I ran a full 7 passes of memtest86 and didn't get any errors. I haven't received any BSODs since changing the frequency of my RAM from 1600 MHz to Auto (which sets it to 1333 MHz). Do you think this could have been the issue? I'll run HDD tests if I get another BSOD, but for now, it seems to be running nicely.
      My System SpecsSystem Spec

Page 5 of 6 FirstFirst ... 3456 LastLast
Various BSODs in Past Two Days
Related Threads
I've been getting seemingly random BSODs on my Win8.1 box for months now. There are several different errors that show up, and most of them seem to point to the drivers. I have no idea which driver could be causing the issue though, as I've reinstalled the majority of them. A few I can remember:...
2x WHEA_UNCORRECTABLE_ERROR BSODs in 3 days in BSOD Crashes and Debugging
I suffered my first BSOD 2 days ago while playing Elite Dangerous. It was a WHEA_UNCORRECTABLE_ERROR with references to GenuineIntel, WIN8_DRIVER_FAULT, and the process was Elite Dangerous. I put it down to faulty code in the game somewhere, but just tonight, while browsing on Firefox, I...
Four different BSODs in two days in BSOD Crashes and Debugging
Hi, In the past two days my Dell laptop (Win8 OS) has crashed four times with different BSOD error messages. What I have attempted is to run my anti-malware software and to go back to a restore point, but it hasn't work so I'm worried it is a problem with the RAM. The errors shown are...
Solved BSODs over the last couple of days in BSOD Crashes and Debugging
Over the last couple of days I've been having random BSOD after a few hours of use or so. I've been unable to find anything that causes it to occur, it appears to just happen randomly. Thanks for any help!
Ended up getting 4 Acer All in One 23" touchscreens at work this past week. Getting them set up for a tradeshow. They are the Acer Aspire 5600U's. They were $999 from NewEgg for Core i3-3110m, 8gb ram, 1TB hard drive, Intel HD400 graphics, DVD burner, 23" 1080p 10 point touchscreen, Windows...
4 of them for work, and 1 which is a Christmas present. Gotta buy some pc's before somebody declares the pc dead.
Hi everyone! I just installed Windows 8 yesterday and after the initial "wow" factor I installed my graphics drivers and rebooted. Upon restart, I got past the welcome screen and logged in (no password error) and after the screen quickly goes blank as if it's about to log in, then it returns to...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook