BSOD error associated with low power mode, thinking software concern


  1. Posts : 8
    Windows 7 Pro x64
       #1

    BSOD error associated with low power mode, thinking software concern


    So I'm having an error currently, and I'm not really sure what it was.

    I think it is linked to when I came here previously, however I am not entirely sure, I followed the advice given and I thought I had fixed it, however a few weeks later my computer is yet again crashing upon entering low power mode.

    I have used the dm log collector application found on this website to collect information of the crash.
      My Computer


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

    Hi lightNRG.

    Click on the button below ....



    It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
    Screenshots and Files - Upload and Post in Seven Forums
      My Computer


  3. Posts : 8
    Windows 7 Pro x64
    Thread Starter
       #3

    That is the utility that I used to collect the .zip file attached to my post.
      My Computer


  4. Posts : 8
    Windows 7 Pro x64
    Thread Starter
       #4

    I redownloaded the utility using the link provided, and ran it again and was given this file.
      My Computer


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

    Hi.

    Are you overclocking?
    As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

    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.

    Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs

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

    Also, can you update the BIOS to version 2.40 from ASRock > Z87 Extreme3 ?

    Let us know the results.
    _________________________________
    Code:
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff8800f286a37, fffff880091c9158, fffff880091c89b0}
    
    Probably caused by : nvlddmkm.sys ( nvlddmkm+199a37 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    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.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8800f286a37, The address that the exception occurred at
    Arg3: fffff880091c9158, Exception Record Address
    Arg4: fffff880091c89b0, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    nvlddmkm+199a37
    fffff880`0f286a37 ff93f81a0000    call    qword ptr [rbx+1AF8h]
    
    EXCEPTION_RECORD:  fffff880091c9158 -- (.exr 0xfffff880091c9158)
    ExceptionAddress: fffff8800f286a37 (nvlddmkm+0x0000000000199a37)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000001af8
    Attempt to read from address 0000000000001af8
    
    CONTEXT:  fffff880091c89b0 -- (.cxr 0xfffff880091c89b0;r)
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=fffffa8008451000 rdi=0000000000000000
    rip=fffff8800f286a37 rsp=fffff880091c9390 rbp=0000000000000000
     r8=0000000000000001  r9=fffff8800f9b48e0 r10=0000000000000000
    r11=fffff880091c9358 r12=fffffa80081a5960 r13=fffffa800791f000
    r14=0000000000000000 r15=0000000000000002
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    nvlddmkm+0x199a37:
    fffff880`0f286a37 ff93f81a0000    call    qword ptr [rbx+1AF8h] ds:002b:00000000`00001af8=????????????????
    Last set context:
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=fffffa8008451000 rdi=0000000000000000
    rip=fffff8800f286a37 rsp=fffff880091c9390 rbp=0000000000000000
     r8=0000000000000001  r9=fffff8800f9b48e0 r10=0000000000000000
    r11=fffff880091c9358 r12=fffffa80081a5960 r13=fffffa800791f000
    r14=0000000000000000 r15=0000000000000002
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    nvlddmkm+0x199a37:
    fffff880`0f286a37 ff93f81a0000    call    qword ptr [rbx+1AF8h] ds:002b:00000000`00001af8=????????????????
    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_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000001af8
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfc100
    GetUlongFromAddress: unable to read from fffff80002cfc1c0
     0000000000001af8 Nonpaged pool
    
    FOLLOWUP_IP: 
    nvlddmkm+199a37
    fffff880`0f286a37 ff93f81a0000    call    qword ptr [rbx+1AF8h]
    
    BUGCHECK_STR:  0x7E
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800f286a37
    
    STACK_TEXT:  
    fffff880`091c9390 00000000`00000000 : 00000000`00000000 fffff880`0f286a2c fffffa80`07a08000 fffffa80`0bf3cb50 : nvlddmkm+0x199a37
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nvlddmkm+199a37
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5315b408
    
    STACK_COMMAND:  .cxr 0xfffff880091c89b0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_nvlddmkm+199a37
    
    BUCKET_ID:  X64_0x7E_nvlddmkm+199a37
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x7e_nvlddmkm+199a37
    
    FAILURE_ID_HASH:  {8a28351f-7dc2-c04d-ddcc-1736fd4cd1fb}
    
    Followup: MachineOwner
    ---------
    
    1: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0f0ed000 fffff880`0fd45000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Tue Mar 04 16:37:52 2014 (5315B408)
        CheckSum:         00C20523
        ImageSize:        00C58000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  6. Posts : 8
    Windows 7 Pro x64
    Thread Starter
       #6

    Using the eXtremem Power Supply calculator, I found it was suggested I have 381W, and I have a 600W Cooler Master PSU installed.

    I have a published snapshot of Speccy that can be found here

    I am unsure what I need to post from the Furmark stress test, however I let it run for a half hour with the settings on the thread. My temperature capped out at 79 C and I saw no artifacts or other glitches during that time.

    I am resetting my computer now to update the BIOS to 2.40.
      My Computer


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

    Apparently everything seems to be nice. :)

    If the BSODs continue even after updating the BIOS, we may need to think about the drivers. So let us know how it is running.
      My Computer


  8. Posts : 8
    Windows 7 Pro x64
    Thread Starter
       #8

    I think that the problem is fixed. I put it into sleep mode earlier and that was unsuccessful, but after rebooting with all the new changes the computer successfully went into power save while I was gone for errands.

    I editted this thinking there was a concern, for now I'm not sure whether it is fixed or not but I hope that it is.
    Last edited by lightNRG; 29 Jun 2014 at 22:09.
      My Computer


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

    You need to observe the situation over at least a week before calling it as fixed. :)
      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 10:25.
Find Us