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 with backup or copy

05 Oct 2010   #1
anaron

Windows 7 Pro 64 bitv & Windows 10 Home
 
 
BSOD with backup or copy

Windows 7 Pro 32 bit for students and faculty retail
Replaced XP Home this week for my grandkids
Custom installed
Dimension 8250 purchased in '03
Hard drives, video card, and a few other things upgraded 3 to 4 years ago. Original motherboard.

First install went really bad with lots of bluescreens. Formated and did another custom install on one of my hard drives. Updated most the drivers that scanned as out dated. Transferred my files etc. Everything good until today when I first tried to backup to My Passport Essentials drive. Got a blue screen. I then tried to copy a 2.2 gb file to my thumb drive. Just before completion got another blue screen. Decided I better find someone who knows what they are doing. I know just enough to be dangerous!
Ron




Attached Files
File Type: zip 10-5-10 Bsod.zip (596.9 KB, 7 views)
My System SpecsSystem Spec
.
05 Oct 2010   #2
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

Quote   Quote: Originally Posted by anaron View Post
Windows 7 Pro 32 bit for students and faculty retail
Replaced XP Home this week for my grandkids
Custom installed
Dimension 8250 purchased in '03
Hard drives, video card, and a few other things upgraded 3 to 4 years ago. Original motherboard.

First install went really bad with lots of bluescreens. Formated and did another custom install on one of my hard drives. Updated most the drivers that scanned as out dated. Transferred my files etc. Everything good until today when I first tried to backup to My Passport Essentials drive. Got a blue screen. I then tried to copy a 2.2 gb file to my thumb drive. Just before completion got another blue screen. Decided I better find someone who knows what they are doing. I know just enough to be dangerous!
Ron


Hi anaron and welcome


These 5 were caused by -
*This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
*The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
*If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.


Because of a difference in the symbols that your version uses we cant tell you which ones.


I would update all the below drivers


How To Find Drivers:
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads


Code:


vmodem.sys        0x8c739000    0x8c7e24c0    0x000a94c0    0x3e25eb75    1/15/2003 19:15:01                        
vvoice.sys        0x8c59c000    0x8c5ab940    0x0000f940    0x3e25eb8c    1/15/2003 19:15:24                        
ptserial.sys        0x91b01000    0x91b4c0e0    0x0004b0e0    0x3e25eb9f    1/15/2003 19:15:43                        
vpctcom.sys        0x8c63d000    0x8c6f9340    0x000bc340    0x3e276840    1/16/2003 22:19:44                                               
pcouffin.sys        0x91a22000    0x91a2d900    0x0000b900    0x457584b9    12/5/2006 10:39:53    uninstall the dvd authoring app that uses this.                    
PxHelp20.sys        0x8c063000    0x8c06c0c0    0x000090c0    0x475dd057    12/10/2007 19:48:39                        
AsIO.sys        0x91abc000    0x91abd440    0x00001440    0x47663cfc    12/17/2007 05:10:20                        




If that doesnt cure the problem put the next dmp files up for us.




Jan


My System SpecsSystem Spec
05 Oct 2010   #3
Lemur

Systems 1 and 2: Windows 7 Enterprise x64, Win 8 Developer
 
 

Quote:
Probably caused by : storport.sys ( storport!RaidpAdapterDpcRoutine+51 )
Need to research...
My System SpecsSystem Spec
.

05 Oct 2010   #4
anaron

Windows 7 Pro 64 bitv & Windows 10 Home
 
 

Will do Jan. I also know I have a driver problem with MY Passport Essential drive. Install it and a while later it can't be found. Am working on that now.

Lemur, that was one of the most repeated error sources on my first install and many bsods.
My System SpecsSystem Spec
05 Oct 2010   #5
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Lemur View Post
Quote:
Probably caused by : storport.sys ( storport!RaidpAdapterDpcRoutine+51 )
Need to research...

