ATI HIS HD 4670 - BSOD (ati3duag.dll) - Page 2

DylanO · 12-04-2008, 01:15 AM

I tried it at 2.2V and this time running counter strike, I got to the server list before it froze. The BOSD only happens when I run a game. I doubt its faulty RAM, cause wouldn't not even be able to run my photoshop, windows media player watching HD movie, etc.? Is that right..?
Or my GPU is a DoA?

**jcgriff2** · 12-04-2008, 01:41 AM

Quote:

Originally Posted by jcgriff2

Are you using a slipstream XP SP3 disc for installation? Did BSODs start before driver updates installed? Any trouble after re-install and before programs installs?

Are all Windows Updates in?

Windows Updates -
http://update.microsoft.com/microsof....aspx?ln=en-us

Flash 6?

PSU ? RAM?

Other items in my post..?

Regards. . .

jcgriff2

.

DylanO · 12-04-2008, 07:45 AM

Yes all updates are finished.
I've tried on two different PSU's, same results.
Most likely RAM, I have to run memtest86+.
I don't think it was flash 6.

DylanO · 12-04-2008, 01:15 PM

Today was the first day to get BOSD without running a game, and it wasn't a ati3duag.dll BOSD too!

I got..
"0x0000004E: PFN_LIST_CORRUPT"
"This indicates that the memory management Page File Number list is corrupted. Can be caused by corrupt physical RAM, or by drivers passing bad memory descriptor lists."

This case is getting more clues and clues..
Does this mean faulty RAM?
Once I get home, I'll try making a bootable disc with memtest86+ and see.

I'll post the decoded minidump or upload it when I get home.
Thanks!

**jcgriff2** · 12-04-2008, 04:09 PM

What was the rest of the bugcheck - 1st parm inside parenthesis may provide add'l info.

Basic 0x4e bugcheck related to page file corruption; however, corrupt data could be placed in good page. PSU, RAM, HDD...

In addition to memtest86+ run chkdsk /r

Try another PSU as has been suggested by others.

Let's try Driver Verifier - never know -
STRT | Run | cmd | type verifier & hit enter - the Verifier screen will appear | do the following:

Code:


1. Select 2nd option - Create custom settings (for code developers)
2. Select 2nd option - Select individual settings from a full list.
3. Check the boxes• Special Pool 
• Pool Tracking 
• Force IRQL checking4. Select last option - Select driver names from a list 
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where Microsoft is not the Provider
7. Click on Finish 
8. Re-boot

If the Driver Verifier (DV) finds a violation, it will BSOD system. This is good thing.

To see status of verifier, type verifier into cmd prompt again - but this time select the last option on the first screen - "Display information about the currently verified drivers..". If you find your system to unstable (the verifier generally consumes CPU & RAM), turn if "off" and re-boot. To turn the Driver Verifier off, bring up command prompt and type verifier /reset then re-boot.

If you get a verifier-enabled BSOD, get it ASAP - go to \windows\minidump - get it, zip it up and attach.

Regards. . .

jcgriff2

.

DylanO · 12-04-2008, 04:34 PM

Ran memtest86+ (version 2.10), passed all test's with no errors.

Here's my recent BSOD, I think it was just a temporary one that came up from Steam (gaming app).

Code:

...............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 0, 1, 0}

Probably caused by : memory_corruption

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000099, A PTE or PFN is corrupt
Arg2: 00000000, page frame number
Arg3: 00000001, current page state
Arg4: 00000000, 0

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


BUGCHECK_STR:  0x4E_99

PFN_PAGE_SINGLE_BIT_ERROR: Bugcheck args 2 and 3 differ by a bit, its hardware error.

MEMORY_CORRUPTOR:  ONE_BIT

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  Steam.exe

LAST_CONTROL_TRANSFER:  from 80522ddc to 804f9f43

