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 on large file transfer to ext HD

20 Jan 2011   #1
roguestate

Windows 7 Ultimate x86
 
 
BSOD on large file transfer to ext HD

This is a recent occurrence that when I transfer large files/folders to a Lacie ext HD, I get a BSOD - Could someone please help.

My Toshiba came with Vista Ultimate, then Toshiba sent me an upgrade CD to Windows Ultimate - but this was over a year ago. The entire system has been satisfactory & stable until this recent series of events.

Hardware info:

Motherboard: Qosmio G50
Basic I/O System(BIOS): v2.10
Central Processing Unit(CPU): Intel(R) Core(TM)2 Duo CPU T9550 @ 2.66GHz
Physical Memory X 2
2GB
2GB
Hard Disk X 2
FUJITSU MHZ2320BH G1 (298.09GB)
TOSHIBA MK4058GSX (372.61GB)
Video Card: NVIDIA GeForce 9600M GT
Monitor: Generic PnP Monitor
Audio Device: Realtek High Definition Audio

System info:

Name: Microsoft Windows 7 Ultimate ()
Version: 6.1.7600
ServicePackMajorVersion: 0
ServicePackMinorVersion: 0
Manufacturer: Microsoft Corporation
BuildType: Multiprocessor Free
CodeSet: 1252
CountryCode: 44
Organization: TOSHIBA
RegisteredUser: Roguestate
NumberOfUsers: 1
MaxNumberOfProcesses: -1
MaxProcessMemorySize: 2GB
VisibleMemorySize: 3GB (Remaining 1.59GB)
VirtualMemorySize: 5.99GB (Remaining 4.28GB)
FreeSpaceInPagingFiles: 2.72GB
SystemDrive: C:
WindowsDirectory: C:\Windows
SystemDirectory: C:\Windows\system32
Registry CurrentSize/MaximumSize: 124MB/682MB

The most recent DMP file produced this:

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


Loading Dump File [C:\Windows\Minidump\012011-25116-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\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 = 0x82e17000 PsLoadedModuleList = 0x82f5f810
Debug session time: Thu Jan 20 04:06:44.213 2011 (UTC + 2:00)
System Uptime: 0 days 0:03:30.852
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, 8b315279}

Probably caused by : partmgr.sys ( partmgr!PmReadWriteCompletion+2b )

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

1: 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: 8b315279, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82f7f718
Unable to read MiSystemVaType memory at 82f5f160
00000000

CURRENT_IRQL: 2

