Welcome Guest ( Log In | Register )

123 Pages « < 40 41 42 43 44 > » Bottom

Outline · [ Standard ] · Linear+

 [FAQ] PC auto restart/Blue Screen (BSOD), All questions go here please.

views
     
francischuahcw
post Sep 15 2008, 02:32 AM

Retired. Do Not Disturb
*******
Senior Member
2,152 posts

Joined: Feb 2006
wat OS you are using?
BaeM
post Sep 15 2008, 02:33 AM

New Member
*
Junior Member
42 posts

Joined: Aug 2008
From: Shah Alam



QUOTE(francischuahcw @ Sep 15 2008, 02:32 AM)
wat OS you are using?
*
using xp home edition sp2
francischuahcw
post Sep 15 2008, 02:36 AM

Retired. Do Not Disturb
*******
Senior Member
2,152 posts

Joined: Feb 2006
did your system experience BSOD while you using your pc?
if never experience sure wont get it.

by the way..
the correct path is

QUOTE
%systemroot%\minidump


%systemroot%\windows\minidump
BaeM
post Sep 15 2008, 03:00 AM

New Member
*
Junior Member
42 posts

Joined: Aug 2008
From: Shah Alam



...

This post has been edited by BaeM: Sep 19 2008, 05:33 AM
francischuahcw
post Sep 15 2008, 11:11 AM

Retired. Do Not Disturb
*******
Senior Member
2,152 posts

Joined: Feb 2006
did you activate your system minidump
if not...
try the below

QUOTE(tthm @ Sep 14 2008, 12:40 AM)
Open System Properties, select Advanced system settings tab and then Startup and Recovery Settings. Under Write debugging information make sure Small memory dump (64KB) is selected. You can see the default Small dump directory: path as %SystemRoot%\Minidump. Restart your computer as instructed and continue using your computer like normal.
This post has been edited by francischuahcw: Sep 15 2008, 11:12 AM
XaVieRGizmo
post Sep 15 2008, 08:34 PM

Getting Started
**
Junior Member
96 posts

Joined: Oct 2005
hi BSOD guru's & Radeon's 4800 series users!



If you have this BSOD error, have a read =)

QUOTE
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8004dd14e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffffa6004633390, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.

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


