BSOD on a network copy

MrBiggz

Member
Greetings!

Hey has anybody gotten any blue's on a network copy? Even a regular copy? I've only encountered one so far. I think I'll try the SP1 RC and see if that helps. I did notice that the copy/move is a bit on the whack side. Moving 2K+ files that take up 1.5Gb should not take 3 hours. When the copy started it just sat there for 5 minutes before it started copying.

The the blue screens. I guess I get the 180 days of free support .. might as well use it. I got three minidumps like to know what they are and solve the problem.

Any insight is welcomed!

Regards! :cool:
 

My Computer

System One

  • CPU
    Intel Core 2 Duo E6750 @ 2.66Ghz
    Motherboard
    Abit IP35 Pro
    Memory
    4Gb Patriot PC1600
    Graphics Card(s)
    EVGA (Nvidia) GT 430 1GB
    Sound Card
    On board
    Monitor(s) Displays
    Syncmaster 2494
    Screen Resolution
    1920 x 1080
Hi Mrbiggz,
When you get a blue screen it should read STOP:0x00000XX or something to that effect. Need that code to help figure out the issue. You can look in the System or Application event log for this error as well. Let us know. Thanks
Raj
 

My Computer

Network copying is a lot better in SP1 rc ;)
 

My Computers

System One System Two

  • Operating System
    Windows 11 Workstation
    Manufacturer/Model
    doofenshmirtz evil incorporated
    CPU
    Ryzen 9 5950X
    Motherboard
    Asus ROG Crosshair VIII Formula
    Memory
    Corsair Vengeance RGB PRO Black 64GB (4x16GB) 3600MHz AMD Ryzen Tuned DDR4
    Graphics Card(s)
    ASUS AMD Radeon RX 6900 XT 16GB ROG Strix LC OC
    Sound Card
    Creative
    Monitor(s) Displays
    3 x27" Dell U2724D & 1 x 34" Dell U3415W
    Hard Drives
    Samsung 980 Pro 1TB M.2 2280 PCI-e 4.0 x4 NVMe Solid State
    Drive
    PSU
    1500W ThermalTake Toughpower
    Case
    ThermalTake Level 10 GT
    Cooling
    Enermax Liqtech 240
    Keyboard
    Surface Ergonomic.
    Mouse
    Logitech Performance MX
    Internet Speed
    350 Mb/s
    Other Info
    WinTV NovaTD
    HP CP1515n Color Laser
    Sony BD-5300S-0B Blu-ray Writer
    Microsoft LifeCam Cinema
    APC 750i Smart UPS
  • Operating System
    windows 10
    Manufacturer/Model
    Surface Pro 3
    CPU
    1.9GHz Intel Core i5-4300U (dual-core, 3MB cache, up to 2.9GHz with Turbo Boost)
    Memory
    4GB
    Graphics card(s)
    Intel HD Graphics 4400
    Monitor(s) Displays
    12" Multi Touch
    Screen Resolution
    2160 x 144
    Hard Drives
    128GB
    Mouse
    Logitech
    Keyboard
    yes
    Internet Speed
    350 Mb/s
Speaking of writing files:
First shipped with Windows Vista, SMB 2.0, also known as the Common Internet File System (CIFS) is also included in Windows Server 2008 and sports a number of improvements over its predecessor. Most immediately noticeable in SMB 2.0 is support for symbolic links, a powerful feature that UNIX admins have enjoyed since the beginning of time. SMB 2.0 also supports the sending of multiple SMB commands in a single network packet, thus significantly reducing the network overhead required for communication. Also increased in SMB 2.0 are the buffer sizes and the number of concurrent allowed file handles, resulting in increased scalability for a pure Windows environment. To work with older systems, Windows Server 2008 supports both SMB 1.0 and SMB 2.0 and automatically uses the version most appropriate for communication. SMB 2.0 is used only between Windows Server 2008 systems and with Windows Vista systems. SMB communication with all other operating systems uses SMB 1.0.
 

My Computer

I had one 0x80000000000002 and two 0x80000000000000

they seem pretty common. I'm installing SP1 RC lets see if that helps!
 

My Computer

System One

  • CPU
    Intel Core 2 Duo E6750 @ 2.66Ghz
    Motherboard
    Abit IP35 Pro
    Memory
    4Gb Patriot PC1600
    Graphics Card(s)
    EVGA (Nvidia) GT 430 1GB
    Sound Card
    On board
    Monitor(s) Displays
    Syncmaster 2494
    Screen Resolution
    1920 x 1080
Back
Top