Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD while backing up data to external USB-HD


  • Please log in to reply
3 replies to this topic

#1 tao2000

tao2000

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:07:09 PM

Posted 10 January 2014 - 02:29 PM

Hi there,

 

   I get the BSOD every time I attempt to backup all the data from a partition in my hard drive to an external USB-HD. The partition with the data does *not* contain the OS in it.I use the software syncback Pro to do all my backups.  I used to be able to do the same type of backup via the same software in the past without a problem.

 

I have exhausted all my resources to solve this issue.  Any help will be much appreciated.

 

Details below:

 

 

Summary
Operating System
Windows 7 Enterprise 64-bit SP1
CPU
Intel Core i7 2630QM @ 2.00GHz 63 °C
Sandy Bridge 32nm Technology
RAM
4.00GB Dual-Channel DDR3 @ 665MHz (9-9-9-24)
Motherboard
ASUSTeK Computer Inc. N53SV (CPU 1)
 
66 °C
Graphics
Generic PnP Monitor (1152x864@60Hz)
L91D D-SUB (1152x864@60Hz)
Intel HD Graphics Family (ASUStek 
 
Computer Inc)
1023MB NVIDIA GeForce GT 540M (ASUStek 
 
Computer Inc) 47 °C
Storage
698GB Seagate ST9750420AS ATA Device 
 
(SATA) 37 °C
Optical Drives
MATbleepA DVD-RAM UJ8A0ASW ATA Device
Audio
Realtek High Definition Audio
Operating System
Windows 7 Enterprise 64-bit SP1
Computer type: Notebook
Installation Date: 6/25/2011 12:10:16 PM
Windows Security Center
User Account Control (UAC)
 
Enabled
Notify level 2 - Default
Firewall Enabled
Windows Update
AutoUpdate Notify prior to 
 
download
Windows Defender
Windows Defender Disabled
Antivirus
Antivirus Enabled
Display Name AVG Anti-Virus Free 
 
Edition 2012
Virus Signature Database Up to 
 
date
.NET Frameworks installed
v4.5 Full
v4.5 Client
v3.5 SP1
v3.0 SP2
v2.0 SP2
Internet Explorer
Version 11.0.9600.16476
PowerShell
Version 2.0
 
==================================================
Dump File         : 010514-67751-01.dmp
Crash Time        : 1/5/2014 8:54:57 PM
Bug Check String  : KERNEL_DATA_INPAGE_ERROR
Bug Check Code    : 0x0000007a
Parameter 1       : fffff6fc`40009a48
Parameter 2       : ffffffff`c000000e
Parameter 3       : 00000000`7061d860
Parameter 4       : fffff880`01349d18
Caused By Driver  : Ntfs.sys
Caused By Address : Ntfs.sys+eed18
File Description  : NT File System Driver
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\010514-67751-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 343,993
Dump File Time    : 1/5/2014 9:05:04 PM
==================================================
 
 
==================================================
Dump File         : 010514-43773-01.dmp
Crash Time        : 1/5/2014 12:50:40 PM
Bug Check String  : DRIVER_POWER_STATE_FAILURE
Bug Check Code    : 0x0000009f
Parameter 1       : 00000000`00000004
Parameter 2       : 00000000`00000258
Parameter 3       : fffffa80`03ff2b50
Parameter 4       : fffff800`00b9c3d0
Caused By Driver  : rdprefmp.sys
Caused By Address : rdprefmp.sys+2625b50
File Description  : RDP Reflector Driver Miniport
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\010514-43773-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 336,281
Dump File Time    : 1/5/2014 12:52:49 PM
==================================================
 
 
 
**************************************************************
 
*****************
*                                                              
 
               *
*                        Bugcheck Analysis                     
 
               *
*                                                              
 
               *
**************************************************************
 
*****************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 7A, {fffff6fc40009a48, ffffffffc000000e, 7061d860, 
 
fffff88001349d18}
 
