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: Unexpected shutdown; no blue screen but got BSOD error report

28 Feb 2014   #1
seven09

Windows 7
 
 
Unexpected shutdown; no blue screen but got BSOD error report

No idea, the screen just went black and the computer restarted


My System SpecsSystem Spec
.
01 Mar 2014   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

A single crash dump is not enough. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffffffffff807, 0, fffff800032f4527, 0}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!ExfReleaseRundownProtection+7 )

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

2: 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: fffffffffffff807, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800032f4527, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000350d100
GetUlongFromAddress: unable to read from fffff8000350d1c0
 fffffffffffff807 

FAULTING_IP: 
nt!ExfReleaseRundownProtection+7
fffff800`032f4527 488b09          mov     rcx,qword ptr [rcx]

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.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  fffff880031af7a0 -- (.trap 0xfffff880031af7a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffffffffff807
rdx=00000000000007ee rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032f4527 rsp=fffff880031af930 rbp=fffff880031afa90
 r8=fffffffffffff807  r9=0000000000000000 r10=fffffa80055c3010
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!ExfReleaseRundownProtection+0x7:
fffff800`032f4527 488b09          mov     rcx,qword ptr [rcx] ds:ffffffff`fffff807=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003353bf0 to fffff800032d5bc0

STACK_TEXT:  
fffff880`031af638 fffff800`03353bf0 : 00000000`00000050 ffffffff`fffff807 00000000`00000000 fffff880`031af7a0 : nt!KeBugCheckEx
fffff880`031af640 fffff800`032d3cee : 00000000`00000000 ffffffff`fffff807 00000000`0000b600 fffffa80`0414f790 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`031af7a0 fffff800`032f4527 : fffff8a0`00000020 fffff8a0`00000000 fffffa80`0414f790 fffffa80`066844d8 : nt!KiPageFault+0x16e
fffff880`031af930 fffff880`0114285b : fffffa80`0414f790 fffff880`031afa90 fffffa80`038752f0 fffff8a0`0399ea30 : nt!ExfReleaseRundownProtection+0x7
fffff880`031af960 fffff880`0113d107 : fffff880`031afa90 00000000`00000001 0000000f`ffffffff 00000000`00000001 : fltmgr! ?? ::FNODOBFM::`string'+0x1887
fffff880`031af9f0 fffff880`0113b6c7 : 00000000`00000000 fffff8a0`047107a0 00000000`00000001 00000000`00000000 : fltmgr!FltpPassThrough+0xb7
fffff880`031afa70 fffff800`035d290e : fffffa80`038752f0 fffffa80`046cd8f0 fffff8a0`047107a0 fffffa80`03654040 : fltmgr!FltpDispatch+0xb7
fffff880`031afad0 fffff800`032dee54 : 00000000`00000001 00000000`00000000 fffffa80`036fc750 00000000`00000000 : nt!IopDeleteFile+0x11e
fffff880`031afb60 fffff800`035765b1 : 00000000`00000000 00000000`0008c081 fffffa80`066d2b10 fffffa80`042956b0 : nt!ObfDereferenceObject+0xd4
fffff880`031afbc0 fffff800`03322311 : fffffa80`066d2b18 00000000`00000001 00000000`00000000 f5374fbf`00000631 : nt!MiSegmentDelete+0xa1
fffff880`031afc00 fffff800`033221d5 : 00000000`00000000 00000000`00000080 fffffa80`036e66f0 fffffa80`00000012 : nt!MiProcessDereferenceList+0x131
fffff880`031afcc0 fffff800`035722ea : aecbaf6d`ffe6f547 efdd98be`72b9ecff 7bf7ec33`aef1fc33 ef1fdc3e`741bdf6f : nt!MiDereferenceSegmentThread+0x10d
fffff880`031afd40 fffff800`032c68e6 : fffff800`03450e80 fffffa80`03706a00 fffff800`0345ecc0 daf7dced`ea3bec1f : nt!PspSystemThreadStartup+0x5a
fffff880`031afd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExfReleaseRundownProtection+7
fffff800`032f4527 488b09          mov     rcx,qword ptr [rcx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!ExfReleaseRundownProtection+7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

IMAGE_VERSION:  6.1.7601.18247

FAILURE_BUCKET_ID:  X64_0x50_nt!ExfReleaseRundownProtection+7

BUCKET_ID:  X64_0x50_nt!ExfReleaseRundownProtection+7

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x50_nt!exfreleaserundownprotection+7

FAILURE_ID_HASH:  {064b56c5-b360-fd59-4341-c3b07b75ba5a}

Followup: MachineOwner
---------
My System SpecsSystem Spec
01 Mar 2014   #3
seven09

Windows 7
 
 

I did remove the others I thought they would be irrelevant

here you go
My System SpecsSystem Spec
.

02 Mar 2014   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

My System SpecsSystem Spec
02 Mar 2014   #5
seven09

Windows 7
 
 

That instruction post to should be edited to remind people to let it run until all system info is retrieved. The completion box for the .dmps pops up too soon..

So here, this one should work
My System SpecsSystem Spec
02 Mar 2014   #6
derekimo

Microsoft Community Contributor Award Recipient

 
 

I'm not getting much info from your dumps,

I notice you have another thread about your RAM,

Let's try this,

information   Information
MemTest86+

Run a minimum of 8 passes, preferably overnight, or until errors occur using MemTest86+.

Use this tutorial to help you use MemTest86+:
RAM - Test with MemTest86+


Let us know the results.

You can also try this after testing your RAM,

information   Information
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Driver Verifier - Enable and Disable

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
System Restore Point - Create

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
Safe Mode
My System SpecsSystem Spec
02 Mar 2014   #7
seven09

Windows 7
 
 

I did run memtest86 for 6 or 7 passes last week...turned up nothing, even for my faulty dimm slot which is damaged..

Strange thing there is both memory sticks are recognized in bios and shows 8gb installed in windows, but only 3.74 usable.
My System SpecsSystem Spec
22 Jul 2015   #8
carita51

Windows 7 Ultimate 32-bit
 
 

Are you running a 32-bit OS? That's why 8GB RAM is only 3.74 useable. 32-Bit systems only allot you to use that much. 64-Bit allows SO much more (but 7 still limits that unless you buy premium versions).
My System SpecsSystem Spec
Reply

 Unexpected shutdown; no blue screen but got BSOD error report




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Blue Screen Error, Unexpected Shutdown
Hello, I reformatted my Dell Inspiron 1545 and did a clean install of windows 7 home premium with the cd that came with the laptop. It's a clean install because I used dban to erase the hard drive. Now the laptop would crash and give me a blue screen error whenever I'm using it. Also ie 11 (if I...
BSOD Help and Support
Windows has recovered from an unexpected shutdown blue screen
Hi, I have been looking around for a solution to this. So far no luck so i thought maybe you guys could help. As of a few weeks ago whenever i seem to leave my computer for a few hours and come back i find that it has restarted. When i log in I receive an error saying that windows has recovered...
BSOD Help and Support
Win7 Unexpected Shutdown while on skype Blue Screen
Hello guys! my laptop crashed once again while making skype video call. :cry: First time this happened I thought it was overheating,so I cleaned cooler. Obv that wasn't the problem. :geek: I have attached a file, hopefully done everything correctly. Big,big thanks in advance!!!
BSOD Help and Support
Windows recovered from an unexpected shutdown (Blue-screen)
Please can someone please identify the problem: Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 2057 Additional information about the problem: BCCode: 124 BCP1: 00000000
BSOD Help and Support
Windows recovered from an unexpected shutdown - Blue Screen -
I have a brand new Desktop PC - running Windows 7 - 8gb ram - iTB HD and I have to say it is running perfectly well. However, when I shut it down yesterday I noticed that the PC restarted itself and stated ' windows had recovered from an unexpected shut down' blue screen, and it gave me details of...
BSOD Help and Support
Windows 7 Unexpected Shutdown Blue Screen Error
My computer has shutdown unexpectedly several times. Every time, I am not using the computer. It always happens when I am away, therefore I have not seen it happen. I simply come back, start it up, login, and get the Unexpected shutdown message. The latest message was: 8/17/2010 9:10PM ...
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 13:45.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App