locked
Crashes at idle time, analysis by Event Viewer table RRS feed

  • Question

  • A crash happens on my computer from time to time and always at idle time. The computer stops responding on the movement of the mouse and hit of the keyboard, I have to do a hard restart. A short-lived  BSD appears on my screen and then the logo with the inscription Resuming Windows followed by a reboot.
    In just the past 2 months there were 11 such crash.

    I suspected that the source of crashes is equipment overheating. I cleaned the air vents and moved the case to a more spacious place. Crashes become more rare.

    But I found a strange pattern. I analyze crashes in an Event Viewer table - Event source: eventlog, ID 6008. These events appear in the Event Viewer table almost immediately after the restart, and in Properties of the event there is the time of the crash - The previous system shutdown at <time> on <date> was unexpected. Thus, the range of time between the registration of the event ID 6008 (actually restarting the computer) and the crash is a completely random value. These ranges of time were from several hours to several tens of minutes for earlier crashes. However, in the last four crashes these ranges of time were 1 - 2 minutes. These coincidences can not be accidental. I think this means that the crashes happened at the time of "awakening" of the computer.

    There is another weird moment. I was trying to determine a connection between the crashes and the Sleep regime of the computer. I put a filter in Event Viewer to display only two events - «entering sleep» and «has resumed from sleeping» (Kernel-Power ID 42 and Power-Troubleshooter ID 1). The result was strange - the «has resumed from sleeping» events were registered only twice in the past month in the presence of «entering sleep» events more than a hundred times. 
    I checked the same filter on another computer with the same OS and got the expected result - the «entering sleep» events and the «has resumed from sleeping» events followed strictly alternating each other.

    How to determine the cause of the crashes? 
    Thursday, February 26, 2015 2:40 AM

