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 Crashes after power outage

10 Feb 2011   #1

Windows 7 Professional 64bit
 
 
BSOD Crashes after power outage

I originally posted this problem a week ago. Zigzag offered up some good suggestions. One of which was to reinstall my video card driver. That seemed to work for a few solid days, but the BSOD problem came back. I'm uploading the most recent perfmon report and dump files. My original post and zigzag's reply can be found here. Below is my original text. Any additional information would be appreciated.

About a month ago, the power went out in the neighborhood. When the power came back on, my computer was really messed up; freezes, blue screens, etc. After an hour or two, I found that one of my memory sticks was damaged. I was finally able to boot into windows and work for a little while. Problem is I still get the blue screens randomly and much too frequently (essentially each session I use the computer, I get at least 1 BSOD). I had windows 7 installed for a full year with virtually no problems on this system.

I have done a clean reinstall of the full retail version of windows 7 x64 professional.
Abit kn9s motherboard
Athlon 64 x2 4200


My System SpecsSystem Spec
10 Feb 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by dgrec3 View Post
I originally posted this problem a week ago. Zigzag offered up some good suggestions. One of which was to reinstall my video card driver. That seemed to work for a few solid days, but the BSOD problem came back. I'm uploading the most recent perfmon report and dump files. My original post and zigzag's reply can be found here. Below is my original text. Any additional information would be appreciated.
About a month ago, the power went out in the neighborhood. When the power came back on, my computer was really messed up; freezes, blue screens, etc. After an hour or two, I found that one of my memory sticks was damaged. I was finally able to boot into windows and work for a little while. Problem is I still get the blue screens randomly and much too frequently (essentially each session I use the computer, I get at least 1 BSOD). I had windows 7 installed for a full year with virtually no problems on this system.

