Blue Screen Of Death

#61
srry for late replay you wont belive but i was playing thanks you soo much for your hard work god bless you never met some one soo smart and nice at the same time =P i really wana thank you for all time u spent with me it was fun thx for everything u teached me stil didnt try the ati radeon 9800 playing on sis onboard you did it man your soo awsome respect !!!!!! :p:p:p:p:p:p

now back for ati radeon when i buy it some time ago it had fan now it brokes can it work whitout fan and not frie the gpu?
 


#62
lol you're welcome, glad to hear it.

No, you can't use the ATI card without a fan. You can attach any fan you have that can fit on it and just re-wire it like the old one. You can rig it anyhow it will stay. Use superglue if you have to lol....as long as the fan is spinning on top of the heat sink, it will be good.

Enjoy. :)
 


#63
what i doo about my sound card i dont have any sound now at all i renamed it aeaudio.bak and if in future i will need too format how i can make system stable?
 


#64
thanks for help again good night didnt sleep good for 4 days
 


#65
Rename it to aeaudio.sys and reboot. I don't think it was causing any issues.

GN and you're welcome.
 


#66
hi how are you today? after 4 hours whith no bsods and restarts i had bsod il upload latest dump
 


Attachments

#67
Mini111710-04 was caused by SiSGRV.dll 2006, which is SiS (R) Compatible Super VGA Dispaly Driver for Windows XP.
 


#68
thanks ffor your respond how i fix that bsod beacuse sisgrp.dll ? its the latest driver i could find
 


#69
thanks ffor your respond how i fix that bsod beacuse sisgrp.dll ? its the latest driver i could find
Uninstall this driver and let the system automtically install Microsoft Generic driver.
 


#70
That won't be good to do because then the video driver will not work at all...The generic display adapter driver will be loaded.

There is simply a fault in SiS drivers and you should do all you can to fix that ATI card and install it.
 


#71
Hey Torrent how are you sorry for lat respond was at friend house and forgot exit forum

btw i fixed all bsods its stable again it happened beacuse i connected keyboard maybe faulty that make it bsod yasterday when we make it stable it was diferent keyboard today i changed keyboared and bsod starts change back bsod gone hope they wont back
 


#72
Nah, it's only a coincidence. The keyboard can not cause the SiS chipset/video driver bsods.
 


#73
for now already 4 hours no bsod or restarts andi am not trying strong games on sis i know its weak i just playing onlline games that dont have strong requerment system
 


#74
[langtitle=iw]Re: Blue Screen Of Death[/langtitle]

[lang=iw]lol just for curious i conected the faulty keyboard after 3 min comp restarted i have 2 comps i post u on good comp wile tryed the keayboard on asus comp[/lang]
 


#75
Re: [langtitle=iw]Re: Blue Screen Of Death[/langtitle]

lol you was right i feell soo stupid now after 4 and half hours i think thats end of it but get bsod i am sorry happiness blinded me soo stupid dam
 


#76
now comp have bsod after long ime not as in the begining here the lates dump
 


Attachments

#77
Install all the SiS drivers. Honestly, nothing else we can do here at Windows7forums for these old antiquated SiS XP problems. If you update and still have bsod, all I can say is to either tolerate them or get a new pc that is capable of running Windows 7 and enjoy a bsod-free experience.

Or fix that ATI card you have and install it....continuously posting the same crash problems over over again is not going to help the situation, unfortunately.

The SiS chipset and video solution is not meant for any type of games at all - "PROCESS_NAME: speed.exe"

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


Loading Dump File [E:\Temp\Rar$DI00.250\Mini111710-09.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_qfe.100427-1650
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Wed Nov 17 11:08:10.218 2010 (UTC - 5:00)
System Uptime: 0 days 0:03:10.774
Loading Kernel Symbols
...............................................................
.......................................
Loading User Symbols
Loading unloaded module list
.................................................
Unable to load image SiSGRV.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SiSGRV.dll
*** ERROR: Module load completed but symbols could not be loaded for SiSGRV.dll
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf054c76, f04f8b3c, 0}

Probably caused by : SiSGRV.dll ( SiSGRV+42c76 )

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

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


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

FAULTING_IP: 
SiSGRV+42c76
bf054c76 8b848684000000  mov     eax,dword ptr [esi+eax*4+84h]

TRAP_FRAME:  f04f8b3c -- (.trap 0xfffffffff04f8b3c)
ErrCode = 00000000
eax=00000001 ebx=00000000 ecx=00000000 edx=000816b2 esi=e12c7010 edi=00060000
eip=bf054c76 esp=f04f8bb0 ebp=00000004 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
SiSGRV+0x42c76:
bf054c76 8b848684000000  mov     eax,dword ptr [esi+eax*4+84h] ds:0023:e12c7098=00000000
Resetting default scope

CUSTOMER_CRASH_COUNT:  9

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  speed.exe

LAST_CONTROL_TRANSFER:  from f7836622 to bf054c76

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
f04f8c1c f7836622 f04f8ce4 e11a2b00 00000000 SiSGRV+0x42c76
f04f8c68 bf000663 f04f8ce4 f04f8d64 0013fd54 watchdog!WdEnterMonitoredSection+0x10
f04f8d40 804de7ec 02400ef8 02400c87 001c76e0 dxg!DxD3dDrawPrimitives2+0x1b9
f04f8d40 7c90e514 02400ef8 02400c87 001c76e0 nt!KiFastCallEntry+0xf8
0013fd64 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND:  kb

FOLLOWUP_IP: 
SiSGRV+42c76
bf054c76 8b848684000000  mov     eax,dword ptr [esi+eax*4+84h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  SiSGRV+42c76

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SiSGRV

IMAGE_NAME:  SiSGRV.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  40a4a09d

FAILURE_BUCKET_ID:  0x8E_SiSGRV+42c76

BUCKET_ID:  0x8E_SiSGRV+42c76

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


Last edited:
#78
thanks for your respond and dont hink we waist all that time for nothing beacuse it was bsod after 3 or less min now after 4 hours soo is really great for me thanks you i wana upload u my video card ati tell me what i can doo on it the fan was like triangle
 


Attachments

Last edited:
#79
dam i sended u wrong bsod dump file i dont need thise game speed.exe i need weaker by alot games thats are online thise graphic card not ment too be played such games
 


#80
here the right bsod whith the right game elementclient its onnline game

here its system requerment

Operating SystemWindows® XP, Windows 2000, Windows Vista, or Windows 7


CPUIntel® Pentium® 4 1.5Ghz or AMD Athlon 1500+ or newer and faster CPU

RAM512MB or more of RAM (Vista and Windows 7 require 1GB or more, 2GB+ preferred)

Graphic Display3D video chipset with pixel and vertex shader model 1.3 supported. GeForce 4 Ti4200 64MB or ATI™ Radeon™ 8500 64MB or newer for Windows XP. For Windows Vista and 7, a GeForce FX 5200 128MB or ATI Radeon 9500 128MB or newer is needed




beafore i moved comp oher room i never had bsods and played that game soo much whithout bsod
 


Attachments

Last edited:
This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.