STACK_TEXT:  
a9c29ba8 80522ddc 0000004e 00000099 00000000 nt!KeBugCheckEx+0x1b
a9c29bd8 80511a55 c0883fd4 000000b6 8a1cff98 nt!MiDecrementShareCount+0x3a
a9c29bfc 805b0253 01a36201 8a1cfda0 007ffff8 nt!MiDeleteValidAddress+0x177
a9c29c1c 805134f7 8a1cfda0 8a1cfed8 8a1cfda0 nt!MiDeleteAddressesInWorkingSet+0x65
a9c29c50 805d2712 001cfda0 8a15fa90 c0000005 nt!MmCleanProcessAddressSpace+0x193
a9c29cf0 805d27f5 c0000005 a9c29d4c 804ff94f nt!PspExitThread+0x680
a9c29cfc 804ff94f 8a15fa90 a9c29d48 a9c29d3c nt!PsExitSpecialApc+0x23
a9c29d4c 80541ef6 00000001 00000000 a9c29d64 nt!KiDeliverApc+0x1af
a9c29d4c 7c9122dd 00000001 00000000 a9c29d64 nt!Kei386EoiHelper+0x3a
WARNING: Frame IP not in any known module. Following frames may be wrong.
109bddd8 00000000 00000000 00000000 00000000 0x7c9122dd


STACK_COMMAND:  kb

FOLLOWUP_NAME:  memory_corruption

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000099, A PTE or PFN is corrupt
Arg2: 00000000, page frame number
Arg3: 00000001, current page state
Arg4: 00000000, 0

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


BUGCHECK_STR:  0x4E_99

PFN_PAGE_SINGLE_BIT_ERROR: Bugcheck args 2 and 3 differ by a bit, its hardware error.

MEMORY_CORRUPTOR:  ONE_BIT

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  Steam.exe

LAST_CONTROL_TRANSFER:  from 80522ddc to 804f9f43

STACK_TEXT:  
a9c29ba8 80522ddc 0000004e 00000099 00000000 nt!KeBugCheckEx+0x1b
a9c29bd8 80511a55 c0883fd4 000000b6 8a1cff98 nt!MiDecrementShareCount+0x3a
a9c29bfc 805b0253 01a36201 8a1cfda0 007ffff8 nt!MiDeleteValidAddress+0x177
a9c29c1c 805134f7 8a1cfda0 8a1cfed8 8a1cfda0 nt!MiDeleteAddressesInWorkingSet+0x65
a9c29c50 805d2712 001cfda0 8a15fa90 c0000005 nt!MmCleanProcessAddressSpace+0x193
a9c29cf0 805d27f5 c0000005 a9c29d4c 804ff94f nt!PspExitThread+0x680
a9c29cfc 804ff94f 8a15fa90 a9c29d48 a9c29d3c nt!PsExitSpecialApc+0x23
a9c29d4c 80541ef6 00000001 00000000 a9c29d64 nt!KiDeliverApc+0x1af
a9c29d4c 7c9122dd 00000001 00000000 a9c29d64 nt!Kei386EoiHelper+0x3a
WARNING: Frame IP not in any known module. Following frames may be wrong.
109bddd8 00000000 00000000 00000000 00000000 0x7c9122dd


STACK_COMMAND:  kb

FOLLOWUP_NAME:  memory_corruption

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

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

DylanO · 12-04-2008, 05:10 PM

Well, I ran chkdsk, but stage 5 (verifying free space), went from 5% to 10% in like 10 minutes, then 10% stood there for like another 12 minutes and I had stuff to do so I restarted.

------

But I'm pretty sure this is the error from DV, cause I got a BSOD a minute after..

Code:

BugCheck 100000D1, {b, 2, 8, b}

Probably caused by : atapi.sys ( atapi!IdePortCompletionDpc+1e )

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

0: 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: 0000000b, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 0000000b, address which referenced memory

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


READ_ADDRESS:  0000000b 

CURRENT_IRQL:  2

FAULTING_IP: 
+b
0000000b ??              ???

PROCESS_NAME:  Idle

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

LAST_CONTROL_TRANSFER:  from b9f12aa8 to 0000000b

FAILED_INSTRUCTION_ADDRESS: 
+b
0000000b ??              ???

STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
805513bc b9f12aa8 8055c0c0 ffdff9c0 000003e6 0xb
80551428 80545e7f 8a4bc0a4 8a4bc030 00000000 atapi!IdePortCompletionDpc+0x1e
80551440 8055be60 ffdffc50 00000000 8055be60 nt!KiRetireDpcList+0x61
80551450 80545d64 00000000 0000000e 00000000 nt!KiIdleThread0
80551454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atapi!IdePortCompletionDpc+1e
b9f12aa8 8d45a4          lea     eax,[ebp-5Ch]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  atapi!IdePortCompletionDpc+1e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atapi

