BSOD when transfering Large files to external HD

K

keroro

New Member
Info about about my system:

My Vista is:
- 32 bit
- Original OS installed on my system
- Its OEM came with my dell XPS 420

-My system is a bit over 3 years old
-I just formatted and reinstalled/ updated my OS a few days ago.
However I was having this problem before the format. I was hoping it would fix it.

I've attached the Zip file with info needed after running the exe file.

A bit about the problem:

The blue screen gives me a

DRIVER_IRQL_NOT_LESS_THAN_OR_EQUAL_TO due to the partmgr.sys file.

The only time i get this error is when im transfering LARGE files over to my 1TB LACIE external hard drive. I own 2 other External Hard drives and they transfer large files just fine. IF i try to transfer the same files/folder to the LAcie 1TB While transfering It will crash and give me that BSOD. The lacie 1TB is healthy. Ive done 2 days of error testing / tech support with LACIE and the drive is clean. I did a reformat of the drive , i did error scans Etc.. I changed power source, usb cables ALl the same error. I've tested the drive on 5 different computers transfering over the exact same files and it works everytime. So its not a problem with the files OR the Drive itself. I can actually move / transfer/ copy smaller folders or files to the lacie 1tb with no crashing. THe only time it crashes is hwen i try to copy files or folders over 1 gig ( doesnt matter what the files are it just crashes while transfering)

Any help would be GREATLY appreciated!

THANKS!
 

Attachments

  • KeroroBSODproblem.zip
    707.7 KB · Views: 15

My Computer

System One

IMO you've done the necessary troubleshooting to be able to blame this on the LACIE drive.
There's 3 or 4 basic causes of BSOD's/crashes:
- hardware issues
- Windows issues
- software (driver) issues
- incompatibility issues

- You've ruled out hardware on everything but the LACIE because everything works fine
- You've most likely ruled out Windows issues by reinstalling the OS
- You can rule out incompatibility issues here: https://www.microsoft.com/windows/compatibility/windows-vista/
- You can rule out software/driver issues (maybe) by running Driver Verifier according to these instructions:
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

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
Click to expand...
 

My Computer

System One

"IMO you've done the necessary troubleshooting to be able to blame this on the LACIE drive."

Maybe you misread my post but the LACIE hardware is healthy. I've tested it on several computers and it works GREAT on everysingle computer but mine. Even though i reformated my windows recently theres obviously a problem with windows. The lacie doesnt need special drivers (it doesnt come with any. its just plug and play) Its compatible with all computers but mine. IT WORKS great at transfering files that are less than 1 GIG. I only encounter this problem when transfering larger files that are over 1 gig.

-I've ruled out Hardware issue with the lacie itself.
-IT's not a software issue because I'm not using any special software. Just windows to copy and paste files.
-As far as incompatibility , I dont see why it would be incompatible with my windows vista when it works fine on 3 other machines that have similar specs to my computer on vista. Its an external plug and play hard drive . Should work on all computers ( and ive tested it to make sure).

Even though I've reformatted my computer and reinstalled my vista OS it has to be a windows problem as everythign else in your list is not to blame. I dont think the steps you're telling me to do with driver verify will work because the driver for this external hard drive is provided by microsoft... It wouldnt give you any more info Than what i already included in the Zip file.

Anyone else have any ideas?
 

My Computer

System One

OK Welll.. For my own entertainment I tried the driver verify thing you told me to.
Ummm I got a new BSOD that ive never seen before like 10 seconds after reboot...Something to do with Fsomethingnet.sys. I didnt get the to see completely.. It was quick. Im sure its recorded in the minidump. ITs definitely not the same BSOD that I get when i try to transfer large files onto the lacie. Are these related at all?

IF i turn off the driver verify I dont get that BSOD at alll ever... The only BSOD that i ever get is when transfering large files/folders to the lacie.

Anyways help is greatly appreciated. Id like to fix this problem as soon as i can.
Thanks
 

Attachments

  • KeroroNewMinidump.zip
    226.7 KB · Views: 10

My Computer

System One

FNETURPX.SYS - FNet User Proxy Driver
Company website here: FNet Corporation

