Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD While Computer is Idle

06 Jun 2015   #1
cricktopsy

New York
 
 
BSOD While Computer is Idle

Already ran memtest and RAM is fine.

I believe it has something to do with sleep/wake on LAN, but not too sure.

Any help is greatly appreciated!


My System SpecsSystem Spec
.
07 Jun 2015   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

How many passes did you run memtest for?

 Clean boot
Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:
  • Click on the
  • Type CMD on Search
  • Left click and Run as Administrator
  • Type SFC /scannow
Full tutorial here:Run Disk Check on your Hard Drive for file system errors and bad sectors on it.

 Hard Drive Diagnostics


  • Double click and open my computer.
  • Right click on desired drive and hit properties.
  • Click on tools tab and Check now.

Read complete instructions on the tutorial: Disk Check

Other Tests:
 


Code:
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\YUSSIKAT\Downloads\MAIN-PC-Sat_06_06_2015_100316_10\060415-8424-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18798.amd64fre.win7sp1_gdr.150316-1654
Machine Name:
Kernel base = 0xfffff800`03405000 PsLoadedModuleList = 0xfffff800`0364a890
Debug session time: Thu Jun  4 10:02:03.796 2015 (UTC + 6:00)
System Uptime: 0 days 10:06:42.935
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
............................................................
Loading User Symbols
Loading unloaded module list
.....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a0a408c258, 1, fffff800035b0157, 5}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Could not read faulting driver name
Probably caused by : dxgkrnl.sys ( dxgkrnl!DoublyLinkedList<DMMVIDPNSOURCEMODE>::DoublyLinkedList<DMMVIDPNSOURCEMODE>+c0 )

Followup: MachineOwner
---------

3: 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: fffff8a0a408c258, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff800035b0157, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800036b4100
GetUlongFromAddress: unable to read from fffff800036b41c0
 fffff8a0a408c258 Paged pool

FAULTING_IP: 
nt!ExAllocatePoolWithTag+537
fffff800`035b0157 48895808        mov     qword ptr [rax+8],rbx

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  fffff88007f42b00 -- (.trap 0xfffff88007f42b00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a0a408c250 rbx=0000000000000000 rcx=fffff8a0213faf20
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800035b0157 rsp=fffff88007f42c90 rbp=0000000000001000
 r8=0000000000000001  r9=fffffa800ca00440 r10=fffffa800ca00288
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!ExAllocatePoolWithTag+0x537:
fffff800`035b0157 48895808        mov     qword ptr [rax+8],rbx ds:fffff8a0`a408c258=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800034f25ca to fffff80003477a40

STACK_TEXT:  
fffff880`07f42998 fffff800`034f25ca : 00000000`00000050 fffff8a0`a408c258 00000000`00000001 fffff880`07f42b00 : nt!KeBugCheckEx
fffff880`07f429a0 fffff800`03475b6e : 00000000`00000001 fffff8a0`a408c258 00000000`00000100 fffffa80`0ca00440 : nt! ?? ::FNODOBFM::`string'+0x402a1
fffff880`07f42b00 fffff800`035b0157 : 00000000`00000001 00000000`00000015 fffff880`07f42d30 fffff800`03475c7d : nt!KiPageFault+0x16e
fffff880`07f42c90 fffff880`048510fc : fffff880`00000002 fffff8a0`1d13bdb0 fffffa80`133b0900 00000000`00000000 : nt!ExAllocatePoolWithTag+0x537
fffff880`07f42d80 fffff880`04851301 : 00000000`00000001 fffff8a0`1d13bd90 00000000`00000000 fffff8a0`240a6690 : dxgkrnl!DoublyLinkedList<DMMVIDPNSOURCEMODE>::DoublyLinkedList<DMMVIDPNSOURCEMODE>+0xc0
fffff880`07f42dd0 fffff880`0485167f : 00000000`00000798 fffff8a0`24f0ae50 fffff8a0`19923240 00000000`000007ff : dxgkrnl!DMMVIDPNSOURCEMODESET::DMMVIDPNSOURCEMODESET+0x51
fffff880`07f42e00 fffff880`048505ec : fffff8a0`00000798 fffff8a0`245d8480 fffff8a0`1adf9628 00000000`000007ff : dxgkrnl!DMMVIDPNSOURCE::DMMVIDPNSOURCE+0x227
fffff880`07f42e40 fffff880`048ff232 : fffffa80`00000798 fffff8a0`1adf9620 00000000`00000000 fffff8a0`245d8480 : dxgkrnl!Set<DMMVIDPNSOURCE>::Set<DMMVIDPNSOURCE>+0xdc
fffff880`07f42e80 fffff880`048d5c9d : fffffa80`00000798 fffff880`07f42fa8 fffffa80`10b499e0 00000000`000007ff : dxgkrnl!DMMVIDPN::DMMVIDPN+0x12a
fffff880`07f42f30 fffff880`048d5eee : 00000000`fffffc52 fffff8a0`18fd8d50 00000000`00000000 fffff880`07f42ff0 : dxgkrnl!VIDPN_MGR::CreateVidPnCopyForClient+0x131
fffff880`07f42f70 fffff880`048e1e65 : fffff8a0`fffffc19 00000000`00000000 fffff8a0`019ae5a0 00000000`00000000 : dxgkrnl!VIDPN_MGR::CreateClientVidPnFromActive+0xf2
fffff880`07f42fa0 fffff880`048df23f : fffff880`0491f0ae 00000000`00000000 00000000`00000000 00000000`00000019 : dxgkrnl!VIDPN_MGR::RestorePresentPathToActiveVidPn+0x139
fffff880`07f43490 fffff880`0491f5cd : fffffa80`10b4d9b0 00000000`00000001 fffff880`07f43550 00000000`00239b42 : dxgkrnl!VIDPN_MGR::_MonitorEventHandler+0x547
fffff880`07f434f0 fffff880`0491f117 : 00000000`ffffffff 00000000`00000001 fffffa80`10b4d978 00000000`00000000 : dxgkrnl!MONITOR_MGR::_IssueMonitorEvent+0x135
fffff880`07f43550 fffff880`0491edf1 : 00000000`00000000 fffff880`048d1a68 00000000`00000001 00000000`00000000 : dxgkrnl!MONITOR_MGR::_EnableDisableMonitorInternal+0x303
fffff880`07f435c0 fffff880`0491a833 : fffffa80`112e9000 00000000`00000001 00000000`00000001 00000000`00000000 : dxgkrnl!MONITOR_MGR::_EnableDisableMonitor+0x165
fffff880`07f43630 fffff880`048d2404 : 00000000`00000000 00000000`00000000 00000000`fffffb12 00000000`00000000 : dxgkrnl!MonitorEnableDisableMonitor+0x173
fffff880`07f43670 fffff880`048c2e41 : fffffa80`10b3fd70 fffffa80`11845010 fffffa80`10b3fd70 fffffa80`10b3fec0 : dxgkrnl!DpiGdoDispatchInternalIoctl+0x99c
fffff880`07f43770 fffff880`05b954ba : fffffa80`11845010 fffffa80`11845010 fffffa80`10b3fd70 00000000`00000000 : dxgkrnl!DpiDispatchInternalIoctl+0xb9
fffff880`07f437c0 fffffa80`11845010 : fffffa80`11845010 fffffa80`10b3fd70 00000000`00000000 00000000`00000001 : nvlddmkm+0x1394ba
fffff880`07f437c8 fffffa80`11845010 : fffffa80`10b3fd70 00000000`00000000 00000000`00000001 00000000`00000000 : 0xfffffa80`11845010
fffff880`07f437d0 fffffa80`10b3fd70 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000004 : 0xfffffa80`11845010
fffff880`07f437d8 00000000`00000000 : 00000000`00000001 00000000`00000000 00000000`00000004 fffff960`00014afa : 0xfffffa80`10b3fd70


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!DoublyLinkedList<DMMVIDPNSOURCEMODE>::DoublyLinkedList<DMMVIDPNSOURCEMODE>+c0
fffff880`048510fc 4c8be0          mov     r12,rax

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  dxgkrnl!DoublyLinkedList<DMMVIDPNSOURCEMODE>::DoublyLinkedList<DMMVIDPNSOURCEMODE>+c0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  539e411c

