Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Bluescreen after Bluescreen... Maybe because of ATI?


06 Apr 2010   #1

 
 
Bluescreen after Bluescreen... Maybe because of ATI?

Hey guys, i've read so many threads now that i thought it would be good to open my own one now...
I have very many Bluescreens, different kinds of errors...
nfts.sys / win32k.sys and some others...
Many people say that's because of the CCC of Ati. Yes, i've got an ATI 5770 HD, so that could be. Maybe there is a way to fix it? I've installed the driver only, installed the driver with CCC and already tried some other things... but... it just seems to do fewer bluescreens, but does them anyway.
ill upload some dmp files, the most recent ones. Thanks guys.

My System SpecsSystem Spec
.

06 Apr 2010   #2

Windows 7 Professional x64
 
 

Welcome!

I do see your video card driver as one of the causes. Do not use CCC, using only the driver.

I also see memory corruption. It may be worth testing your RAM. Download a copy of Memtest86 and burn the ISO to a CD using ImgBurn. Boot from the CD, and run at least 5 passes.

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


Loading Dump File [C:\Users\Jonathan\Desktop\040410-18174-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
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`02a4e000 PsLoadedModuleList = 0xfffff800`02c8be50
Debug session time: Sun Apr  4 07:14:39.414 2010 (GMT-4)
System Uptime: 0 days 0:22:10.553
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88004a996d6, fffff88009e877f0, 0}