FAULTING_IP:
+fffffa6004633390
fffffa60`04633390 ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

Any Gainward 4870 Users having this issue Yet?

vista 64
phenom quadcore
4gb 800mhz
Gainward 4870
Latest drivers

The thing is, im aware that this error is produced by nvidia drivers, but im on ATI, never heard of ATI having this issue

Im now downloading the hotfix for ATI 4800 series on this stupid un-responsive nvlddmkm.sys, the thing is, nvlddmkm is not located anywhere within the thread stack, so WTF?!

Hotfix here
http://www.techspot.com/drivers/driver/fil...ormation/10364/

Any new 4800 series users experiencing this and have fixed it? If you have, please state how'd you fix it, as im doubting this 'hotfix' will fix it.

I'll let you know if this fixes it.

This post has been edited by XaVieRGizmo: Sep 15 2008, 08:54 PM
ezu_din
post Sep 15 2008, 09:55 PM

Getting Started
**
Junior Member
111 posts

Joined: May 2007


plz do check my minidump files..


Attached File(s)
Attached File  minidumps_2_.zip ( 18.07k ) Number of downloads: 13
francischuahcw
post Sep 15 2008, 10:45 PM

Retired. Do Not Disturb
*******
Senior Member
2,152 posts

Joined: Feb 2006
QUOTE(ezu_din @ Sep 15 2008, 09:55 PM)
plz do check my minidump files..
*
QUOTE
FAULTING_IP:
+0
00000000 ??              ???

EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 00000000
  ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 0

FAULTING_THREAD:  00000000

BUGCHECK_STR:  HANG

DEFAULT_BUCKET_ID:  APPLICATION_HANG

PROCESS_NAME:  firefox.exe

ERROR_CODE: (NTSTATUS) 0xcfffffff - <Unable to get error code text>

DERIVED_WAIT_CHAIN: 

Dl Eid Cid    WaitType
-- --- ------- --------------------------
  0  fb8.fbc Handle               

WAIT_CHAIN_COMMAND:  ~0s;k;;

BLOCKING_THREAD:  00000fbc

PRIMARY_PROBLEM_CLASS:  APPLICATION_HANG

LAST_CONTROL_TRANSFER:  from 779a06a0 to 779a0f34

STACK_TEXT: 
002ee66c 779a06a0 774377d4 000000b4 00000000 ntdll!KiFastSystemCallRet
002ee670 774377d4 000000b4 00000000 00000000 ntdll!NtWaitForSingleObject+0xc
002ee6e0 77437742 000000b4 ffffffff 00000000 kernel32!WaitForSingleObjectEx+0xbe
002ee6f4 6d2931d2 000000b4 ffffffff 000502c4 kernel32!WaitForSingleObject+0x12
WARNING: Stack unwind information not available. Following frames may be wrong.
002eea38 6e0ca4b4 6cf71da1 02c68a84 002eea6c xul+0x3331d2
002eea50 6cf6f8c2 002eea6c b88ba87f 00000046 mozcrt19+0x3a4b4
002eeac8 6d038d12 002eee14 b88ba86f 02c68a80 xul+0xf8c2
002eec88 6cfa65e3 00000046 00000000 002eee10 xul+0xd8d12
002eee30 775a8c32 6d1a707c 000402b0 00000004 xul+0x465e3
002eee34 6d1a707c 000402b0 00000004 002eee6c user32!NtUserDestroyWindow+0xc
002eeef4 77413549 002eef94 775f76b4 cffe72e3 xul+0x24707c
002eef9c 775b1a10 000402b0 00000016 00000001 kernel32!InternalFindAtom+0x141
002eefc8 775b1ae8 6d59fb6c 000402b0 00000016 user32!InternalCallWinProc+0x23
002ef040 775b1c03 00000000 6d59fb6c 000402b0 user32!UserCallWinProcCheckWow+0x14b
002ef09c 775b3656 00c2d198 00000016 00000001 user32!DispatchClientMessage+0xda
002ef0c4 779a0e6e 002ef0dc 00000018 002ef1cc user32!__fnDWORD+0x24
002ef0f0 775b2335 775b18f3 00040350 0000003b ntdll!KiUserCallbackDispatcher+0x2e
002ef0f4 775b18f3 00040350 0000003b 0000010c user32!NtUserMessageCall+0xc
002ef178 775b1d87 00040350 0000003b 0000010c user32!RealDefWindowProcWorker+0x6f
002ef194 775b1de4 00040350 0000003b 0000010c user32!RealDefWindowProcW+0x47
002ef1dc 775b1a10 00040350 0000003b 0000010c user32!DefWindowProcW+0x6f
002ef208 775b1ae8 6d12700a 00040350 0000003b user32!InternalCallWinProc+0x23
002ef280 775b2d6e 00000000 6d12700a 00040350 user32!UserCallWinProcCheckWow+0x14b
002ef2b0 775b2d14 6d12700a 00040350 0000003b user32!CallWindowProcAorW+0x97
002ef2d0 6cfa65fd 6d12700a 00040350 0000003b user32!CallWindowProcW+0x1b
00000000 00000000 00000000 00000000 00000000 xul+0x465fd


FOLLOWUP_IP:
xul+3331d2
6d2931d2 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  xul+3331d2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: xul

IMAGE_NAME:  xul.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  486bacbc

STACK_COMMAND:  ~0s ; kb

BUCKET_ID:  HANG_xul+3331d2

FAILURE_BUCKET_ID: xul.dll!Unknown_cfffffff_APPLICATION_HANG

Followup: MachineOwner
---------
the error that cause you to have BSOD is being pointed to your application
xul.dll refer to Mozilla Firefox dll file.
uninstall and reinstallation seems not able to solve the problem.

you can refer article from below link to overcome your problem
http://support.mozilla.com/tiki-view_forum...72837&forumId=1

This post has been edited by francischuahcw: Sep 15 2008, 10:45 PM
ask8900
post Sep 16 2008, 10:20 PM

Casual
***
Junior Member
340 posts

Joined: Sep 2007
From: malacca


i need help my pc Auto restat no stop cry.gif
all si fu si jie i Help me thx Q notworthy.gif

stop 0x000000c2 (0x0000007,0x00000CD4,0x02060002,0x89265718)
francischuahcw
post Sep 17 2008, 12:06 AM

Retired. Do Not Disturb
*******
Senior Member
2,152 posts

Joined: Feb 2006
QUOTE(ask8900 @ Sep 16 2008, 10:20 PM)
i need help my pc Auto restat no stop  cry.gif
all si fu si jie i Help me thx Q  notworthy.gif

stop 0x000000c2 (0x0000007,0x00000CD4,0x02060002,0x89265718)
*
Hi there,
can you get into safe mode?
please upload your minidump file here
C:\windows\minidump.

from the above information i suspect is about BAD_POOL_CALLER.
did you see any other additional information there?
if yes please post it here so that easier to help you identify
Thanks
ivanchin99
post Sep 17 2008, 05:49 PM

Enthusiast
*****
Senior Member
813 posts

Joined: Oct 2004
From: Miri


GG, bsod again rclxms.gif

» Click to show Spoiler - click again to hide... «


while playing bioshock and didnt save for 2 hrs doh.gif

Attached File  Mini091708_01.zip ( 18.25k ) Number of downloads: 15



Added on September 17, 2008, 7:09 pmbah.. one stick of my ram failed memtest86+ test #4 =.="

This post has been edited by ivanchin99: Sep 17 2008, 07:09 PM
francischuahcw
post Sep 17 2008, 07:21 PM

Retired. Do Not Disturb
*******
Senior Member
2,152 posts

Joined: Feb 2006
QUOTE

Probably caused by : dxg.sys ( dxg!bDdSecureSystemMemorySurface+51 )

Followup: MachineOwner
---------
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.

Could not read faulting driver name

READ_ADDRESS:  ef75bcfc

FAULTING_IP:
nt!MiLocateAndReserveWsle+51
80505f07 8b0c81          mov     ecx,dword ptr [ecx+eax*4]

MM_INTERNAL_CODE:  2
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  Bioshock.exe

TRAP_FRAME:  a96d2ba8 -- (.trap 0xffffffffa96d2ba8)
ErrCode = 00000000
eax=2cf31000 ebx=00080000 ecx=00001000 edx=fffff000 esi=2cece000 edi=2cf31000
eip=80615a83 esp=a96d2c1c ebp=a96d2c24 iopl=0         nv up ei ng nz na pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010287
nt!ProbeForWrite+0x39:
80615a83 8a06            mov     al,byte ptr [esi]          ds:0023:2cece000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from 80520971 to 80505f07

STACK_TEXT: 
a96d2b38 80520971 c0883cfc 2cece000 2cece000 nt!MiLocateAndReserveWsle+0x51
a96d2b90 80544578 81c53784 2cece000 80000000 nt!MmAccessFault+0xfaf
a96d2b90 80615a83 81c53784 2cece000 80000000 nt!KiTrap0E+0xd0
a96d2c24 bf004e51 2ceb0040 00080000 00000004 nt!ProbeForWrite+0x39
a96d2c5c bf00b771 e68fb9d8 a96d2d64 0052f52c dxg!bDdSecureSystemMemorySurface+0x51
a96d2d44 8054161c 0d200003 00000000 2796df78 dxg!DxDdCreateSurfaceObject+0xbd
a96d2d44 7c90e4f4 0d200003 00000000 2796df78 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0052f54c 00000000 00000000 00000000 00000000 0x7c90e4f4

STACK_COMMAND:  kb
FOLLOWUP_IP:
dxg!bDdSecureSystemMemorySurface+51
bf004e51 834dfcff        or      dword ptr [ebp-4],0FFFFFFFFh
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  dxg!bDdSecureSystemMemorySurface+51
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: dxg
IMAGE_NAME:  dxg.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  48025323
FAILURE_BUCKET_ID:  0x50_dxg!bDdSecureSystemMemorySurface+51
BUCKET_ID:  0x50_dxg!bDdSecureSystemMemorySurface+51

Followup: MachineOwner
---------
Hi there, the error occurs on your Dxg.sys which refers to your DirectX Graphic Driver
Please make sure that your DirectX driver is not corrupted. you can try install the latest version for it.
Another factor that can cause to this faulty is the overheat issue.
Based on the condition that you experience this BSOD is most probably because of overheat issue but please do check your dx driver.
Thanks

This post has been edited by francischuahcw: Sep 17 2008, 07:25 PM
tthm
post Sep 17 2008, 07:56 PM

Death of Blue Screen
Group Icon
VIP
1,342 posts

Joined: Jun 2005


QUOTE(ivanchin99 @ Sep 17 2008, 05:49 PM)
GG, bsod again rclxms.gif

» Click to show Spoiler - click again to hide... «


while playing bioshock and didnt save for 2 hrs  doh.gif

Attached File  Mini091708_01.zip ( 18.25k ) Number of downloads: 15



Added on September 17, 2008, 7:09 pmbah.. one stick of my ram failed memtest86+ test #4 =.="
*
Try using just 1 piece of ram one at a time and run memory test to confirm memory failure (starting with the failed ram stick). Need you to confirm if the same error appear again or not. Otherwise suspecting unstable motherboard or overheating component (motherboard or ram chip).
ivanchin99
post Sep 17 2008, 10:54 PM

Enthusiast
*****
Senior Member
813 posts

Joined: Oct 2004
From: Miri


I'm using one stick of the ram now.. Another kept failing test 4 in memtest+ sad.gif

But i just loaded Bioshock and wanted to replay again and got this =.= vmad.gif

» Click to show Spoiler - click again to hide... «


Attached File  Mini091708_03.zip ( 16.77k ) Number of downloads: 10



Added on September 17, 2008, 10:57 pm
QUOTE(francischuahcw @ Sep 17 2008, 07:21 PM)
Hi there, the error occurs on your Dxg.sys which refers to your DirectX Graphic Driver
Please make sure that your DirectX driver is not corrupted. you can try install the latest version for it.
Another factor that can cause to this faulty is the overheat issue.
Based on the condition that you experience this BSOD is most probably because of overheat issue but please do check your dx driver.
Thanks
*
hmm, i didnt make any changes to the directx driver just before the i got the bsod =/ Infact, the last installation was F.E.A.R and then i went on to play for quite a few hours without any problem..


-----------------------------

This minidump was the 2nd one but before the one above
» Click to show Spoiler - click again to hide... «

Attached File  Mini091708_03.zip ( 16.77k ) Number of downloads: 10



funny how when it bsod, they all come in quick succession

This post has been edited by ivanchin99: Sep 17 2008, 11:14 PM
francischuahcw
post Sep 17 2008, 11:52 PM

Retired. Do Not Disturb
*******
Senior Member
2,152 posts

Joined: Feb 2006
Your ati system files seems to be corrupted too. quite a number of corruption that you encounter.

I think your motherboard generally is very unstable already so that the file cannot be run properly.
you have take out the faulty ram and leave with a healthy ram to run the system?

i might suspect your Hdd is unstable too. did you run CHKDSK for disc scan?
ivanchin99
post Sep 18 2008, 12:46 AM

Enthusiast
*****
Senior Member
813 posts

Joined: Oct 2004
From: Miri


Update: so i switch the ram slot from 1/2 to 2/3 and now i dont get any errors anymore rclxms.gif
weird how 1 broken ram slot can give so many different symptoms

thanks for all the help and hope i dont need to visit this thread ever again whistling.gif

I guess because ram handles everything on the pc, hence a erroneous ram slot can give so many weird symptoms tongue.gif

This post has been edited by ivanchin99: Sep 18 2008, 12:47 AM
tthm
post Sep 18 2008, 09:32 PM

Death of Blue Screen
Group Icon
VIP
1,342 posts

Joined: Jun 2005


QUOTE(ivanchin99 @ Sep 18 2008, 12:46 AM)
Update: so i switch the ram slot from 1/2 to 2/3 and now i dont get any errors anymore  rclxms.gif
weird how 1 broken ram slot can give so many different symptoms

thanks for all the help and hope i dont need to visit this thread ever again  whistling.gif

I guess because ram handles everything on the pc, hence a erroneous ram slot can give so many weird symptoms tongue.gif
*
Good to hear that.

No more warranty left for your motherboard? Some motherboard like Intel comes with 3 years warranty.
davidwee1987
post Sep 19 2008, 07:28 PM

Getting Started
**
Junior Member
69 posts

Joined: May 2006
Hihi.. Pls help me.. I'm having constant BSOD.. i really dont know what to do.. i tried switching ram and graphic card but i have still no idea what is causing the BSOD.
my sysm configuration is intel q9450, 2Gb ddr3, msi x48c, 9800GX2.,850 watt. windows vista
i have uploaded the minidump.
thx a lot for those willing to help..


Attached File(s)
Attached File  Mini091608_01.zip ( 23.6k ) Number of downloads: 11
Attached File  Mini091908_01.zip ( 23.28k ) Number of downloads: 9
francischuahcw
post Sep 19 2008, 07:34 PM

Retired. Do Not Disturb
*******
Senior Member
2,152 posts

Joined: Feb 2006
Hi there,
Your concern noted.
I have download your file and debug is on the way.
Will upload and let you know the result once available.
Kindly be patient.


Added on September 19, 2008, 8:14 pm
QUOTE
Debugging Details:
------------------

GetPointerFromAddress: unable to read from 8256a6d8
Unable to read MiSystemVaType memory at 8254b2e0



POOL_ADDRESS: GetPointerFromAddress: unable to read from 8256a6d8
Unable to read MiSystemVaType memory at 8254b2e0
861e7a10

BUGCHECK_STR:  0xc2_7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  BitComet.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82522c2c to 824f96d9

STACK_TEXT: 
9751a29c 82522c2c 000000c2 00000007 0000110b nt!KeBugCheckEx+0x1e
9751a310 88483370 861e7a10 00000000 00000000 nt!ExFreePoolWithTag+0x17f
9751a320 8f9cee9e 861e7a10 00000000 00000000 ndis!NdisFreeMemory+0x16
WARNING: Stack unwind information not available. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 klim6+0x1e9e


STACK_COMMAND:  kb

FOLLOWUP_IP:
klim6+1e9e
8f9cee9e ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  klim6+1e9e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: klim6

IMAGE_NAME:  klim6.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4874caf9

FAILURE_BUCKET_ID:  0xc2_7_klim6+1e9e

BUCKET_ID:  0xc2_7_klim6+1e9e

Followup: MachineOwner
---------
Hi there,
the result above shows the main reason that causes you to experience BSOD is the system file klim6.sys which refers to Kaspersky Lab Intermediate Network Driver.
the location for it is \SystemRoot\system32\DRIVERS\klim6.sys

some reference at the link below
http://www.runscanner.net/filelibrary/klim6.sys.html
http://forums.techguy.org/windows-vista/70...eath-blues.html

therefore suggestion is to remove your Kaspersky antivirus 6.0 which is not compatible with your Vista Window. You can get Kaspersky 2009 as available in the Garage Sales section which are compatible to Vista.

Thanks

This post has been edited by francischuahcw: Sep 19 2008, 08:14 PM
davidwee1987
post Sep 19 2008, 08:25 PM

Getting Started
**
Junior Member
69 posts

Joined: May 2006
i am using kaspersky 2009. bought from garage sale.
any other possility ?
should i remove it and try other antivirus ?

123 Pages « < 40 41 42 43 44 > » Top
 

Change to:
| Lo-Fi Version
0.0230sec    0.29    6 queries    GZIP Disabled
Time is now: 8th December 2025 - 09:03 AM