BSOD during WET restore

OldDogEyes said:

Howdy,

My first post to SevenForums and unfortunately I am posting with a problem and not with a solution to someone else's problem... Here is a summary of my problem:

• Recevied a BSOD while restoring the contents of the Windows Easy Transfer file saved to a USB Hard Drive.
• Machine is HP Model m9517c - Quad Core AMD Phenom, 8 gb memory, 1tb hard drive, GeForce 9100 video card. Full specs here: specs
• The machine came preinstalled with Vista Home Premium 64bit and I'm just now putting Seven on it (also 64 bit).
• My install was a clean one, deleted partitions, windows created a 100mb partition and then the main partition of around 930gigs.
• Didn't seem to have any problems with install and it took about 25 minutes.
• Updated my bios to the latest before installing Seven (can't remember the version).

Here are the order of steps that I did:

• After Seven was done installing, I immediately went to WET to restore my data.
• I did not allow WindowsUpdate to do anything nor did I install any applications or drivers.

And finally, I'm attaching a ZIP file with the dump and xml files that windows produced when I booted up in addition to the text of the message:

===============================
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 34
BCP1: 0000000000050830
BCP2: FFFFF8800319A588
BCP3: FFFFF88003199DE0
BCP4: FFFFF800026ABAED
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\031510-18798-01.dmp
C:\Users\Doug\AppData\Local\Temp\WER-68921-0.sysdata.xml

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

Finally, I have not done anything yet - waiting on advice as to what I should do next. Many thanks in advance for your help!

Doug

Hi and welcome

This crash was caused by memory corruption. I would download memtestx86 and run it for 5 passes.

Let us know the results


Ken

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\031510-18798-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02651000 PsLoadedModuleList = 0xfffff800`0288ee50
Debug session time: Mon Mar 15 15:23:50.357 2010 (GMT-4)
System Uptime: 0 days 0:20:40.710
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 34, {50830, fffff8800319a588, fffff88003199de0, fffff800026abaed}

Probably caused by : memory_corruption ( nt!MiDereferenceControlAreaPfn+5d )

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

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

CACHE_MANAGER (34)
    See the comment for FAT_FILE_SYSTEM (0x23)
Arguments:
Arg1: 0000000000050830
Arg2: fffff8800319a588
Arg3: fffff88003199de0
Arg4: fffff800026abaed

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


EXCEPTION_RECORD:  fffff8800319a588 -- (.exr 0xfffff8800319a588)
ExceptionAddress: fffff800026abaed (nt!MiDereferenceControlAreaPfn+0x000000000000005d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88003199de0 -- (.cxr 0xfffff88003199de0)
rax=0000000000000002 rbx=e56c694600150000 rcx=e56c694600150000
rdx=0000000000000001 rsi=0000000000000001 rdi=000fffffffffffff
rip=fffff800026abaed rsp=fffff8800319a7c0 rbp=0000000000000000
 r8=0000000000000001  r9=fffff8000284dd01 r10=0000000000000002
r11=0000000000000001 r12=fffff88002f64180 r13=0000000000000000
r14=0000000000000001 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!MiDereferenceControlAreaPfn+0x5d:
fffff800`026abaed f00fba69481f    lock bts dword ptr [rcx+48h],1Fh ds:002b:e56c6946`00150048=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

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 fffff800028f90e0
 ffffffffffffffff 

FOLLOWUP_IP: 
nt!MiDereferenceControlAreaPfn+5d
fffff800`026abaed f00fba69481f    lock bts dword ptr [rcx+48h],1Fh

FAULTING_IP: 
nt!MiDereferenceControlAreaPfn+5d
fffff800`026abaed f00fba69481f    lock bts dword ptr [rcx+48h],1Fh

BUGCHECK_STR:  0x34

LAST_CONTROL_TRANSFER:  from fffff800026865ac to fffff800026abaed

STACK_TEXT:  
fffff880`0319a7c0 fffff800`026865ac : 00000000`00000002 00000000`00000000 fffffa80`038eba50 00000000`00000002 : nt!MiDereferenceControlAreaPfn+0x5d
fffff880`0319a830 fffff800`0278223d : fffffa80`038eba50 fffff880`0319a980 00000000`00000080 00000000`00192e26 : nt!MiRestoreTransitionPte+0xcc
fffff880`0319a890 fffff800`026669d5 : fa800693`be5004c0 fffff880`0319a980 00000000`00000a10 00000000`00000000 : nt!MiRemoveLowestPriorityStandbyPage+0x2ad
fffff880`0319a910 fffff800`0296296a : fffffa80`089fc000 fffffa80`00000001 fffffa80`089fc000 00000000`00000005 : nt! ?? ::FNODOBFM::`string'+0x2d968
fffff880`0319aa80 fffff800`02673a67 : fffffa80`089fc000 00000019`b7871000 00000019`b7871000 fffff800`028665a0 : nt!MmPrefetchForCacheManager+0x96
fffff880`0319aad0 fffff800`026b6db6 : fffffa80`06fa43a0 fffff880`0319ac00 00000000`00000005 fffff800`00000000 : nt!CcPerformReadAhead+0x2f3
fffff880`0319ac00 fffff800`026d0161 : fffffa80`06719800 fffff800`026b6b98 fffff800`028c8150 fffffa80`00003001 : nt!CcWorkerThread+0x21e
fffff880`0319acb0 fffff800`02966166 : 0000051c`00000000 fffffa80`0671a040 00000000`00000080 fffffa80`066a49e0 : nt!ExpWorkerThread+0x111
fffff880`0319ad40 fffff800`026a1486 : fffff880`02f64180 fffffa80`0671a040 fffff880`02f6efc0 0000051c`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0319ad80 00000000`00000000 : fffff880`0319b000 fffff880`03195000 fffff880`0319a6e0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiDereferenceControlAreaPfn+5d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

STACK_COMMAND:  .cxr 0xfffff88003199de0 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x34_nt!MiDereferenceControlAreaPfn+5d

BUCKET_ID:  X64_0x34_nt!MiDereferenceControlAreaPfn+5d

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

Ken,

Thanks for the tip... Did as you suggested and let it run overnight... ended up finishing five and a half passes with zero errors.

Question: I recall that there was some issue with installing VISTA if you had more than a certain amount of ram... I think if I remember you needed to take some ram out, install and then once installed, add it back in. I might be mistaken about that. But in any case, is there any indication that there has been problems installing Seven with 8gb of ram?

I also tried HP's tech support since my system is still under warranty. Level 1 tech was a joke. I don't think he understood what a dump file was.

So what I'm doing is I wiped the drive again and am reinstalling Seven from scratch again and I was planning on letting Windows Update do it's thing before trying to restore my data with WET. Maybe I don't have all of the drivers that I need with the initial install of Seven?

Any other suggestions or ideas?

Thanks,
Doug

Try setting your power option to high performance, then do the WET. For some reason the default power option setting for Windows 7 doesn't give the proper hardware voltage. The symptoms are always hardware related, but are false positives because of low voltage. Changing that setting solved ALL my problems with Windows 7.

So I wanted to thank everyone for the suggestions. I have been able to successfully restore my settings and data via WET. In the end, I think that the problem that I had was caused by the fact that I had NOT allowed Windows Update to install the necessary drivers for my hardware. So the second time I attempted to restore my settings and data I allowed Windows Update to install all of it's updates and everything worked perfectly.

Doug