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

Ativvaxx.dll Blue Screen Of Death


  • Please log in to reply
10 replies to this topic

#1 ShindouRyan

ShindouRyan

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:04:51 AM

Posted 25 August 2011 - 07:50 AM

I am using Window XP Pro, here are the result of analysis:


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


Loading Dump File [C:\WINDOWS\Minidump\Mini082511-04.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:
Unable to load image 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 XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Thu Aug 25 20:11:27.546 2011 (GMT+8)
System Uptime: 0 days 0:13:26.471
Unable to load image 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
................
Unable to load image ativvaxx.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ativvaxx.dll
*** ERROR: Module load completed but symbols could not be loaded for ativvaxx.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf9db120, a2b3cbe0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ativvaxx.dll ( ativvaxx+15120 )

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

2: 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: c0000005, The exception code that was not handled
Arg2: bf9db120, The address that the exception occurred at
Arg3: a2b3cbe0, Trap Frame
Arg4: 00000000

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

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.

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4dae3aa0

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

FAULTING_IP:
ativvaxx+15120
bf9db120 8b11 mov edx,dword ptr [ecx]

TRAP_FRAME: a2b3cbe0 -- (.trap 0xffffffffa2b3cbe0)
ErrCode = 00000000
eax=80004001 ebx=e19d8018 ecx=00000000 edx=e1ee4360 esi=e41afeac edi=80004005
eip=bf9db120 esp=a2b3cc54 ebp=e41afea8 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
ativvaxx+0x15120:
bf9db120 8b11 mov edx,dword ptr [ecx] ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from bf00705b to bf9db120

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a2b3cc9c bf00705b e43a8328 a2b3cd64 0012e328 ativvaxx+0x15120
a2b3cd48 bf00f7b8 ffffffff a2b3cd64 804dd99f dxg!DxDdCreateMoComp+0x1a3
a2b3cd54 804dd99f 75200025 0012e32c 0012e36c dxg!GUID_MiscellaneousCallbacks+0x2ac
a2b3cd64 7c90e514 badb0d00 0012e320 00000000 nt+0x699f
a2b3cd68 badb0d00 0012e320 00000000 00000000 0x7c90e514
a2b3cd6c 0012e320 00000000 00000000 00000000 0xbadb0d00
a2b3cd70 00000000 00000000 00000000 00000000 0x12e320


STACK_COMMAND: kb

FOLLOWUP_IP:
ativvaxx+15120
bf9db120 8b11 mov edx,dword ptr [ecx]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ativvaxx+15120

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ativvaxx

IMAGE_NAME: ativvaxx.dll

BUCKET_ID: WRONG_SYMBOLS

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

2: 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: c0000005, The exception code that was not handled
Arg2: bf9db120, The address that the exception occurred at
Arg3: a2b3cbe0, Trap Frame
Arg4: 00000000

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

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.

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4dae3aa0

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

FAULTING_IP:
ativvaxx+15120
bf9db120 8b11 mov edx,dword ptr [ecx]

TRAP_FRAME: a2b3cbe0 -- (.trap 0xffffffffa2b3cbe0)
ErrCode = 00000000
eax=80004001 ebx=e19d8018 ecx=00000000 edx=e1ee4360 esi=e41afeac edi=80004005
eip=bf9db120 esp=a2b3cc54 ebp=e41afea8 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
ativvaxx+0x15120:
bf9db120 8b11 mov edx,dword ptr [ecx] ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from bf00705b to bf9db120

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a2b3cc9c bf00705b e43a8328 a2b3cd64 0012e328 ativvaxx+0x15120
a2b3cd48 bf00f7b8 ffffffff a2b3cd64 804dd99f dxg!DxDdCreateMoComp+0x1a3
a2b3cd54 804dd99f 75200025 0012e32c 0012e36c dxg!GUID_MiscellaneousCallbacks+0x2ac
a2b3cd64 7c90e514 badb0d00 0012e320 00000000 nt+0x699f
a2b3cd68 badb0d00 0012e320 00000000 00000000 0x7c90e514
a2b3cd6c 0012e320 00000000 00000000 00000000 0xbadb0d00
a2b3cd70 00000000 00000000 00000000 00000000 0x12e320


STACK_COMMAND: kb

FOLLOWUP_IP:
ativvaxx+15120
bf9db120 8b11 mov edx,dword ptr [ecx]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ativvaxx+15120

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ativvaxx

IMAGE_NAME: ativvaxx.dll

BUCKET_ID: WRONG_SYMBOLS

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

2: 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: c0000005, The exception code that was not handled
Arg2: bf9db120, The address that the exception occurred at
Arg3: a2b3cbe0, Trap Frame
Arg4: 00000000

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

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.

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4dae3aa0

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

FAULTING_IP:
ativvaxx+15120
bf9db120 8b11 mov edx,dword ptr [ecx]

TRAP_FRAME: a2b3cbe0 -- (.trap 0xffffffffa2b3cbe0)
ErrCode = 00000000
eax=80004001 ebx=e19d8018 ecx=00000000 edx=e1ee4360 esi=e41afeac edi=80004005
eip=bf9db120 esp=a2b3cc54 ebp=e41afea8 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
ativvaxx+0x15120:
bf9db120 8b11 mov edx,dword ptr [ecx] ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from bf00705b to bf9db120

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a2b3cc9c bf00705b e43a8328 a2b3cd64 0012e328 ativvaxx+0x15120
a2b3cd48 bf00f7b8 ffffffff a2b3cd64 804dd99f dxg!DxDdCreateMoComp+0x1a3
a2b3cd54 804dd99f 75200025 0012e32c 0012e36c dxg!GUID_MiscellaneousCallbacks+0x2ac
a2b3cd64 7c90e514 badb0d00 0012e320 00000000 nt+0x699f
a2b3cd68 badb0d00 0012e320 00000000 00000000 0x7c90e514
a2b3cd6c 0012e320 00000000 00000000 00000000 0xbadb0d00
a2b3cd70 00000000 00000000 00000000 00000000 0x12e320


STACK_COMMAND: kb

FOLLOWUP_IP:
ativvaxx+15120
bf9db120 8b11 mov edx,dword ptr [ecx]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ativvaxx+15120

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ativvaxx

IMAGE_NAME: ativvaxx.dll

BUCKET_ID: WRONG_SYMBOLS

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

Please help out with this problem...

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,405 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:51 AM

Posted 25 August 2011 - 08:03 AM

I would try uninstalling...then reinstalling the ATI/Radeon video drivers.

Louis

#3 ShindouRyan

ShindouRyan
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:04:51 AM

Posted 27 August 2011 - 12:22 PM

I would try uninstalling...then reinstalling the ATI/Radeon video drivers.

Louis


Ok i will give it a try thank you.

#4 ShindouRyan

ShindouRyan
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:04:51 AM

Posted 28 August 2011 - 07:22 AM

After i reinstall my ATI Radeon drivers when my browser was loading videos, example youtube videos my computer just restart itself without showing any thing... please help with this problem.

#5 ShindouRyan

ShindouRyan
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:04:51 AM

Posted 28 August 2011 - 02:53 PM

Okie this is what happen after i uninstall and reinstall my ATI Radeon Drivers:

Posted Image

And here is the Analysis:


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


Loading Dump File [C:\WINDOWS\Minidump\Mini082911-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:
Unable to load image 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 XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Mon Aug 29 03:33:56.296 2011 (GMT+8)
System Uptime: 0 days 0:13:12.229
Unable to load image 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
............
Unable to load image ativvaxx.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ativvaxx.dll
*** ERROR: Module load completed but symbols could not be loaded for ativvaxx.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf9db090, a53c3be0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ativvaxx.dll ( ativvaxx+15090 )

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

Please help with this problem...

#6 diggi

diggi

  • Members
  • 335 posts
  • OFFLINE
  •  
  • Local time:03:51 AM

Posted 29 August 2011 - 11:13 AM

Your best bet might be to reinstall windows with only 1 stick of ram
Install ATI driver and restart
Install other drivers and restart after every installation

NOTE:TURN OFF AV AND FIREWALL!!!!!!!!!!!!!! DURING PROCESS

I had an ATIdvag2 BSOD on my asrock 880 gextreme 3 this seems to have solved the issue

#7 hamluis

hamluis

    Moderator


  • Moderator
  • 55,405 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:51 AM

Posted 30 August 2011 - 07:26 AM

The online sites with videos...rely upon java and flash player as properly installed components of systems.

You might try uninstalling each, then updating to the most current version of each.

Let's try this.

Download/install BlueScreenView, http://www.nirsoft.net/utils/blue_screen_view.html .

Double-click BlueScreenView.exe file.

When auto-scan is done (screen comes up), click Edit/Select All...then File/Save Selected Items.

Save the report as BSOD.txt.

Open BSOD.txt in Notepad, copy all content and paste it into your next reply.

Louis

#8 ShindouRyan

ShindouRyan
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:04:51 AM

Posted 31 August 2011 - 02:23 PM

Sorry for the late reply, here is the report from the BlueScreenView :

==================================================
Dump File : Mini090111-01.dmp
Crash Time : 9/1/2011 3:17:11 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf9db090
Parameter 3 : 0xa440ebe0
Parameter 4 : 0x00000000
Caused By Driver : ativvaxx.dll
Caused By Address : ativvaxx.dll+15090
File Description : Radeon Video Acceleration Universal Driver
Product Name : Advanced Micro Devices, Inc. Radeon Video Acceleration Universal Driver
Company : Advanced Micro Devices, Inc.
File Version : 6.14.10.0321
Processor : 32-bit
Crash Address : ativvaxx.dll+15090
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini090111-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
Dump File Size : 118,784
==================================================

#9 hamluis

hamluis

    Moderator


  • Moderator
  • 55,405 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:51 AM

Posted 31 August 2011 - 02:51 PM

http://msdn.microsoft.com/en-us/library/ff557203(v=vs.85).aspx

I'd say that Steps 2 and 3 might be in order.

Louis

#10 ShindouRyan

ShindouRyan
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:04:51 AM

Posted 31 August 2011 - 02:53 PM

hmm i guess i just have 2 reformat my computer... if there is still a problem then i guess its my graphic card error... anyway thanks for your help Louis.

#11 hamluis

hamluis

    Moderator


  • Moderator
  • 55,405 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:51 AM

Posted 31 August 2011 - 04:58 PM

Well...if you have a malware or a hardware problem...reformatting won't address/fix either.

I wasn't much help...but I try :).

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users