Probably caused by : ntkrnlmp.exe ( nt! ?? 
 
::FNODOBFM::`string'+36c1a )
 
Followup: MachineOwner
---------
 
4: kd> !analyze -v
**************************************************************
 
*****************
*                                                              
 
               *
*                        Bugcheck Analysis                     
 
               *
*                                                              
 
               *
**************************************************************
 
*****************
 
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  
 
Typically caused by
a bad block in the paging file or disk controller error. Also 
 
see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 
 
0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request 
 
failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc40009a48, lock type that was held (value 1,2,3, 
 
or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status 
 
code)
Arg3: 000000007061d860, current process (virtual address for 
 
lock type 3, or PTE)
Arg4: fffff88001349d18, virtual address that could not be in-
 
paged (or PTE contents if arg1 is a PTE address)
 
Debugging Details:
------------------
 
 
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not 
 
exist was specified.
 
DISK_HARDWARE_ERROR: There was error with disk hardware
 
BUGCHECK_STR:  0x7a_c000000e
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  0
 
TRAP_FRAME:  fffff88003506b20 -- (.trap 0xfffff88003506b20)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88001349d18 rbx=0000000000000000 rcx=fffff88003506cf0
rdx=fffff88003507b60 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001349d18 rsp=fffff88003506cb8 rbp=fffff88003506df0
 r8=fffff88003507500  r9=fffff88003506df0 r10=fffff88003507d60
r11=fffff88003506d28 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
Ntfs! ?? ::NNGAKEGL::`string'+0x2bf0:
fffff880`01349d18 55              push    rbp
Resetting default scope
 
LAST_CONTROL_TRANSFER:  from fffff80003544752 to 
 
fffff800034d1bc0
 
STACK_TEXT:  
fffff880`03506808 fffff800`03544752 : 00000000`0000007a 
 
fffff6fc`40009a48 ffffffff`c000000e 00000000`7061d860 : nt!
 
KeBugCheckEx
fffff880`03506810 fffff800`034f891f : fffffa80`045b6710 
 
fffff880`03506980 fffff800`0370c540 fffffa80`045b6710 : nt! ?? 
 
::FNODOBFM::`string'+0x36c1a
fffff880`035068f0 fffff800`034df1b9 : 00000000`00000000 
 
00000000`00000008 ffffffff`ffffffff 80500000`4725c882 : nt!
 
MiIssueHardFault+0x28b
fffff880`035069c0 fffff800`034cfcee : 00000000`00000008 
 
fffff880`01349d18 fffff880`00000000 fffff880`012a9e18 : nt!
 
MmAccessFault+0x1399
fffff880`03506b20 fffff880`01349d18 : fffff800`034fccdc 
 
00000000`c000000e fffff880`03506b70 fffff880`03507410 : nt!
 
KiPageFault+0x16e
fffff880`03506cb8 fffff800`034fccdc : 00000000`c000000e 
 
fffff880`03506b70 fffff880`03507410 00000000`c000000e : Ntfs! 
 
?? ::NNGAKEGL::`string'+0x2bf0
fffff880`03506cc0 fffff800`034fc75d : fffff880`012a9e0c 
 
fffff880`03507b60 00000000`00000000 fffff880`0125b000 : nt!
 
_C_specific_handler+0x8c
fffff880`03506d30 fffff800`034fb535 : fffff880`012a9e0c 
 
fffff880`03506da8 fffff880`03507460 fffff880`0125b000 : nt!
 
RtlpExecuteHandlerForException+0xd
fffff880`03506d60 fffff800`034fe832 : fffff880`03507460 
 
fffff880`03507500 00000000`00000001 fffff800`03567619 : nt!
 
RtlDispatchException+0x415
fffff880`03507440 fffff800`034fa1e0 : fffff980`05f00000 
 
00000000`00000000 fffff880`00000004 fffff880`03507a18 : nt!
 
RtlRaiseStatus+0x4e
fffff880`035079e0 fffff800`034fa644 : fffffa80`066c1af0 
 
fffffa80`040d8000 fffff880`03507b20 fffff880`00000000 : nt!
 
CcMapAndCopyInToCache+0x35f
fffff880`03507ad0 fffff880`012f6a59 : 00000000`00002390 
 
fffffa80`06e50600 fffff880`03507bc0 fffffa80`00002348 : nt!
 
CcCopyWrite+0x194
fffff880`03507b60 fffff880`0105a102 : fffffa80`06e50600 
 
fffff880`0105d4f2 00000000`00002348 00000000`00002301 : Ntfs!
 
NtfsCopyWriteA+0x1e9
fffff880`03507d60 fffff880`0105d8ba : fffff880`03507e30 
 
fffffa80`066da0d8 fffffa80`040d8000 00000000`00002300 : 
 
fltmgr!FltpPerformFastIoCall+0xf2
fffff880`03507dc0 fffff880`0107b83e : 00000000`00002348 
 
00000000`00000000 fffffa80`06e50600 fffff880`03507f30 : 
 
fltmgr!FltpPassThroughFastIo+0xda
fffff880`03507e00 fffff800`037e594e : fffffa80`06e50674 
 
fffff880`03508440 00000000`00000000 fffffa80`06e50674 : 
 
fltmgr!FltpFastIoWrite+0x1ce
fffff880`03507ea0 fffff800`034d0e53 : 00001f80`00100000 
 
00000000`00000000 00000000`00000000 00000000`00000000 : nt!
 
NtWriteFile+0x5ad
fffff880`03507fa0 fffff800`034cd410 : fffff800`03739bd3 
 
fffffa80`040d8000 fffffa80`04064780 00000000`00000000 : nt!
 
KiSystemServiceCopyEnd+0x13
fffff880`035081a8 fffff800`03739bd3 : fffffa80`040d8000 
 
fffffa80`04064780 00000000`00000000 fffff800`037ef96b : nt!
 
KiServiceLinkage
fffff880`035081b0 fffff800`037f113e : 00000000`00000048 
 
00000000`00000000 fffffa80`040d8000 00000000`c0000000 : nt!
 
EtwpRealtimeSaveBuffer+0x93
fffff880`03508220 fffff800`037f11c2 : fffffa80`04064780 
 
fffffa80`040d8000 00000000`c0000001 00000000`00000000 : nt!
 
EtwpFlushBufferToRealtime+0x7a
fffff880`03508250 fffff800`03512109 : 00000000`00000000 
 
00000000`00000001 fffffa80`04064780 00000000`00000000 : nt!
 
EtwpFlushBuffer+0x7a
fffff880`03508290 fffff800`038292ed : fffffa80`04060000 
 
00000000`00000001 00000000`00000000 fffffa80`040d8020 : nt!
 
EtwpFlushActiveBuffers+0x2bd
fffff880`03508b80 fffff800`0376e2ea : 00000000`00000000 
 
fffffa80`04065040 00000000`00000080 fffffa80`03f58890 : nt! ?? 
 
::NNGAKEGL::`string'+0x4299a
fffff880`03508c00 fffff800`034c28e6 : fffff880`009b2180 
 
fffffa80`04065040 fffff880`009bd0c0 fffffa80`04021810 : nt!
 
PspSystemThreadStartup+0x5a
fffff880`03508c40 00000000`00000000 : fffff880`03509000 
 
fffff880`03503000 fffff880`03507710 00000000`00000000 : nt!
 
KiStartSystemThread+0x16
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+36c1a
fffff800`03544752 cc              int     3
 
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+36c1a
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
IMAGE_NAME:  ntkrnlmp.exe
 
DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035
 
FAILURE_BUCKET_ID:  X64_0x7a_c000000e_nt!_??
 
_::FNODOBFM::_string_+36c1a
 
BUCKET_ID:  X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_
 
+36c1a
 
Followup: MachineOwner
---------


BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,127 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:09 PM

Posted 10 January 2014 - 04:59 PM

Reference re error:  Bug Check 0x9F DRIVER_POWER_STATE_FAILURE - http://msdn.microsoft.com/en-us/library/ff559329(v=vs.85).aspx

 

Possibly useful related topic:  Having issues with BSOD DRIVER_POWER_STATE_FAILURE - http://www.bleepingcomputer.com/forums/t/520064/having-issues-with-bsod-driver-power-state-failure-0x0000009f/

 

ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
DISK_HARDWARE_ERROR: There was error with disk hardware
 
I'd say that points to a problem with your external drives connection or functionality.  I would test the functional status of that drive.
 

Please download MiniToolBox  , save it to your desktop and run it.
 
Checkmark the following checkboxes:
  List last 10 Event Viewer log
  List Installed Programs
  List Users, Partitions and Memory size.
 
Click Go and paste the content into your next post.
 
Also...please Publish a Snapshot using Speccy - http://www.bleepingcomputer.com/forums/topic323892.html/page__p__1797792#entry1797792 , taking care to post the link of the snapshot in your next post.
 
Louis


Edited by hamluis, 10 January 2014 - 05:09 PM.


#3 tao2000

tao2000
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:07:09 PM

Posted 10 January 2014 - 07:41 PM

Thanks so much Louis!, let me investigate the information you sent. 



#4 hamluis

hamluis

    Moderator


  • Moderator
  • 56,127 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:09 PM

Posted 11 January 2014 - 10:40 AM

:thumbup2: .

 

Louis






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users