BSoD While Gaming

Your ATI Tools software is the cause, please remove it and stop any overlocking

giveio.sys (dated 1996) may be related to a software from giveio , ADC Analsyzer or Disspy, remove such software

Code:

giveio.sys        0x86433000    0x86433680    0x00000680    0x316334f5    04/04/1996 06:33:25

   Warning

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
You can use MagicDisc as an alternative

Code:

sptd.sys        0x85c93000    0x85d86000    0x000f3000    0x4ad245ea    12/10/2009 00:54:02

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck CD, {a4695000, 0, 8325f8b7, 0}

Probably caused by : ATITool.sys ( ATITool+2017 )


PAGE_FAULT_BEYOND_END_OF_ALLOCATION (cd)
N bytes of memory was allocated and more than N bytes are being referenced.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: a4695000, memory referenced
Arg2: 00000000, value 0 = read operation, 1 = write operation
Arg3: 8325f8b7, if non-zero, the address which referenced memory.
Arg4: 00000000, Mm internal code.

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 833ad718
Unable to read MiSystemVaType memory at 8338d160
 a4695000 

FAULTING_IP: 
nt!wcsrchr+a
8325f8b7 668b08          mov     cx,word ptr [eax]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xCD

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  80786928 -- (.trap 0xffffffff80786928)
ErrCode = 00000000
eax=a4695000 ebx=a35880a0 ecx=00007979 edx=a4694fe0 esi=9ec5aea0 edi=a35880c0
eip=8325f8b7 esp=8078699c ebp=8078699c iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
nt!wcsrchr+0xa:
8325f8b7 668b08          mov     cx,word ptr [eax]        ds:0023:a4695000=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8328b628 to 832ca9eb

STACK_TEXT:  
80786910 8328b628 00000000 a4695000 00000000 nt!MmAccessFault+0x106
80786910 8325f8b7 00000000 a4695000 00000000 nt!KiTrap0E+0xdc
8078699c a3582017 a4694fe0 0000005c 9ec75000 nt!wcsrchr+0xa
WARNING: Stack unwind information not available. Following frames may be wrong.
807869b8 833e873e 9ec5aea0 9ec75000 00000000 ATITool+0x2017
00000000 00000000 00000000 00000000 00000000 nt!IopLoadDriver+0x7ed


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ATITool+2017
a3582017 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  ATITool+2017

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ATITool

IMAGE_NAME:  ATITool.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  455479e3

FAILURE_BUCKET_ID:  0xCD_VRF_ATITool+2017

BUCKET_ID:  0xCD_VRF_ATITool+2017

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

Uninstalled all that you stated. The givio was from Speedfan. I tested it by going into the game, Heroes of Newerth. Ran fine, but right when I joined the lobby, another BSoD happened. It was irql_driver_less than something. I hit the reset button before it could create a dump file. What are the usual causes of that?

iarvee said:

Uninstalled all that you stated. The givio was from Speedfan. I tested it by going into the game, Heroes of Newerth. Ran fine, but right when I joined the lobby, another BSoD happened. It was irql_driver_less than something. I hit the reset button before it could create a dump file. What are the usual causes of that?

We need the dump files to be able to give you a cause, wait it to crash again and upload the latest dumps :)

Bump.

An Unknown module is causing your crash, probably malware. Run a scan of Malwarebytes and SFC /SCANNOW Command - System File Checker

Please install the latest Nvidia driver http://www.nvidia.com/object/win7-wi...ql-driver.html

Code:

Unknown_Module_00000000        0x00000000    0x00000000    0x00000000    0x00000000

Remove any Symantec products and Deamon Tools/Alcohol 120

Code:

sptd.sys        0x8b68a000    0x8b77d000    0x000f3000    0x4ad245ea    12/10/2009 00:54:02                
SYMDS.SYS        0x8b91e000    0x8b975000    0x00057000    0x4cb8950b    15/10/2010 21:53:15                
SYMEFA.SYS        0x8ba07000    0x8baab000    0x000a4000    0x4ce1ac63    16/11/2010 01:55:47

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 9a723f2f, 8da929d4, 8da925b0}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: 9a723f2f, The address that the exception occurred at
Arg3: 8da929d4, Exception Record Address
Arg4: 8da925b0, Context Record Address

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


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

FAULTING_IP: 
+19
9a723f2f 890e            mov     dword ptr [esi],ecx

EXCEPTION_RECORD:  8da929d4 -- (.exr 0xffffffff8da929d4)
ExceptionAddress: 9a723f2f
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000001
   Parameter[1]: 78c353a8
Attempt to write to address 78c353a8

CONTEXT:  8da925b0 -- (.cxr 0xffffffff8da925b0)
eax=86447e50 ebx=88100000 ecx=86519d78 edx=c6e234d8 esi=78c353a8 edi=86447e20
eip=9a723f2f esp=8da92a9c ebp=8da92aa0 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
9a723f2f 890e            mov     dword ptr [esi],ecx  ds:0023:78c353a8=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  00000001

EXCEPTION_PARAMETER2:  78c353a8

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 83378718
Unable to read MiSystemVaType memory at 83358160
 78c353a8 

FOLLOWUP_IP: 
+19
9a723f2f 890e            mov     dword ptr [esi],ecx

FAILED_INSTRUCTION_ADDRESS: 
+19
9a723f2f 890e            mov     dword ptr [esi],ecx

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 9a71cbf7 to 9a723f2f

STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
8da92aa0 9a71cbf7 86447e20 877358f4 88100000 0x9a723f2f
8da92ab8 9a71e9be 00000000 86447e20 00000001 0x9a71cbf7
8da92c34 83625ba9 8329b502 00000002 8da92c58 0x9a71e9be
8da92d18 9a736141 86466aa8 85b97008 8da92d3c hal!KfLowerIrql+0x61
8da92d50 8341e9df 880e6008 c6791ca6 00000000 0x9a736141
8da92d90 832d01d9 9a736406 880e6008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x7E_BAD_IP_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  0x7E_BAD_IP_ANALYSIS_INCONCLUSIVE

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

While MBAM is scanning, i have a few questions. If I'll uninstall Norton, then what antivirus should I use? also, if I were to buy a new motherboard, would it fix the BSoD?

iarvee said:

While MBAM is scanning, i have a few questions. If I'll uninstall Norton, then what antivirus should I use? also, if I were to buy a new motherboard, would it fix the BSoD?

Use MSE

Alright. I can't finish the scan of MBAM. I keep getting the BSoD after at least an hour of being idle. Here's the dumpfile.