IMAGE_NAME:  atapi.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4802539d

FAILURE_BUCKET_ID:  0xD1_CODE_AV_BAD_IP_atapi!IdePortCompletionDpc+1e

BUCKET_ID:  0xD1_CODE_AV_BAD_IP_atapi!IdePortCompletionDpc+1e

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

DylanO · 12-04-2008, 05:30 PM

Actually ever since, I did the DV..
I'm getting these BOSD's now.
right above^^ got that again..

EDIT:

I'm pretty sure these problem's are happening because, the HD 4670 video card I have is possibly has dead video RAM. This thread right here.. He had problems with his video card, and whenever I started a game I would see blue patches similar to that and quick blackish scan lines would come up. Can't show you cause I will get another BSOD, but looks very similar to that thread. Should I RMA it?

DylanO · 12-04-2008, 09:52 PM

How do I fix that IRQ thing, ever since I did that DV it screwed it up, but don't worry I'm just going to reformat again and install windows, I think that would be the most stress-free thing to do right now, a bowl of lovely medical cannabis and watching it format.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {1464a241, 2, 1, 804fa049}

Probably caused by : memory_corruption

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 1464a241, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 804fa049, address which referenced memory

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


WRITE_ADDRESS:  1464a241 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeCancelTimer+d
804fa049 808b55088a5a03  or      byte ptr [ebx+5A8A0855h],3

CUSTOMER_CRASH_COUNT:  5

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xA

PROCESS_NAME:  explorer.exe

UNALIGNED_STACK_POINTER:  ba4c71fb

LAST_CONTROL_TRANSFER:  from 4cbfbcba to 804fa049

STACK_TEXT:  
ba4cbf93 4cbfbcba d5d8dcba 274060b9 27774489 nt!KeCancelTimer+0xd
WARNING: Frame IP not in any known module. Following frames may be wrong.
ba4cbf9b 274060b9 27774489 dff00089 274000ff 0x4cbfbcba
ba4cbf9f 27774489 dff00089 274000ff 27405089 0x274060b9
ba4cbfa3 dff00089 274000ff 27405089 70680089 0x27774489
ba4cbfa7 274000ff 27405089 70680089 02deffba 0xdff00089
ba4cbfab 27405089 70680089 02deffba 4cbfcc7a 0x274000ff
ba4cbfaf 70680089 02deffba 4cbfcc7a d5f896ba 0x27405089
ba4cbfb3 02deffba 4cbfcc7a d5f896ba 05cbb0b9 0x70680089
ba4cbfb7 4cbfcc7a d5f896ba 05cbb0b9 dff9c08a 0x2deffba
ba4cbfbb d5f896ba 05cbb0b9 dff9c08a dff980ff 0x4cbfcc7a
ba4cbfbf 05cbb0b9 dff9c08a dff980ff 545e7fff 0xd5f896ba
ba4cbfc3 dff9c08a dff980ff 545e7fff 27770480 0x5cbb0b9
ba4cbfc7 dff980ff 545e7fff 27770480 27400089 0xdff9c08a
ba4cbfcb 545e7fff 27770480 27400089 00000089 0xdff980ff
ba4cbfcf 27770480 27400089 00000089 00000000 0x545e7fff
ba4cbfd3 27400089 00000089 00000000 ed2fac00 0x27770480
ba4cbfd7 00000000 00000000 ed2fac00 4ea23f82 0x27400089


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    804fa040-804fa047  8 bytes - nt!KeCancelTimer+4
	[ ec 53 33 c9 ff 15 88 80:03 c8 89 4d e4 3b 4d 0c ]
8 errors : !nt (804fa040-804fa047)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

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

Now it's memory_corruption?

But, I un-installed the video card and played a game on onboard graphics, it ran perfect until that DV thing messed it up with the BSOD's now. So I'm positive now that it was the graphics card I assume. What do you think. I'm RMA'ing it, possibly if I can switch it for a different card.