FAULTING_IP:
partmgr!PmReadWriteCompletion+2b
8b315279 8b00 mov eax,dword ptr [eax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: 807e6a94 -- (.trap 0xffffffff807e6a94)
ErrCode = 00000000
eax=00000000 ebx=856be500 ecx=87610d00 edx=00000000 esi=856be6fc edi=8761a370
eip=8b315279 esp=807e6b08 ebp=807e6b14 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
partmgr!PmReadWriteCompletion+0x2b:
8b315279 8b00 mov eax,dword ptr [eax] ds:0023:00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 8b315279 to 82e5d82b

STACK_TEXT:
807e6a94 8b315279 badb0d00 00000000 8761a3f8 nt!KiTrap0E+0x2cf
807e6b14 82e7fb33 8761a2b8 856be500 00000000 partmgr!PmReadWriteCompletion+0x2b
807e6b58 8baf8498 807e6b8c 8baf8abd 8761a3f8 nt!IopfCompleteRequest+0x128
807e6b60 8baf8abd 8761a3f8 856be500 00000001 CLASSPNP!ClassCompleteRequest+0x11
807e6b8c 82e7fb33 00000000 8760d520 0001ddf8 CLASSPNP!TransferPktComplete+0x2e4
807e6bd0 91a8f868 82e57354 858c0cf0 00000000 nt!IopfCompleteRequest+0x128
807e6c00 91a90178 857bcc80 8760d520 85e9eb00 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6e0
807e6c2c 91a939af 87254028 872540f0 87254a98 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x33b
807e6c54 91a8dd18 87254028 87254a98 87254002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc
807e6c78 82e7f3b5 87254aa4 87254002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
807e6cd4 82e7f218 807ca120 807cf800 00000000 nt!KiExecuteAllDpcs+0xf9
807e6d20 82e7f038 00000000 0000000e ffffffff nt!KiRetireDpcList+0xd5
807e6d24 00000000 0000000e ffffffff ffffffff nt!KiIdleLoop+0x38


STACK_COMMAND: kb

FOLLOWUP_IP:
partmgr!PmReadWriteCompletion+2b
8b315279 8b00 mov eax,dword ptr [eax]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: partmgr!PmReadWriteCompletion+2b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: partmgr

IMAGE_NAME: partmgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf27

FAILURE_BUCKET_ID: 0xD1_partmgr!PmReadWriteCompletion+2b

BUCKET_ID: 0xD1_partmgr!PmReadWriteCompletion+2b

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

1: 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: 8b315279, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82f7f718
Unable to read MiSystemVaType memory at 82f5f160
00000000

CURRENT_IRQL: 2

FAULTING_IP:
partmgr!PmReadWriteCompletion+2b
8b315279 8b00 mov eax,dword ptr [eax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: 807e6a94 -- (.trap 0xffffffff807e6a94)
ErrCode = 00000000
eax=00000000 ebx=856be500 ecx=87610d00 edx=00000000 esi=856be6fc edi=8761a370
eip=8b315279 esp=807e6b08 ebp=807e6b14 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
partmgr!PmReadWriteCompletion+0x2b:
8b315279 8b00 mov eax,dword ptr [eax] ds:0023:00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 8b315279 to 82e5d82b

STACK_TEXT:
807e6a94 8b315279 badb0d00 00000000 8761a3f8 nt!KiTrap0E+0x2cf
807e6b14 82e7fb33 8761a2b8 856be500 00000000 partmgr!PmReadWriteCompletion+0x2b
807e6b58 8baf8498 807e6b8c 8baf8abd 8761a3f8 nt!IopfCompleteRequest+0x128
807e6b60 8baf8abd 8761a3f8 856be500 00000001 CLASSPNP!ClassCompleteRequest+0x11
807e6b8c 82e7fb33 00000000 8760d520 0001ddf8 CLASSPNP!TransferPktComplete+0x2e4
807e6bd0 91a8f868 82e57354 858c0cf0 00000000 nt!IopfCompleteRequest+0x128
807e6c00 91a90178 857bcc80 8760d520 85e9eb00 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6e0
807e6c2c 91a939af 87254028 872540f0 87254a98 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x33b
807e6c54 91a8dd18 87254028 87254a98 87254002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc
807e6c78 82e7f3b5 87254aa4 87254002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
807e6cd4 82e7f218 807ca120 807cf800 00000000 nt!KiExecuteAllDpcs+0xf9
807e6d20 82e7f038 00000000 0000000e ffffffff nt!KiRetireDpcList+0xd5
807e6d24 00000000 0000000e ffffffff ffffffff nt!KiIdleLoop+0x38


STACK_COMMAND: kb

FOLLOWUP_IP:
partmgr!PmReadWriteCompletion+2b
8b315279 8b00 mov eax,dword ptr [eax]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: partmgr!PmReadWriteCompletion+2b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: partmgr

IMAGE_NAME: partmgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf27

FAILURE_BUCKET_ID: 0xD1_partmgr!PmReadWriteCompletion+2b

BUCKET_ID: 0xD1_partmgr!PmReadWriteCompletion+2b

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

1: kd> .trap 0xffffffff807e6a94
ErrCode = 00000000
eax=00000000 ebx=856be500 ecx=87610d00 edx=00000000 esi=856be6fc edi=8761a370
eip=8b315279 esp=807e6b08 ebp=807e6b14 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
partmgr!PmReadWriteCompletion+0x2b:
8b315279 8b00 mov eax,dword ptr [eax] ds:0023:00000000=????????
Could you please help me analyse this, like I say, I've had no problems with this system & my troubleshooting is rusty.

Thanks in advance



My System SpecsSystem Spec
.
20 Jan 2011   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by roguestate View Post
This is a recent occurrence that when I transfer large files/folders to a Lacie ext HD, I get a BSOD - Could someone please help.

My Toshiba came with Vista Ultimate, then Toshiba sent me an upgrade CD to Windows Ultimate - but this was over a year ago. The entire system has been satisfactory & stable until this recent series of events.

Hardware info:

Motherboard: Qosmio G50
Basic I/O System(BIOS): v2.10
Central Processing Unit(CPU): Intel(R) Core(TM)2 Duo CPU T9550 @ 2.66GHz
Physical Memory X 2
2GB
2GB
Hard Disk X 2
FUJITSU MHZ2320BH G1 (298.09GB)
TOSHIBA MK4058GSX (372.61GB)
Video Card: NVIDIA GeForce 9600M GT
Monitor: Generic PnP Monitor
Audio Device: Realtek High Definition Audio

System info:

Name: Microsoft Windows 7 Ultimate ()
Version: 6.1.7600
ServicePackMajorVersion: 0
ServicePackMinorVersion: 0
Manufacturer: Microsoft Corporation
BuildType: Multiprocessor Free
CodeSet: 1252
CountryCode: 44
Organization: TOSHIBA
RegisteredUser: Roguestate
NumberOfUsers: 1
MaxNumberOfProcesses: -1
MaxProcessMemorySize: 2GB
VisibleMemorySize: 3GB (Remaining 1.59GB)
VirtualMemorySize: 5.99GB (Remaining 4.28GB)
FreeSpaceInPagingFiles: 2.72GB
SystemDrive: C:
WindowsDirectory: C:\Windows
SystemDirectory: C:\Windows\system32
Registry CurrentSize/MaximumSize: 124MB/682MB

The most recent DMP file produced this:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\012011-25116-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\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 = 0x82e17000 PsLoadedModuleList = 0x82f5f810
Debug session time: Thu Jan 20 04:06:44.213 2011 (UTC + 2:00)
System Uptime: 0 days 0:03:30.852
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, 8b315279}

Probably caused by : partmgr.sys ( partmgr!PmReadWriteCompletion+2b )

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

1: 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: 8b315279, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82f7f718
Unable to read MiSystemVaType memory at 82f5f160
 00000000 

CURRENT_IRQL:  2

FAULTING_IP: 
partmgr!PmReadWriteCompletion+2b
8b315279 8b00            mov     eax,dword ptr [eax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  807e6a94 -- (.trap 0xffffffff807e6a94)
ErrCode = 00000000
eax=00000000 ebx=856be500 ecx=87610d00 edx=00000000 esi=856be6fc edi=8761a370
eip=8b315279 esp=807e6b08 ebp=807e6b14 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
partmgr!PmReadWriteCompletion+0x2b:
8b315279 8b00            mov     eax,dword ptr [eax]  ds:0023:00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8b315279 to 82e5d82b

STACK_TEXT:  
807e6a94 8b315279 badb0d00 00000000 8761a3f8 nt!KiTrap0E+0x2cf
807e6b14 82e7fb33 8761a2b8 856be500 00000000 partmgr!PmReadWriteCompletion+0x2b
807e6b58 8baf8498 807e6b8c 8baf8abd 8761a3f8 nt!IopfCompleteRequest+0x128
807e6b60 8baf8abd 8761a3f8 856be500 00000001 CLASSPNP!ClassCompleteRequest+0x11
807e6b8c 82e7fb33 00000000 8760d520 0001ddf8 CLASSPNP!TransferPktComplete+0x2e4
807e6bd0 91a8f868 82e57354 858c0cf0 00000000 nt!IopfCompleteRequest+0x128
807e6c00 91a90178 857bcc80 8760d520 85e9eb00 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6e0
807e6c2c 91a939af 87254028 872540f0 87254a98 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x33b
807e6c54 91a8dd18 87254028 87254a98 87254002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc
807e6c78 82e7f3b5 87254aa4 87254002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
807e6cd4 82e7f218 807ca120 807cf800 00000000 nt!KiExecuteAllDpcs+0xf9
807e6d20 82e7f038 00000000 0000000e ffffffff nt!KiRetireDpcList+0xd5
807e6d24 00000000 0000000e ffffffff ffffffff nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_IP: 
partmgr!PmReadWriteCompletion+2b
8b315279 8b00            mov     eax,dword ptr [eax]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  partmgr!PmReadWriteCompletion+2b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: partmgr

IMAGE_NAME:  partmgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf27

FAILURE_BUCKET_ID:  0xD1_partmgr!PmReadWriteCompletion+2b

BUCKET_ID:  0xD1_partmgr!PmReadWriteCompletion+2b

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

1: 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: 8b315279, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82f7f718
Unable to read MiSystemVaType memory at 82f5f160
 00000000 

CURRENT_IRQL:  2

FAULTING_IP: 
partmgr!PmReadWriteCompletion+2b
8b315279 8b00            mov     eax,dword ptr [eax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  807e6a94 -- (.trap 0xffffffff807e6a94)
ErrCode = 00000000
eax=00000000 ebx=856be500 ecx=87610d00 edx=00000000 esi=856be6fc edi=8761a370
eip=8b315279 esp=807e6b08 ebp=807e6b14 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
partmgr!PmReadWriteCompletion+0x2b:
8b315279 8b00            mov     eax,dword ptr [eax]  ds:0023:00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8b315279 to 82e5d82b

STACK_TEXT:  
807e6a94 8b315279 badb0d00 00000000 8761a3f8 nt!KiTrap0E+0x2cf
807e6b14 82e7fb33 8761a2b8 856be500 00000000 partmgr!PmReadWriteCompletion+0x2b
807e6b58 8baf8498 807e6b8c 8baf8abd 8761a3f8 nt!IopfCompleteRequest+0x128
807e6b60 8baf8abd 8761a3f8 856be500 00000001 CLASSPNP!ClassCompleteRequest+0x11
807e6b8c 82e7fb33 00000000 8760d520 0001ddf8 CLASSPNP!TransferPktComplete+0x2e4
807e6bd0 91a8f868 82e57354 858c0cf0 00000000 nt!IopfCompleteRequest+0x128
807e6c00 91a90178 857bcc80 8760d520 85e9eb00 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6e0
807e6c2c 91a939af 87254028 872540f0 87254a98 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x33b
807e6c54 91a8dd18 87254028 87254a98 87254002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc
807e6c78 82e7f3b5 87254aa4 87254002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
807e6cd4 82e7f218 807ca120 807cf800 00000000 nt!KiExecuteAllDpcs+0xf9
807e6d20 82e7f038 00000000 0000000e ffffffff nt!KiRetireDpcList+0xd5
807e6d24 00000000 0000000e ffffffff ffffffff nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_IP: 
partmgr!PmReadWriteCompletion+2b
8b315279 8b00            mov     eax,dword ptr [eax]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  partmgr!PmReadWriteCompletion+2b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: partmgr

IMAGE_NAME:  partmgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf27

FAILURE_BUCKET_ID:  0xD1_partmgr!PmReadWriteCompletion+2b

BUCKET_ID:  0xD1_partmgr!PmReadWriteCompletion+2b

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

1: kd> .trap 0xffffffff807e6a94
ErrCode = 00000000
eax=00000000 ebx=856be500 ecx=87610d00 edx=00000000 esi=856be6fc edi=8761a370
eip=8b315279 esp=807e6b08 ebp=807e6b14 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
partmgr!PmReadWriteCompletion+0x2b:
8b315279 8b00            mov     eax,dword ptr [eax]  ds:0023:00000000=????????
Could you please help me analyse this, like I say, I've had no problems with this system & my troubleshooting is rusty.

Thanks in advance

Might have something to do with a 10 year old driver

Code:
ASPI32.SYS    9/10/1999 18:46:10    0x37d99842    0x91af3000    0x91af6e40        0x00003e40
I would suggest you update aspi and run a system file check to verify and repair the partmgr and the rest of the OS files

SFC /SCANNOW Command - System File Checker

running the rest of the DMP's now

EDIT stack relevant. your USBPORT is failing probably because of the aspi driver. update to test or run driver verifier to check.. BE SURE you have a backup before running driver verifier.

Beyond that, please run Verifier with these settings:
Quote:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Code:
Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
http://support.microsoft.com/kb/244617

Code:
STACK_TEXT:  
82f3da94 8b312279 badb0d00 00000000 8a8c1030 nt!KiTrap0E+0x2cf
82f3db14 82e7fb33 86d44300 85a07d08 00000000 partmgr!PmReadWriteCompletion+0x2b
82f3db58 8bb00498 82f3db8c 8bb00abd 8a8c1030 nt!IopfCompleteRequest+0x128
82f3db60 8bb00abd 8a8c1030 85a07d08 00000001 CLASSPNP!ClassCompleteRequest+0x11
82f3db8c 82e7fb33 00000000 8a619310 00636c18 CLASSPNP!TransferPktComplete+0x2e4
82f3dbd0 91f5d868 82e57354 85bd1610 00000000 nt!IopfCompleteRequest+0x128
82f3dc00 91f5e178 85770fe0 8a619310 8a673940 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6e0
82f3dc2c 91f619af 872cc028 872cc0f0 872cca98 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x33b
82f3dc54 91f5bd18 872cc028 872cca98 872cc002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc
82f3dc78 82e7f3b5 872ccaa4 872cc002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
82f3dcd4 82e7f218 82f40d20 82f4a280 00000000 nt!KiExecuteAllDpcs+0xf9
82f3dd20 82e7f038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
82f3dd24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
My System SpecsSystem Spec
20 Jan 2011   #3
roguestate

Windows 7 Ultimate x86
 
 

Thanks - could you please explain how to update aspi.sys. I find articles dating back to 2002 & OS Win 95/98/ME. I have absolutely no idea what it is or where to find it.

This is the first step in the solution?

I've found a driver from 2002 & updated
My System SpecsSystem Spec
.

22 Jan 2011   #4
roguestate

Windows 7 Ultimate x86
 
 

Followed all your advice, but the problem persists.

Has anyone else experienced this?
My System SpecsSystem Spec
15 Feb 2011   #5
roguestate

Windows 7 Ultimate x86
 
 

I uninstalled the USB boost software and everything appears to be fixed & this seems to be the solution for those experiencing similar problems.
My System SpecsSystem Spec
Reply

 BSOD on large file transfer to ext HD




Thread Tools




Similar help and support threads
Thread Forum
Can't transfer large file to external drive
I'm trying to do a simple back up. One 12g folder transfer to an external hard drive. Drag and dropping will will stop working about 1/4 of the way through. I tried TeraCopy and that gets through about 6g before it stops working. Any idea what is wrong?
Hardware & Devices
Why does transfer of large files slow down computer so much
I have a decent system yet when I transfer large files from one hard drive to another it causes computer to be unworkably slow Any ideas how to address this problem? mobo: asus p8p67 pro ram : 16 gb gskill video: nvidia gtx 560 ti cpu: intel i7 2600k 3.4ghz HDD: 120gb intel ssd, 3tb...
Performance & Maintenance
BSOD when extracting large file
My laptop always gets bluescreen when extracting large file from .rar files my laptop is Lenovo V470c .dmp file is in attachment
BSOD Help and Support
BSOD when running handbrake or during large file transfers
This is a computer that I built a couple of months ago and it consistently crashes when running handbrake, not every time but say 3 out of 4 times. It will also crash when making large file transfers like moving my movies from one hard drive to another. I have ran Memtest86 without any problems. I...
BSOD Help and Support
Home Network Large File Transfer Lockup
Just installed Win7 64 Home Pro from XP two days ago. The last remaining issue I need to solve is a drag and drop file transfer to my other home network computer (HNC). So far I've been able to d&d files from the HNC via Acronis WD in it's explorer mode without any issues, some sized in the...
Network & Sharing
BSOD on large file transfers
I have been trying to reload all the data back to the pc after reinstalling windows. whenever I try to copy a folder larger then 10GB it will copy most of the files but then crash with a BSOD the error info is listed below. Problem signature: Problem Event Name: BlueScreen OS Version: ...
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 06:02.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App