I have done a clean reinstall of the full retail version of windows 7 x64 professional.
Abit kn9s motherboard
Athlon 64 x2 4200
These were caused by your mozy.sys backed. I would remove it

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\020911-38250-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a07000 PsLoadedModuleList = 0xfffff800`02c44e50
Debug session time: Wed Feb  9 22:29:55.333 2011 (GMT-5)
System Uptime: 0 days 12:20:48.848
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, {fffffa800eb3ce14, 1, fffff88001033280, 2}

Unable to load image \SystemRoot\system32\DRIVERS\mozy.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mozy.sys
*** ERROR: Module load completed but symbols could not be loaded for mozy.sys

Could not read faulting driver name
Probably caused by : mozy.sys ( mozy+46e5 )

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

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

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002caf0e0
 fffffa800eb3ce14 

FAULTING_IP: 
fltmgr!FltpPurgeVolumeNameCache+50
fffff880`01033280 f083454401      lock add dword ptr [rbp+44h],1

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  setup.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880080b83f0 -- (.trap 0xfffff880080b83f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800eb3ce00 rbx=0000000000000000 rcx=fffffa8004c5d518
rdx=ffffffffffffff01 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001033280 rsp=fffff880080b8580 rbp=fffffa800eb3cdd0
 r8=ffffffffffffffff  r9=ffffffffffffffff r10=fffff80002a07000
r11=00000000000004b6 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
fltmgr!FltpPurgeVolumeNameCache+0x50:
fffff880`01033280 f083454401      lock add dword ptr [rbp+44h],1 ss:0018:fffffa80`0eb3ce14=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002af68f2 to fffff80002a77740

STACK_TEXT:  
fffff880`080b8288 fffff800`02af68f2 : 00000000`00000050 fffffa80`0eb3ce14 00000000`00000001 fffff880`080b83f0 : nt!KeBugCheckEx
fffff880`080b8290 fffff800`02a7582e : 00000000`00000001 fffffa80`0ab3cc50 fffffa80`04c5d000 fffffa80`0d7a1010 : nt! ?? ::FNODOBFM::`string'+0x40ec0
fffff880`080b83f0 fffff880`01033280 : 00000000`00000000 fffffa80`0ab3cc50 fffffa80`0ab3cc50 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`080b8580 fffff880`0102aa30 : fffffa80`03f0eb10 fffffa80`04c5d010 00000000`00000000 fffffa80`0d713368 : fltmgr!FltpPurgeVolumeNameCache+0x50
fffff880`080b85c0 fffff880`01023d4b : fffffa80`04c5d010 00000000`00000000 fffffa80`0d7cadd0 00000000`00000000 : fltmgr! ?? ::NNGAKEGL::`string'+0x1a04
fffff880`080b8600 fffff880`0100606a : fffffa80`0d7c9010 fffffa80`04c5c500 002e0037`00390035 fffff880`00340039 : fltmgr!FltpReinstateNameCachingAllFrames+0x4b
fffff880`080b8630 fffff800`02a79d26 : 00000000`00000000 ffffe529`f0cb0116 fffffa80`048bd798 00000000`00000001 : fltmgr!FltpPassThroughCompletion+0x8a
fffff880`080b8670 fffff880`01218f30 : fffffa80`08cc9ca0 00000000`00000001 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`080b8750 fffff880`012a2dfa : fffff8a0`0b7c87f0 fffffa80`048bb180 00000000`00000000 00000000`00000701 : Ntfs!NtfsExtendedCompleteRequestInternal+0x110
fffff880`080b8790 fffff880`01211e0c : fffffa80`08cc9ca0 fffffa80`0d713010 fffff880`080b8901 fffff880`080b8800 : Ntfs!NtfsCommonSetInformation+0xef1
fffff880`080b8870 fffff880`0100323f : fffffa80`0d7133b0 fffffa80`0d713010 fffffa80`08cc9ca0 fffff880`080b8898 : Ntfs!NtfsFsdSetInformation+0x11c
fffff880`080b88f0 fffff880`010016df : fffffa80`04c5c500 fffffa80`0d7c8500 fffffa80`04c5c500 fffffa80`0d713010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`080b8980 fffff880`03ce36e5 : fffffa80`0d7133b0 fffffa80`0d7c8500 00000000`00000000 fffff880`080b89b0 : fltmgr!FltpDispatch+0xcf
fffff880`080b89e0 fffffa80`0d7133b0 : fffffa80`0d7c8500 00000000`00000000 fffff880`080b89b0 00000000`00000240 : mozy+0x46e5
fffff880`080b89e8 fffffa80`0d7c8500 : 00000000`00000000 fffff880`080b89b0 00000000`00000240 00000000`00000000 : 0xfffffa80`0d7133b0
fffff880`080b89f0 00000000`00000000 : fffff880`080b89b0 00000000`00000240 00000000`00000000 00000000`00060001 : 0xfffffa80`0d7c8500


STACK_COMMAND:  kb

FOLLOWUP_IP: 
mozy+46e5
fffff880`03ce36e5 ??              ???

SYMBOL_STACK_INDEX:  d

SYMBOL_NAME:  mozy+46e5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: mozy

IMAGE_NAME:  mozy.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cd87bff

FAILURE_BUCKET_ID:  X64_0x50_mozy+46e5

BUCKET_ID:  X64_0x50_mozy+46e5

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

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

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


Could not read faulting driver name

WRITE_ADDRESS:  fffffa800eb3ce14 

FAULTING_IP: 
fltmgr!FltpPurgeVolumeNameCache+50
fffff880`01033280 f083454401      lock add dword ptr [rbp+44h],1

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  setup.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880080b83f0 -- (.trap 0xfffff880080b83f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800eb3ce00 rbx=0000000000000000 rcx=fffffa8004c5d518
rdx=ffffffffffffff01 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001033280 rsp=fffff880080b8580 rbp=fffffa800eb3cdd0
 r8=ffffffffffffffff  r9=ffffffffffffffff r10=fffff80002a07000
r11=00000000000004b6 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
fltmgr!FltpPurgeVolumeNameCache+0x50:
fffff880`01033280 f083454401      lock add dword ptr [rbp+44h],1 ss:0018:fffffa80`0eb3ce14=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002af68f2 to fffff80002a77740

STACK_TEXT:  
fffff880`080b8288 fffff800`02af68f2 : 00000000`00000050 fffffa80`0eb3ce14 00000000`00000001 fffff880`080b83f0 : nt!KeBugCheckEx
fffff880`080b8290 fffff800`02a7582e : 00000000`00000001 fffffa80`0ab3cc50 fffffa80`04c5d000 fffffa80`0d7a1010 : nt! ?? ::FNODOBFM::`string'+0x40ec0
fffff880`080b83f0 fffff880`01033280 : 00000000`00000000 fffffa80`0ab3cc50 fffffa80`0ab3cc50 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`080b8580 fffff880`0102aa30 : fffffa80`03f0eb10 fffffa80`04c5d010 00000000`00000000 fffffa80`0d713368 : fltmgr!FltpPurgeVolumeNameCache+0x50
fffff880`080b85c0 fffff880`01023d4b : fffffa80`04c5d010 00000000`00000000 fffffa80`0d7cadd0 00000000`00000000 : fltmgr! ?? ::NNGAKEGL::`string'+0x1a04
fffff880`080b8600 fffff880`0100606a : fffffa80`0d7c9010 fffffa80`04c5c500 002e0037`00390035 fffff880`00340039 : fltmgr!FltpReinstateNameCachingAllFrames+0x4b
fffff880`080b8630 fffff800`02a79d26 : 00000000`00000000 ffffe529`f0cb0116 fffffa80`048bd798 00000000`00000001 : fltmgr!FltpPassThroughCompletion+0x8a
fffff880`080b8670 fffff880`01218f30 : fffffa80`08cc9ca0 00000000`00000001 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`080b8750 fffff880`012a2dfa : fffff8a0`0b7c87f0 fffffa80`048bb180 00000000`00000000 00000000`00000701 : Ntfs!NtfsExtendedCompleteRequestInternal+0x110
fffff880`080b8790 fffff880`01211e0c : fffffa80`08cc9ca0 fffffa80`0d713010 fffff880`080b8901 fffff880`080b8800 : Ntfs!NtfsCommonSetInformation+0xef1
fffff880`080b8870 fffff880`0100323f : fffffa80`0d7133b0 fffffa80`0d713010 fffffa80`08cc9ca0 fffff880`080b8898 : Ntfs!NtfsFsdSetInformation+0x11c
fffff880`080b88f0 fffff880`010016df : fffffa80`04c5c500 fffffa80`0d7c8500 fffffa80`04c5c500 fffffa80`0d713010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`080b8980 fffff880`03ce36e5 : fffffa80`0d7133b0 fffffa80`0d7c8500 00000000`00000000 fffff880`080b89b0 : fltmgr!FltpDispatch+0xcf
fffff880`080b89e0 fffffa80`0d7133b0 : fffffa80`0d7c8500 00000000`00000000 fffff880`080b89b0 00000000`00000240 : mozy+0x46e5
fffff880`080b89e8 fffffa80`0d7c8500 : 00000000`00000000 fffff880`080b89b0 00000000`00000240 00000000`00000000 : 0xfffffa80`0d7133b0
fffff880`080b89f0 00000000`00000000 : fffff880`080b89b0 00000000`00000240 00000000`00000000 00000000`00060001 : 0xfffffa80`0d7c8500


STACK_COMMAND:  kb

FOLLOWUP_IP: 
mozy+46e5
fffff880`03ce36e5 ??              ???

SYMBOL_STACK_INDEX:  d

SYMBOL_NAME:  mozy+46e5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: mozy

IMAGE_NAME:  mozy.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cd87bff

FAILURE_BUCKET_ID:  X64_0x50_mozy+46e5

BUCKET_ID:  X64_0x50_mozy+46e5

Followup: MachineOwner
---------
My System SpecsSystem Spec
10 Feb 2011   #3

Windows 7 Professional 64bit
 
 

Thanks, zigzag. You're the man (or woman, not to be presumptuous). I'm happy to remove mozy altogether since they want to increase my yearly payment by 600% (no exaggeration). Thanks again!
My System SpecsSystem Spec
.


27 Mar 2011   #4

Windows 7 Professional 64bit
 
 
Getting Better, But...

As per Zig Zag's instructions (two different occasions now), I have started to decrease the frequency of the BSOD. What used to happen within 30-60 minutes now happens a few days apart. I'm very grateful for the help. Can you, Zig Zag, or anyone else help me whittle the problem down some more? I have attached the new report and dump files.

Thank you!
My System SpecsSystem Spec
Reply

 BSOD Crashes after power outage





Thread Tools



Similar help and support threads for2: BSOD Crashes after power outage
Thread Forum
Solved BSOD following power outage BSOD Help and Support
Solved power outage = not genuine Windows Updates & Activation
How to get auto restart after power outage? General Discussion
Solved No LAN Connection after power outage Network & Sharing
BSOD Crashes after power outage BSOD Help and Support
Power Outage.. now computer won't turn on General Discussion
Power Outage During Win 7 Upgrade Installation & Setup

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 11:22 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