12-04-2008, 01:15 AM	#21 (permalink)
DylanO Registered User Join Date: Feb 2007 Location: 127.0.0.1:1000 Posts: 89 OS: Windows XP Professional My System	Re: ATI HIS HD 4670 - BSOD (ati3duag.dll) I tried it at 2.2V and this time running counter strike, I got to the server list before it froze. The BOSD only happens when I run a game. I doubt its faulty RAM, cause wouldn't not even be able to run my photoshop, windows media player watching HD movie, etc.? Is that right..? Or my GPU is a DoA? __________________ - Dylan O.

12-04-2008, 07:45 AM	#23 (permalink)
DylanO Registered User Join Date: Feb 2007 Location: 127.0.0.1:1000 Posts: 89 OS: Windows XP Professional My System	Re: ATI HIS HD 4670 - BSOD (ati3duag.dll) Yes all updates are finished. I've tried on two different PSU's, same results. Most likely RAM, I have to run memtest86+. I don't think it was flash 6. __________________ - Dylan O.

12-04-2008, 01:15 PM	#24 (permalink)
DylanO Registered User Join Date: Feb 2007 Location: 127.0.0.1:1000 Posts: 89 OS: Windows XP Professional My System	Re: ATI HIS HD 4670 - BSOD (ati3duag.dll) Today was the first day to get BOSD without running a game, and it wasn't a ati3duag.dll BOSD too! I got.. "0x0000004E: PFN_LIST_CORRUPT" "This indicates that the memory management Page File Number list is corrupted. Can be caused by corrupt physical RAM, or by drivers passing bad memory descriptor lists." This case is getting more clues and clues.. Does this mean faulty RAM? Once I get home, I'll try making a bootable disc with memtest86+ and see. I'll post the decoded minidump or upload it when I get home. Thanks! __________________ - Dylan O. Last edited by DylanO; 12-04-2008 at 01:17 PM.

12-04-2008, 04:09 PM	#25 (permalink)
jcgriff2 Moderator, Microsoft Support Join Date: Sep 2007 Location: Palm Springs, California Posts: 10,028 OS: Windows 7, Vista Ultimate My System	Re: ATI HIS HD 4670 - BSOD (ati3duag.dll) What was the rest of the bugcheck - 1st parm inside parenthesis may provide add'l info. Basic 0x4e bugcheck related to page file corruption; however, corrupt data could be placed in good page. PSU, RAM, HDD... In addition to memtest86+ run chkdsk /r Try another PSU as has been suggested by others. Let's try Driver Verifier - never know - STRT \| Run \| cmd \| type verifier & hit enter - the Verifier screen will appear \| do the following: Code: 1. Select 2nd option - Create custom settings (for code developers) 2. Select 2nd option - Select individual settings from a full list. 3. Check the boxes • Special Pool • Pool Tracking • Force IRQL checking 4. Select last option - Select driver names from a list 5. Click on the Provider heading - sorts list by Provider 6. Check ALL boxes where Microsoft is not the Provider 7. Click on Finish 8. Re-boot If the Driver Verifier (DV) finds a violation, it will BSOD system. This is good thing. To see status of verifier, type verifier into cmd prompt again - but this time select the last option on the first screen - "Display information about the currently verified drivers..". If you find your system to unstable (the verifier generally consumes CPU & RAM), turn if "off" and re-boot. To turn the Driver Verifier off, bring up command prompt and type verifier /reset then re-boot. If you get a verifier-enabled BSOD, get it ASAP - go to \windows\minidump - get it, zip it up and attach. Regards. . . jcgriff2 . __________________ . . . . . . . . BSOD Posting Instructions B Expecting a reply and waiting > 36 hours ? Send a PM to me containing a link to your thread My availability will be limited through ~ December 1, 2009

12-04-2008, 05:30 PM	#28 (permalink)
DylanO Registered User Join Date: Feb 2007 Location: 127.0.0.1:1000 Posts: 89 OS: Windows XP Professional My System	Re: ATI HIS HD 4670 - BSOD (ati3duag.dll) Actually ever since, I did the DV.. I'm getting these BOSD's now. right above^^ got that again.. EDIT: I'm pretty sure these problem's are happening because, the HD 4670 video card I have is possibly has dead video RAM. This thread right here.. He had problems with his video card, and whenever I started a game I would see blue patches similar to that and quick blackish scan lines would come up. Can't show you cause I will get another BSOD, but looks very similar to that thread. Should I RMA it? __________________ - Dylan O. Last edited by DylanO; 12-04-2008 at 05:50 PM.