Answers

  • levgorin

    DirectX is having problems setting the power state.  Since DirectX is installed by the video driver and since yours is not current (2014) I would start by removing the current driver and installing the Feb 2015 driver. 

    Also Please run powercfg -a from an elevated command prompt so we can see what power states are supported.

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\022315-19905-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    WARNING: Whitespace at start of path element
    WARNING: Whitespace at end of path element
    Error: Empty Path.
    Symbol search path is: 
    SRV*e:\symbols*http://msdl.microsoft.com/download/symbols 
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18717.x86fre.win7sp1_gdr.150113-1808
    Machine Name:
    Kernel base = 0x82e4c000 PsLoadedModuleList = 0x82f965b0
    Debug session time: Mon Feb 23 00:36:44.642 2015 (UTC - 5:00)
    System Uptime: 4 days 18:36:01.469
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module list
    ..................................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {ed356000, 0, 82e84e73, 0}
    
    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+17971f )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: ed356000, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 82e84e73, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 00000000, (reserved)
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 82fb684c
    Unable to read MiSystemVaType memory at 82f95f00
     ed356000 
    
    FAULTING_IP: 
    nt!memcpy+33
    82e84e73 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]
    
    MM_INTERNAL_CODE:  0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    TRAP_FRAME:  ba89f574 -- (.trap 0xffffffffba89f574)
    ErrCode = 00000000
    eax=ed366000 ebx=9ff10000 ecx=00004000 edx=00000000 esi=ed356000 edi=9ff10000
    eip=82e84e73 esp=ba89f5e8 ebp=ba89f5f0 iopl=0         nv up ei pl nz ac po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010212
    nt!memcpy+0x33:
    82e84e73 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 82e8ca78 to 82ed99ad
    
    STACK_TEXT:  
    ba89f55c 82e8ca78 00000000 ed356000 00000000 nt!MmAccessFault+0x104
    ba89f55c 82e84e73 00000000 ed356000 00000000 nt!KiTrap0E+0xdc
    ba89f5f0 9579671f 9ff10000 ed356000 00010000 nt!memcpy+0x33
    WARNING: Stack unwind information not available. Following frames may be wrong.
    ba89f608 957f3f05 9ff10000 ed356000 00010000 nvlddmkm+0x17971f
    ba89f620 957f453f 87801000 86ae8688 86b40788 nvlddmkm+0x1d6f05
    ba89f6e0 95e5fce4 877f7000 87808958 86ae8688 nvlddmkm+0x1d753f
    ba89f808 95ea430d 877f7000 877ff000 00000000 nvlddmkm+0x842ce4
    ba89f858 95769875 877f7000 00000000 86c95000 nvlddmkm+0x88730d
    ba89f8ec 956d78b0 00000000 00000000 00000001 nvlddmkm+0x14c875
    ba89f9bc 956d7089 00000001 00000001 00000002 nvlddmkm+0xba8b0
    ba89fa7c 95e1ba60 ffffffff 00000001 00000002 nvlddmkm+0xba089
    ba89fab0 96111148 86c95000 ffffffff 00000001 nvlddmkm+0x7fea60
    ba89fad4 96111d00 86bca7d0 86c95000 ffffffff dxgkrnl!DpiDxgkDdiSetPowerState+0x36
    ba89fb00 96111ac9 8595f920 00000001 00000005 dxgkrnl!DpiFdoSetAdapterPowerState+0x202
    ba89fb44 9611177a 8595f920 ae1863b0 ba89fb78 dxgkrnl!DpiFdoHandleDevicePower+0x346
    ba89fb54 9611126d 8595f920 ae1863b0 ae186444 dxgkrnl!DpiFdoDispatchPower+0x21
    ba89fb78 95728cfc 8595f920 ae1863b0 00000023 dxgkrnl!DpiDispatchPower+0xc8
    ba89fbe0 9572857e 8595f920 ae1863b0 8595f920 nvlddmkm+0x10bcfc
    ba89fbf8 82e61e6d 8595f920 ae1863b0 00000000 nvlddmkm+0x10b57e
    ba89fc50 83055fdf 88a97458 9772e257 00000000 nt!PopIrpWorker+0x351
    ba89fc90 82efc699 82e61b1c 88a97458 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvlddmkm+17971f
    9579671f ??              ???
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nvlddmkm+17971f
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53b44481
    
    FAILURE_BUCKET_ID:  0x50_nvlddmkm+17971f
    
    BUCKET_ID:  0x50_nvlddmkm+17971f
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x50_nvlddmkm+17971f
    
    FAILURE_ID_HASH:  {5a3d007f-d684-75eb-c5ef-176ed5e3aea3}
    
    Followup: MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Saturday, March 7, 2015 7:05 PM
    Friday, February 27, 2015 12:31 PM
  • Your current Chipset and BIOS Versions, seem to be older than the most current versions available for your system.

    I mention this because your system does not seem to be handling power commands or selective suspend requests very  well.

    STACK_TEXT: 
    ba89f55c 82e8ca78 00000000 ed356000 00000000 nt!MmAccessFault+0x104
    ba89f55c 82e84e73 00000000 ed356000 00000000 nt!KiTrap0E+0xdc
    ba89f5f0 9579671f 9ff10000 ed356000 00010000 nt!memcpy+0x33
    WARNING: Stack unwind information not available. Following frames may be wrong.
    ba89f608 957f3f05 9ff10000 ed356000 00010000 nvlddmkm+0x17971f
    ba89f620 957f453f 87801000 86ae8688 86b40788 nvlddmkm+0x1d6f05
    ba89f6e0 95e5fce4 877f7000 87808958 86ae8688 nvlddmkm+0x1d753f
    ba89f808 95ea430d 877f7000 877ff000 00000000 nvlddmkm+0x842ce4
    ba89f858 95769875 877f7000 00000000 86c95000 nvlddmkm+0x88730d
    ba89f8ec 956d78b0 00000000 00000000 00000001 nvlddmkm+0x14c875
    ba89f9bc 956d7089 00000001 00000001 00000002 nvlddmkm+0xba8b0
    ba89fa7c 95e1ba60 ffffffff 00000001 00000002 nvlddmkm+0xba089
    ba89fab0 96111148 86c95000 ffffffff 00000001 nvlddmkm+0x7fea60
    ba89fad4 96111d00 86bca7d0 86c95000 ffffffff dxgkrnl!DpiDxgkDdiSetPowerState+0x36
    ba89fb00 96111ac9 8595f920 00000001 00000005 dxgkrnl!DpiFdoSetAdapterPowerState+0x202
    ba89fb44 9611177a 8595f920 ae1863b0 ba89fb78 dxgkrnl!DpiFdoHandleDevicePower+0x346
    ba89fb54 9611126d 8595f920 ae1863b0 ae186444 dxgkrnl!DpiFdoDispatchPower+0x21
    ba89fb78 95728cfc 8595f920 ae1863b0 00000023 dxgkrnl!DpiDispatchPower+0xc8
    ba89fbe0 9572857e 8595f920 ae1863b0 8595f920 nvlddmkm+0x10bcfc
    ba89fbf8 82e61e6d 8595f920 ae1863b0 00000000 nvlddmkm+0x10b57e
    ba89fc50 83055fdf 88a97458 9772e257 00000000 nt!PopIrpWorker+0x351
    ba89fc90 82efc699 82e61b1c 88a97458 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

    I believe updating your chipset and BIOS version could help in that aspect.

    Machine ID Information [From Smbios 2.7, DMIVersion 39, Size=3932]
    BiosMajorRelease = 4
    BiosMinorRelease = 6
    BiosVendor = American Megatrends Inc.
    BiosVersion = 1401
    BiosReleaseDate = 02/18/2013
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    SystemFamily = To be filled by O.E.M.
    SystemVersion = System Version
    SystemSKU = SKU
    BaseBoardManufacturer = ASUSTeK COMPUTER INC.
    BaseBoardProduct = P8B75-M
    BaseBoardVersion = Rev X.0x

    You can see what updates are available in the link below.

    ASUSTeK P8B75-M Driver & Tools
    http://www.asus.com/Motherboards/P8B75M/HelpDesk_Download/

    As for the nVidia Display, you can uninstall the current version, and "Clean" reinstall it.

    Guide on how to install the NVIDIA Display Driver under Windows 7/Windows 8.
    http://nvidia.custhelp.com/app/answers/detail/a_id/2900/~/guide-on-how-to-install-the-nvidia-display-driver-under-windows-7%2Fwindows-8

    Note: See, Custom (Advanced) section of the knowledgebase article.

    Note: You may also want to run a disk check for errors on the volume, because of the nature of some of the crashes.


    Check your hard disk for errors in Windows 7

    http://support.microsoft.com/kb/2641432/

    • Marked as answer by ZigZag3143x Saturday, March 7, 2015 7:05 PM
    Tuesday, March 3, 2015 5:43 PM