Probably caused by : atipmdag.sys ( atipmdag+2896d6 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88004a996d6, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88009e877f0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
atipmdag+2896d6
fffff880`04a996d6 66398a94000000  cmp     word ptr [rdx+94h],cx

CONTEXT:  fffff88009e877f0 -- (.cxr 0xfffff88009e877f0)
rax=000000000d330800 rbx=fffff8a00c8883b0 rcx=0000000000000d33
rdx=00fff8a00c6a95b0 rsi=fffffa8007138810 rdi=fffffa8004163a40
rip=fffff88004a996d6 rsp=fffff88009e881d8 rbp=fffffa8004642010
 r8=fffffa8007138810  r9=000000000001fcb0 r10=fffff8a00c8883b0
r11=fffff88009e881d8 r12=00000000000000d2 r13=00000000000002da
r14=0000000000000116 r15=fffff8800e1a0000
iopl=0         nv up ei pl nz ac po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010216
atipmdag+0x2896d6:
fffff880`04a996d6 66398a94000000  cmp     word ptr [rdx+94h],cx ds:002b:00fff8a0`0c6a9644=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  engine.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88004a996d6

STACK_TEXT:  
fffff880`09e881d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atipmdag+0x2896d6


FOLLOWUP_IP: 
atipmdag+2896d6
fffff880`04a996d6 66398a94000000  cmp     word ptr [rdx+94h],cx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atipmdag+2896d6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atipmdag

IMAGE_NAME:  atipmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b8ddbbc

STACK_COMMAND:  .cxr 0xfffff88009e877f0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_atipmdag+2896d6

BUCKET_ID:  X64_0x3B_atipmdag+2896d6

Followup: MachineOwner
---------
My System SpecsSystem Spec
06 Apr 2010   #3

 
 

Yea thank you for the answer.
I downloaded already the driver only... i try to deinstall all ati drivers and try to install only the driver... Hope that works.
I used the microsoft diagnostic for the ram and there was no error... but okay, i will download memtest too.
Between the first message and this message there was one again...
Ill give you some feedback from my side when i did the tests. thx.
My System SpecsSystem Spec
.


06 Apr 2010   #4

Windows 7 Professional x64
 
 

It looks as if the problem is definitely with your GFX card driver. It's just a matter of trial-and-error now, trying to find a driver that works.

The latest driver isn't always the best. Sometimes older drivers work better, like for my nVidia GeForce 7200 GS.
My System SpecsSystem Spec
06 Apr 2010   #5

 
 

Quote   Quote: Originally Posted by Jonathan_King View Post
The latest driver isn't always the best.
Yeah i ran the memtest now... i made a photo of one error... and broke up the test after approx 45min at test 6.

it says:
Tst:8
Pass:0
Failing Address:000cff41dac - 3327.2MB
Good:cbff8caa
Bad:cb008caa
Err-Bits:00ff0000
Count: 1

and i deinstalled the ati now and installed the driver only. lets see if i get again a bluescreen....
and what can i do against the error? is it bad? do i have to put out ram? :s i have got 3 ram pieces... 1gb 1gb and 2gb... :s the 1gb and 1gb are dual channel able.
greetings
My System SpecsSystem Spec
06 Apr 2010   #6

Windows 7 Professional x64
 
 

If memtest turns up errors, it can mean a few things.

1) Your timings may be wrong.

2) You have at least 1 bad stick of RAM

3) You have at least one bad slot on your motherboard.

Try testing one of the sticks in all 3 slots; if it checks out, your slots are OK and one of the other sticks is bad
My System SpecsSystem Spec
06 Apr 2010   #7

 
 

Ah okay... i'll do that tomorrow if i have time. til now its running without bluescreen. lets see if there will be an error tomorrow, thx til now =)
if you mean the timings of the ram... all are 5-5-5-15.
and uhm, maybe i should test stick 1 at slot 1, stick 2 at slot 2, stick 3 at slot3. if anywhere an error appears, i know that the slot or the stick is bad. then ill take another stick (which was tested before) and put it into that slot... i think that would be the best case to test everything^^
edit:just came an bluescreen...
usbport.sys
ill upload the dump
thx =)
My System SpecsSystem Spec
08 Apr 2010   #8

 
 

bump? :s
My System SpecsSystem Spec
08 Apr 2010   #9

Windows 7 Professional x64
 
 

Try uninstalling any virtualization programs you may have, such as Daemon Tools and CD emulators.

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


Loading Dump File [C:\Users\Jonathan\Desktop\040610-24804-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
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`02a55000 PsLoadedModuleList = 0xfffff800`02c92e50
Debug session time: Tue Apr  6 17:16:04.430 2010 (GMT-4)
System Uptime: 0 days 2:25:08.568
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa8046a6c390, 2, 0, fffff8800515bb5c}

Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

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.
Arguments:
Arg1: fffffa8046a6c390, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800515bb5c, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfd0e0
 fffffa8046a6c390 

CURRENT_IRQL:  2

FAULTING_IP: 
USBPORT!USBPORT_Xdpc_End+1c
fffff880`0515bb5c 488b8b4033ed41  mov     rcx,qword ptr [rbx+41ED3340h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xD1

PROCESS_NAME:  chrome.exe

TRAP_FRAME:  fffff880009b0c90 -- (.trap 0xfffff880009b0c90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880009b0e28 rbx=0000000000000000 rcx=fffffa8004b99050
rdx=fffffa8004b99a10 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800515bb5c rsp=fffff880009b0e20 rbp=fffff880009b0e20
 r8=000000004f444600  r9=fffffa80039df100 r10=00000000ffffffff
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
USBPORT!USBPORT_Xdpc_End+0x1c:
fffff880`0515bb5c 488b8b4033ed41  mov     rcx,qword ptr [rbx+41ED3340h] ds:9050:00000000`41ed3340=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ac6469 to fffff80002ac6f00

STACK_TEXT:  
fffff880`009b0b48 fffff800`02ac6469 : 00000000`0000000a fffffa80`46a6c390 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`009b0b50 fffff800`02ac50e0 : fffffa80`039f64a0 fffffa80`04b99050 fffffa80`039df000 fffff880`052abcfa : nt!KiBugCheckDispatch+0x69
fffff880`009b0c90 fffff880`0515bb5c : 00000000`ffffffff fffffa80`05086702 fffffa80`04b99050 00000000`00000000 : nt!KiPageFault+0x260
fffff880`009b0e20 fffffa80`04b99a10 : fffff880`009b0ef8 fffff880`010804ce fffffa80`05086000 fffffa80`04b99a10 : USBPORT!USBPORT_Xdpc_End+0x1c
fffff880`009b0e50 fffff880`009b0ef8 : fffff880`010804ce fffffa80`05086000 fffffa80`04b99a10 fffffa80`05086750 : 0xfffffa80`04b99a10
fffff880`009b0e58 fffff880`010804ce : fffffa80`05086000 fffffa80`04b99a10 fffffa80`05086750 fffffa80`04b99a28 : 0xfffff880`009b0ef8
fffff880`009b0e60 fffffa80`05086000 : fffffa80`04b99a10 fffffa80`05086750 fffffa80`04b99a28 fffffa80`00000002 : sptd+0x424ce
fffff880`009b0e68 fffffa80`04b99a10 : fffffa80`05086750 fffffa80`04b99a28 fffffa80`00000002 01cad5ce`5da02da8 : 0xfffffa80`05086000
fffff880`009b0e70 fffffa80`05086750 : fffffa80`04b99a28 fffffa80`00000002 01cad5ce`5da02da8 00000000`752e2450 : 0xfffffa80`04b99a10
fffff880`009b0e78 fffffa80`04b99a28 : fffffa80`00000002 01cad5ce`5da02da8 00000000`752e2450 00000000`00000022 : 0xfffffa80`05086750
fffff880`009b0e80 fffffa80`00000002 : 01cad5ce`5da02da8 00000000`752e2450 00000000`00000022 00000000`00000000 : 0xfffffa80`04b99a28
fffff880`009b0e88 01cad5ce`5da02da8 : 00000000`752e2450 00000000`00000022 00000000`00000000 00000000`00000000 : 0xfffffa80`00000002
fffff880`009b0e90 00000000`752e2450 : 00000000`00000022 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1cad5ce`5da02da8
fffff880`009b0e98 00000000`00000022 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`04b99a28 : 0x752e2450
fffff880`009b0ea0 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`04b99a28 fffffa80`04b99a10 : 0x22


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !USBPORT
8 errors : !USBPORT (fffff8800515bb46-fffff8800515bb7e)
fffff8800515bb40  48  8b  c4  48  89  58 *00  48  89  68  10  48  89  70 *00  48 H..H.X.H.h.H.p.H
fffff8800515bb50  89  78  20  41  54  48 *8b  ec  20  48  8b  fa  48  8b *8b  40 .x ATH.. H..H..@
fffff8800515bb60  33  ed  41  83  cc  ff *8b  8b  d9  48  39  6a  28  74 *c9  41 3.A......H9j(t.A
fffff8800515bb70  8b  c4  f0  0f  c1  42 *eb  8b  4a  20  41  03  c4  48 *00  c8 .....B..J A..H..

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------
But it does appear as if your RAM or motherboard is faulty. Test individual sticks until you determine which stick or which slot is bad.

If it turns out the slot is bad, you will need to replace your motherboard.
My System SpecsSystem Spec
Reply

 Bluescreen after Bluescreen... Maybe because of ATI?




Thread Tools



Similar help and support threads for2: Bluescreen after Bluescreen... Maybe because of ATI?
Thread Forum
BlueScreen BSOD Help and Support
When a bluescreen isnt a bluescreen Performance & Maintenance
Getting Bluescreen lately BSOD Help and Support
BlueScreen BSOD Help and Support
Bluescreen BSOD Help and Support
HELP! HELP! Bluescreen! BSOD Help and Support
BlueScreen BSOD Help and Support

Our Sites

Site Links

About Us

Find 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 04:17 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33