Which dmp did you get that from?? I also found wrong symbols and no data we all reading the same dmp files?


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\10-5-10 Bsod\100510-82328-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
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: 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x8280c000 PsLoadedModuleList = 0x8294b570
Debug session time: Tue Oct  5 16:22:18.884 2010 (GMT-4)
System Uptime: 0 days 0:03:25.962
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : ntkrnlmp.exe ( nt!Kei386EoiHelper+29d3 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 00000000, address which referenced memory

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:  
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: 8280c000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3f9b

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 00000000 

CURRENT_IRQL:  0

FAULTING_IP: 
+71f952f035fd960
00000000 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

LAST_CONTROL_TRANSFER:  from 00000000 to 82844b7b

FAILED_INSTRUCTION_ADDRESS: 
+71f952f035fd960
00000000 ??              ???

STACK_TEXT:  
8292abe0 00000000 badb0d00 ffff0001 854d8002 nt!Kei386EoiHelper+0x29d3


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!Kei386EoiHelper+29d3
82844b7b 833d205e968200  cmp     dword ptr [nt!KiBugCheckData+0x30c0 (82965e20)],0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!Kei386EoiHelper+29d3

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID:  WRONG_SYMBOLS

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

old drivers
Code:
PfModNT.sys        0x9a1e8000    0x9a1ebda0    0x00003da0    0x3e657ad0    3/5/2003 00:19:28                        
BCMSM.sys        0x8da51000    0x8db5df80    0x0010cf80    0x3f4d715e    8/27/2003 23:05:02                        
ctoss2k.sys        0x8f1b7000    0x8f1e28e0    0x0002b8e0    0x3f6e46a9    9/21/2003 20:47:37                        
ctsfm2k.sys        0x8f1e3000    0x8f202b80    0x0001fb80    0x3f6e46c4    9/21/2003 20:48:04                        
P16X.sys        0x8f02a000    0x8f16eb80    0x00144b80    0x3f6e7dd8    9/22/2003 00:43:04                        
PxHelp20.sys        0x87d6e000    0x87d72d20    0x00004d20    0x409a7a91    5/6/2004 13:49:05                        
e100b325.sys        0x8f203000    0x8f229e00    0x00026e00    0x473de72c    11/16/2007 14:53:32
My System SpecsSystem Spec
05 Oct 2010   #6
Lemur

Systems 1 and 2: Windows 7 Enterprise x64, Win 8 Developer
 
 

Quote   Quote: Originally Posted by zigzag3143 View Post
Quote   Quote: Originally Posted by Lemur View Post
Quote:
Probably caused by : storport.sys ( storport!RaidpAdapterDpcRoutine+51 )
Need to research...
Which dmp did you get that from?? I also found wrong symbols and no data we all reading the same dmp files?
Ken, that was from both dmps.
My System SpecsSystem Spec
05 Oct 2010   #7
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Lemur View Post
Quote   Quote: Originally Posted by zigzag3143 View Post
Quote   Quote: Originally Posted by Lemur View Post
Need to research...
Which dmp did you get that from?? I also found wrong symbols and no data we all reading the same dmp files?
Ken, that was from both dmps.
can you post the info from one I got wrong symbols and no info thanks in advance.
My System SpecsSystem Spec
05 Oct 2010   #8
Lemur

Systems 1 and 2: Windows 7 Enterprise x64, Win 8 Developer
 
 

Ken, found this in both dmps.

Quote:
Loading Dump File [C:\Users\Mark\Desktop\bsod\100510-82328-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\windows\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x8280c000 PsLoadedModuleList = 0x8294b570
Debug session time: Tue Oct 5 16:22:18.884 2010 (GMT-4)
System Uptime: 0 days 0:03:25.962
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, 0}

Probably caused by : storport.sys ( storport!RaidpAdapterDpcRoutine+51 )
My System SpecsSystem Spec
05 Oct 2010   #9
zigzag3143

Win 8 Release candidate 8400
 
 

Lemur thanks for the verification. I thought it was my problem just wanted to make sure.
My System SpecsSystem Spec
06 Oct 2010   #10
karlsnooks

MS Windows 7 Ultimate SP1 64-bit
 
 

anaron,
Is that old computer even on the list of approved computers?

Check with the manufactuer to see what he has to say about running Win 7 on it and if it's even possible, a list of driver updates and any possible bios update.

Windows 7 Compatibility Center home
My System SpecsSystem Spec
Reply

 BSOD with backup or copy




Thread Tools




Similar help and support threads
Thread Forum
SAM syskey, cannot copy backup to usb
Hello guys and gals...... Long story short as I'm sure no one wants to hear the dorky details. The USB with the stored syskey(start up key) file was misplaced. I however did make a backup of the file. Not entirely sure how right i did things. I just opened the USB drive and copied the file...
System Security
Trying to copy backup file from one HD to another
So I created a backup of a friend's laptop on my external hard drive because she didn't own one yet. Now she's bought one and I'm trying to copy the backup file to it. When I drag the file to copy I get a message saying I will need admin permissions to copy, but when I just click continue it...
Backup and Restore
How to copy the Windows 7 DVD for backup?
Hello -- I am sending my old computer to my sister, and have re-installed the original Windows 7 from the DVD. I want her to have a backup / install disc in case she needs it for system repair in the future. However, I do not want to send my original Windows 7 DVD. What is the best...
Backup and Restore
How to get a backup copy of windows 7
Please suggest how to take a backup copy of preloaded windows7 in my new Toshiba Laptop. What do I need for that?
Backup and Restore
BSOD Using Cobain Backup, occurs when performing shadow volume copy
I have been trying to use an automated backup program for my Windows 7 Pro x64 machine and I keep running into a BSOD during the backups. I have tried using a couple of different programs and I get the error with both of them. I believe it has to do with the Shadow Volume Copy but am not sure. ...
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 09:57.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App