Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Minidump file


  • Please log in to reply
14 replies to this topic

#1 rexbenefit

rexbenefit

  • Members
  • 44 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cincinnati, OH.
  • Local time:09:11 AM

Posted 20 October 2008 - 07:56 AM

Hi All,

My crashing issue is getting worse. Now I'm crashing on boot. Was thinking this is a vid card issue but now not so sure. The following is the boot file info. Any help would be appreciated. I have just installed new vid drivers and this wasn't happening prior other than in my Everquest game.


Microsoft ® Windows Debugger Version 6.9.0003.113 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [I:\WINDOWS\Minidump\Mini102008-05.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*i:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.080814-1233
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a6a0
Debug session time: Mon Oct 20 08:38:36.281 2008 (GMT-4)
System Uptime: 0 days 0:02:23.860
Loading Kernel Symbols
........................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {f05c371c, 0, 804e70d5, 2}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiLocateAndReserveWsle+52 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: f05c371c, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 804e70d5, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: f05c371c

FAULTING_IP:
nt!MiLocateAndReserveWsle+52
804e70d5 8b0490 mov eax,dword ptr [eax+edx*4]

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 5

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: ashServ.exe

LAST_CONTROL_TRANSFER: from 804e910b to 804e70d5

STACK_TEXT:
aee24c08 804e910b c050369c 7c34d37c 81cef738 nt!MiLocateAndReserveWsle+0x52
aee24c20 804e9cd1 7c34d37c c01f0d34 81cef738 nt!MiAddValidPageToWorkingSet+0x84
aee24c50 804e9bd9 00000000 7c34d37c c01f0d34 nt!MiCompleteProtoPteFault+0x167
aee24c80 804e929f 00000000 7c34d37c c01f0d34 nt!MiResolveProtoPteFault+0x17d
aee24cfc 804e901e 00000000 7c34d37c c01f0d34 nt!MiDispatchFault+0x13b
aee24d4c 804e1718 00000000 7c34d37c 01000001 nt!MmAccessFault+0xc09
aee24d4c 7c34d37c 00000000 7c34d37c 01000001 nt!KiTrap0E+0xcc
WARNING: Frame IP not in any known module. Following frames may be wrong.
010894dc 00000000 00000000 00000000 00000000 0x7c34d37c


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiLocateAndReserveWsle+52
804e70d5 8b0490 mov eax,dword ptr [eax+edx*4]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiLocateAndReserveWsle+52

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48a4023c

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x50_nt!MiLocateAndReserveWsle+52

BUCKET_ID: 0x50_nt!MiLocateAndReserveWsle+52

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

BC AdBot (Login to Remove)

 


m

#2 rexbenefit

rexbenefit
  • Topic Starter

  • Members
  • 44 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cincinnati, OH.
  • Local time:09:11 AM

Posted 20 October 2008 - 08:03 AM

Here is the first file from this morning.

BTW, I have a built machine, ASUS A7N8X Deluxe mobo, AMD XP3000 Barton, 2-80GB HD, RADEON 9800 PRO 256MB, Sound Blaster 2


Microsoft ® Windows Debugger Version 6.9.0003.113 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [I:\WINDOWS\Minidump\Mini102008-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*i:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.080814-1233
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a6a0
Debug session time: Mon Oct 20 07:41:31.890 2008 (GMT-4)
System Uptime: 0 days 0:11:45.498
Loading Kernel Symbols
..................................................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
Unable to load image ati3duag.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ati3duag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {d, 0, 0, 0}

Probably caused by : ati3duag.dll ( ati3duag+119418 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x7f_d

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: eqgame.exe

LAST_CONTROL_TRANSFER: from bf2ad418 to e39a18fa

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
adbeb90c bf2ad418 e394aa40 adbeb9a0 e38dd420 0xe39a18fa
adbeb910 e394aa40 adbeb9a0 e38dd420 bf2ad442 ati3duag+0x119418
adbeb914 adbeb9a0 e38dd420 bf2ad442 e38dd42c 0xe394aa40
adbeb918 e38dd420 bf2ad442 e38dd42c e38dd2e0 0xadbeb9a0
adbeb9a0 00000000 7dccccce 7dccccce 7dccccce 0xe38dd420


STACK_COMMAND: kb

FOLLOWUP_IP:
ati3duag+119418
bf2ad418 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: ati3duag+119418

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ati3duag

IMAGE_NAME: ati3duag.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 486d9269

FAILURE_BUCKET_ID: 0x7f_d_ati3duag+119418

BUCKET_ID: 0x7f_d_ati3duag+119418

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

kd> lmvm ati3duag
start end module name
bf194000 bf5305a0 ati3duag T (no symbols)
Loaded symbol image file: ati3duag.dll
Image path: ati3duag.dll
Image name: ati3duag.dll
Timestamp: Thu Jul 03 23:00:57 2008 (486D9269)
CheckSum: 0039D0CD
ImageSize: 0039C5A0
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0

#3 rexbenefit

rexbenefit
  • Topic Starter

  • Members
  • 44 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cincinnati, OH.
  • Local time:09:11 AM

Posted 20 October 2008 - 09:35 AM

Here is the latest:


Microsoft ® Windows Debugger Version 6.9.0003.113 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [I:\WINDOWS\Minidump\Mini102008-06.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*i:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.080814-1233
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a6a0
Debug session time: Mon Oct 20 09:24:34.593 2008 (GMT-4)
System Uptime: 0 days 0:45:35.177
Loading Kernel Symbols
..................................................................................................................................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, c2cc5001, 63ea, c0c00000}

Probably caused by : memory_corruption ( nt!MiLocateWsle+c0 )

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041284, A PTE or the working set list is corrupt.
Arg2: c2cc5001
Arg3: 000063ea
Arg4: c0c00000

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


BUGCHECK_STR: 0x1a_41284

CUSTOMER_CRASH_COUNT: 6

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 80524df7 to 8053356e

STACK_TEXT:
f78c2bec 80524df7 0000001a 00041284 c2cc5001 nt!KeBugCheckEx+0x1b
f78c2c24 804f5e9f 000063ea 88575d10 8a3b4db8 nt!MiLocateWsle+0xc0
f78c2c64 805668f8 c2cc5000 884b2c88 00000000 nt!MmUnmapViewInSystemCache+0xc2
f78c2c7c 804f6136 8a3b4db8 88575d10 00000000 nt!CcUnmapVacb+0x2a
f78c2cac 804f6346 00000000 00000000 88575d74 nt!CcUnmapVacbArray+0xdf
f78c2cc8 804f62b8 88575d10 806ee298 88575d10 nt!CcUnmapAndPurge+0x20
f78c2cf4 804ec12f 00000001 80556890 89d92bc0 nt!CcDeleteSharedCacheMap+0xa6
f78c2d2c 804e4f1d 8a3bf1e0 805616c0 8a3c2640 nt!CcWriteBehind+0x316
f78c2d74 804e426b 8a3bf1e0 00000000 8a3c2640 nt!CcWorkerThread+0x126
f78c2dac 8057d17b 8a3bf1e0 00000000 00000000 nt!ExpWorkerThread+0x100
f78c2ddc 804f827a 804e4196 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiLocateWsle+c0
80524df7 006a00 add byte ptr [edx],ch

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiLocateWsle+c0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48a4023c

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x1a_41284_nt!MiLocateWsle+c0

BUCKET_ID: 0x1a_41284_nt!MiLocateWsle+c0

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

kd> lmvm nt
start end module name
804d7000 806eb500 nt (pdb symbols) i:\symbols\ntoskrnl.pdb\9FAD72E3DB2240D99CB55FCC4F7CE1182\ntoskrnl.pdb
Loaded symbol image file: ntoskrnl.exe
Mapped memory image file: i:\symbols\ntoskrnl.exe\48A4023C214500\ntoskrnl.exe
Image path: ntoskrnl.exe
Image name: ntoskrnl.exe
Timestamp: Thu Aug 14 06:00:28 2008 (48A4023C)
CheckSum: 002147EA
ImageSize: 00214500
File version: 5.1.2600.3427
Product version: 5.1.2600.3427
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntoskrnl.exe
OriginalFilename: ntoskrnl.exe
ProductVersion: 5.1.2600.3427
FileVersion: 5.1.2600.3427 (xpsp_sp2_gdr.080814-1233)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.

#4 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:02:11 PM

Posted 20 October 2008 - 12:42 PM

Are the insides of your computer clean?

#5 rexbenefit

rexbenefit
  • Topic Starter

  • Members
  • 44 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cincinnati, OH.
  • Local time:09:11 AM

Posted 21 October 2008 - 11:40 AM

OK, the machine did need a good cleaning.

Edited by rexbenefit, 21 October 2008 - 03:16 PM.


#6 rexbenefit

rexbenefit
  • Topic Starter

  • Members
  • 44 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cincinnati, OH.
  • Local time:09:11 AM

Posted 21 October 2008 - 03:17 PM

Was up about an hour and then crashed again. Here is the minidump file. If I could localize which proggie is giveing me issues I would update or dump it to keep the system running.

Any help is appreciated.

Microsoft ® Windows Debugger Version 6.9.0003.113 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [I:\WINDOWS\Minidump\Mini102108-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*i:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.080814-1233
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a6a0
Debug session time: Tue Oct 21 16:02:33.453 2008 (GMT-4)
System Uptime: 0 days 1:12:12.046
Loading Kernel Symbols
.....................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
Unable to load image ati3duag.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ati3duag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c000001d, e3b40780, ad54888c, 0}

Probably caused by : ati3duag.dll ( ati3duag+107e58 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c000001d, The exception code that was not handled
Arg2: e3b40780, The address that the exception occurred at
Arg3: ad54888c, Trap Frame
Arg4: 00000000

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


OVERLAPPED_MODULE: Address regions for 'kmixer' and 'CTERFXFX.SYS' overlap

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

FAULTING_IP:
+ffffffffe3b40780
e3b40780 f20fd6d1 movdq2q mm2,xmm1

TRAP_FRAME: ad54888c -- (.trap 0xffffffffad54888c)
ErrCode = 00000000
eax=e729b6c0 ebx=e3940040 ecx=00000007 edx=00000090 esi=e398eac0 edi=e398eac0
eip=e3b40780 esp=ad548900 ebp=ad54890c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
e3b40780 f20fd6d1 movdq2q mm2,xmm1
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: eqgame.exe

LAST_CONTROL_TRANSFER: from bf2a5e58 to e3b40780

FAILED_INSTRUCTION_ADDRESS:
+ffffffffe3b40780
e3b40780 f20fd6d1 movdq2q mm2,xmm1

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
ad54890c bf2a5e58 e398eac0 ad5489a0 e392142c 0xe3b40780
ad548910 e398eac0 ad5489a0 e392142c bf2a5e82 ati3duag+0x107e58
ad548914 ad5489a0 e392142c bf2a5e82 e3921438 0xe398eac0
ad548918 e392142c bf2a5e82 e3921438 e39212e0 0xad5489a0
ad5489a0 00000000 7dccccce 7dccccce 7dccccce 0xe392142c


STACK_COMMAND: kb

FOLLOWUP_IP:
ati3duag+107e58
bf2a5e58 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: ati3duag+107e58

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ati3duag

IMAGE_NAME: ati3duag.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 48d99dc6

FAILURE_BUCKET_ID: 0x8E_BAD_IP_ati3duag+107e58

BUCKET_ID: 0x8E_BAD_IP_ati3duag+107e58

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

kd> lmvm ati3duag
start end module name
bf19e000 bf570ba0 ati3duag T (no symbols)
Loaded symbol image file: ati3duag.dll
Image path: ati3duag.dll
Image name: ati3duag.dll
Timestamp: Tue Sep 23 21:54:14 2008 (48D99DC6)
CheckSum: 003DD46B
ImageSize: 003D2BA0
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0

#7 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:02:11 PM

Posted 21 October 2008 - 03:46 PM

Id get Driver Cleaner Pro to completely remove your ati drivers then install a fresh downloaded copy.

#8 peterdiva

peterdiva

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Western Australia
  • Local time:10:11 PM

Posted 21 October 2008 - 04:32 PM

As above, but install the Omega drivers instead. They're known to fix both of the ATI crashes you're getting.

http://www.omegadrivers.net/ati_winxp.php

#9 hamluis

hamluis

    Moderator


  • Moderator
  • 54,830 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:11 AM

Posted 22 October 2008 - 09:10 AM

If you don't have MS.Net already installed, do so before downloading/installing any ATI drivers.

Omega drivers are slightly modified ATI drivers and should be considered as identical for download purposes.

http://en.wikipedia.org/wiki/Omega_drivers

Louis

#10 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,073 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:09:11 AM

Posted 23 October 2008 - 11:06 AM

If you installed the certified ATI drivers previously, then it's unlikely that the ATI drivers are the problem (unlikely - NOT impossible).

The errors all seem to revolve around memory issues, so I'd suggest a memory diagnostic in order to rule that out. Here's a free, bootable one that I've used: http://www.memtest86.com/
Just read the instructions and boot from the CD that you make in order to run the test. Let the test run for a minimum of 3 passes (but overnight is better). If it starts giving errors, you can safely stop the test and we can figure out where to go from there.

If it doesn't give you errors, then I'd have to suspect the Everquest game - in particular the eqgame.exe file that's cited in quite a few of the error reports. To see if it's that, uninstall Everquest and then install a freshly downloaded copy (to ensure that a corruption in the original file isn't causing this).
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#11 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:02:11 PM

Posted 23 October 2008 - 02:26 PM

If you installed the certified ATI drivers previously, then it's unlikely that the ATI drivers are the problem (unlikely - NOT impossible).



ATI has been notorious for releasing buggy drivers in the past. It is one reason they lost me as a customer.

#12 rexbenefit

rexbenefit
  • Topic Starter

  • Members
  • 44 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cincinnati, OH.
  • Local time:09:11 AM

Posted 24 October 2008 - 02:35 AM

UPDATE:

OK, want to start by saying you guys are awesome! The help I received here is second to none.

I proceeded as instructed. Ran Driver Cleaner per the instructions, re-installed the latest ATI drivers from a fresh d-load, the problem was still there. System encounterd a BSOD 000008E crash inside 1 hour. Looked at the minidump and it was the same ATI3duag.dll bad instruction showing. I thought maybe I had not done something right so I went through the process again. Only this time, I hit clean a second time while running DC. Sure enough, it found more driver trash to be deleted.

I had d-loaded the Omega drivers and made the decision to install them this time as I had no luck at all with the ATI drivers. Best decision I ever made concerning this PC. I also deleted and re-installed some files Sony recommends to ensure the EQ program is not corrupt.

The system is running great, no crashes at all to date. I let the game run for 24 hours straight, no crashes. It seems I will no longer be using ATI drivers in my system. The graphics look better than ever on standard settings with the Omega drivers. I'm not an overclock guy, never wanted to risk a burn up of the vid card. There is much greater control with the Omega drivers and tools as well. These drivers ROCK! If Omega ever goes away I can guarantee so will the ATI card in my system. I would have a hard time buying another ATI product in the future absed on this experience.

Thanks again for all the help,

Rex

#13 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:02:11 PM

Posted 24 October 2008 - 01:24 PM

UPDATE:

OK, want to start by saying you guys are awesome! The help I received here is second to none.

I proceeded as instructed. Ran Driver Cleaner per the instructions, re-installed the latest ATI drivers from a fresh d-load, the problem was still there. System encounterd a BSOD 000008E crash inside 1 hour. Looked at the minidump and it was the same ATI3duag.dll bad instruction showing. I thought maybe I had not done something right so I went through the process again. Only this time, I hit clean a second time while running DC. Sure enough, it found more driver trash to be deleted.

I had d-loaded the Omega drivers and made the decision to install them this time as I had no luck at all with the ATI drivers. Best decision I ever made concerning this PC. I also deleted and re-installed some files Sony recommends to ensure the EQ program is not corrupt.

The system is running great, no crashes at all to date. I let the game run for 24 hours straight, no crashes. It seems I will no longer be using ATI drivers in my system. The graphics look better than ever on standard settings with the Omega drivers. I'm not an overclock guy, never wanted to risk a burn up of the vid card. There is much greater control with the Omega drivers and tools as well. These drivers ROCK! If Omega ever goes away I can guarantee so will the ATI card in my system. I would have a hard time buying another ATI product in the future absed on this experience.

Thanks again for all the help,

Rex


And this post is one reason, why ATI Lost me as a future customer. I shouldn't have to install modified drivers to get a product I purchased to work right. The Official ATI ones should be enough.

I am now a happy nVIdia user, and I will be for life.

#14 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,073 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:09:11 AM

Posted 25 October 2008 - 06:22 AM

Glad to hear that this has worked for you!
ATI lost me long ago (issues with a TVWonder card), so I was unaware of these driver issues.
I learn something new here every day!
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#15 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:02:11 PM

Posted 25 October 2008 - 02:29 PM

Glad to hear that this has worked for you!
ATI lost me long ago (issues with a TVWonder card), so I was unaware of these driver issues.
I learn something new here every day!


Just spreading my experience with ATI.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users