BSOD - File Transfer to USB drive

[mesteele101]

This has happened on all versions of Windows 7. Upgrading and fresh install has the same results.

Transferring a 45GB file to a USB drive will sometimes transfer to 25% then I get a white screen causing me to reboot. Sometimes the screen stays gray and if I have any open windows they flash black. There are times when the file actually completes, however the status bar hangs at around 25%.

If someone could check out this dump file and assist I would be grateful.

TIA...

 

[mesteele101]

Ok, new install not allowing Windows to update anything on install. The problem still exists. The problem is not just with file transfers to a USB drive, but transfers from any drive to any drive causes the transfer window to stop, the screen goes black and then any open window stays black and the screen flashes gray. Sometimes just before the whole screen goes black about 1" of the top of my screen turns black. I've also got a solid white screen causing me to reboot. I've also got a BSOD that auto reboots throwing a recovery error.

This is really frustrating because Windows 7 runs so well except this one problem. I'm guessing that I may need to wait for the official release as this problem shouldn't exist in the RTM. I have absolutely no problems with Vista so why in the heck is Windows 7 having this problem. I know it's BETA and these problems exist. I now others are having these problems and I hope MS has them resolved so, I'm installing 7127 and I see there is another later release, so I'm off to see it has this problem.

 

[Hammerhead786]

You have a bugcheck 124 error which is a fatal hardware error. I would guess that this is related to your graphics card. there is a known issue relating to the PCI Express bus. Have a look at this:

BSOD 0x00000124 - Windows 7 RC1 Upgrade from Windows Vista Ultimate

I think that the issue has been corrected in build 7127.

 

[mesteele101]

Nope, running 7127 and this is still an ongoing issue. Fresh install or an upgrade it's still there. I've tried 7000, 7100, and 7127.

Vista does not show this problem at all. It looks like Microsoft has dropped the ball on this one. I already switched out my video card when I upgraded to Vista for Aero compatability. Maybe Microsoft is in the revenu generating business for the Video card makers....

@Hammerhead786
I see you have basically the same MB as me and your not having these problems. Seems kinda strange. What BIOS revision are you running?

 

[Hammerhead786]

I'm running bios 1002 which is the latest. I have installed the
15.35_nforce_win7_64bit_international_whql drivers from Nvidia. I'm using Catlyst 9.3 drivers for Vista which are the only ones for my x1950 graphics card. I installed only the wireless drivers for the wireless card and not the complete app. All the other drivers are Win 7 native.

Aside from that I've got Office 2007 installed, Logitech Setpoint, Skype, Firefox, Debugging Tools, Nokia Pc Suite and Avg free edition. After having resolved a cpu overheating issue recently my machine is running like a barefoot man over hot coals.

 

[usasma]

The first dump (STOP 0x124) doesn't give us much info, but the second points to your ATI drivers while they're working with DirectX. I'd suggest trying other ATI drivers (I use the one's from Windows Update on my 4870 w/o issues).

Here's the second dump file:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\FUBAR-RC1-Desktop\Downloads\dump\Minidump\051909-26937-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:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7127 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7127.0.x86fre.winmain.090507-1820
Machine Name:
Kernel base = 0x82840000 PsLoadedModuleList = 0x8297f570
Debug session time: Tue May 19 19:25:31.270 2009 (GMT-4)
System Uptime: 0 days 0:48:04.146
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
................
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 86743d48, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 00000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 00000000, Pointer to offending driver name.
Arg4: 00000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

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

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************REMOVED ERROR MESSAGE STUFF FROM HERE - usasma

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: dxgkrnl

FAULTING_MODULE: 82840000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a03bbea

