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.

BSoD over and over

Discussion in 'Windows XP' started by Slinger, 2007/02/11.

  1. 2007/02/11
    Slinger

    Slinger Inactive Thread Starter

    Joined:
    2007/02/11
    Messages:
    7
    Likes Received:
    0
    My computer keeps rebooting with a BSod.

    Error is 0x0000007f (0x0000000D,0x00000000,0x00000000,0x00000000)

    I realize this error means unknown error, I can format and start over as a last resort but I'd rather fix this problem since this is the second time it's happened in 6 months. I formated and replaced the MB last time, I thought it was an IDE problem since lots of my files became corrupted.

    If anyone can supply and help or if you need some info from the computer let me know I'll try my best ( it only runs for at most 5 min).

    Any way to find out what the problem is or how to fix it.

    Ron
     
  2. 2007/02/11
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    Hi, Ron. Welcome to Windows BBS! :)

    Please carefully follow all the instructions in this link and then paste your DebugWiz-generated BSOD dump log analysis reports in this thread. The additional information the DebugWiz-generated reports provide might help us narrow down the culprit more quickly.

    EDIT:
    Microsoft KB Article 137539: General causes of "STOP 0x0000007F" errors
     
    Last edited: 2007/02/11

  3. to hide this advert.

  4. 2007/02/11
    Slinger

    Slinger Inactive Thread Starter

    Joined:
    2007/02/11
    Messages:
    7
    Likes Received:
    0
    Opened log file 'c:\debuglog.txt'

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


    Loading Dump File [C:\WINDOWS\Minidump\Mini021207-01.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 2) MP (2 procs) Free x86 compatible
    Product: WinNt
    Built by: 2600.xpsp_sp2_gdr.050301-1519
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
    Debug session time: Mon Feb 12 00:07:18.937 2007 (GMT-5)
    System Uptime: 0 days 0:05:22.640
    Loading Kernel Symbols
    ........................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ....................................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7F, {d, 0, 0, 0}

    Probably caused by : win32k.sys ( win32k!BltLnkRect+8c8 )

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

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

    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault). The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
    use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
    use .trap on that value
    Else
    .trap on the appropriate frame will show where the trap was taken
    (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000d, EXCEPTION_GP_FAULT
    Arg2: 00000000
    Arg3: 00000000
    Arg4: 00000000

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


    BUGCHECK_STR: 0x7f_d

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    LAST_CONTROL_TRANSFER: from bf80f592 to 804e122c

    STACK_TEXT:
    a850e8e4 bf80f592 badb0d00 a850ecd0 bf98fd50 nt!KiSystemFatalException+0xf
    a850e978 bf8348c2 00000001 a850ef18 a850ef1c win32k!memmove
    a850eef8 bf833e8a 00000008 a850ef18 e270c9f8 win32k!BltLnkRect+0x8c8
    a850f194 bf82f649 00000000 e2604008 00000000 win32k!BltLnk+0x74a
    a850f218 bf846980 e17792d8 e2604018 e17792d8 win32k!EngBitBlt+0x3cb
    a850f368 bf8474c2 a850f464 e1500bb8 00000000 win32k!BLTRECORD::bBitBlt+0x725
    a850f498 bf835ca6 ae01033a 00000000 00000040 win32k!GreStretchBltInternal+0x5fd
    a850f4d4 bf83d4fe ae01033a 00000000 00000040 win32k!GreStretchBlt+0x30
    a850f524 bf83d785 00000001 00000000 00000040 win32k!BltIcon+0xde
    a850f57c bf83d5ce ae01033a 00000000 00000040 win32k!_DrawIconEx+0x240
    a850f5d0 804dd99f ae01033a 00000000 00000040 win32k!NtUserDrawIconEx+0xa9
    a850f5d0 7c90eb94 ae01033a 00000000 00000040 nt!KiFastCallEntry+0xfc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    00c3f770 00000000 00000000 00000000 00000000 0x7c90eb94


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    win32k!BltLnkRect+8c8
    bf8348c2 037e5c add edi,dword ptr [esi+5Ch]

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: win32k!BltLnkRect+8c8

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME: win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 43446a58

    FAILURE_BUCKET_ID: 0x7f_d_win32k!BltLnkRect+8c8

    BUCKET_ID: 0x7f_d_win32k!BltLnkRect+8c8

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

    eax=ffdff13c ebx=00000000 ecx=00000000 edx=a850e9a8 esi=a850ee0c edi=bf80f592
    eip=804e122c esp=a850e8cc ebp=a850e8e4 iopl=0 nv up di ng nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000086
    nt!KiSystemFatalException+0xf:
    804e122c c3 ret
    ChildEBP RetAddr Args to Child
    a850e8e4 bf80f592 badb0d00 a850ecd0 bf98fd50 nt!KiSystemFatalException+0xf (FPO: [0,0] TrapFrame @ a850e8e4)
    a850e978 bf8348c2 00000001 a850ef18 a850ef1c win32k!memmove
    a850eef8 bf833e8a 00000008 a850ef18 e270c9f8 win32k!BltLnkRect+0x8c8 (FPO: [Non-Fpo])
    a850f194 bf82f649 00000000 e2604008 00000000 win32k!BltLnk+0x74a (FPO: [Non-Fpo])
    a850f218 bf846980 e17792d8 e2604018 e17792d8 win32k!EngBitBlt+0x3cb (FPO: [Non-Fpo])
    a850f368 bf8474c2 a850f464 e1500bb8 00000000 win32k!BLTRECORD::bBitBlt+0x725 (FPO: [Non-Fpo])
    a850f498 bf835ca6 ae01033a 00000000 00000040 win32k!GreStretchBltInternal+0x5fd (FPO: [Non-Fpo])
    a850f4d4 bf83d4fe ae01033a 00000000 00000040 win32k!GreStretchBlt+0x30 (FPO: [Non-Fpo])
    a850f524 bf83d785 00000001 00000000 00000040 win32k!BltIcon+0xde (FPO: [Non-Fpo])
    a850f57c bf83d5ce ae01033a 00000000 00000040 win32k!_DrawIconEx+0x240 (FPO: [Non-Fpo])
    a850f5d0 804dd99f ae01033a 00000000 00000040 win32k!NtUserDrawIconEx+0xa9 (FPO: [Non-Fpo])
    a850f5d0 7c90eb94 ae01033a 00000000 00000040 nt!KiFastCallEntry+0xfc (FPO: [0,0] TrapFrame @ a850f604)
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    00c3f770 00000000 00000000 00000000 00000000 0x7c90eb94
    start end module name
    804d7000 806fd000 nt ntkrnlmp.exe Tue Mar 01 19:57:27 2005 (42250F77)
    806fd000 8071dd00 hal halmacpi.dll Wed Aug 04 01:59:09 2004 (41107B2D)
    a8187000 a81c7280 HTTP HTTP.sys Thu Mar 16 19:33:09 2006 (441A03C5)
    a8538000 a8589480 srv srv.sys Mon Aug 14 06:34:39 2006 (44E051BF)
    a86ca000 a86f6400 mrxdav mrxdav.sys Wed Aug 04 02:00:49 2004 (41107B91)
    a8737000 a8739c00 secdrv secdrv.sys Wed Mar 19 06:33:46 2003 (3E78559A)
    a8937000 a893a280 ndisuio ndisuio.sys Wed Aug 04 02:03:10 2004 (41107C1E)
    a8943000 a8946e60 AegisP AegisP.sys Fri Nov 19 15:55:14 2004 (419E5DB2)
    aac67000 aac7e480 dump_atapi dump_atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
    aaca7000 aad15a00 mrxsmb mrxsmb.sys Fri May 05 05:41:42 2006 (445B1DD6)
    aad16000 aad40a00 rdbss rdbss.sys Fri May 05 05:47:55 2006 (445B1F4B)
    aad41000 aad62d00 afd afd.sys Wed Aug 04 02:14:13 2004 (41107EB5)
    aad63000 aad8ac00 netbt netbt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
    aad8b000 aadabf00 ipnat ipnat.sys Wed Sep 29 18:28:36 2004 (415B3714)
    aadac000 aae03d80 tcpip tcpip.sys Thu Apr 20 07:51:47 2006 (444775D3)
    aae04000 aae16400 ipsec ipsec.sys Wed Aug 04 02:14:27 2004 (41107EC3)
    aae51000 aae83680 UdfReadr_xp UdfReadr_xp.SYS Mon Jan 13 13:15:13 2003 (3E230231)
    aae88000 aae8a900 Dxapi Dxapi.sys Fri Aug 17 16:53:19 2001 (3B7D843F)
    aaea4000 aaea7a00 kbdhid kbdhid.sys Wed Aug 04 01:58:33 2004 (41107B09)
    aaea8000 aaeaaf80 mouhid mouhid.sys Fri Aug 17 16:47:57 2001 (3B7D82FD)
    aaebe000 aaefae00 cdudf_xp cdudf_xp.SYS Mon Jan 13 13:14:56 2003 (3E230220)
    aaf1b000 aaf37720 pwd_2k pwd_2k.SYS Mon Jan 13 13:17:32 2003 (3E2302BC)
    bf800000 bf9c1180 win32k win32k.sys Wed Oct 05 20:05:44 2005 (43446A58)
    bf9c2000 bf9d3580 dxg dxg.sys Wed Aug 04 02:00:51 2004 (41107B93)
    bf9d4000 bfa18000 ati2dvag ati2dvag.dll Sat Dec 16 21:50:46 2006 (4584B086)
    bfa18000 bfa65000 ati2cqag ati2cqag.dll Sat Dec 16 21:10:56 2006 (4584A730)
    bfa65000 bfab1000 atikvmag atikvmag.dll Sat Dec 16 21:17:15 2006 (4584A8AB)
    f70fa000 f712d180 update update.sys Wed Sep 01 18:27:22 2004 (41364CCA)
    f712e000 f7150680 ks ks.sys Wed Aug 04 02:15:20 2004 (41107EF8)
    f7151000 f7161e00 psched psched.sys Wed Aug 04 02:04:16 2004 (41107C60)
    f7162000 f7178680 ndiswan ndiswan.sys Wed Aug 04 02:14:30 2004 (41107EC6)
    f7179000 f718c900 parport parport.sys Wed Aug 04 01:59:04 2004 (41107B28)
    f718d000 f71e7180 bcmwl5 bcmwl5.sys Wed Dec 22 02:15:37 2004 (41C91F19)
    f71e8000 f720ae80 USBPORT USBPORT.SYS Wed Aug 04 02:08:34 2004 (41107D62)
    f720b000 f721e780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 02:07:04 2004 (41107D08)
    f721f000 f7426000 ati2mtag ati2mtag.sys Sat Dec 16 21:50:28 2006 (4584B074)
    f746e000 f7488580 Mup Mup.sys Wed Aug 04 02:15:20 2004 (41107EF8)
    f7489000 f74b5a80 NDIS NDIS.sys Wed Aug 04 02:14:27 2004 (41107EC3)
    f74b6000 f7542480 Ntfs Ntfs.sys Wed Aug 04 02:15:06 2004 (41107EEA)
    f7543000 f7559780 KSecDD KSecDD.sys Wed Aug 04 01:59:45 2004 (41107B51)
    f755a000 f756bf00 sr sr.sys Wed Aug 04 02:06:22 2004 (41107CDE)
    f756c000 f758b780 fltmgr fltmgr.sys Mon Aug 21 05:14:57 2006 (44E97991)
    f758c000 f75a3480 atapi atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
    f75a4000 f75c2880 ftdisk ftdisk.sys Fri Aug 17 16:52:41 2001 (3B7D8419)
    f75c3000 f75d3a80 pci pci.sys Wed Aug 04 02:07:45 2004 (41107D31)
    f75d4000 f7601d80 ACPI ACPI.sys Wed Aug 04 02:07:35 2004 (41107D27)
    f7623000 f762bc00 isapnp isapnp.sys Fri Aug 17 16:58:01 2001 (3B7D8559)
    f7633000 f763d500 MountMgr MountMgr.sys Wed Aug 04 01:58:29 2004 (41107B05)
    f7643000 f764fc80 VolSnap VolSnap.sys Wed Aug 04 02:00:14 2004 (41107B6E)
    f7653000 f765be00 disk disk.sys Wed Aug 04 01:59:53 2004 (41107B59)
    f7663000 f766f200 CLASSPNP CLASSPNP.SYS Wed Aug 04 02:14:26 2004 (41107EC2)
    f7673000 f767d580 agp440 agp440.sys Wed Aug 04 02:07:40 2004 (41107D2C)
    f76a3000 f76af000 ATITool ATITool.sys Thu Dec 29 18:04:24 2005 (43B46B78)
    f76b3000 f76bbd00 intelppm intelppm.sys Wed Aug 04 01:59:19 2004 (41107B37)
    f76c3000 f76d2d80 serial serial.sys Wed Aug 04 02:15:51 2004 (41107F17)
    f7723000 f772f880 rasl2tp rasl2tp.sys Wed Aug 04 02:14:21 2004 (41107EBD)
    f7733000 f773d200 raspppoe raspppoe.sys Wed Aug 04 02:05:06 2004 (41107C92)
    f7743000 f774ed00 raspptp raspptp.sys Wed Aug 04 02:14:26 2004 (41107EC2)
    f7753000 f775b900 msgpc msgpc.sys Wed Aug 04 02:04:11 2004 (41107C5B)
    f7763000 f776cf00 termdd termdd.sys Wed Aug 04 01:58:52 2004 (41107B1C)
    f77a3000 f77ac480 NDProxy NDProxy.SYS Fri Aug 17 16:55:30 2001 (3B7D84C2)
    f77b3000 f77c1100 usbhub usbhub.sys Wed Aug 04 02:08:40 2004 (41107D68)
    f77d3000 f77e29c0 Cdr4_xp Cdr4_xp.SYS Mon Jan 13 13:19:21 2003 (3E230329)
    f77f3000 f77fb700 wanarp wanarp.sys Wed Aug 04 02:04:57 2004 (41107C89)
    f7803000 f780b700 netbios netbios.sys Wed Aug 04 02:03:19 2004 (41107C27)
    f7843000 f784b880 Fips Fips.SYS Fri Aug 17 21:31:49 2001 (3B7DC585)
    f7863000 f786bd80 HIDCLASS HIDCLASS.SYS Wed Aug 04 02:08:18 2004 (41107D52)
    f78a3000 f78a9200 PCIIDEX PCIIDEX.SYS Wed Aug 04 01:59:40 2004 (41107B4C)
    f78ab000 f78af900 PartMgr PartMgr.sys Fri Aug 17 21:32:23 2001 (3B7DC5A7)
    f78b3000 f78b7e20 PxHelp20 PxHelp20.sys Mon Apr 25 15:48:02 2005 (426D4972)
    f78db000 f78e0000 usbuhci usbuhci.sys Wed Aug 04 02:08:34 2004 (41107D62)
    f78e3000 f78e9800 usbehci usbehci.sys Wed Aug 04 02:08:34 2004 (41107D62)
    f790b000 f790f880 TDI TDI.SYS Wed Aug 04 02:07:47 2004 (41107D33)
    f791b000 f791f580 ptilink ptilink.sys Fri Aug 17 16:49:53 2001 (3B7D8371)
    f792b000 f792f080 raspti raspti.sys Fri Aug 17 16:55:32 2001 (3B7D84C4)
    f7933000 f7939000 kbdclass kbdclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
    f793b000 f7940a00 mouclass mouclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
    f7973000 f7978ae0 Cdralw2k Cdralw2k.SYS Mon Jan 13 13:19:14 2003 (3E230322)
    f798b000 f7991180 HIDPARSE HIDPARSE.SYS Wed Aug 04 02:08:15 2004 (41107D4F)
    f7993000 f7998200 vga vga.sys Wed Aug 04 02:07:06 2004 (41107D0A)
    f79a3000 f79a7a80 Msfs Msfs.SYS Wed Aug 04 02:00:37 2004 (41107B85)
    f79b3000 f79ba880 Npfs Npfs.SYS Wed Aug 04 02:00:38 2004 (41107B86)
    f79e3000 f79eab80 usbccgp usbccgp.sys Wed Aug 04 02:08:45 2004 (41107D6D)
    f7a0b000 f7a0f500 watchdog watchdog.sys Wed Aug 04 02:07:32 2004 (41107D24)
    f7a33000 f7a36000 BOOTVID BOOTVID.dll Fri Aug 17 16:49:09 2001 (3B7D8345)
    f7ac7000 f7acac80 serenum serenum.sys Wed Aug 04 01:59:06 2004 (41107B2A)
    f7ad3000 f7ad5580 ndistapi ndistapi.sys Fri Aug 17 16:55:29 2001 (3B7D84C1)
    f7adb000 f7add280 rasacd rasacd.sys Fri Aug 17 16:55:39 2001 (3B7D84CB)
    f7aef000 f7af2c80 mssmbios mssmbios.sys Wed Aug 04 02:07:47 2004 (41107D33)
    f7b1f000 f7b21580 hidusb hidusb.sys Fri Aug 17 17:02:16 2001 (3B7D8658)
    f7b23000 f7b24b80 kdcom kdcom.dll Fri Aug 17 16:49:10 2001 (3B7D8346)
    f7b25000 f7b26100 WMILIB WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
    f7b3f000 f7b40100 swenum swenum.sys Wed Aug 04 01:58:41 2004 (41107B11)
    f7b45000 f7b46280 USBD USBD.SYS Fri Aug 17 17:02:58 2001 (3B7D8682)
    f7b4b000 f7b4cf00 Fs_Rec Fs_Rec.SYS Fri Aug 17 16:49:37 2001 (3B7D8361)
    f7b4f000 f7b50080 Beep Beep.SYS Fri Aug 17 16:47:33 2001 (3B7D82E5)
    f7b53000 f7b54080 mnmdd mnmdd.SYS Fri Aug 17 16:57:28 2001 (3B7D8538)
    f7b57000 f7b58080 RDPCDD RDPCDD.sys Fri Aug 17 16:46:56 2001 (3B7D82C0)
    f7b5d000 f7b5e100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
    f7b93000 f7b94a80 ParVdm ParVdm.SYS Fri Aug 17 16:49:49 2001 (3B7D836D)
    f7beb000 f7bebd00 pciide pciide.sys Fri Aug 17 16:51:49 2001 (3B7D83E5)
    f7c0f000 f7c0fd00 dxgthk dxgthk.sys Fri Aug 17 16:53:12 2001 (3B7D8438)
    f7ca5000 f7ca5c00 audstub audstub.sys Fri Aug 17 16:59:40 2001 (3B7D85BC)
    f7cd4000 f7cd4b80 Null Null.SYS Fri Aug 17 16:47:39 2001 (3B7D82EB)
    f7d3c000 f7d3cda0 aslm75 aslm75.sys Tue Apr 22 21:15:58 1997 (335D62CE)

    Unloaded modules:
    a7f37000 a7f46000 drmk.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7d41000 f7d42000 drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a7cdd000 a7d08000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a7da8000 a7dcc000 portcls.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7853000 f7860000 DMusic.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a7dcc000 a7def000 aec.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a802f000 a803d000 swmidi.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a7ec7000 a7ed6000 sysaudio.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7bb7000 f7bb9000 splitter.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a8a47000 a8a52000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a801f000 a802a000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a7f47000 a7f52000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a803f000 a804a000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a7e67000 a7e72000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a7e87000 a7e92000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a7ef7000 a7f02000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a89b7000 a89bb000 icd2w2kl.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a89bf000 a89c2000 icd2w2k.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7833000 f783e000 Imapi.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7823000 f7832000 redbook.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7813000 f781c000 processr.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7442000 f7446000 kbdhid.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f77e3000 f77f0000 i8042prt.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f795b000 f7960000 Cdaudio.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f77c3000 f77d0000 cdrom.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f744a000 f744d000 Sfloppy.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7b39000 f7b3b000 USBD.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7713000 f771e000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7b35000 f7b37000 USBD.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7703000 f770e000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7b31000 f7b33000 USBD.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f76f3000 f76fe000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7b2d000 f7b2f000 USBD.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f76e3000 f76ee000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7b29000 f7b2b000 USBD.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f76d3000 f76de000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    Closing open log file c:\debuglog.txt
     
  5. 2007/02/12
    cpc2004

    cpc2004 Inactive

    Joined:
    2005/07/08
    Messages:
    366
    Likes Received:
    0
    Bugcheck code 7F with interrupt code D is usually related to hardware error (ie RAM, CPU or M/B). From the stack trace, I find the footprint of memmove and this is symptom of faulty ram. Run memtest to stress test the ram.

     
  6. 2007/02/12
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
  7. 2007/02/12
    Slinger

    Slinger Inactive Thread Starter

    Joined:
    2007/02/11
    Messages:
    7
    Likes Received:
    0
    Ram

    I have yet to try and ram testes yet but since I have 2 512MB modules I tried removing one at a a time and see if the problem resolved itself, unfortunately it did not, I will try a RAM tester when I get home today, is MEMTEST floppy based? Since windows won't even boot now I have to boot another way.

    Ron
     
  8. 2007/02/12
    Slinger

    Slinger Inactive Thread Starter

    Joined:
    2007/02/11
    Messages:
    7
    Likes Received:
    0
    RAM test done

    I ran through 7 passes of the ram test and there were no errors.

    I was running a progra, that recorded all temps and voltages, when I look back I can see that the 12V line was around 11.8v. I put in a new PS and I still have the same problem so I can rule out the PS.

    I have removed everything except for the video card( I even tried 3 different cards), Keyboard and mouse.

    Don't know what this means but if the computer can run for 3 hours doing a ram test would than not mean the hardware is OK?

    btw Since all this has started I've noticed that it hangs at the BIOS POST screen for about 30 sec and then after it for another 30 sec. Very annoying!!

    Ron
     
    Last edited: 2007/02/12
  9. 2007/02/13
    cpc2004

    cpc2004 Inactive

    Joined:
    2005/07/08
    Messages:
    366
    Likes Received:
    0
    Refer the 4th post of the following problem.
    http://www.windowsbbs.com/showthread.php?p=285763#post285763

     
  10. 2007/02/13
    Slinger

    Slinger Inactive Thread Starter

    Joined:
    2007/02/11
    Messages:
    7
    Likes Received:
    0
    Solved

    I purchased a new MB today and I'm back up and running. The chipset on my old P4P800 was running very hot so I figured that it might be bad.

    Ron
     
  11. 2007/02/14
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    Hi, Slinger.

    Thanks for following up with your resolution. Perhaps other people with the same or similar problem who run across this thread will also benefit.

    BTW, how did you determine that the chipset was "very hot "?
     
  12. 2007/02/14
    Slinger

    Slinger Inactive Thread Starter

    Joined:
    2007/02/11
    Messages:
    7
    Likes Received:
    0
    I touched it..... LOL

    My system is liquid cooled except the chipset still has it's heatsink on it, I'm wondering if maybe it reqired the little bit of air that would be blowing off the CPU fan to help cool itself, I wouldn't think so. Either way I'm purchasing a Chipset cooler to place inline with my CPU and GPU cooler.

    Ron
     
  13. 2007/02/14
    cpc2004

    cpc2004 Inactive

    Joined:
    2005/07/08
    Messages:
    366
    Likes Received:
    0
    Do you still get blue screen after you replace the motherboard?

     
  14. 2007/02/14
    Slinger

    Slinger Inactive Thread Starter

    Joined:
    2007/02/11
    Messages:
    7
    Likes Received:
    0
    Nope, it's been running straight for 30 hours and not even a program has crashed and I'm running it hard with BOINC running in the background, windows accpeted the new MB without a problem.

    Ron
     

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.