blue screen of death file transfer over 4gb

Page 1 of 2 12 LastLast

  1. Posts : 73
    w7 dual boot vista32
       #1

    blue screen of death file transfer over 4gb


    when I try to move 4bg or larger from one computer to another over LAN I get a BSOD at the very end. happened on a previous 7 install as well.

    anyone else getting this? I did not get the code but I will try later and write it down.
      My Computer


  2. Posts : 18,404
    Windows 7 Ultimate x64 SP1
       #2

    This seems to be something that some people have had problems with. Maybe send feedback on it and maybe they'll fix it.

    A couple of threads mentioning it.

    https://www.sevenforums.com/general-d...s-7-crash.html
    https://www.sevenforums.com/general-d...-bugcheck.html
      My Computer


  3. Posts : 2,899
    Windows 7 Ult x64(x2), HomePrem x32(x4), Server 08 (+VM), 08 R2 (VM) , SuSe 11.2 (VM), XP 32 (VM)
       #3

    actually if you have a dmp post it up...
    ill see if we can find the issue at hand....
    from what i have seen the (dmp file brought by notinf and another that was able to debug his...)
    it leads me to say that the tdx.sys file is the one doing it...
    as per explained here...
    tdx.sys causing BSOD - Fixed!
      My Computer


  4. Posts : 73
    w7 dual boot vista32
    Thread Starter
       #4

    Here is the latest minidump
      My Computer


  5. Posts : 1,519
    El Capitan / Windows 10
       #5

    where?
      My Computer


  6. Posts : 2,899
    Windows 7 Ult x64(x2), HomePrem x32(x4), Server 08 (+VM), 08 R2 (VM) , SuSe 11.2 (VM), XP 32 (VM)
       #6

    yeah same as baarod...

    upload as a zip so you can upload it here...
      My Computer


  7. Posts : 2,899
    Windows 7 Ult x64(x2), HomePrem x32(x4), Server 08 (+VM), 08 R2 (VM) , SuSe 11.2 (VM), XP 32 (VM)
       #7

    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.
    Probably caused by : tdx.sys ( tdx+ffc0 )
    Arguments:
    Arg1: 00000000000000b8, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff8800133dfc0, address which referenced memory
    Followup: MachineOwner

    yep same file...
    you using broadcom??
    its looking to me that broadcom drivers are the one responsible for this as the people that are having this files bsod on them are either using broadcom wireless or wired based chips with incompatible drivers...
      My Computer


  8. Posts : 1,519
    El Capitan / Windows 10
       #8

    Yay darkassain. You're starting to get good at this
      My Computer


  9. Posts : 2,899
    Windows 7 Ult x64(x2), HomePrem x32(x4), Server 08 (+VM), 08 R2 (VM) , SuSe 11.2 (VM), XP 32 (VM)
       #9

    baarod said:
    Yay darkassain. You're starting to get good at this
    lmao
    hey i haven't had enough time set up my machine....
    i was telling myself i would install the debugging tools (eventually)...
    well last time i windgb was in xp ...
    finally smarteye reminded me about it and i finally got installed...
      My Computer


  10. Posts : 18,404
    Windows 7 Ultimate x64 SP1
       #10

    I think that was me that reminded you, but maybe you're talking about something else. lol
    Download Windows 7 Beta Checked Builds
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About 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 03:00.
Find Us