FAULTING_THREAD: 86743d48

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 91c9842b to 828fbf28

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a2edb948 91c9842b 000000ea 86743d48 00000000 nt+0xbbf28
a2edb98c 91c912a6 a2edb9d8 00000000 91c8c099 dxgkrnl+0x1242b
a2edb9b4 8d434a21 a2edb9d8 00000000 00000000 dxgkrnl+0xb2a6
a2edba04 8d42ec0a 8d53900f a2edba9c 00000bb8 atikmdag+0x27a21
a2edba24 8d540e45 86ccd001 a2edba3c 85d55140 atikmdag+0x21c0a
a2edba7c 8d53928f 85d55008 8d53900f a2edba9c atikmdag+0x133e45
a2edbaac 8d545d61 85d55008 00000004 00000000 atikmdag+0x12c28f
a2edbadc 8d5478f9 00000000 85d55008 85d55140 atikmdag+0x138d61
a2edbb04 8d54033c 00100403 00000000 86489010 atikmdag+0x13a8f9
a2edbb20 8d536ae5 85d55008 a2edbb40 8d4105f1 atikmdag+0x13333c
a2edbb2c 8d4105f1 85d55008 84eb79c0 00000000 atikmdag+0x129ae5
a2edbb40 8d41b194 00000000 c0000001 84eb79c0 atikmdag+0x35f1
a2edbb70 8d41c259 86c16000 86c16000 8280e6ee atikmdag+0xe194
a2edbb84 91d0785a 00000000 86d84510 86c16000 atikmdag+0xf259
a2edbba8 91d0779b 85d11788 86d84510 00000000 dxgkrnl+0x8185a
a2edbbd0 91d07570 86d84510 86d84510 8bf3007e dxgkrnl+0x8179b
a2edbbec 91d4392c 00000000 00000000 a2edbcb0 dxgkrnl+0x81570
a2edbc64 91d6acd9 fffffcfb 0002cd0e 00000000 dxgmms1+0x692c
a2edbc90 91d4a993 85d11788 a2edbcb0 00000102 dxgmms1+0x2dcd9
a2edbd28 91d6f4b7 00000000 82879d54 85d11788 dxgmms1+0xd993
a2edbd3c 91d6f573 85d11788 00000000 86743d48 dxgmms1+0x324b7
a2edbd50 82a17121 85d11788 e063d57a 00000000 dxgmms1+0x32573
a2edbd90 828bad99 91d6f4f4 85d11788 00000000 nt+0x1d7121
00000000 00000000 00000000 00000000 00000000 nt+0x7ad99


STACK_COMMAND: .thread 0xffffffff86743d48 ; kb

FOLLOWUP_IP:
dxgkrnl+1242b
91c9842b ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: dxgkrnl+1242b

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: dxgkrnl.sys

BUCKET_ID: WRONG_SYMBOLS

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

1: kd> .thread
Implicit thread is now 86743d48
1: kd> kb
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
a2edb948 91c9842b 000000ea 86743d48 00000000 nt+0xbbf28
a2edb98c 91c912a6 a2edb9d8 00000000 91c8c099 dxgkrnl+0x1242b
a2edb9b4 8d434a21 a2edb9d8 00000000 00000000 dxgkrnl+0xb2a6
a2edba04 8d42ec0a 8d53900f a2edba9c 00000bb8 atikmdag+0x27a21
a2edba24 8d540e45 86ccd001 a2edba3c 85d55140 atikmdag+0x21c0a
a2edba7c 8d53928f 85d55008 8d53900f a2edba9c atikmdag+0x133e45
a2edbaac 8d545d61 85d55008 00000004 00000000 atikmdag+0x12c28f
a2edbadc 8d5478f9 00000000 85d55008 85d55140 atikmdag+0x138d61
a2edbb04 8d54033c 00100403 00000000 86489010 atikmdag+0x13a8f9
a2edbb20 8d536ae5 85d55008 a2edbb40 8d4105f1 atikmdag+0x13333c
a2edbb2c 8d4105f1 85d55008 84eb79c0 00000000 atikmdag+0x129ae5
a2edbb40 8d41b194 00000000 c0000001 84eb79c0 atikmdag+0x35f1
a2edbb70 8d41c259 86c16000 86c16000 8280e6ee atikmdag+0xe194
a2edbb84 91d0785a 00000000 86d84510 86c16000 atikmdag+0xf259
a2edbba8 91d0779b 85d11788 86d84510 00000000 dxgkrnl+0x8185a
a2edbbd0 91d07570 86d84510 86d84510 8bf3007e dxgkrnl+0x8179b
a2edbbec 91d4392c 00000000 00000000 a2edbcb0 dxgkrnl+0x81570
a2edbc64 91d6acd9 fffffcfb 0002cd0e 00000000 dxgmms1+0x692c
a2edbc90 91d4a993 85d11788 a2edbcb0 00000102 dxgmms1+0x2dcd9
a2edbd28 91d6f4b7 00000000 82879d54 85d11788 dxgmms1+0xd993

 

[mesteele101]

I tried display drivers, Windows fresh install, Windows Update, and latest from nvidia. All with the same result.

I installed the latest 15.23_nforce_winvista32_international_whql driver.

I see that nforce4 has moved to legacy. Maybe it's time to upgrade my MB?

 

[usasma]

It's possible that the nForce drivers are causing this - but you really can't tell until there's a Windows 7 driver made for it.

Although lot's of people are having success with the leaked builds, they aren't as thoroughly tested as the 7000 and 7100 builds. So, IMO, you're more likely to have issues with them.

 

[mesteele101]

It's happend on 7000, 7100, and 7127. This will most likely be a problem until it goes gold, or I get another MB.

The x64 version requires me to enable 'Memory Remap' in the BIOS before it will install. Vista x64 does not require it enabled.