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: Cold Boot BSOD

13 Mar 2010   #1

Windows 7 Ultimate 64-bit
 
 
Cold Boot BSOD

BSOD on startup after 8 hours or so of being off overnight. Occurs everyday.
Ran memtest+86 & passed 7 loops..

I remove a ram stick & replace it for the BSODs to go away and windows to startup, continues to run fine all day.

Ran through windbg but I don't really know what I'm looking at.
I have also attached my minidump file and my system.nfo for reference if needed.

In hopes that I was reading the results correctly I updated my nvidia drivers from nvidia's website and thought it would help, but no luck.

Thanks in advance, any ideas or suggestions are appreciated.

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


Loading Dump File [c:\windows\minidump\031310-15406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;symsrv*symsrv.dll*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a15000 PsLoadedModuleList = 0xfffff800`02c52e50
Debug session time: Sat Mar 13 07:43:47.609 2010 (UTC - 6:00)
System Uptime: 0 days 0:00:15.015
Loading Kernel Symbols
...............................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {10, 2, 1, fffff80002aac35f}

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+1fd27 )
Processing initial command '!analyze -v'

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002aac35f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbd0e0
 0000000000000010 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReplenishPageSlist+100
fffff800`02aac35f f00fba6b1000    lock bts dword ptr [rbx+10h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  csrss.exe

TRAP_FRAME:  fffff88005de5ac0 -- (.trap 0xfffff88005de5ac0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffffffffffffff rbx=0000000000000000 rcx=fdffffffffffffff
rdx=0000000000000047 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002aac35f rsp=fffff88005de5c50 rbp=fffffa8006600de8
 r8=fffff80002cbf400  r9=fffffa8006600000 r10=000000000021ffff
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiReplenishPageSlist+0x100:
fffff800`02aac35f f00fba6b1000    lock bts dword ptr [rbx+10h],0 ds:00000000`00000010=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a86469 to fffff80002a86f00

STACK_TEXT:  
fffff880`05de5978 fffff800`02a86469 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`05de5980 fffff800`02a850e0 : 00000000`00000021 00000000`00000000 fffffa80`079c6c40 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`05de5ac0 fffff800`02aac35f : fffffa80`0890ac50 fffff880`04948887 fffffa80`078e7010 00000000`00000801 : nt!KiPageFault+0x260
fffff880`05de5c50 fffff800`02ba76ec : fffff800`02cbf400 00000000`0000174e 00000000`00000059 fffffa80`028390b0 : nt!MiReplenishPageSlist+0x100
fffff880`05de5cb0 fffff800`02ba7f06 : 00000000`00000080 00000000`00004000 00000000`00000000 00000000`0021ffff : nt!MiAllocateMdlPagesByLists+0x60c
fffff880`05de5de0 fffff800`02ba8769 : 00000000`00000001 fffff880`05de6801 fffffa80`07cb3000 fffff880`038d5000 : nt!MiAllocatePagesForMdl+0x456
fffff880`05de5ee0 fffff880`04824d27 : 00000000`00000000 fffffa80`07b77ba0 00000000`00000000 fffff880`05de6980 : nt!MmAllocatePagesForMdlEx+0x89
fffff880`05de5f20 00000000`00000000 : fffffa80`07b77ba0 00000000`00000000 fffff880`05de6980 fffffa80`00000001 : nvlddmkm+0x1fd27


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+1fd27
fffff880`04824d27 ??              ???

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  nvlddmkm+1fd27

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5ce19c

FAILURE_BUCKET_ID:  X64_0xA_nvlddmkm+1fd27

BUCKET_ID:  X64_0xA_nvlddmkm+1fd27

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


My System SpecsSystem Spec
.

13 Mar 2010   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by David63dn View Post
BSOD on startup after 8 hours or so of being off overnight. Occurs everyday.
Ran memtest+86 & passed 7 loops..

I remove a ram stick & replace it for the BSODs to go away and windows to startup, continues to run fine all day.

Ran through windbg but I don't really know what I'm looking at.
I have also attached my minidump file and my system.nfo for reference if needed.

In hopes that I was reading the results correctly I updated my nvidia drivers from nvidia's website and thought it would help, but no luck.

Thanks in advance, any ideas or suggestions are appreciated.

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


Loading Dump File [c:\windows\minidump\031310-15406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;symsrv*symsrv.dll*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a15000 PsLoadedModuleList = 0xfffff800`02c52e50
Debug session time: Sat Mar 13 07:43:47.609 2010 (UTC - 6:00)
System Uptime: 0 days 0:00:15.015
Loading Kernel Symbols
...............................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {10, 2, 1, fffff80002aac35f}

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+1fd27 )
Processing initial command '!analyze -v'

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002aac35f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbd0e0
 0000000000000010 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReplenishPageSlist+100
fffff800`02aac35f f00fba6b1000    lock bts dword ptr [rbx+10h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  csrss.exe

TRAP_FRAME:  fffff88005de5ac0 -- (.trap 0xfffff88005de5ac0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffffffffffffff rbx=0000000000000000 rcx=fdffffffffffffff
rdx=0000000000000047 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002aac35f rsp=fffff88005de5c50 rbp=fffffa8006600de8
 r8=fffff80002cbf400  r9=fffffa8006600000 r10=000000000021ffff
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiReplenishPageSlist+0x100:
fffff800`02aac35f f00fba6b1000    lock bts dword ptr [rbx+10h],0 ds:00000000`00000010=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a86469 to fffff80002a86f00

STACK_TEXT:  
fffff880`05de5978 fffff800`02a86469 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`05de5980 fffff800`02a850e0 : 00000000`00000021 00000000`00000000 fffffa80`079c6c40 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`05de5ac0 fffff800`02aac35f : fffffa80`0890ac50 fffff880`04948887 fffffa80`078e7010 00000000`00000801 : nt!KiPageFault+0x260
fffff880`05de5c50 fffff800`02ba76ec : fffff800`02cbf400 00000000`0000174e 00000000`00000059 fffffa80`028390b0 : nt!MiReplenishPageSlist+0x100
fffff880`05de5cb0 fffff800`02ba7f06 : 00000000`00000080 00000000`00004000 00000000`00000000 00000000`0021ffff : nt!MiAllocateMdlPagesByLists+0x60c
fffff880`05de5de0 fffff800`02ba8769 : 00000000`00000001 fffff880`05de6801 fffffa80`07cb3000 fffff880`038d5000 : nt!MiAllocatePagesForMdl+0x456
fffff880`05de5ee0 fffff880`04824d27 : 00000000`00000000 fffffa80`07b77ba0 00000000`00000000 fffff880`05de6980 : nt!MmAllocatePagesForMdlEx+0x89
fffff880`05de5f20 00000000`00000000 : fffffa80`07b77ba0 00000000`00000000 fffff880`05de6980 fffffa80`00000001 : nvlddmkm+0x1fd27


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+1fd27
fffff880`04824d27 ??              ???

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  nvlddmkm+1fd27

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5ce19c

FAILURE_BUCKET_ID:  X64_0xA_nvlddmkm+1fd27

BUCKET_ID:  X64_0xA_nvlddmkm+1fd27

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

Great first post. The DMP does indeed point to your video driver. Sometimes to remove all trace of an old driver you must use their un-installer.

You should google the uninstaller and remove all vestiges of the old driver. The DL and install a new copy.

I would also run a system file check to verify and repair your system files
(type cmd in search>right click and run as admin>sfc /scannow)

Let us know the results as you may have to re-run SFC.

Let us know if you need help


Ken
My System SpecsSystem Spec
13 Mar 2010   #3

Windows 7 Ultimate 64-bit
 
 

I had just finished running sfc before your post, all was well. I ran the uninstaller and ran driver sweeper in safe mode. Continued to run the installer and then ran sfc again which turned out fine.

In device manager there is a "other device" that is not recognized which is named coprocessor. I have to install drivers from my motherboards cd but it has nothing to do with video so I am going to leave it there for now until I can see if anything has changed tomorrow.

I will post tomorrow morning (about 24 hours from now) after a cold boot with results. And thanks for the help I appreciate it.
My System SpecsSystem Spec
.


13 Mar 2010   #4

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by David63dn View Post
I had just finished running sfc before your post, all was well. I ran the uninstaller and ran driver sweeper in safe mode. Continued to run the installer and then ran sfc again which turned out fine.

In device manager there is a "other device" that is not recognized which is named coprocessor. I have to install drivers from my motherboards cd but it has nothing to do with video so I am going to leave it there for now until I can see if anything has changed tomorrow.

I will post tomorrow morning (about 24 hours from now) after a cold boot with results. And thanks for the help I appreciate it.

BSOD on cold boot may be a power plan (sleep/hibernate) cofiguration issue.

Ken
My System SpecsSystem Spec
13 Mar 2010   #5

Windows 7 Ultimate 64-bit
 
 

Quote:
BSOD on cold boot may be a power plan (sleep/hibernate) cofiguration issue.
How would I troubleshoot that?
My System SpecsSystem Spec
13 Mar 2010   #6

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by David63dn View Post
Quote:
BSOD on cold boot may be a power plan (sleep/hibernate) cofiguration issue.
How would I troubleshoot that?


You can run powercfg in a cmd window. there is s switch (i forget which) that will give you a report of the various states.

to view the switches type cmd in search. then type powercfg /? and it will display the various switches.

I am sure someone will drive by here and know which one it is.


Ken
My System SpecsSystem Spec
13 Mar 2010   #7

Windows 7 Ultimate 64-bit
 
 

I ran powercfg -energy and got some results however I don't see that my system should ever sleep or hibernate. Below is the result and attached rar with html file if that is easier to read.

Code:
 Power Efficiency Diagnostics Report
Computer Name ACER-PC 
Scan Time 2010-03-13T16:26:35Z      
Scan Duration 60 seconds                       
System Manufacturer MSI      
System Product Name MS-7612 
BIOS Date 12/15/2009 
BIOS Version V1.2      
OS Build 7600      
Platform Role PlatformRoleDesktop      
Plugged In true      
Process Count 52      
Thread Count 630      
Report GUID                      {fe5070e4-3cb1-4fff-95a6-50cd96c81473}                  Analysis Results
  Errors
      Power Policy:Power Plan Personality is  High Performance (Plugged In)
    The current power plan personality is  High Performance when the system is plugged in.
    
      Power Policy:Display timeout disabled  (Plugged In)
    The display is not configured to turn  off after a period of inactivity.
    
      Power Policy:Sleep timeout is disabled  (Plugged In)
    The computer is not configured to  automatically sleep after a period of inactivity.
    
      Power Policy:Disk idle is disabled  (Plugged In)
    The disk is not configured to turn  off after a period of disk inactivity.
    
      Power Policy:Minimum processor performance  state is 100% (Plugged In)
    The processor is not configured to  automatically reduce power consumption based on activity.
    
      Power Policy:USB Selective Suspend is  disabled (Plugged In)
    The current power policy has globally  disabled USB selective suspend.
    
      Power Policy:PCI Express ASPM is disabled  (Plugged In)
    The current power policy for PCI  Express Active State Power Management (ASPM) is configured to Off.
    
      USB Suspend:USB Device not Entering  Suspend
    The USB device did not enter the  Suspend state.  
     Processor power management may be prevented if a 
     USB  device does not enter the Suspend state when not in use.
      Device Name USB Composite Device 
      Host Controller ID PCI\VEN_10DE&DEV_077D      
      Host Controller Location PCI bus 0, device 4, function 0      
      Device ID USB\VID_099A&PID_2515 Port Path 2    
  
  
      USB Suspend:USB Device not Entering  Suspend
    The USB device did not enter the  Suspend state.  
    Processor power management may be prevented if a 
   USB  device does not enter the Suspend state when not in use.
      Device Name USB Root Hub      
      Host Controller ID PCI\VEN_10DE&DEV_077D      
      Host Controller Location PCI bus 0, device 4, function 0     
      Device ID USB\VID_10DE&PID_077D Port Path 
    
  
  
      USB Suspend:USB Device not Entering  Suspend
    The USB device did not enter the  Suspend state.  
     Processor power management may be prevented if a 
     USB  device does not enter the Suspend state when not in use.
      Device Name USB Root Hub      
      Host Controller ID PCI\VEN_10DE&DEV_077C 
      Host Controller Location PCI bus 0, device 2, function 1 
      Device ID USB\VID_10DE&PID_077C Port Path 
    
  
  
      USB Suspend:USB Device not Entering  Suspend
    The USB device did not enter the  Suspend state.  
     Processor power management may be prevented if a 
     USB  device does not enter the Suspend state when not in use.
      Device Name USB Root Hub      
      Host Controller ID PCI\VEN_10DE&DEV_077B      
      Host Controller Location PCI bus 0, device 2, function 0      
      Device ID USB\VID_10DE&PID_077B Port Path 
    
  
  
      USB Suspend:USB Device not Entering  Suspend
    The USB device did not enter the  Suspend state.  
    Processor power management may be prevented if a 
    USB  device does not enter the Suspend state when not in use.
      Device Name USB Root Hub      
      Host Controller ID PCI\VEN_10DE&DEV_077E      
      Host Controller Location PCI bus 0, device 4, function 1      
      Device ID USB\VID_10DE&PID_077E Port Path 
    
  
  
      Platform Power Management  Capabilities:System firmware (BIOS) does not support S3.
    The hardware in this computer does  not support the S3 sleep state.

  
  
  Warnings

      Power Policy:802.11 Radio Power Policy is  Maximum Performance (Plugged In)
    The current power policy for  802.11-compatible wireless network adapters
      is not configured to use  low-power modes.

  
  
  Information

      Platform Timer Resolution:Platform Timer  Resolution
    The default platform timer resolution  is 15.6ms (15625000ns) and should be used whenever the system is idle.   
      If the timer resolution is increased, processor power management  technologies may not be effective.  
      The timer resolution may be  increased due to multimedia playback or graphical animations.
      Current Timer Resolution (100ns units) 156250    
  
  
      Power Policy:Active Power Plan
    The current power plan in use
                            Plan Name                                             OEM High Performance                       Plan GUID {8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c}    
  
  
      Power Policy:Power Plan Personality  (Plugged In)
    The personality of the current power  plan when the system is plugged in.
      Personality                           High Performance                          
  
  
      Power Policy:Video quality (Plugged In)
    Enables Windows Media Player to  optimize for quality or power savings when playing video.
      Quality Mode                           Optimize for Video Quality                          
  
  
      System Availability Requests:Analysis  Success
    Analysis was successful. No energy  efficiency problems were found.  No information was returned.

  
  
      CPU Utilization:Processor utilization is  low
    The average processor utilization  during the trace was very low.  The system will consume less power when  the average processor utilization is very low.
      Average Utilization (%) 0.55    
  
  
      Battery:Analysis Success
    Analysis was successful. No energy  efficiency problems were found.  No information was returned.

  
  
      Platform Power Management  Capabilities:Supported Sleep States
    Sleep states allow the computer to  enter low-power modes after a period of inactivity.  The S3 sleep state  is the default sleep state for Windows platforms.  The S3 sleep state  consumes only enough power to preserve memory contents and allow the  computer to resume working quickly.  Very few platforms support the S1  or S2 Sleep states.
      S1 Sleep Supported true S2 Sleep Supported false S3 Sleep Supported false S4 Sleep Supported true    
  
  
      Platform Power Management  Capabilities:Processor Power Management Capabilities
    Effective processor power management  enables the computer to automatically balance performance and energy  consumption.
      Group 0 Index 0 Idle (C) State Count 1 Performance (P) State Count 0 Throttle (T) State Count 0    
  
  
      Platform Power Management  Capabilities:Processor Power Management Capabilities
    Effective processor power management  enables the computer to automatically balance performance and energy  consumption.
      Group 0 Index 1 Idle (C) State Count 1 Performance (P) State Count 0 Throttle (T) State Count 0    
  
  
      Platform Power Management  Capabilities:Processor Power Management Capabilities
    Effective processor power management  enables the computer to automatically balance performance and energy  consumption.
      Group 0 Index 2 Idle (C) State Count 1 Performance (P) State Count 0 Throttle (T) State Count 0
My System SpecsSystem Spec
14 Mar 2010   #8

Windows 7 Ultimate 64-bit
 
 

System was off for about 6 hours while I was gone. Was up for about 5 minutes before I hit start>Shutdown. Before it could shutdown I got a BSOD & immediate restart, I was unable to read it and no minidump or information in Action Center. System restarted and I logged in then BSOD as I was looking for the minidump.
This time system created a minidump file which is different from my last. Take a look, I ran it through windbg, see if you have any advice for me.
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [c:\windows\minidump\031310-18250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;symsrv*symsrv.dll*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a4e000 PsLoadedModuleList = 0xfffff800`02c8be50
Debug session time: Sat Mar 13 22:50:18.727 2010 (UTC - 6:00)
System Uptime: 0 days 0:03:32.149
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88009ce9368, fffff88009ce8bc0, fffff8800125cb5a}

Processing initial command '!analyze -v'
Probably caused by : Ntfs.sys ( Ntfs!NtfsCleanupIrpContext+595 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff88009ce9368
Arg3: fffff88009ce8bc0
Arg4: fffff8800125cb5a

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


EXCEPTION_RECORD:  fffff88009ce9368 -- (.exr 0xfffff88009ce9368)
ExceptionAddress: fffff8800125cb5a (Ntfs!NtfsCleanupIrpContext+0x0000000000000595)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88009ce8bc0 -- (.cxr 0xfffff88009ce8bc0)
rax=fa80081c75f004c0 rbx=fffff88009ce97b0 rcx=fffff8a0019dd2c0
rdx=0000000000000000 rsi=fffffa800514b250 rdi=fffff8a001bdd140
rip=fffff8800125cb5a rsp=fffff88009ce95a0 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000001 r10=fffff88009ce97b0
r11=fffff8a001bdd2b0 r12=0000000000000001 r13=0000000000000702
r14=0000000080000005 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
Ntfs!NtfsCleanupIrpContext+0x595:
fffff880`0125cb5a 4c895808        mov     qword ptr [rax+8],r11 ds:002b:fa80081c`75f004c8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  1

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf60e0
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs!NtfsCleanupIrpContext+595
fffff880`0125cb5a 4c895808        mov     qword ptr [rax+8],r11

FAULTING_IP: 
Ntfs!NtfsCleanupIrpContext+595
fffff880`0125cb5a 4c895808        mov     qword ptr [rax+8],r11

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff88001261ef4 to fffff8800125cb5a

STACK_TEXT:  
fffff880`09ce95a0 fffff880`01261ef4 : fffff880`09ce97b0 fffffa80`00000001 00000000`00000000 fffffa80`0514b250 : Ntfs!NtfsCleanupIrpContext+0x595
fffff880`09ce95f0 fffff880`012e5765 : fffff8a0`01bdd010 fffff880`09ce97b0 00000000`80000005 fffff8a0`01bdd100 : Ntfs!NtfsExtendedCompleteRequestInternal+0xd4
fffff880`09ce9630 fffff880`012e5906 : fffff880`09ce97b0 fffffa80`0514b250 fffff880`00000000 fffffa80`00000068 : Ntfs!NtfsCommonQueryInformation+0xf6d
fffff880`09ce9710 fffff880`012e5ea4 : fffff880`09ce97b0 fffffa80`0514b250 fffffa80`0514b5f0 00000000`00000000 : Ntfs!NtfsFsdDispatchSwitch+0x106
fffff880`09ce9790 fffff880`00dad23f : fffff880`09ce9a30 fffff880`00dacbe9 fffff880`09ce9a00 fffffa80`05048c05 : Ntfs!NtfsFsdDispatchWait+0x14
fffff880`09ce9980 fffff880`00dab6df : fffffa80`05fa3b60 00000000`00000000 fffffa80`05fa3b00 fffffa80`0514b250 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`09ce9a10 fffff800`02da0c7a : fffffa80`0514b250 fffff880`09ce9ca0 00000000`0732e1a0 00000000`00000012 : fltmgr!FltpDispatch+0xcf
fffff880`09ce9a70 fffff800`02abf153 : 00000000`00000634 00000000`0732e188 00000000`0732e1a0 00000000`00000068 : nt!NtQueryInformationFile+0x535
fffff880`09ce9bb0 00000000`77abffca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0732e118 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77abffca


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsCleanupIrpContext+595

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

STACK_COMMAND:  .cxr 0xfffff88009ce8bc0 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCleanupIrpContext+595

BUCKET_ID:  X64_0x24_Ntfs!NtfsCleanupIrpContext+595

Followup: MachineOwner
---------
Rar of original minidump file included for reference if needed.
Thanks in advance.

EDIT: After post I ran chkdsk /r with no problems reported.
Code:
Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  76800 file records processed.                                          File verification completed.
  54 large file records processed.                                      0 bad file records processed.                                        2 EA records processed.                                              44 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  107934 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  76800 file SDs/SIDs processed.                                         Cleaning up 255 unused index entries from index $SII of file 0x9.
Cleaning up 255 unused index entries from index $SDH of file 0x9.
Cleaning up 255 unused security descriptors.
Security descriptor verification completed.
  15568 data files processed.                                            CHKDSK is verifying Usn Journal...
  34068784 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  76784 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  11502788 free clusters processed.                                         Free space verification is complete.
Windows has checked the file system and found no problems.

  78148607 KB total disk space.
  31917624 KB in 56947 files.
     40896 KB in 15569 indexes.
         0 KB in bad sectors.
    178931 KB in use by the system.
     65536 KB occupied by the log file.
  46011156 KB available on disk.

      4096 bytes in each allocation unit.
  19537151 total allocation units on disk.
  11502789 allocation units available on disk.

Internal Info:
00 2c 01 00 4f 1b 01 00 ff 25 02 00 00 00 00 00  .,..O....%......
32 01 00 00 2c 00 00 00 00 00 00 00 00 00 00 00  2...,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.
My System SpecsSystem Spec
16 Mar 2010   #9

Windows 7 x64
 
 

David,

I'm having the exact same issues with my machine as well. I just can't turn it off for more than 4+ hrs it seems. When I boot out of a cold shutdown I need to run Memtest86+ for a couple passes before the machien will boot up. I can also restart the machine perfectly fine. I'm hoping some advice comes along soon because my situation is very similiar to yours and I would like to know how to fix it.
My System SpecsSystem Spec
16 Mar 2010   #10

Windows 7 Ultimate 64-bit
 
 

While I am still self diagnosing my issues, I can only recommend running memtest86 on your g.skill ram one stick at a time. And let it run for about 8 loops on each stick. Let it run overnight as it will take about 8 hours give or take.
In my research I have come across many similar issues to my own that are caused by bad RAM. G.skill is known for its bad sticks as they have little to no quality tests. I may even RMA my RAM for exchange even though memtest86 is coming out clean just to see if it will help and the fact that I only have 2 weeks left to RMA it through newegg.
Best of luck to you and check back on this thread I will post when I find a solution... and I will find a solution.
My System SpecsSystem Spec
Reply

 Cold Boot BSOD





Thread Tools



Similar help and support threads for2: Cold Boot BSOD
Thread Forum
Random Freezing/BSOD, Boot Disk Failure, OK Cold Boot then Repeat BSOD Help and Support
Cold Boot BSOD....I believe... BSOD Help and Support
BSOD only on cold boot BSOD Help and Support
BSOD KSOD No Boot Win7 64bit Cold Boot BSOD Help and Support
Sometimes BSOD - Cold boot BSOD Help and Support
BSOD w/cold boot BSOD Help and Support
BSOD on cold boot 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 03:10 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33