Please remove the program associated with this driver. If unable to find out which program it is, rename the FNETURPX.SYS file (it's in C:\Windows\System32\drivers) to FNETURPX.BAK then reboot to ensure that it stays renamed. Then see if that eliminates the BSOD's during large file transfers.

BSOD BUGCHECK SUMMARY
Code: 
[font=lucida console]
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Debug session time: Tue Sep  7 09:40:26.733 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:43.576
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
BugCheck D5, {ac4def80, 0, 8d66ef16, 0}
*** WARNING: Unable to verify timestamp for FNETURPX.SYS
*** ERROR: Module load completed but symbols could not be loaded for FNETURPX.SYS
Probably caused by : FNETURPX.SYS ( FNETURPX+f16 )
BUGCHECK_STR:  0xD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Debug session time: Tue Sep  7 09:36:49.993 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:05.866
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
BugCheck D5, {a7b1cf80, 0, 8d264f16, 0}
*** WARNING: Unable to verify timestamp for FNETURPX.SYS
*** ERROR: Module load completed but symbols could not be loaded for FNETURPX.SYS
Probably caused by : FNETURPX.SYS ( FNETURPX+f16 )
BUGCHECK_STR:  0xD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Debug session time: Tue Sep  7 09:33:17.583 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:49.443
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
BugCheck D5, {abb08f80, 0, 8d05ff16, 0}
*** WARNING: Unable to verify timestamp for FNETURPX.SYS
*** ERROR: Module load completed but symbols could not be loaded for FNETURPX.SYS
Probably caused by : FNETURPX.SYS ( FNETURPX+f16 )
BUGCHECK_STR:  0xD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Debug session time: Tue Sep  7 09:29:51.455 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:27.299
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
BugCheck D5, {a782af80, 0, 8d266f16, 0}
*** WARNING: Unable to verify timestamp for FNETURPX.SYS
*** ERROR: Module load completed but symbols could not be loaded for FNETURPX.SYS
Probably caused by : FNETURPX.SYS ( FNETURPX+f16 )
BUGCHECK_STR:  0xD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Debug session time: Mon Sep  6 11:04:53.793 2010 (UTC - 4:00)
System Uptime: 1 days 0:22:40.530
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
*** ERROR: Module load completed but symbols could not be loaded for partmgr.sys
BugCheck D1, {0, 2, 0, 80717161}
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for CLASSPNP.SYS - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for USBPORT.SYS - 
Probably caused by : partmgr.sys ( partmgr+1161 )
BUGCHECK_STR:  0xD1
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Debug session time: Sun Sep  5 10:41:52.489 2010 (UTC - 4:00)
System Uptime: 0 days 0:38:47.216
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
*** ERROR: Module load completed but symbols could not be loaded for partmgr.sys
BugCheck D1, {0, 2, 0, 80717161}
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for CLASSPNP.SYS - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for USBPORT.SYS - 
Probably caused by : partmgr.sys ( partmgr+1161 )
BUGCHECK_STR:  0xD1
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Debug session time: Sun Sep  5 10:02:11.663 2010 (UTC - 4:00)
System Uptime: 1 days 11:37:59.893
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
*** ERROR: Module load completed but symbols could not be loaded for partmgr.sys
BugCheck D1, {0, 2, 0, 8231523b}
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for CLASSPNP.SYS - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for USBPORT.SYS - 
Probably caused by : partmgr.sys ( partmgr+123b )
BUGCHECK_STR:  0xD1
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Debug session time: Fri Sep  3 22:23:48.885 2010 (UTC - 4:00)
System Uptime: 0 days 11:33:20.558
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
*** ERROR: Module load completed but symbols could not be loaded for partmgr.sys
BugCheck D1, {0, 2, 0, 80710161}
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for CLASSPNP.SYS - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for USBPORT.SYS - 
Probably caused by : partmgr.sys ( partmgr+1161 )
BUGCHECK_STR:  0xD1
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Thu Sep  2 12:09:51.077 2010 (UTC - 4:00)
System Uptime: 0 days 1:27:28.932
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
*** ERROR: Module load completed but symbols could not be loaded for partmgr.sys
BugCheck D1, {8, 2, 1, 8070f210}
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for CLASSPNP.SYS - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for USBPORT.SYS - 
Probably caused by : partmgr.sys ( partmgr+1210 )
BUGCHECK_STR:  0xD1
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Debug session time: Thu Sep  2 01:54:06.264 2010 (UTC - 4:00)
System Uptime: 0 days 1:30:40.007
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
*** ERROR: Module load completed but symbols could not be loaded for partmgr.sys
BugCheck D1, {0, 2, 0, 8070e161}
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for CLASSPNP.SYS - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for USBPORT.SYS - 
Probably caused by : partmgr.sys ( partmgr+1161 )
BUGCHECK_STR:  0xD1
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  
 
 [/font]
 

My Computer

System One

Looks like that solved the problem! THANKS!!!

The program was named FNET usb turbo boost. A small program that came with the Lacie drive that supposedly made transfer 2 times faster. I didn't know it was installed. Interesting. Uninstalling it fixed the problem! I can now transfer files over 1 gig no problem. WEIRRRRRRRRRD

ALSO, my system NOW boots noticeably faster than before.

Thanks. glad i did the driver verify ....

Case closed!
 

My Computer

System One

Ive done 2 days of error testing / tech support with LACIE and the drive is clean.
Click to expand...
Makes ya wonder about the tech support, doesn't it?

Glad you got it fixed tho', thanks for letting us know!
 

My Computer

System One

You must log in or register to reply here.
Back
Top