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.

PC keeps restarting at various times

Discussion in 'Windows XP' started by pushprajpradhan, 2008/09/05.

  1. 2008/09/05
    pushprajpradhan

    pushprajpradhan Inactive Thread Starter

    Joined:
    2008/09/05
    Messages:
    4
    Likes Received:
    0
    hi folks, my PC restarts unexpectedly.well sometimes it keeps running flawlessly, but sometimes it keeps restarting at various times. like for example, if i play/listen to music/do any other work it keeps working normally, but say if i start to download from the internet and start browsing the internet it will restart at any point but that doesn't happen every time, sometimes it runs flawlessly even doing the browsing and downloading. i am really frustrated about this, since my download plan is night unlimited and i have to leave my PC on entire night for upgrades/downloads it restarts itself so the upgrade/download is interrupted. please help me.
    here's my system specs:
    CPU Type-Quad Core Intel Core 2 Quad Q6600, 2400 MHz
    Motherboard Name-Intel Pearl Creek DG31PR
    Motherboard Chipset-Intel Bearlake G31
    System Memory -3059 MB (DDR2-800 DDR2 SDRAM) -it's actually 2*2GB
    Operating System-Microsoft Windows XP Professional SP2
    Video Adapter-ATI Radeon HD 2400 PRO (512 MB)
    Disk Drive-WD 250 GB Sata
    well here is the debug log:
    Code:
    please see new log in my next reply, cannot add here due to character limit (35000)
    please help me guys, i am getting very much frustrated:confused: by this random BSOD(and restart) problem.
    Thanks for taking your time and reading my problem :D
     
    Last edited: 2008/09/06
  2. 2008/09/06
    Steve R Jones

    Steve R Jones SuperGeek Staff

    Joined:
    2001/12/30
    Messages:
    12,317
    Likes Received:
    252
    Is your pc randomly rebooting itself? You can go to

    Control Panel->System icon->Advance tab->Startup & Recovery Settings button. UNcheck/disable the "auto reboot" option. Instead of rebooting you'll probably get a Blue Screen of Death (BSOD) which can be searched on for a solution.

    You can go to http://support.microsoft.com/search/?adv=1 to search on for example: STOP 0x00000050
     

  3. to hide this advert.

  4. 2008/09/06
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    That's quite an old one. Better find a more recent one.

    Also, you seem to have a symbol problem - please make sure you have the correct symbols installed. More info here: http://www.windowsbbs.com/showthread.php?t=33471

    You have to remain connected to the Internet while running the wizard.
     
    Arie,
    #3
  5. 2008/09/06
    pushprajpradhan

    pushprajpradhan Inactive Thread Starter

    Joined:
    2008/09/05
    Messages:
    4
    Likes Received:
    0
    here's new log:Opened log file 'c:\debuglog.txt'
    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\WINDOWS\Minidump\Mini090608-05.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
    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 2) MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0
    Debug session time: Sat Sep 6 08:53:42.281 2008 (GMT+5)
    System Uptime: 0 days 0:37:16.210
    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
    ..............
    *** ERROR: Module load completed but symbols could not be loaded for Sacm2A.sys
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000D1, {6, 2, 0, f7a0e504}

    ***** 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 : Sacm2A.sys ( Sacm2A+cd8 )

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

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 00000006, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: f7a0e504, address which referenced memory

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

    MODULE_NAME: Sacm2A

    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 40c8573c

    READ_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    00000006

    CURRENT_IRQL: 2

    FAULTING_IP:
    NDIS!NdisQueryBuffer+11
    f7a0e504 f6460605 test byte ptr [esi+6],5

    CUSTOMER_CRASH_COUNT: 5

    DEFAULT_BUCKET_ID: WRONG_SYMBOLS

    BUGCHECK_STR: 0xD1

    LAST_CONTROL_TRANSFER: from ad422cd8 to f7a0e504

    STACK_TEXT:
    f78ae958 ad422cd8 00000000 f78ae978 f78ae998 NDIS!NdisQueryBuffer+0x11
    f78ae97c ad422c46 8a0106c8 89ee7310 00000036 Sacm2A+0xcd8
    f78ae9bc ad422b2d 00000003 89ee72f0 00000103 Sacm2A+0xc46
    f78ae9d4 f7a0df86 8a0106c8 f78aea08 00000000 Sacm2A+0xb2d
    f78ae9fc b9a7b528 8aa2e008 89ee7310 89ee72d8 NDIS!ndisMSendX+0x1bd
    f78aea38 f7a0b985 8ab283f8 89ee7310 00000002 psched!MpSend+0x706
    f78aea60 ad362d00 8aa2a2d0 89ee7310 8aa29008 NDIS!ndisMSendX+0x1d6
    f78aea88 ad3628ce 8aa29008 89ee7310 89e5c2c8 tcpip!ARPSendData+0x198
    f78aeab4 ad36270a 8aa29008 f78aea02 00000001 tcpip!ARPTransmit+0x193
    f78aeae4 ad3624ad 8aa2b1d8 0100f33c 89ee7310 tcpip!SendIPPacket+0x18e
    f78aec30 ad363546 ad3a04b8 00000000 8a0564f0 tcpip!IPTransmit+0x2859
    f78aec7c ad379850 02bd25b0 80562f00 00000000 tcpip!SendACK+0x2d8
    f78aec9c ad379a87 00000002 00000002 00000000 tcpip!ProcessPerCpuTCBDelayQ+0xc6
    f78aed18 ad35f3ec ad3a7938 00000000 f7717980 tcpip!TCBTimeout+0xba7
    f78aed28 804dd26b ad3a7948 ad3a7938 f65e9d54 tcpip!TCBTimeoutdpc+0xf
    WARNING: Stack unwind information not available. Following frames may be wrong.
    f78aed3c 80562f00 f7719e20 f7717c50 00000000 nt+0x626b
    f78aed40 f7719e20 f7717c50 00000000 f7719e20 nt+0x8bf00
    f78aed44 f7717c50 00000000 f7719e20 804dd14b 0xf7719e20
    f78aed48 00000000 f7719e20 804dd14b 00000000 0xf7717c50


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    Sacm2A+cd8
    ad422cd8 8b451c mov eax,dword ptr [ebp+1Ch]

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: Sacm2A+cd8

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: Sacm2A.sys

    BUCKET_ID: WRONG_SYMBOLS

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

    eax=00000000 ebx=f78ae9a8 ecx=f78ae978 edx=00000530 esi=00000000 edi=f78ae978
    eip=f7a0e504 esp=f78ae950 ebp=f78ae958 iopl=0 nv up ei ng nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
    NDIS!NdisQueryBuffer+0x11:
    f7a0e504 f6460605 test byte ptr [esi+6],5 ds:0023:00000006=??
    ChildEBP RetAddr Args to Child
    f78ae958 ad422cd8 00000000 f78ae978 f78ae998 NDIS!NdisQueryBuffer+0x11 (FPO: [Non-Fpo])
    f78ae97c ad422c46 8a0106c8 89ee7310 00000036 Sacm2A+0xcd8 (FPO: [Non-Fpo])
    f78ae9bc ad422b2d 00000003 89ee72f0 00000103 Sacm2A+0xc46 (FPO: [Non-Fpo])
    f78ae9d4 f7a0df86 8a0106c8 f78aea08 00000000 Sacm2A+0xb2d (FPO: [Uses EBP] [3,0,4])
    f78ae9fc b9a7b528 8aa2e008 89ee7310 89ee72d8 NDIS!ndisMSendX+0x1bd (FPO: [Non-Fpo])
    f78aea38 f7a0b985 8ab283f8 89ee7310 00000002 psched!MpSend+0x706 (FPO: [Non-Fpo])
    f78aea60 ad362d00 8aa2a2d0 89ee7310 8aa29008 NDIS!ndisMSendX+0x1d6 (FPO: [Non-Fpo])
    f78aea88 ad3628ce 8aa29008 89ee7310 89e5c2c8 tcpip!ARPSendData+0x198 (FPO: [Non-Fpo])
    f78aeab4 ad36270a 8aa29008 f78aea02 00000001 tcpip!ARPTransmit+0x193 (FPO: [Non-Fpo])
    f78aeae4 ad3624ad 8aa2b1d8 0100f33c 89ee7310 tcpip!SendIPPacket+0x18e (FPO: [Non-Fpo])
    f78aec30 ad363546 ad3a04b8 00000000 8a0564f0 tcpip!IPTransmit+0x2859 (FPO: [Non-Fpo])
    f78aec7c ad379850 02bd25b0 80562f00 00000000 tcpip!SendACK+0x2d8 (FPO: [Non-Fpo])
    f78aec9c ad379a87 00000002 00000002 00000000 tcpip!ProcessPerCpuTCBDelayQ+0xc6 (FPO: [Non-Fpo])
    f78aed18 ad35f3ec ad3a7938 00000000 f7717980 tcpip!TCBTimeout+0xba7 (FPO: [Non-Fpo])
    f78aed28 804dd26b ad3a7948 ad3a7938 f65e9d54 tcpip!TCBTimeoutdpc+0xf (FPO: [Non-Fpo])
    WARNING: Stack unwind information not available. Following frames may be wrong.
    f78aed3c 80562f00 f7719e20 f7717c50 00000000 nt+0x626b
    f78aed40 f7719e20 f7717c50 00000000 f7719e20 nt+0x8bf00
    f78aed44 f7717c50 00000000 f7719e20 804dd14b 0xf7719e20
    f78aed48 00000000 f7719e20 804dd14b 00000000 0xf7717c50
    start end module name
    804d7000 80723000 nt ntoskrnl.exe Wed Aug 04 11:48:18 2004 (41107FAA)
    80723000 80743d00 hal halmacpi.dll Wed Aug 04 11:29:09 2004 (41107B2D)
    aa160000 aa1a0280 HTTP HTTP.sys Fri Mar 17 06:03:09 2006 (441A03C5)
    aa4e9000 aa53b180 srv srv.sys Wed Aug 04 11:44:44 2004 (41107ED4)
    aa7e4000 aa810400 mrxdav mrxdav.sys Wed Aug 04 11:30:49 2004 (41107B91)
    aa9ee000 aaa02400 wdmaud wdmaud.sys Wed Aug 04 11:45:03 2004 (41107EE7)
    aab33000 aab41d80 sysaudio sysaudio.sys Wed Aug 04 11:45:54 2004 (41107F1A)
    aad43000 aad46280 ndisuio ndisuio.sys Wed Aug 04 11:33:10 2004 (41107C1E)
    ad03b000 ad03c100 hiber_WMILIB hiber_WMILIB.SYS Sat Aug 18 02:37:23 2001 (3B7D878B)
    ad088000 ad09f480 dump_atapi dump_atapi.sys Wed Aug 04 11:29:41 2004 (41107B4D)
    ad0a0000 ad168a60 avg7core avg7core.sys Wed Oct 10 21:53:39 2007 (470CFC8B)
    ad169000 ad1d7380 mrxsmb mrxsmb.sys Wed Aug 04 11:45:14 2004 (41107EF2)
    ad200000 ad22b180 rdbss rdbss.sys Wed Aug 04 11:50:05 2004 (41108015)
    ad2cc000 ad2edd00 afd afd.sys Wed Aug 04 11:44:13 2004 (41107EB5)
    ad2ee000 ad30ef00 ipnat ipnat.sys Wed Aug 04 11:34:48 2004 (41107C80)
    ad30f000 ad336c00 netbt netbt.sys Wed Aug 04 11:44:36 2004 (41107ECC)
    ad35f000 ad3b6a80 tcpip tcpip.sys Wed Aug 04 11:44:39 2004 (41107ECF)
    ad3b7000 ad3c9400 ipsec ipsec.sys Wed Aug 04 11:44:27 2004 (41107EC3)
    ad3f6000 ad3f8900 Dxapi Dxapi.sys Sat Aug 18 02:23:19 2001 (3B7D843F)
    ad422000 ad425800 Sacm2A Sacm2A.sys Thu Jun 10 18:12:36 2004 (40C8573C)
    ad43a000 ad899000 RtkHDAud RtkHDAud.sys Fri Jun 22 15:44:34 2007 (467BA10A)
    ad899000 ad8ba700 portcls portcls.sys Wed Mar 17 00:28:17 2004 (40574E49)
    ad8bb000 ad8d5000 AtiHdAud AtiHdAud.sys Fri Dec 29 01:14:43 2006 (45941EAB)
    b98f5000 b9928200 update update.sys Wed Aug 04 11:28:32 2004 (41107B08)
    b99ed000 b99ef280 rasacd rasacd.sys Sat Aug 18 02:25:39 2001 (3B7D84CB)
    b99f1000 b9a21100 rdpdr rdpdr.sys Wed Aug 04 11:31:10 2004 (41107BA6)
    b9a72000 b9a82e00 psched psched.sys Wed Aug 04 11:34:16 2004 (41107C60)
    b9a83000 b9a99680 ndiswan ndiswan.sys Wed Aug 04 11:44:30 2004 (41107EC6)
    b9a9a000 b9abc680 ks ks.sys Wed Aug 04 11:45:20 2004 (41107EF8)
    b9abd000 b9adfe80 USBPORT USBPORT.SYS Wed Aug 04 11:38:34 2004 (41107D62)
    b9ae0000 b9af6300 Rtenicxp Rtenicxp.sys Tue Feb 06 22:13:26 2007 (45C8B02E)
    b9af7000 b9b1c000 HDAudBus HDAudBus.sys Sat Jan 08 06:37:15 2005 (41DF3243)
    b9b1c000 b9b2f780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 11:37:04 2004 (41107D08)
    b9b4b000 b9b4bc00 audstub audstub.sys Sat Aug 18 02:29:40 2001 (3B7D85BC)
    b9b80000 b9b81000 avgclean avgclean.sys Mon Dec 03 17:39:01 2007 (4753F1DD)
    b9b8c000 b9b8cb80 Null Null.SYS Sat Aug 18 02:17:39 2001 (3B7D82EB)
    b9bd0000 b9bd0d00 dxgthk dxgthk.sys Sat Aug 18 02:23:12 2001 (3B7D8438)
    b9bf5000 ba0fc000 ati2mtag ati2mtag.sys Fri Aug 01 10:02:11 2008 (489291CB)
    ba6ca000 ba6d6e20 SCDEmu SCDEmu.SYS Mon Jul 07 13:10:49 2008 (4871C881)
    ba6da000 ba6e2700 netbios netbios.sys Wed Aug 04 11:33:19 2004 (41107C27)
    ba6ea000 ba6f2700 wanarp wanarp.sys Wed Aug 04 11:34:57 2004 (41107C89)
    ba70a000 ba718000 libusb0 libusb0.sys Thu Mar 10 01:20:17 2005 (422F5379)
    ba71a000 ba728100 usbhub usbhub.sys Wed Aug 04 11:38:40 2004 (41107D68)
    ba72a000 ba738b80 drmk drmk.sys Wed Aug 04 11:37:54 2004 (41107D3A)
    ba73a000 ba743480 NDProxy NDProxy.SYS Sat Aug 18 02:25:30 2001 (3B7D84C2)
    ba7da000 ba7ddc80 mssmbios mssmbios.sys Wed Aug 04 11:37:47 2004 (41107D33)
    bf000000 bf011580 dxg dxg.sys Wed Aug 04 11:30:51 2004 (41107B93)
    bf012000 bf062000 ati2dvag ati2dvag.dll Fri Aug 01 10:02:34 2008 (489291E2)
    bf062000 bf0eb000 ati2cqag ati2cqag.dll Fri Aug 01 09:04:12 2008 (48928434)
    bf0eb000 bf157000 atikvmag atikvmag.dll Fri Aug 01 09:12:09 2008 (48928611)
    bf157000 bf19a000 atiok3x2 atiok3x2.dll Fri Aug 01 10:28:18 2008 (489297EA)
    bf19a000 bf556700 ati3duag ati3duag.dll Fri Aug 01 09:40:40 2008 (48928CC0)
    bf557000 bf76c180 ativvaxx ativvaxx.dll Fri Aug 01 09:29:30 2008 (48928A22)
    bf800000 bf9c0380 win32k win32k.sys Wed Aug 04 11:47:30 2004 (41107F7A)
    f7402000 f740a900 msgpc msgpc.sys Wed Aug 04 11:34:11 2004 (41107C5B)
    f7412000 f741dd00 raspptp raspptp.sys Wed Aug 04 11:44:26 2004 (41107EC2)
    f7422000 f742c200 raspppoe raspppoe.sys Wed Aug 04 11:35:06 2004 (41107C92)
    f7432000 f743e880 rasl2tp rasl2tp.sys Wed Aug 04 11:44:21 2004 (41107EBD)
    f7442000 f744ad00 intelppm intelppm.sys Wed Aug 04 11:29:19 2004 (41107B37)
    f7452000 f7460080 redbook redbook.sys Wed Aug 04 11:29:34 2004 (41107B46)
    f7462000 f746e180 cdrom cdrom.sys Wed Aug 04 11:29:52 2004 (41107B58)
    f7472000 f747c380 imapi imapi.sys Wed Aug 04 11:30:12 2004 (41107B6C)
    f7482000 f7492a80 pci pci.sys Wed Aug 04 11:37:45 2004 (41107D31)
    f7493000 f74c0d80 ACPI ACPI.sys Wed Aug 04 11:37:35 2004 (41107D27)
    f74c1000 f74d8800 SCSIPORT SCSIPORT.SYS Wed Aug 04 11:29:39 2004 (41107B4B)
    f74d9000 f75d6000 sptd sptd.sys Wed Jan 02 22:05:37 2008 (477BBD59)
    f75f7000 f75ffc00 isapnp isapnp.sys Sat Aug 18 02:28:01 2001 (3B7D8559)
    f7607000 f7611500 MountMgr MountMgr.sys Wed Aug 04 11:28:29 2004 (41107B05)
    f7617000 f7623c80 VolSnap VolSnap.sys Wed Aug 04 11:30:14 2004 (41107B6E)
    f7627000 f762fe00 disk disk.sys Wed Aug 04 11:29:53 2004 (41107B59)
    f7637000 f7643200 CLASSPNP CLASSPNP.SYS Wed Aug 04 11:44:26 2004 (41107EC2)
    f7657000 f765f880 Fips Fips.SYS Sat Aug 18 07:01:49 2001 (3B7DC585)
    f7677000 f7686900 Cdfs Cdfs.SYS Wed Aug 04 11:44:09 2004 (41107EB1)
    f76e7000 f76f3e00 i8042prt i8042prt.sys Wed Aug 04 11:44:36 2004 (41107ECC)
    f76f7000 f7706d80 serial serial.sys Wed Aug 04 11:45:51 2004 (41107F17)
    f7707000 f770d200 PCIIDEX PCIIDEX.SYS Wed Aug 04 11:29:40 2004 (41107B4C)
    f770f000 f7713900 PartMgr PartMgr.sys Sat Aug 18 07:02:23 2001 (3B7DC5A7)
    f772f000 f7733500 watchdog watchdog.sys Wed Aug 04 11:37:32 2004 (41107D24)
    f778f000 f7794000 usbuhci usbuhci.sys Wed Aug 04 11:38:34 2004 (41107D62)
    f7797000 f779d800 usbehci usbehci.sys Wed Aug 04 11:38:34 2004 (41107D62)
    f779f000 f77a5000 kbdclass kbdclass.sys Wed Aug 04 11:28:32 2004 (41107B08)
    f77a7000 f77aca00 mouclass mouclass.sys Wed Aug 04 11:28:32 2004 (41107B08)
    f77af000 f77b5b00 fdc fdc.sys Wed Aug 04 11:29:25 2004 (41107B3D)
    f77b7000 f77bdb00 ElbyCDFL ElbyCDFL.sys Fri Dec 15 02:52:33 2006 (4581C099)
    f77bf000 f77c3880 TDI TDI.SYS Wed Aug 04 11:37:47 2004 (41107D33)
    f77c7000 f77cb580 ptilink ptilink.sys Sat Aug 18 02:19:53 2001 (3B7D8371)
    f77cf000 f77d3080 raspti raspti.sys Sat Aug 18 02:25:32 2001 (3B7D84C4)
    f77df000 f77e4200 vga vga.sys Wed Aug 04 11:37:06 2004 (41107D0A)
    f77e7000 f77eba80 Msfs Msfs.SYS Wed Aug 04 11:30:37 2004 (41107B85)
    f77ef000 f77f6880 Npfs Npfs.SYS Wed Aug 04 11:30:38 2004 (41107B86)
    f781f000 f7825c80 avg7rsxp avg7rsxp.sys Tue Jan 30 20:38:42 2007 (45BF5F7A)
    f782a000 f7841480 atapi atapi.sys Wed Aug 04 11:29:41 2004 (41107B4D)
    f7842000 f7867700 dmio dmio.sys Wed Aug 04 11:37:13 2004 (41107D11)
    f7868000 f7886880 ftdisk ftdisk.sys Sat Aug 18 02:22:41 2001 (3B7D8419)
    f7887000 f7890f00 termdd termdd.sys Wed Aug 04 11:28:52 2004 (41107B1C)
    f7897000 f789a000 BOOTVID BOOTVID.dll Sat Aug 18 02:19:09 2001 (3B7D8345)
    f7947000 f794ac80 serenum serenum.sys Wed Aug 04 11:29:06 2004 (41107B2A)
    f794b000 f794d580 ndistapi ndistapi.sys Sat Aug 18 02:25:29 2001 (3B7D84C1)
    f7956000 f7967f00 sr sr.sys Wed Aug 04 11:36:22 2004 (41107CDE)
    f7968000 f7986780 fltMgr fltMgr.sys Wed Aug 04 11:31:17 2004 (41107BAD)
    f7987000 f7988b80 kdcom kdcom.dll Sat Aug 18 02:19:10 2001 (3B7D8346)
    f7989000 f798a100 WMILIB WMILIB.SYS Sat Aug 18 02:37:23 2001 (3B7D878B)
    f798b000 f798c700 dmload dmload.sys Sat Aug 18 02:28:15 2001 (3B7D8567)
    f799d000 f799e100 swenum swenum.sys Wed Aug 04 11:28:41 2004 (41107B11)
    f79a3000 f79a4280 USBD USBD.SYS Sat Aug 18 02:32:58 2001 (3B7D8682)
    f79a5000 f79a6f00 Fs_Rec Fs_Rec.SYS Sat Aug 18 02:19:37 2001 (3B7D8361)
    f79a7000 f79a8080 Beep Beep.SYS Sat Aug 18 02:17:33 2001 (3B7D82E5)
    f79a9000 f79aa080 mnmdd mnmdd.SYS Sat Aug 18 02:27:28 2001 (3B7D8538)
    f79ab000 f79ac080 RDPCDD RDPCDD.sys Sat Aug 18 02:16:56 2001 (3B7D82C0)
    f79af000 f79b0080 avg7rsw avg7rsw.sys Tue Jul 26 17:40:51 2005 (42E6284B)
    f79b1000 f79b2100 dump_WMILIB dump_WMILIB.SYS Sat Aug 18 02:37:23 2001 (3B7D878B)
    f79b5000 f79b6360 avgtdi avgtdi.sys Thu Aug 25 15:29:58 2005 (430D969E)
    f79b9000 f79baf80 ElbyCDIO ElbyCDIO.sys Wed Dec 13 04:18:53 2006 (457F31D5)
    f7a0b000 f7a37a80 NDIS NDIS.sys Wed Aug 04 11:44:27 2004 (41107EC3)
    f7a38000 f7a4e780 KSecDD KSecDD.sys Wed Aug 04 11:29:45 2004 (41107B51)
    f7a4f000 f7a4fd00 pciide pciide.sys Sat Aug 18 02:21:49 2001 (3B7D83E5)
    f7b37000 f7b51580 Mup Mup.sys Wed Aug 04 11:45:20 2004 (41107EF8)
    f7b52000 f7bde480 Ntfs Ntfs.sys Wed Aug 04 11:45:06 2004 (41107EEA)

    Unloaded modules:
    a9e66000 a9e90000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a9e66000 a9e90000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a9e0b000 a9e23000 hiber_atapi.
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a9e35000 a9e4d000 hiber_atapi.
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    aa9a1000 aa9cb000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    aa9cb000 aa9ee000 aec.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7aac000 f7aad000 drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    aaaf3000 aab00000 DMusic.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    aab03000 aab11000 swmidi.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f79f1000 f79f3000 splitter.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    aa780000 aa794000 parport.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7687000 f7693000 ATITool.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f77d7000 f77dc000 Cdaudio.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f793f000 f7942000 Sfloppy.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    Closing open log file c:\debuglog.txt

    and here's the stop error-STOP:0x000000D1 (0x00000006, 0x00000002, 0x00000000, 0xf7A0E504)
    NDIS.sys - Address f7A0E504 base at f7A0B000
    next reply
     
  6. 2008/09/06
    pushprajpradhan

    pushprajpradhan Inactive Thread Starter

    Joined:
    2008/09/05
    Messages:
    4
    Likes Received:
    0
    sir i am connected to internet while doing running debugwiz and i followed the exact instruction given here http://www.windowsbbs.com/general-discussions/33471-dump-data-collection-tool-instructions.html, here's a screen shot of debugwiz please see if anything is wrong http://i90.photobucket.com/albums/k267/pushprajpradhan/debugwiz1.jpg also i installed new ATi drivers, updated BIOS, also did memtest86 check for RAM's (no errors found). is PSU causing the problem? i think it's PSU and thats why i am already thinking of buying a new PSU, please help.:)
    sorry for double reply, but i had to do it becoz of character limit of a reply:D
     
  7. 2008/09/07
    Steve R Jones

    Steve R Jones SuperGeek Staff

    Joined:
    2001/12/30
    Messages:
    12,317
    Likes Received:
    252
    While you're waiting for some help on the debug log, did you try searching the Stop Error Code?
     

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.