IMAGE_VERSION:  6.1.7601.18510

FAILURE_BUCKET_ID:  X64_0x50_dxgkrnl!DoublyLinkedList_DMMVIDPNSOURCEMODE_::DoublyLinkedList_DMMVIDPNSOURCEMODE_+c0

BUCKET_ID:  X64_0x50_dxgkrnl!DoublyLinkedList_DMMVIDPNSOURCEMODE_::DoublyLinkedList_DMMVIDPNSOURCEMODE_+c0

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x50_dxgkrnl!doublylinkedlist_dmmvidpnsourcemode_::doublylinkedlist_dmmvidpnsourcemode_+c0

FAILURE_ID_HASH:  {398dfb1e-11d6-99aa-714b-2d8ee89b2024}

Followup: MachineOwner
---------

3: kd> lmvm nvlddmkm
start             end                 module name
fffff880`05a5c000 fffff880`06494000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Apr 09 02:32:37 2015 (55259065)
    CheckSum:         009F7AE7
    ImageSize:        00A38000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
07 Jun 2015   #3
cricktopsy

New York
 
 

I ran 4 passes - took almost 10 hours

Ran SFC/Disk check as well - still nothing
My System SpecsSystem Spec
.

Reply

 BSOD While Computer is Idle




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD while computer is idle
Hello I'm writing to see if you can provide troubleshooting assistance with daily BSOD events I'm getting on my computer. They've been happening over the past week-2 weeks, primarily when the computer has been idle (i.e. at night, when I have been at work). I primarily use this machine for...
BSOD Help and Support
BSOD when computer goes idle
My computer seems to regularly get BSOD after it goes into idle mode for a while. It's been like this since I got the computer. I installed a better graphics card on day one so I'm not positive if that's the reason. It never happens for anything else. Only when it goes idle for a long time. One...
BSOD Help and Support
BSOD when computer is idle
I have been getting many BSOD messages lately. My screen has never actually turned blue, but that's what Windows calls it... Anyways, they usually tend to happen when I leave my computer idle. I have checked and it isn't a battery problem. This latest BSOD happened while I was doing a system scan...
BSOD Help and Support
BSOD While Computer was idle
Okay this is the second time that this happened. I was watching TV with my laptop running on the side. I had a few programs opened like Chrome and Notepad. Anyways I don't actually see the Blue Screen of Death, maybe because my monitor was asleep. So my computer just randomly restarts and once I...
BSOD Help and Support
BSOD - Crashes while computer idle/not idle (Unpredictable)
Windows 7 Enterprise 64bit Clean installation to windows 7 from Windows XP professional Hardware 18 months old OS installed 2 weeks ago I am currently facing the lovely BSOD error. The computer was recently upgraded from windows XP to Windows 7 enterprise 64bit , this was a fresh...
BSOD Help and Support
BSOD Computer was idle
It BSOD's about once a week! No clue why!
BSOD Help and Support


Our Sites

Site Links

About Us

Find 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 12:45.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App