Windows 7: Blue Screen Dump File - Help Needed!

briansnj · 30 Jan 2010

Newer motherboard. Everything was running fine. Fresh install of Win 7 Pro 64 bit. Ran fine for a month. Now getting strange crashes at random times.

Only seems to happen when I am gaming or when I transfer heavy amounts of data to same hard drive or between HDs.

Windows 7 Pro 64 bit, fresh install before. Thought maybe something went bad. Just did a fresh REBUILD but it has returned.

AMD Phenom 955 AM3, 4GB 1600+ DDR3, 2 Seagate HDs - 500GB and 1TB, Gigabyte GA-MA790GPT-UD3H with latest BIOS.
Further in depth details of my system are in my profile for you if needed.

I tried using MS Debugging Tools but I am not sure what to make of it. I am an experienced PC builder since 1993. But this has me baffled.

I need to know if my mobo is bad and needs RMA or if this is a corrupt or bad driver maybe from an MS update.

Thanks for any help. Debug translation quoted and included inside zip file with minidump.

Quote:

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

Loading Dump File [C:\Users\Tester\Desktop\013010-34663-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a65000 PsLoadedModuleList = 0xfffff800`02ca2e50
Debug session time: Sat Jan 30 19:39:45.900 2010 (GMT-5)
System Uptime: 0 days 0:03:40.570
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ataport.SYS ( ataport!IdeTranslateCompletedRequest+232 )

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP:
+0
00000000`00000000 ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x1E

PROCESS_NAME: System

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff88002ffb778 -- (.exr 0xfffff88002ffb778)
ExceptionAddress: fffff88000c03e2e (ataport!IdeTranslateCompletedRequest+0x0000000000000232)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff88002ffb820 -- (.trap 0xfffff88002ffb820)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000200 rbx=0000000000000000 rcx=fffffa800819f010
rdx=fffffa800482c1b0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000c03e2e rsp=fffff88002ffb9b0 rbp=fffffa800482c1b0
r8=0000000000000001 r9=0000000000000000 r10=fffffa80047e9620
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
ataport!IdeTranslateCompletedRequest+0x232:
fffff880`00c03e2e 41ff5708 call qword ptr [r15+8] ds:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002acec2e to fffff80002ad6ed0

STACK_TEXT:
fffff880`02ffa858 fffff800`02acec2e : 00000000`00000000 00000000`ffffffff fffff880`02ffafd0 fffff800`02b03e28 : nt!KeBugCheck
fffff880`02ffa860 fffff800`02afcbed : fffff800`02ce3c24 fffff800`02c1ca3c fffff800`02a65000 fffff880`02ffb778 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffa890 fffff800`02b04250 : fffff800`02c24b5c fffff880`02ffa908 fffff880`02ffb778 fffff800`02a65000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffa8c0 fffff800`02b111b5 : fffff880`02ffb778 fffff880`02ffafd0 fffff880`00000000 fffffa80`0819f010 : nt!RtlDispatchException+0x410
fffff880`02ffafa0 fffff800`02ad6542 : fffff880`02ffb778 00000000`00000002 fffff880`02ffb820 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`02ffb640 fffff800`02ad4e4a : 00000000`00000001 fffff880`04d93698 fffffa80`047e8100 fffff880`00c04552 : nt!KiExceptionDispatch+0xc2
fffff880`02ffb820 fffff880`00c03e2e : 00000000`00000002 00000000`00000000 fffffa80`00000030 fffff880`04d98d75 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffb9b0 fffff880`00c0c7ed : fffffa80`047e81a0 fffffa80`0819f010 00000000`00000000 00000000`0000000b : ataport!IdeTranslateCompletedRequest+0x232
fffff880`02ffbae0 fffff880`00c0c0ec : fffffa80`047e81a0 00000000`00000000 fffffa80`047e81a0 00000000`00000000 : ataport!IdeProcessCompletedRequests+0x4d5
fffff880`02ffbc10 fffff800`02ae25dc : fffff880`02fd3180 00000000`29526ecf fffffa80`047e8050 fffffa80`047e8118 : ataport!IdePortCompletionDpc+0x1a8
fffff880`02ffbcd0 fffff800`02adf6fa : fffff880`02fd3180 fffff880`02fddfc0 00000000`00000000 fffff880`00c0bf44 : nt!KiRetireDpcList+0x1bc
fffff880`02ffbd80 00000000`00000000 : fffff880`02ffc000 fffff880`02ff6000 fffff880`02ffbd40 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND: kb

FOLLOWUP_IP:
ataport!IdeTranslateCompletedRequest+232
fffff880`00c03e2e 41ff5708 call qword ptr [r15+8]

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: ataport!IdeTranslateCompletedRequest+232

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ataport

IMAGE_NAME: ataport.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc118

FAILURE_BUCKET_ID: X64_0x1E_ataport!IdeTranslateCompletedRequest+232

BUCKET_ID: X64_0x1E_ataport!IdeTranslateCompletedRequest+232

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

zigzag3143 · 31 Jan 2010

Quote: Originally Posted by briansnj

Newer motherboard. Everything was running fine. Fresh install of Win 7 Pro 64 bit. Ran fine for a month. Now getting strange crashes at random times.

Only seems to happen when I am gaming or when I transfer heavy amounts of data to same hard drive or between HDs.

Windows 7 Pro 64 bit, fresh install before. Thought maybe something went bad. Just did a fresh REBUILD but it has returned.

AMD Phenom 955 AM3, 4GB 1600+ DDR3, 2 Seagate HDs - 500GB and 1TB, Gigabyte GA-MA790GPT-UD3H with latest BIOS.
Further in depth details of my system are in my profile for you if needed.

I tried using MS Debugging Tools but I am not sure what to make of it. I am an experienced PC builder since 1993. But this has me baffled.

I need to know if my mobo is bad and needs RMA or if this is a corrupt or bad driver maybe from an MS update.

Thanks for any help. Debug translation quoted and included inside zip file with minidump.

Quote:

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

Loading Dump File [C:\Users\Tester\Desktop\013010-34663-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a65000 PsLoadedModuleList = 0xfffff800`02ca2e50
Debug session time: Sat Jan 30 19:39:45.900 2010 (GMT-5)
System Uptime: 0 days 0:03:40.570
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ataport.SYS ( ataport!IdeTranslateCompletedRequest+232 )

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP:
+0
00000000`00000000 ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x1E

PROCESS_NAME: System

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff88002ffb778 -- (.exr 0xfffff88002ffb778)
ExceptionAddress: fffff88000c03e2e (ataport!IdeTranslateCompletedRequest+0x0000000000000232)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff88002ffb820 -- (.trap 0xfffff88002ffb820)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000200 rbx=0000000000000000 rcx=fffffa800819f010
rdx=fffffa800482c1b0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000c03e2e rsp=fffff88002ffb9b0 rbp=fffffa800482c1b0
r8=0000000000000001 r9=0000000000000000 r10=fffffa80047e9620
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
ataport!IdeTranslateCompletedRequest+0x232:
fffff880`00c03e2e 41ff5708 call qword ptr [r15+8] ds:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002acec2e to fffff80002ad6ed0

STACK_TEXT:
fffff880`02ffa858 fffff800`02acec2e : 00000000`00000000 00000000`ffffffff fffff880`02ffafd0 fffff800`02b03e28 : nt!KeBugCheck
fffff880`02ffa860 fffff800`02afcbed : fffff800`02ce3c24 fffff800`02c1ca3c fffff800`02a65000 fffff880`02ffb778 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffa890 fffff800`02b04250 : fffff800`02c24b5c fffff880`02ffa908 fffff880`02ffb778 fffff800`02a65000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffa8c0 fffff800`02b111b5 : fffff880`02ffb778 fffff880`02ffafd0 fffff880`00000000 fffffa80`0819f010 : nt!RtlDispatchException+0x410
fffff880`02ffafa0 fffff800`02ad6542 : fffff880`02ffb778 00000000`00000002 fffff880`02ffb820 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`02ffb640 fffff800`02ad4e4a : 00000000`00000001 fffff880`04d93698 fffffa80`047e8100 fffff880`00c04552 : nt!KiExceptionDispatch+0xc2
fffff880`02ffb820 fffff880`00c03e2e : 00000000`00000002 00000000`00000000 fffffa80`00000030 fffff880`04d98d75 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffb9b0 fffff880`00c0c7ed : fffffa80`047e81a0 fffffa80`0819f010 00000000`00000000 00000000`0000000b : ataport!IdeTranslateCompletedRequest+0x232
fffff880`02ffbae0 fffff880`00c0c0ec : fffffa80`047e81a0 00000000`00000000 fffffa80`047e81a0 00000000`00000000 : ataport!IdeProcessCompletedRequests+0x4d5
fffff880`02ffbc10 fffff800`02ae25dc : fffff880`02fd3180 00000000`29526ecf fffffa80`047e8050 fffffa80`047e8118 : ataport!IdePortCompletionDpc+0x1a8
fffff880`02ffbcd0 fffff800`02adf6fa : fffff880`02fd3180 fffff880`02fddfc0 00000000`00000000 fffff880`00c0bf44 : nt!KiRetireDpcList+0x1bc
fffff880`02ffbd80 00000000`00000000 : fffff880`02ffc000 fffff880`02ff6000 fffff880`02ffbd40 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND: kb

FOLLOWUP_IP:
ataport!IdeTranslateCompletedRequest+232
fffff880`00c03e2e 41ff5708 call qword ptr [r15+8]

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: ataport!IdeTranslateCompletedRequest+232

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ataport

IMAGE_NAME: ataport.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc118

FAILURE_BUCKET_ID: X64_0x1E_ataport!IdeTranslateCompletedRequest+232

BUCKET_ID: X64_0x1E_ataport!IdeTranslateCompletedRequest+232

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

Hi and welcome

Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS. In this case bad driver ataport.sys

simply reinstall and run a system file check
type cmd in search>right click and run as admin>sfc /scannow

Good luck

Ken

briansnj · 31 Jan 2010

Hi Ken,
Thanks for the fast response.

Real quick, did you mean reinstall the bad driver? Or reinstall the OS over itself or wipe clean and do a fresh install.

Cause I did do a fresh, clean, careful rebuild and that failed. lol

I'll assume you meant the drivers first so I will do that as I await response.

briansnj · 31 Jan 2010

OK.
Got the latest drivers from Gigabyte and had the AMD Catalyst 10.1 set already.

Did the SFC /SCANNOW...showed no problems before and after I reloaded drivers.

Windows Update shows nothing needs updating.

Rebooted. Tried to move 80GB of data from a NAS device back to my freshly formatted spare hard drive ( before coming here I thought the HD was causing the problems so I wiped it and repartitioned)

It crashed not 60 seconds into that transfer.

Attached is minidump and report in TEXT format from debug tools like before. This time the error is different. Progress maybe? lol

briansnj · 31 Jan 2010

Tried again to see if I got a different cause from minidump.

YEP!

Pasted just the bottom part for you.

Quote:

STACK_COMMAND: kb

FOLLOWUP_IP:
rdbss!RxMapUserBuffer+3d
fffff880`03f07411 488bd8 mov rbx,rax

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: rdbss!RxMapUserBuffer+3d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: rdbss

IMAGE_NAME: rdbss.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc219

FAILURE_BUCKET_ID: X64_0xA_rdbss!RxMapUserBuffer+3d

BUCKET_ID: X64_0xA_rdbss!RxMapUserBuffer+3d

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

briansnj · 31 Jan 2010

Ran some hardware diagnostics on mobo and used things like Seagate Tools on my HDs, and ran Memtest+ 4.00 for over 8 passes so far without a single glitch.

Did all this before and got the same results...all hardware seems fine.

usasma · 31 Jan 2010

3 memory dumps - 3 different errors (STOP 0x1E; 0xA; 0x4E) and 3 different causes (ntoskrnl.exe; ataport.sys; rdbss.sys)
This pattern usually points to a hardware error - but with only 3 memory dumps it's a stretch to call this a "pattern"

Please update this older driver: ctac32k.sys Wed Jul 02 04:38:22 2008
It's a component of your Creative Audio Product by Creative Technology Ltd (Creative Labs Online Store).

Beyond this, I'd suggest carefully running these 2 stress tests on your system:

Quote:

Additional tests for certain specific circumstances:
Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Try this free stress test: Free Software - GIMPS

If they don't reveal anything, then I'd suggest starting with this hardware stripdown procedure to see if you can narrow down the problem device(s): Hardware Troubleshooting Via System Stripdown

Because you indicated that you could RMA the motherboard - I'd suggest doing it just because you can. Troubleshooting a motherboard hardware problem is a very difficult proposition. It can take a very long time to do and you still may not be sure even then.

Here's a summary of the BSOD's:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jan 30 19:39:45.900 2010 (GMT-5)
System Uptime: 0 days 0:03:40.570
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ataport.SYS ( ataport!IdeTranslateCompletedRequest+232 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan 31 11:34:30.940 2010 (GMT-5)
System Uptime: 0 days 0:06:04.610
BugCheck 4E, {7, 1c63, ff00000000000000, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+16e06 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan 31 11:58:22.684 2010 (GMT-5)
System Uptime: 0 days 0:08:53.964
BugCheck A, {fffff703a0005bc0, 2, 0, fffff80002af0851}
Probably caused by : rdbss.sys ( rdbss!RxMapUserBuffer+3d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe

briansnj · 31 Jan 2010

OK. Thanks for the guidance. I am thinking along the same lines. Will check out your links too.

I am leaning towards defective HD or Motherboard. Because this error only happens when I move data or swap data a lot...like playing games, transfer large GBs of data from HD to HD or HD to NAS or HD to other network PC.

I can cruise the net, and do tons of other things and it may or may not crash. But guaranteed if I move data. lol

Just wiped out my other HD, did a fresh install of Win 7 Pro 64, installed only latest and necessary drivers and had 2 or 3 crashes ONLY when I did the 'data transfer' test. lol

My vid card is solid. Stresses it on my other PC. No problems. Memory checks out fine over and over. Only thing new is the Phenom 955
and Gigabyte motherboard. No OCing or anything weird.

I will try swapping out a HD that I know is fine and see if that solves it. Then can try my old but similar MSI mobo and old AMD Phenom 940.

Wish me luck!

Feel free to post further advice if something comes to mind!

Windows 7: Blue Screen Dump File - Help Needed!

Blue Screen Dump File - Help Needed! problems?