1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Problem with my computer..

Discussion in 'Windows XP' started by Wissam, 2009/08/31.

  1. 2009/08/31
    Wissam

    Wissam Inactive Thread Starter

    Joined:
    2009/08/31
    Messages:
    5
    Likes Received:
    0
    hello,
    I bought my computer before like 4 years ago, and I upgraded the memory (it was 1 GB 4x256MB, now it's 4 GB 4x1GB) and I also installed a graphics card (ATI 512 MB) *my computer's current specs are all listed*.

    the problem is that my pc restarts sometimes and gives the: "The system has recovered from a serious error." message, it happens mostly while playing a high demanding game so first thing I checked if my graphics card driver is correctly installed and up-to-date, after that i used Everest software to see if the temperatures are high, I noticed that the CPU fan (mounted over a huge heat sinker) blows directly on the big graphics card so I fixed that by installing external fans and the temperatures really dropped, but the problem wasn't solved..

    my current temperatures now are : motherboard = 30°C , cpu = 27°C , GPU = 50°C , harddisks = 40°C , i think they are all normal.

    note : - it happened a couple of times too while playing a simple flash game online, restart with the same message.
    - i got all the data saved (.dmp file) about when it asks you to report the problem to microsoft.

    your replies are highly appreciated.. thanks.
     
  2. 2009/08/31
    Admin.

    Admin. Administrator Administrator Staff

    Joined:
    2001/12/30
    Messages:
    6,687
    Likes Received:
    107
    Follow these instructions to post a Dump Data Log.

    If you do not have a dump, ensure that your machine is configured to write out a dump by following the directions from microsoft

    Please note:
     

  3. to hide this advert.

  4. 2009/08/31
    Wissam

    Wissam Inactive Thread Starter

    Joined:
    2009/08/31
    Messages:
    5
    Likes Received:
    0
    debug log

    Opened log file 'c:debuglog.txt'

    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini083109-02.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: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp.080413-2111
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
    Debug session time: Mon Aug 31 22:50:07.785 2009 (GMT+2)
    System Uptime: 0 days 7:46:31.147
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............
    Loading User Symbols
    Loading unloaded module list
    ..................
    *** ERROR: Module load completed but symbols could not be loaded for ALCXSENS.SYS
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c000001d, b977c40f, a5a3dc7f, 0}

    Probably caused by : memory_corruption

    Followup: memory_corruption
    ---------

    1: kd> !analyze -v;r;kv;lmtn;.logclose;q
    *******************************************************************************
    * *
    * 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: b977c40f, The address that the exception occurred at
    Arg3: a5a3dc7f, Trap Frame
    Arg4: 00000000

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


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

    FAULTING_IP:
    ALCXSENS+2740f
    b977c40f 8e70d9 mov st(-2),word ptr [eax-27h]

    TRAP_FRAME: a5a3dc7f -- (.trap 0xffffffffa5a3dc7f)
    .trap 0xffffffffa5a3dc7f
    ErrCode = 00000000
    eax=00000068 ebx=00000005 ecx=00000003 edx=8a0ebea4 esi=8a0eb8ec edi=8a0ed8ac
    eip=b977c40f esp=a5a3dcf3 ebp=00000010 iopl=0 nv up ei ng nz na pe cy
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010287
    ALCXSENS+0x2740f:
    b977c40f 8e70d9 mov st(-2),word ptr [eax-27h] ds:0023:00000041=????
    .trap
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: CODE_CORRUPTION

    BUGCHECK_STR: 0x8E

    PROCESS_NAME: System

    UNALIGNED_STACK_POINTER: a5a3dcf3

    LAST_CONTROL_TRANSFER: from 0eb90000 to b977c40f

    FAILED_INSTRUCTION_ADDRESS:
    ALCXSENS+2740f
    b977c40f 8e70d9 mov st(-2),word ptr [eax-27h]

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a5a3dcef 0eb90000 0000018a 0ed23800 0eb8308a ALCXSENS+0x2740f
    a5a3dcf3 00000000 0ed23800 0eb8308a 2a00008a 0xeb90000


    STACK_COMMAND: kb

    CHKIMG_EXTENSION: !chkimg -lo 50 -db !ALCXSENS
    !chkimg -lo 50 -db !ALCXSENS
    8 errors : !ALCXSENS (b977c406-b977c437)
    b977c400 c1 d8 4c 24 10 de *84 *8e c1 d9 44 24 2c d8 4c 8e ..L$......D$,.L.

    b977c410 70 d9 44 24 30 d8 *df *e0 10 de e9 d8 44 24 30 d9 p.D$0.......D$0.

    b977c420 54 24 30 d8 42 fc *48 *d8 fc d9 c0 d8 47 f4 d9 57 T$0.B.H.....G..W

    b977c430 f4 d9 5c 8e 70 8b *50 *eb 89 44 8e 20 75 02 33 c9 ..\.p.P..D. u.3.


    MODULE_NAME: memory_corruption

    IMAGE_NAME: memory_corruption

    FOLLOWUP_NAME: memory_corruption

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MEMORY_CORRUPTOR: STRIDE

    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE

    BUCKET_ID: MEMORY_CORRUPTION_STRIDE

    Followup: memory_corruption
    ---------

    eax=00000068 ebx=00000005 ecx=00000003 edx=8a0ebea4 esi=8a0eb8ec edi=8a0ed8ac
    eip=b977c40f esp=a5a3dcf3 ebp=00000010 iopl=0 nv up ei ng nz na pe cy
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010287
    ALCXSENS+0x2740f:
    b977c40f 8e70d9 mov st(-2),word ptr [eax-27h] ds:0023:00000041=????
    ChildEBP RetAddr Args to Child
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a5a3dcef 0eb90000 0000018a 0ed23800 0eb8308a ALCXSENS+0x2740f
    a5a3dcf3 00000000 0ed23800 0eb8308a 2a00008a 0xeb90000
    start end module name
    804d7000 806ff000 nt ntkrnlmp.exe Sun Apr 13 21:24:23 2008 (48025DE7)
    806ff000 8071fd00 hal halmacpi.dll Sun Apr 13 20:31:27 2008 (4802517F)
    a4fea000 a5014180 kmixer kmixer.sys Sun Apr 13 20:45:07 2008 (480254B3)
    a551b000 a552e180 NAVENG NAVENG.SYS Sat Aug 22 07:31:12 2009 (4A8F82A0)
    a552f000 a5670800 NAVEX15 NAVEX15.SYS Sat Aug 22 07:37:19 2009 (4A8F840F)
    a5671000 a56ba000 SRTSP SRTSP.SYS Tue Jan 22 06:58:54 2008 (4795780E)
    a57aa000 a57ec000 SymIDSCo SymIDSCo.sys Mon Jan 12 23:33:44 2009 (496BB738)
    a583c000 a5851f00 SYMFW SYMFW.SYS Wed Feb 11 00:22:54 2009 (4991FE3E)
    a5a12000 a5a15d00 SYMREDRV SYMREDRV.SYS Wed Feb 11 00:23:05 2009 (4991FE49)
    a5a5a000 a5a9aa80 HTTP HTTP.sys Sun Apr 13 20:53:48 2008 (480256BC)
    a5df4000 a5e45c00 srv srv.sys Sun Apr 13 21:15:08 2008 (48025BBC)
    a60da000 a60ee480 wdmaud wdmaud.sys Sun Apr 13 21:17:18 2008 (48025C3E)
    a6193000 a6195e40 mdmxsdk mdmxsdk.sys Wed Mar 17 21:04:10 2004 (4058A12A)
    a61b7000 a61e3180 mrxdav mrxdav.sys Sun Apr 13 20:32:42 2008 (480251CA)
    a62a4000 a62b2d80 sysaudio sysaudio.sys Sun Apr 13 21:15:55 2008 (48025BEB)
    a6638000 a663b900 ndisuio ndisuio.sys Sun Apr 13 20:55:57 2008 (4802573D)
    a8984000 a899b900 dump_atapi dump_atapi.sys Sun Apr 13 20:40:29 2008 (4802539D)
    a899c000 a89b9000 EraserUtilRebootDrv EraserUtilRebootDrv.sys Tue Aug 18 01:05:39 2009 (4A89E243)
    a89b9000 a8a17000 eeCtrl eeCtrl.sys Tue Aug 18 01:05:39 2009 (4A89E243)
    a8a17000 a8a86780 mrxsmb mrxsmb.sys Sun Apr 13 21:16:58 2008 (48025C2A)
    a8a87000 a8ab1e80 rdbss rdbss.sys Sun Apr 13 21:28:38 2008 (48025EE6)
    a8ada000 a8ae1c80 SYMIDS SYMIDS.SYS Wed Feb 11 00:23:02 2009 (4991FE46)
    a8aea000 a8af1800 SYMNDIS SYMNDIS.SYS Wed Feb 11 00:22:42 2009 (4991FE32)
    a8b02000 a8b72000 SPBBCDrv SPBBCDrv.sys Fri Aug 29 00:10:06 2008 (48B7223E)
    a8b72000 a8b93d00 afd afd.sys Fri Jun 20 13:48:02 2008 (485B98F2)
    a8b94000 a8bbbc00 netbt netbt.sys Sun Apr 13 21:20:59 2008 (48025D1B)
    a8bbc000 a8be1000 SYMEVENT SYMEVENT.SYS Tue Aug 05 01:28:32 2008 (489790A0)
    a8be1000 a8c06500 ipnat ipnat.sys Sun Apr 13 20:57:10 2008 (48025786)
    a8c07000 a8c32680 SYMTDI SYMTDI.SYS Wed Feb 11 00:22:31 2009 (4991FE27)
    a8f60000 a8f62900 Dxapi Dxapi.sys Fri Aug 17 22:53:19 2001 (3B7D843F)
    a8f78000 a8fd0480 tcpip tcpip.sys Fri Jun 20 13:58:59 2008 (485B9B83)
    a8fd1000 a8fe3600 ipsec ipsec.sys Sun Apr 13 21:19:42 2008 (48025CCE)
    b9149000 b9149b80 Null Null.SYS Fri Aug 17 22:47:39 2001 (3B7D82EB)
    b9278000 b92d5f00 update update.sys Sun Apr 13 20:39:46 2008 (48025372)
    b92fe000 b932de80 rdpdr rdpdr.sys Sun Apr 13 20:32:50 2008 (480251D2)
    b932e000 b9332500 watchdog watchdog.sys Sun Apr 13 20:44:59 2008 (480254AB)
    b933e000 b9345780 CO_Mon CO_Mon.sys Wed Aug 08 23:39:53 2007 (46BA3829)
    b968d000 b969de00 psched psched.sys Sun Apr 13 20:56:36 2008 (48025764)
    b96be000 b96cd900 Cdfs Cdfs.SYS Sun Apr 13 21:14:21 2008 (48025B8D)
    b970e000 b9718e00 Fips Fips.SYS Sun Apr 13 20:33:27 2008 (480251F7)
    b973e000 b9754580 ndiswan ndiswan.sys Sun Apr 13 21:20:41 2008 (48025D09)
    b9755000 b97b7d00 ALCXSENS ALCXSENS.SYS Fri Aug 08 15:27:06 2003 (3F33A52A)
    b97b8000 b97dba80 portcls portcls.sys Sun Apr 13 21:19:40 2008 (48025CCC)
    b97dc000 b984ac80 ALCXWDM ALCXWDM.SYS Thu Aug 21 10:31:50 2003 (3F448376)
    b984b000 b985e900 parport parport.sys Sun Apr 13 20:40:09 2008 (48025389)
    b985f000 b9889d00 b57xp32 b57xp32.sys Thu May 22 03:47:11 2003 (3ECC2C1F)
    b988a000 b9931400 HSFCXTS2 HSFCXTS2.sys Fri Jun 18 00:55:36 2004 (40D22168)
    b9932000 b9a30480 HSFDPSP2 HSFDPSP2.sys Fri Jun 18 00:55:00 2004 (40D22144)
    b9a31000 b9a53700 ks ks.sys Sun Apr 13 21:16:34 2008 (48025C12)
    b9a54000 b9a89b80 HSFBS2S2 HSFBS2S2.sys Fri Jun 18 00:56:20 2004 (40D22194)
    b9a8a000 b9aad200 USBPORT USBPORT.SYS Sun Apr 13 20:45:34 2008 (480254CE)
    b9aae000 b9ac1f00 VIDEOPRT VIDEOPRT.SYS Sun Apr 13 20:44:39 2008 (48025497)
    b9ac2000 b9f2a000 ati2mtag ati2mtag.sys Mon May 12 17:54:20 2008 (4828682C)
    b9f64000 b9f66280 rasacd rasacd.sys Fri Aug 17 22:55:39 2001 (3B7D84CB)
    ba710000 ba71bd00 raspptp raspptp.sys Sun Apr 13 21:19:47 2008 (48025CD3)
    ba720000 ba72a200 raspppoe raspppoe.sys Sun Apr 13 20:57:31 2008 (4802579B)
    ba730000 ba73c880 rasl2tp rasl2tp.sys Sun Apr 13 21:19:43 2008 (48025CCF)
    ba740000 ba74eb00 drmk drmk.sys Sun Apr 13 20:45:12 2008 (480254B8)
    ba750000 ba75a480 imapi imapi.sys Sun Apr 13 20:40:57 2008 (480253B9)
    ba760000 ba76e100 redbook redbook.sys Sun Apr 13 20:40:27 2008 (4802539B)
    ba770000 ba77f600 cdrom cdrom.sys Sun Apr 13 20:40:45 2008 (480253AD)
    ba780000 ba78cd00 i8042prt i8042prt.sys Sun Apr 13 21:17:59 2008 (48025C67)
    ba790000 ba79fc00 serial serial.sys Sun Apr 13 21:15:44 2008 (48025BE0)
    ba7a0000 ba7a8e00 intelppm intelppm.sys Sun Apr 13 20:31:31 2008 (48025183)
    ba7d4000 ba7d7c80 mssmbios mssmbios.sys Sun Apr 13 20:36:45 2008 (480252BD)
    ba7f4000 ba7f6780 ndistapi ndistapi.sys Sun Apr 13 20:57:27 2008 (48025797)
    bf000000 bf011600 dxg dxg.sys Sun Apr 13 20:38:27 2008 (48025323)
    bf012000 bf060000 ati2dvag ati2dvag.dll Mon May 12 17:54:44 2008 (48286844)
    bf060000 bf0e6000 ati2cqag ati2cqag.dll Mon May 12 16:57:07 2008 (48285AC3)
    bf0e6000 bf146000 atikvmag atikvmag.dll Mon May 12 17:05:19 2008 (48285CAF)
    bf146000 bf185000 atiok3x2 atiok3x2.dll Mon May 12 17:02:31 2008 (48285C07)
    bf185000 bf493060 ati3duag ati3duag.dll Mon May 12 17:32:49 2008 (48286321)
    bf494000 bf67c300 ativvaxx ativvaxx.dll Mon May 12 17:22:54 2008 (482860CE)
    bf800000 bf9c2980 win32k win32k.sys Sun Apr 13 21:29:46 2008 (48025F2A)
    f7413000 f7429880 KSecDD KSecDD.sys Sun Apr 13 20:31:40 2008 (4802518C)
    f742a000 f743bf00 sr sr.sys Sun Apr 13 20:36:50 2008 (480252C2)
    f743c000 f745bb00 fltMgr fltMgr.sys Sun Apr 13 20:32:58 2008 (480251DA)
    f745c000 f7473880 SCSIPORT SCSIPORT.SYS Sun Apr 13 20:40:29 2008 (4802539D)
    f7474000 f748b900 atapi atapi.sys Sun Apr 13 20:40:29 2008 (4802539D)
    f748c000 f74b1700 dmio dmio.sys Sun Apr 13 20:44:45 2008 (4802549D)
    f74b2000 f74d0880 ftdisk ftdisk.sys Fri Aug 17 22:52:41 2001 (3B7D8419)
    f74d1000 f74da080 SRTSPX SRTSPX.SYS Tue Jan 22 07:00:19 2008 (47957863)
    f74e1000 f74e9780 netbios netbios.sys Sun Apr 13 20:56:01 2008 (48025741)
    f74f1000 f74f9700 wanarp wanarp.sys Sun Apr 13 20:57:20 2008 (48025790)
    f7501000 f750a000 HIDCLASS HIDCLASS.SYS Sun Apr 13 20:45:25 2008 (480254C5)
    f7571000 f7581a80 pci pci.sys Sun Apr 13 20:36:43 2008 (480252BB)
    f7582000 f75afd80 ACPI ACPI.sys Sun Apr 13 20:36:33 2008 (480252B1)
    f75b0000 f75d5e00 d347bus d347bus.sys Sun Aug 22 15:31:09 2004 (4128A01D)
    f75f7000 f7600180 isapnp isapnp.sys Sun Apr 13 20:36:40 2008 (480252B8)
    f7607000 f7611580 MountMgr MountMgr.sys Sun Apr 13 20:39:45 2008 (48025371)
    f7617000 f7623c80 VolSnap VolSnap.sys Sun Apr 13 20:41:00 2008 (480253BC)
    f7627000 f762fe00 disk disk.sys Sun Apr 13 20:40:46 2008 (480253AE)
    f7637000 f7643180 CLASSPNP CLASSPNP.SYS Sun Apr 13 21:16:21 2008 (48025C05)
    f7647000 f7651580 agp440 agp440.sys Sun Apr 13 20:36:37 2008 (480252B5)
    f7677000 f767f900 msgpc msgpc.sys Sun Apr 13 20:56:32 2008 (48025760)
    f7697000 f76a0f00 termdd termdd.sys Sun Apr 13 20:38:36 2008 (4802532C)
    f76a7000 f76b0e80 NDProxy NDProxy.SYS Sun Apr 13 20:57:28 2008 (48025798)
    f76d7000 f76e5880 usbhub usbhub.sys Sun Apr 13 20:45:36 2008 (480254D0)
    f7707000 f770d180 PCIIDEX PCIIDEX.SYS Sun Apr 13 20:40:29 2008 (4802539D)
    f770f000 f7713d00 PartMgr PartMgr.sys Sun Apr 13 20:40:48 2008 (480253B0)
    f775f000 f7765180 HIDPARSE HIDPARSE.SYS Sun Apr 13 20:45:22 2008 (480254C2)
    f77a7000 f77ac080 usbuhci usbuhci.sys Sun Apr 13 20:45:34 2008 (480254CE)
    f77af000 f77b6600 usbehci usbehci.sys Sun Apr 13 20:45:34 2008 (480254CE)
    f77b7000 f77be580 Modem Modem.SYS Sun Apr 13 21:00:18 2008 (48025842)
    f77bf000 f77c0000 fdc fdc.sys unavailable (00000000)
    f77c7000 f77cd000 kbdclass kbdclass.sys Sun Apr 13 20:39:46 2008 (48025372)
    f77cf000 f77d3a80 TDI TDI.SYS Sun Apr 13 21:00:04 2008 (48025834)
    f77d7000 f77db580 ptilink ptilink.sys Fri Aug 17 22:49:53 2001 (3B7D8371)
    f77df000 f77e3080 raspti raspti.sys Fri Aug 17 22:55:32 2001 (3B7D84C4)
    f77e7000 f77eca00 mouclass mouclass.sys Sun Apr 13 20:39:47 2008 (48025373)
    f77ef000 f77f5000 SymIM SymIM.sys Wed Feb 11 00:23:11 2009 (4991FE4F)
    f77f7000 f77fc000 flpydisk flpydisk.sys Sun Apr 13 20:40:24 2008 (48025398)
    f7807000 f780c200 vga vga.sys Sun Apr 13 20:44:40 2008 (48025498)
    f780f000 f7813a80 Msfs Msfs.SYS Sun Apr 13 20:32:38 2008 (480251C6)
    f7817000 f781e880 Npfs Npfs.SYS Sun Apr 13 20:32:38 2008 (480251C6)
    f7850000 f7869b80 Mup Mup.sys Sun Apr 13 21:17:05 2008 (48025C31)
    f786a000 f7896980 NDIS NDIS.sys Sun Apr 13 21:20:35 2008 (48025D03)
    f7897000 f789a000 BOOTVID BOOTVID.dll Fri Aug 17 22:49:09 2001 (3B7D8345)
    f7927000 f7929880 hidusb hidusb.sys Sun Apr 13 20:45:27 2008 (480254C7)
    f792b000 f792df80 mouhid mouhid.sys Fri Aug 17 22:47:57 2001 (3B7D82FD)
    f7947000 f794ad80 serenum serenum.sys Sun Apr 13 20:40:12 2008 (4802538C)
    f794b000 f794d700 GEARAspiWDM GEARAspiWDM.sys Tue Apr 08 21:15:38 2008 (47FBC45A)
    f7987000 f7988b80 kdcom kdcom.dll Fri Aug 17 22:49:10 2001 (3B7D8346)
    f7989000 f798a100 WMILIB WMILIB.SYS Fri Aug 17 23:07:23 2001 (3B7D878B)
    f798b000 f798c580 intelide intelide.sys Sun Apr 13 20:40:29 2008 (4802539D)
    f798d000 f798e700 dmload dmload.sys Fri Aug 17 22:58:15 2001 (3B7D8567)
    f798f000 f7990480 d347prt d347prt.sys Sun Aug 22 15:31:48 2004 (4128A044)
    f799d000 f799eb00 SYMDNS SYMDNS.SYS Wed Feb 11 00:22:34 2009 (4991FE2A)
    f79ab000 f79ac100 swenum swenum.sys Sun Apr 13 20:39:52 2008 (48025378)
    f79ad000 f79ae280 USBD USBD.SYS Fri Aug 17 23:02:58 2001 (3B7D8682)
    f79af000 f79b0f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 22:49:37 2001 (3B7D8361)
    f79b1000 f79b2080 Beep Beep.SYS Fri Aug 17 22:47:33 2001 (3B7D82E5)
    f79b3000 f79b4080 mnmdd mnmdd.SYS Fri Aug 17 22:57:28 2001 (3B7D8538)
    f79b5000 f79b6080 RDPCDD RDPCDD.sys Fri Aug 17 22:46:56 2001 (3B7D82C0)
    f79cf000 f79d0100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 23:07:23 2001 (3B7D878B)
    f79f1000 f79f2a80 ParVdm ParVdm.SYS Fri Aug 17 22:49:49 2001 (3B7D836D)
    f7a4f000 f7a4fd00 PCIIde PCIIde.sys Fri Aug 17 22:51:49 2001 (3B7D83E5)
    f7a8b000 f7a8bd00 dxgthk dxgthk.sys Fri Aug 17 22:53:12 2001 (3B7D8438)
    f7abb000 f7abbc00 audstub audstub.sys Fri Aug 17 22:59:40 2001 (3B7D85BC)
    f7b52000 f7bde600 Ntfs Ntfs.sys Sun Apr 13 21:15:49 2008 (48025BE5)

    Unloaded modules:
    b972e000 b9738000 kerneld.wnt
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a4fea000 a5015000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a51a5000 a51d0000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a6052000 a6054000 splitter.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f79d5000 f79d7000 splitter.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a51a5000 a51d0000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a51a5000 a51d0000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a51a5000 a51d0000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a51a5000 a51d0000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a5400000 a542b000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a6064000 a608f000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7a6a000 f7a6b000 drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a608f000 a60b2000 aec.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a6234000 a6241000 DMusic.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a6244000 a6252000 swmidi.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7991000 f7993000 splitter.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f77ff000 f7804000 Cdaudio.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b9f68000 b9f6b000 Sfloppy.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    Closing open log file c:debuglog.txt
     
  5. 2009/09/01
    Wissam

    Wissam Inactive Thread Starter

    Joined:
    2009/08/31
    Messages:
    5
    Likes Received:
    0
    maybe it has to do with my directX / graphics card ?

    hi again,
    the debuglog i posted above is one of the 4 .dmp files that i found, it was the most recent one, so last night i debugged the other 3 files and i compared the results with some online search, i found these tags in each one of them :

    1- Probably caused by : HSFBS2S2.sys ( HSFBS2S2!ControlHDW+92c )

    2- Probably caused by : HSFBS2S2.sys ( HSFBS2S2!ControlHDW+92c )

    3- Probably caused by : dxg.sys ( dxg!pDdLockSurfaceOrBuffer+4b2 )

    4- Probably caused by : memory_corruption (this is the one i posted here)

    i think it has to do with my DirectX/Graphics card ..
    my DirectX is : 4.09.00.0904 (DirectX 9.0c)

    and also, last week i ran 'dxdiag' from start->run , and the same problem happened, restart and showing a serious error message with .dmp file (this is the number 3 above)

    so could it be that my graphics card has a problem with this directX version ?

    i still got the whole debug logs saved, if you need any more details..
     
  6. 2009/09/01
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Start by testing your memory. Run Memtest86 or Windows Memory Diagnostic.

    Please note:

     
    Arie,
    #5
  7. 2009/09/01
    Wissam

    Wissam Inactive Thread Starter

    Joined:
    2009/08/31
    Messages:
    5
    Likes Received:
    0
    no errors with RAM

    I just finished testing the memory with Windows Memory Diagnostic, and it didnt show any errors.
     
  8. 2009/09/01
    Wissam

    Wissam Inactive Thread Starter

    Joined:
    2009/08/31
    Messages:
    5
    Likes Received:
    0
    I fully uninstalled the drivers for the graphics card and installed the newest ones from the official site of Ati , i also installed all the updates recommended from microsoft, then i tried if the same thing happens again, the game (warcraft III) was just perfect for more than 2 hours, then my system restarted again, i debugged the dump file and i found this on the beginning of it :

    *** ERROR: Symbol file could not be found. Defaulted to export symbols for ati3duag.dll -
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007E, {c0000005, c01ee8f0, a60f7a78, a60f7774}

    ***** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 : hardware

    Followup: MachineOwner
    ---------
    *** Possible invalid call from bf22caa2 ( ati3duag!pDdHslSharedMemCalloc+0x20282 )
    *** Expected target bf1ee8f0 ( ati3duag!bGDI3DQueryDesktopCompositionSupport+0x84b0 )

    0: kd> !analyze -v;r;kv;lmtn;.logclose;q
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************


    so this time it says : Probably caused by : hardware ..
    and i can see an ATI function involved when the error happened..

    i opened my Event Viewer to find any errors at the same time the restart happened, and i found this one :

    Event Type: Error
    Event Source: System Error
    Event Category: (102)
    Event ID: 1003
    Date: 9/2/2009
    Time: 3:53:47 AM
    User: N/A
    Computer: METALLICA
    Description:
    Error code 1000007e, parameter1 c0000005, parameter2 c01ee8f0, parameter3 a60f7a78, parameter4 a60f7774.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 53 79 73 74 65 6d 20 45 System E
    0008: 72 72 6f 72 20 20 45 72 rror Er
    0010: 72 6f 72 20 63 6f 64 65 ror code
    0018: 20 31 30 30 30 30 30 37 1000007
    0020: 65 20 20 50 61 72 61 6d e Param
    0028: 65 74 65 72 73 20 63 30 eters c0
    0030: 30 30 30 30 30 35 2c 20 000005,
    0038: 63 30 31 65 65 38 66 30 c01ee8f0
    0040: 2c 20 61 36 30 66 37 61 , a60f7a
    0048: 37 38 2c 20 61 36 30 66 78, a60f
    0050: 37 37 37 34 7774


    everytime i get a different cause on these dump files.. why ?
     
  9. 2009/09/02
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Arie,
    #8
  10. 2009/09/02
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    That (usually) indicates a hardware problem.

    Still suspect memory. Like I said, memory testing programs only show results with severely defective memory.

    Next test the installed RAM in various configurations. If you have a single module swap it around the slots. If you have a pair of modules run each one singly, swapping between slots; then run them in pairs swapping between pairs of slots. If you have 2 sets of matched modules do not get them mixed up.
     
    Arie,
    #9

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.