All replies

  •  We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  


    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask


    Wanikiya and Dyami--Team Zigzag

    Thursday, February 26, 2015 3:31 AM
  • Thanks for your participation, Wanikiya and Dyami. I am sending you the  last 5 Minidump files. - 

    rghost.net/7Db8hqzkV 

    Friday, February 27, 2015 1:01 AM
  • levgorin

    DirectX is having problems setting the power state.  Since DirectX is installed by the video driver and since yours is not current (2014) I would start by removing the current driver and installing the Feb 2015 driver. 

    Also Please run powercfg -a from an elevated command prompt so we can see what power states are supported.

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\022315-19905-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    WARNING: Whitespace at start of path element
    WARNING: Whitespace at end of path element
    Error: Empty Path.
    Symbol search path is: 
    SRV*e:\symbols*http://msdl.microsoft.com/download/symbols 
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18717.x86fre.win7sp1_gdr.150113-1808
    Machine Name:
    Kernel base = 0x82e4c000 PsLoadedModuleList = 0x82f965b0
    Debug session time: Mon Feb 23 00:36:44.642 2015 (UTC - 5:00)
    System Uptime: 4 days 18:36:01.469
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module list
    ..................................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {ed356000, 0, 82e84e73, 0}
    
    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+17971f )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: ed356000, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 82e84e73, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 00000000, (reserved)
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 82fb684c
    Unable to read MiSystemVaType memory at 82f95f00
     ed356000 
    
    FAULTING_IP: 
    nt!memcpy+33
    82e84e73 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]
    
    MM_INTERNAL_CODE:  0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    TRAP_FRAME:  ba89f574 -- (.trap 0xffffffffba89f574)
    ErrCode = 00000000
    eax=ed366000 ebx=9ff10000 ecx=00004000 edx=00000000 esi=ed356000 edi=9ff10000
    eip=82e84e73 esp=ba89f5e8 ebp=ba89f5f0 iopl=0         nv up ei pl nz ac po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010212
    nt!memcpy+0x33:
    82e84e73 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 82e8ca78 to 82ed99ad
    
    STACK_TEXT:  
    ba89f55c 82e8ca78 00000000 ed356000 00000000 nt!MmAccessFault+0x104
    ba89f55c 82e84e73 00000000 ed356000 00000000 nt!KiTrap0E+0xdc
    ba89f5f0 9579671f 9ff10000 ed356000 00010000 nt!memcpy+0x33
    WARNING: Stack unwind information not available. Following frames may be wrong.
    ba89f608 957f3f05 9ff10000 ed356000 00010000 nvlddmkm+0x17971f
    ba89f620 957f453f 87801000 86ae8688 86b40788 nvlddmkm+0x1d6f05
    ba89f6e0 95e5fce4 877f7000 87808958 86ae8688 nvlddmkm+0x1d753f
    ba89f808 95ea430d 877f7000 877ff000 00000000 nvlddmkm+0x842ce4
    ba89f858 95769875 877f7000 00000000 86c95000 nvlddmkm+0x88730d
    ba89f8ec 956d78b0 00000000 00000000 00000001 nvlddmkm+0x14c875
    ba89f9bc 956d7089 00000001 00000001 00000002 nvlddmkm+0xba8b0
    ba89fa7c 95e1ba60 ffffffff 00000001 00000002 nvlddmkm+0xba089
    ba89fab0 96111148 86c95000 ffffffff 00000001 nvlddmkm+0x7fea60
    ba89fad4 96111d00 86bca7d0 86c95000 ffffffff dxgkrnl!DpiDxgkDdiSetPowerState+0x36
    ba89fb00 96111ac9 8595f920 00000001 00000005 dxgkrnl!DpiFdoSetAdapterPowerState+0x202
    ba89fb44 9611177a 8595f920 ae1863b0 ba89fb78 dxgkrnl!DpiFdoHandleDevicePower+0x346
    ba89fb54 9611126d 8595f920 ae1863b0 ae186444 dxgkrnl!DpiFdoDispatchPower+0x21
    ba89fb78 95728cfc 8595f920 ae1863b0 00000023 dxgkrnl!DpiDispatchPower+0xc8
    ba89fbe0 9572857e 8595f920 ae1863b0 8595f920 nvlddmkm+0x10bcfc
    ba89fbf8 82e61e6d 8595f920 ae1863b0 00000000 nvlddmkm+0x10b57e
    ba89fc50 83055fdf 88a97458 9772e257 00000000 nt!PopIrpWorker+0x351
    ba89fc90 82efc699 82e61b1c 88a97458 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvlddmkm+17971f
    9579671f ??              ???
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nvlddmkm+17971f
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53b44481
    
    FAILURE_BUCKET_ID:  0x50_nvlddmkm+17971f
    
    BUCKET_ID:  0x50_nvlddmkm+17971f
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x50_nvlddmkm+17971f
    
    FAILURE_ID_HASH:  {5a3d007f-d684-75eb-c5ef-176ed5e3aea3}
    
    Followup: MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Saturday, March 7, 2015 7:05 PM
    Friday, February 27, 2015 12:31 PM
  • Thanks for your participation!

    Here is the result of running the powercfg –a:

    ===============================

    C:\Users\Nathalie>powercfg -a

    The following sleep states are available on this system: Standby ( S3 ) Hibernate Hybrid Sleep

    The following sleep states are not available on this system:

    Standby (S1)

            The system firmware does not support this standby state.

    Standby (S2)

            The system firmware does not support this standby state.

    C:\Users\Nathalie>

    The settings of the power plan are: Turn off the display 10 minutes, Put the computer to sleep 45 minutes.

    Regarding DirectX. I ran dxdiag, and did not receive any alarms - under Windows 7 installed DirectX 11 - that is all. I have another computer under Windows 7, in which there is no crashes. Dxdiag gives the same message there, and there is the same dxgkrnl.sys with the same date.

    I tried to update dxgkrnl.sys through Device Meneger, but did not find there such an opportunity.

    Automatic update of operating system from Microsoft is set on both computers.

    I could not find a driver update from Microsoft for DirectX 11 on the Internet. There are only numerous pages of other authors who encourage people to download and run a program that will improve all at once. But I try not to use such proposals, because I have a sad experience in this part.

    But I found the difference in Windows 7 between my two computers. On the computer on which there WERE NO CRASHES, there is

    c: \ Windows \ assembly \ GAC \ Microsoft.DirectX folder and 8 other similar  folders. On the computer on which WERE CRASHES there are no such folders.

    Could this difference be the reason for the crashes? 

    Sunday, March 1, 2015 2:31 AM
  • Hi,

    From your dump file, it point to NVIDIA display driver.

    Uninstall NVIDIA driver and install the new nvidia software driver for test.

    Update DirectX as the following article:

    How to install the latest version of DirectX

    http://support.microsoft.com/kb/179113

     


    Karen Hu
    TechNet Community Support

    Tuesday, March 3, 2015 7:07 AM
  • Your current Chipset and BIOS Versions, seem to be older than the most current versions available for your system.

    I mention this because your system does not seem to be handling power commands or selective suspend requests very  well.

    STACK_TEXT: 
    ba89f55c 82e8ca78 00000000 ed356000 00000000 nt!MmAccessFault+0x104
    ba89f55c 82e84e73 00000000 ed356000 00000000 nt!KiTrap0E+0xdc
    ba89f5f0 9579671f 9ff10000 ed356000 00010000 nt!memcpy+0x33
    WARNING: Stack unwind information not available. Following frames may be wrong.
    ba89f608 957f3f05 9ff10000 ed356000 00010000 nvlddmkm+0x17971f
    ba89f620 957f453f 87801000 86ae8688 86b40788 nvlddmkm+0x1d6f05
    ba89f6e0 95e5fce4 877f7000 87808958 86ae8688 nvlddmkm+0x1d753f
    ba89f808 95ea430d 877f7000 877ff000 00000000 nvlddmkm+0x842ce4
    ba89f858 95769875 877f7000 00000000 86c95000 nvlddmkm+0x88730d
    ba89f8ec 956d78b0 00000000 00000000 00000001 nvlddmkm+0x14c875
    ba89f9bc 956d7089 00000001 00000001 00000002 nvlddmkm+0xba8b0
    ba89fa7c 95e1ba60 ffffffff 00000001 00000002 nvlddmkm+0xba089
    ba89fab0 96111148 86c95000 ffffffff 00000001 nvlddmkm+0x7fea60
    ba89fad4 96111d00 86bca7d0 86c95000 ffffffff dxgkrnl!DpiDxgkDdiSetPowerState+0x36
    ba89fb00 96111ac9 8595f920 00000001 00000005 dxgkrnl!DpiFdoSetAdapterPowerState+0x202
    ba89fb44 9611177a 8595f920 ae1863b0 ba89fb78 dxgkrnl!DpiFdoHandleDevicePower+0x346
    ba89fb54 9611126d 8595f920 ae1863b0 ae186444 dxgkrnl!DpiFdoDispatchPower+0x21
    ba89fb78 95728cfc 8595f920 ae1863b0 00000023 dxgkrnl!DpiDispatchPower+0xc8
    ba89fbe0 9572857e 8595f920 ae1863b0 8595f920 nvlddmkm+0x10bcfc
    ba89fbf8 82e61e6d 8595f920 ae1863b0 00000000 nvlddmkm+0x10b57e
    ba89fc50 83055fdf 88a97458 9772e257 00000000 nt!PopIrpWorker+0x351
    ba89fc90 82efc699 82e61b1c 88a97458 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

    I believe updating your chipset and BIOS version could help in that aspect.

    Machine ID Information [From Smbios 2.7, DMIVersion 39, Size=3932]
    BiosMajorRelease = 4
    BiosMinorRelease = 6
    BiosVendor = American Megatrends Inc.
    BiosVersion = 1401
    BiosReleaseDate = 02/18/2013
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    SystemFamily = To be filled by O.E.M.
    SystemVersion = System Version
    SystemSKU = SKU
    BaseBoardManufacturer = ASUSTeK COMPUTER INC.
    BaseBoardProduct = P8B75-M
    BaseBoardVersion = Rev X.0x

    You can see what updates are available in the link below.

    ASUSTeK P8B75-M Driver & Tools
    http://www.asus.com/Motherboards/P8B75M/HelpDesk_Download/

    As for the nVidia Display, you can uninstall the current version, and "Clean" reinstall it.

    Guide on how to install the NVIDIA Display Driver under Windows 7/Windows 8.
    http://nvidia.custhelp.com/app/answers/detail/a_id/2900/~/guide-on-how-to-install-the-nvidia-display-driver-under-windows-7%2Fwindows-8

    Note: See, Custom (Advanced) section of the knowledgebase article.

    Note: You may also want to run a disk check for errors on the volume, because of the nature of some of the crashes.


    Check your hard disk for errors in Windows 7

    http://support.microsoft.com/kb/2641432/

    • Marked as answer by ZigZag3143x Saturday, March 7, 2015 7:05 PM
    Tuesday, March 3, 2015 5:43 PM