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.

XP Pro crash - reboot or blue screen [Dump Data]

Discussion in 'Windows XP' started by Vegeta, 2006/05/29.

  1. 2006/05/29
    Vegeta

    Vegeta Inactive Thread Starter

    Joined:
    2006/05/29
    Messages:
    7
    Likes Received:
    0
    Well as so many others, I have the same problem now. Windows XP Pro (SP2) crashes randomly, and I get a couple of different errors. I'm having almost the same problem as the guy in this thread.
    It started with that I was having this problem once every day, when I turned on my computer. I thought it was a software problem, but even after formating my drive and reinstalling win XP, I'm having the same problem.
    When I boot the computer, after everthing is loading, I get an error message where windows asks if I want to send a report to microsoft. A System Error in Category (102) and Event 1003.
    My crashs are random errors, and occur almost randomly. But recently I've realised that when I start a game (Counter-Strike), some minuts after I start the game, my computer reboots (no blue screen). It does this only once, after the reboot, it doens't reboot again when I start the game.
    I have seen many different blue screen errors, like the ones the guy in that thread has, expect the "STOP 50 error ", I don't know about that.

    Now I have quite a couple of Dump File text files, which I got by using the software some guy in this forum refered to, the "debugwiz ". I will post 1 of them to begin with

    The latest one

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

    Opened log file 'c:\debuglog.txt'

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


    Loading Dump File [C:\WINDOWS\Minidump\Mini052906-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) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp.051019-1519
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a520
    Debug session time: Mon May 29 15:47:43.899 2006 (GMT+2)
    System Uptime: 0 days 1:27:51.460
    Loading Kernel Symbols
    ........................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ...........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007F, {8, 80042000, 0, 0}

    Probably caused by : memory_corruption

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

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

    UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
    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: 00000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 80042000
    Arg3: 00000000
    Arg4: 00000000

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


    BUGCHECK_STR: 0x7f_8

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: CODE_CORRUPTION

    LAST_CONTROL_TRANSFER: from 00000000 to 804e1693

    STACK_TEXT:
    b95a7fdc 00000000 00000000 00000000 00000000 nt!KiTrap0E+0x47


    STACK_COMMAND: kb

    CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
    !chkimg -lo 50 -db !nt
    5 errors : !nt (804e1745-804e8f44)
    804e1740 05 00 e9 15 d9 *7f ff b9 e3 20 4e 80 39 4d 68 0f ......... N.9Mh.

    ...

    804e8f00 53 56 57 64 a1 *04 01 00 00 8b 58 44 89 5d dc ff SVWd......XD.]..

    ...

    804e8f20 0a c1 ef 14 *80 *c6 fc ff 3f 00 81 e7 fc 0f 00 00 ........?.......

    ...

    804e8f40 ff 0f 87 58 *70 01 00 8b 45 0c 3b 05 38 ef 55 80 ...Xp...E.;.8.U.


    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=00000023 ebx=b95a8080 ecx=000066c8 edx=e4170000 esi=00019b20 edi=804e8f09
    eip=804e1693 esp=b95a7fdc ebp=b95a7fdc iopl=0 nv up di pl zr na po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010046
    nt!KiTrap0E+0x47:
    804e1693 89550c mov [ebp+0xc],edx ss:0010:b95a7fe8=????????
    ChildEBP RetAddr Args to Child
    b95a7fdc 00000000 00000000 00000000 00000000 nt!KiTrap0E+0x47 (FPO: [0,0] TrapFrame-EDITED @ 00000000)
    start end module name
    804d7000 806eb400 nt ntoskrnl.exe Thu Oct 20 02:06:01 2005 (4356DF69)
    806ec000 806ffd00 hal halacpi.dll Tue Nov 16 02:37:02 2004 (419959BE)
    b7c39000 b7c62f00 kmixer kmixer.sys Wed Aug 04 08:07:46 2004 (41107D32)
    b92d6000 b9316080 HTTP HTTP.sys Sat Oct 09 01:18:26 2004 (41672042)
    b95e7000 b960ef00 secdrv secdrv.sys Tue Aug 31 15:42:55 2004 (4134805F)
    b96bf000 b96ce900 Cdfs Cdfs.SYS Wed Aug 04 08:14:09 2004 (41107EB1)
    b97c7000 b9818300 srv srv.sys Tue May 10 02:22:19 2005 (427FFEBB)
    b9931000 b995d400 mrxdav mrxdav.sys Wed Aug 04 08:00:49 2004 (41107B91)
    b9b43000 b9b57400 wdmaud wdmaud.sys Wed Aug 04 08:15:03 2004 (41107EE7)
    ba5b0000 ba5b3900 ndisuio ndisuio.sys Tue Jun 21 03:52:55 2005 (42B772F7)
    bf000000 bf011580 dxg dxg.sys Wed Aug 04 08:00:51 2004 (41107B93)
    bf012000 bf3dae00 nv4_disp nv4_disp.dll Fri Mar 10 01:31:16 2006 (4410C8D4)
    bf800000 bf9c1100 win32k win32k.sys Thu Oct 06 02:09:50 2005 (43446B4E)
    f614f000 f6166580 dump_atapi dump_atapi.sys Wed Jul 06 01:45:22 2005 (42CB1B92)
    f618f000 f61b2100 Fastfat Fastfat.SYS Sat Jun 04 02:11:30 2005 (42A0F1B2)
    f61b3000 f62707a0 avg7core avg7core.sys Mon May 22 13:20:22 2006 (44719E76)
    f6271000 f6292100 ipnat ipnat.sys Fri Oct 21 03:47:17 2005 (435848A5)
    f6293000 f6301900 mrxsmb mrxsmb.sys Tue Oct 18 01:54:38 2005 (435439BE)
    f632a000 f6354a00 rdbss rdbss.sys Thu Oct 28 03:14:55 2004 (4180480F)
    f6355000 f6376d00 afd afd.sys Wed Aug 04 08:14:13 2004 (41107EB5)
    f6377000 f639ec00 netbt netbt.sys Wed Aug 04 08:14:36 2004 (41107ECC)
    f639f000 f63f7000 tcpip tcpip.sys Fri Jan 13 18:07:06 2006 (43C7DE3A)
    f63f7000 f6409400 ipsec ipsec.sys Wed Aug 04 08:14:27 2004 (41107EC3)
    f7572000 f75a5180 update update.sys Thu Sep 02 00:27:22 2004 (41364CCA)
    f75a6000 f75d5a80 rdpdr rdpdr.sys Thu Jun 02 03:42:19 2005 (429E63FB)
    f787e000 f7880f80 mouhid mouhid.sys Fri Aug 17 22:47:57 2001 (3B7D82FD)
    f789e000 f78aee00 psched psched.sys Wed Aug 04 08:04:16 2004 (41107C60)
    f78af000 f78c5680 ndiswan ndiswan.sys Wed Aug 04 08:14:30 2004 (41107EC6)
    f78c6000 f78d7080 LMouKE LMouKE.Sys Wed Mar 29 02:55:57 2006 (4429DB1D)
    f78d8000 f78eb900 parport parport.sys Wed Aug 04 07:59:04 2004 (41107B28)
    f78ec000 f790fa00 portcls portcls.sys Wed Feb 01 02:31:45 2006 (43E00F81)
    f7910000 f7952620 ALCXWDM ALCXWDM.SYS Mon Feb 04 09:35:39 2002 (3C5E47DB)
    f7953000 f7975700 ks ks.sys Thu Dec 29 01:29:29 2005 (43B32DE9)
    f7976000 f7998f00 USBPORT USBPORT.SYS Wed Oct 26 01:39:41 2005 (435EC23D)
    f7999000 f79ac780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 08:07:04 2004 (41107D08)
    f79ad000 f7d28340 nv4_mini nv4_mini.sys Fri Mar 10 01:40:42 2006 (4410CB0A)
    f7d5f000 f7d61900 Dxapi Dxapi.sys Fri Aug 17 22:53:19 2001 (3B7D843F)
    f835c000 f8375a80 Mup Mup.sys Fri Sep 23 03:26:18 2005 (433359BA)
    f8376000 f83a2a80 NDIS NDIS.sys Wed Aug 04 08:14:27 2004 (41107EC3)
    f83a3000 f842f600 Ntfs Ntfs.sys Tue Nov 29 02:19:54 2005 (438BACBA)
    f8430000 f8446780 KSecDD KSecDD.sys Wed Aug 04 07:59:45 2004 (41107B51)
    f8447000 f8458f00 sr sr.sys Wed Aug 04 08:06:22 2004 (41107CDE)
    f8459000 f8477780 fltMgr fltMgr.sys Wed Aug 04 08:01:17 2004 (41107BAD)
    f8478000 f848f580 atapi atapi.sys Wed Jul 06 01:45:22 2005 (42CB1B92)
    f8490000 f84b5700 dmio dmio.sys Wed Aug 04 08:07:13 2004 (41107D11)
    f84b6000 f84d4880 ftdisk ftdisk.sys Fri Aug 17 22:52:41 2001 (3B7D8419)
    f84d5000 f84e5a80 pci pci.sys Thu Dec 16 19:34:40 2004 (41C1D540)
    f84e6000 f8513d80 ACPI ACPI.sys Wed Aug 04 08:07:35 2004 (41107D27)
    f8535000 f853dc00 isapnp isapnp.sys Fri Aug 17 22:58:01 2001 (3B7D8559)
    f8545000 f854f500 MountMgr MountMgr.sys Wed Aug 04 07:58:29 2004 (41107B05)
    f8555000 f8561c80 VolSnap VolSnap.sys Wed Aug 04 08:00:14 2004 (41107B6E)
    f8565000 f856de00 disk disk.sys Wed Aug 04 07:59:53 2004 (41107B59)
    f8575000 f8581180 CLASSPNP CLASSPNP.SYS Thu Oct 06 01:53:44 2005 (43446788)
    f8585000 f858f500 viaagp viaagp.sys Wed Aug 04 08:07:42 2004 (41107D2E)
    f85d5000 f85dd700 netbios netbios.sys Wed Aug 04 08:03:19 2004 (41107C27)
    f85e5000 f85ed880 Fips Fips.SYS Sat Aug 18 03:31:49 2001 (3B7DC585)
    f85f5000 f85fd700 wanarp wanarp.sys Wed Aug 04 08:04:57 2004 (41107C89)
    f8615000 f861df80 LHidUsbK LHidUsbK.Sys Wed Mar 29 02:55:19 2006 (4429DAF7)
    f8625000 f862dd80 HIDCLASS HIDCLASS.SYS Wed Aug 04 08:08:18 2004 (41107D52)
    f8655000 f865dd00 intelppm intelppm.sys Fri Aug 27 23:42:44 2004 (412FAAD4)
    f8665000 f866f400 imapi imapi.sys Fri Aug 13 19:17:15 2004 (411CF79B)
    f8675000 f8681180 cdrom cdrom.sys Wed Aug 04 07:59:52 2004 (41107B58)
    f8685000 f8693080 redbook redbook.sys Wed Aug 04 07:59:34 2004 (41107B46)
    f8695000 f86a3b80 drmk drmk.sys Wed Aug 04 08:07:54 2004 (41107D3A)
    f86a5000 f86b4d80 serial serial.sys Wed Aug 04 08:15:51 2004 (41107F17)
    f86b5000 f86c1e00 i8042prt i8042prt.sys Wed Aug 04 08:14:36 2004 (41107ECC)
    f86c5000 f86d2a00 L8042mou L8042mou.Sys Wed Mar 29 02:55:03 2006 (4429DAE7)
    f86d5000 f86e1880 rasl2tp rasl2tp.sys Wed Aug 04 08:14:21 2004 (41107EBD)
    f86e5000 f86ef200 raspppoe raspppoe.sys Wed Aug 04 08:05:06 2004 (41107C92)
    f86f5000 f8700d00 raspptp raspptp.sys Wed Aug 04 08:14:26 2004 (41107EC2)
    f8705000 f870d900 msgpc msgpc.sys Wed Aug 04 08:04:11 2004 (41107C5B)
    f8735000 f873ef00 termdd termdd.sys Wed Aug 04 07:58:52 2004 (41107B1C)
    f8745000 f874e480 NDProxy NDProxy.SYS Fri Aug 17 22:55:30 2001 (3B7D84C2)
    f8755000 f8763280 usbhub usbhub.sys Tue Feb 14 02:16:57 2006 (43F12F89)
    f8765000 f8773d80 sysaudio sysaudio.sys Wed Aug 04 08:15:54 2004 (41107F1A)
    f87b5000 f87bb200 PCIIDEX PCIIDEX.SYS Wed Aug 04 07:59:40 2004 (41107B4C)
    f87bd000 f87c1900 PartMgr PartMgr.sys Sat Aug 18 03:32:23 2001 (3B7DC5A7)
    f87c5000 f87ccd80 viaagp1 viaagp1.sys Wed Jul 24 11:44:31 2002 (3D3E76FF)
    f87e5000 f87e9720 PStrip PStrip.SYS Mon Nov 08 13:02:53 2004 (418F606D)
    f8805000 f880a200 RTL8139 RTL8139.SYS Fri Jun 13 07:29:46 2003 (3EE9614A)
    f880d000 f8812000 usbuhci usbuhci.sys Wed Aug 04 08:08:34 2004 (41107D62)
    f8815000 f881ba80 usbehci usbehci.sys Wed Oct 26 01:39:41 2005 (435EC23D)
    f881d000 f881e000 fdc fdc.sys unavailable (00000000)
    f8825000 f882aa00 mouclass mouclass.sys Wed Aug 04 07:58:32 2004 (41107B08)
    f882d000 f8833000 kbdclass kbdclass.sys Wed Aug 04 07:58:32 2004 (41107B08)
    f8835000 f8839880 TDI TDI.SYS Wed Aug 04 08:07:47 2004 (41107D33)
    f8845000 f8849580 ptilink ptilink.sys Fri Aug 17 22:49:53 2001 (3B7D8371)
    f884d000 f8851080 raspti raspti.sys Fri Aug 17 22:55:32 2001 (3B7D84C4)
    f8875000 f887a000 flpydisk flpydisk.sys Wed Aug 04 07:59:24 2004 (41107B3C)
    f8885000 f888a200 vga vga.sys Wed Aug 04 08:07:06 2004 (41107D0A)
    f888d000 f8891a80 Msfs Msfs.SYS Wed Aug 04 08:00:37 2004 (41107B85)
    f8895000 f889c880 Npfs Npfs.SYS Wed Aug 04 08:00:38 2004 (41107B86)
    f88a5000 f88abf00 avg7rsxp avg7rsxp.sys Thu Feb 23 00:39:36 2006 (43FCF638)
    f88ad000 f88b3180 HIDPARSE HIDPARSE.SYS Wed Aug 04 08:08:15 2004 (41107D4F)
    f88b5000 f88bb980 LHidKE LHidKE.Sys Wed Mar 29 02:56:06 2006 (4429DB26)
    f88cd000 f88d1500 watchdog watchdog.sys Wed Aug 04 08:07:32 2004 (41107D24)
    f8945000 f8948000 BOOTVID BOOTVID.dll Fri Aug 17 22:49:09 2001 (3B7D8345)
    f89d1000 f89d3280 rasacd rasacd.sys Fri Aug 17 22:55:39 2001 (3B7D84CB)
    f89f1000 f89f4c80 serenum serenum.sys Wed Aug 04 07:59:06 2004 (41107B2A)
    f89f5000 f89f7980 gameenum gameenum.sys Wed Aug 04 08:08:20 2004 (41107D54)
    f89f9000 f89fb580 ndistapi ndistapi.sys Fri Aug 17 22:55:29 2001 (3B7D84C1)
    f8a15000 f8a18c80 mssmbios mssmbios.sys Wed Aug 04 08:07:47 2004 (41107D33)
    f8a35000 f8a36b80 kdcom kdcom.dll Fri Aug 17 22:49:10 2001 (3B7D8346)
    f8a37000 f8a38100 WMILIB WMILIB.SYS Fri Aug 17 23:07:23 2001 (3B7D878B)
    f8a39000 f8a3a500 viaide viaide.sys Wed Aug 04 07:59:42 2004 (41107B4E)
    f8a3b000 f8a3c700 dmload dmload.sys Fri Aug 17 22:58:15 2001 (3B7D8567)
    f8a45000 f8a46100 swenum swenum.sys Wed Aug 04 07:58:41 2004 (41107B11)
    f8a47000 f8a48280 USBD USBD.SYS Fri Aug 17 23:02:58 2001 (3B7D8682)
    f8a55000 f8a56f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 22:49:37 2001 (3B7D8361)
    f8a57000 f8a58080 Beep Beep.SYS Fri Aug 17 22:47:33 2001 (3B7D82E5)
    f8a59000 f8a5a080 mnmdd mnmdd.SYS Fri Aug 17 22:57:28 2001 (3B7D8538)
    f8a5b000 f8a5c080 RDPCDD RDPCDD.sys Fri Aug 17 22:46:56 2001 (3B7D82C0)
    f8a5d000 f8a5e080 avg7rsw avg7rsw.sys Tue Jul 26 14:10:51 2005 (42E6284B)
    f8a67000 f8a68a80 ParVdm ParVdm.SYS Fri Aug 17 22:49:49 2001 (3B7D836D)
    f8a73000 f8a74100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 23:07:23 2001 (3B7D878B)
    f8a99000 f8a9a900 splitter splitter.sys Wed Aug 04 08:07:46 2004 (41107D32)
    f8b60000 f8b60d00 dxgthk dxgthk.sys Fri Aug 17 22:53:12 2001 (3B7D8438)
    f8bd6000 f8bd6b80 msmpu401 msmpu401.sys Fri Aug 17 22:59:59 2001 (3B7D85CF)
    f8bd7000 f8bd7c00 audstub audstub.sys Fri Aug 17 22:59:40 2001 (3B7D85BC)
    f8c81000 f8c81b80 Null Null.SYS Fri Aug 17 22:47:39 2001 (3B7D82EB)
    f8c82000 f8c82b40 VIAPFD VIAPFD.SYS Tue Dec 18 07:45:02 2001 (3C1EE5EE)

    Unloaded modules:
    b891c000 b8946000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f8aef000 f8af1000 splitter.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f8a8f000 f8a91000 splitter.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b9a56000 b9a80000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f8b86000 f8b87000 drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba438000 ba445000 DMusic.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba550000 ba55e000 swmidi.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b9a80000 b9aa3000 aec.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f8a4b000 f8a4d000 splitter.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f887d000 f8882000 Cdaudio.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f89cd000 f89d0000 Sfloppy.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    Closing open log file c:\debuglog.txt

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

    I just like to know if this error is due to damaged RAM or a damaged Disk Drive or maybe something else?
    I hope someone can help me with this.
     
  2. 2006/05/29
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Vegeta - Welcome to the Board :)

    Strong indication in your dump of memory corruption.
    Download Window Memory Diagnostic Tool from MS and run it.
     

  3. to hide this advert.

  4. 2006/05/29
    Vegeta

    Vegeta Inactive Thread Starter

    Joined:
    2006/05/29
    Messages:
    7
    Likes Received:
    0
    Thanks PeteC, I'm glad to be here :)

    The line "Probably caused by : memory_corruption" as you quickly noticed was also what I noticed at the first place, but didn't think that it was about the RAM. I ran that memtest, and it seems that it will take a while before it finishs, so I will wait and let run over the night.

    I also have other errors with

    "Probably caused by : win32k.sys ( win32k!PALLOCMEM+2c ) "

    "Probably caused by : Npfs.SYS ( Npfs!NpAddDataQueueEntry+133 ) "

    "Probably caused by : ntoskrnl.exe ( nt!KiTrap0E+1b ) "

    I did a search on these problems but didn't understand the first 2 problems, but there is something maybe useful about the last her.

    But are these problems even related to my original issue? Otherwhise it seems almost all my errors include

    "Probably caused by : memory_corruption "

    One thing I forgot about was, that the computer didn't crash during Win XP install, nor did I ever experience a crash during a Safe Mode.
     
  5. 2006/05/29
    Vegeta

    Vegeta Inactive Thread Starter

    Joined:
    2006/05/29
    Messages:
    7
    Likes Received:
    0
    It seems that after I ran the memtest, the Event log is corrupt, I get the message

    "The event log file is corrupt. "

    And info about this on MS website doesn't seem to apply to my problem... Can that software cause this problem?
     
  6. 2006/05/29
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    See how the memory checks out - I have edited your thread title to indicate that dump data is included - we have a guy on the Board who is able to interpret this data.

    The memory test runs outside of Windows in a DOS emulator so is unlikely to corrupt anything in Windows.
    what source - Event Viewer in XP?

    It would be a goood idea to run chkdsk /r on your drive and see if any problems are seen - chkdsk
     
  7. 2006/05/30
    Vegeta

    Vegeta Inactive Thread Starter

    Joined:
    2006/05/29
    Messages:
    7
    Likes Received:
    0
    I ran the memtest over the night (about 9 hours), with about 16 passes on the extended test, and no error was found.

    I also tried the chkdsk /r and /f, but right after it finished the display just went on, and I didn't make it to see if there was any error, but I think it would have noticed me if there was.

    Yes, it is the event viewer in Win XP, but only the System event log is corrupt, I get that message when I try to acces it. But the Application event log is working just fine.

    *** UPDATE: I have fixed the problem with the Event Log.

    I'm suspecting my DVD+/-RW drive to be the cause of the problem. Now I don't remember when exactly this started, but I think it was after I got that drive, and switched it with my DVD drive, so I was running with both a CD-RW drive AND a DVD+/-RW drive. I unplugged the CD-RW drive, and I think I reduced the frequency of the errors/crashes, but I'm unsure about this. Could this be causing the problem?
     
    Last edited: 2006/05/30
  8. 2006/05/30
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Possibly - it is important to ensure that the drives are jumpered correctly - the one at the end of the ribbon cable should be set as master, the other as slave - check it out :)

    I have run a couple of optical drives for years, currently a pair of DVD writers, with no problems.
     
  9. 2006/05/30
    Vegeta

    Vegeta Inactive Thread Starter

    Joined:
    2006/05/29
    Messages:
    7
    Likes Received:
    0
    As far as I know, the jumpers are correctly placed. I now have unplugged both devices, to see if the error occurs even without them. I will post back if the problems occures again, with the newest Dump Data.
     
  10. 2006/05/31
    Vegeta

    Vegeta Inactive Thread Starter

    Joined:
    2006/05/29
    Messages:
    7
    Likes Received:
    0
    Well the error occured, and here I'm again :)

    It is happening much more frequent now. It happend 4 times today!
    The first 3 times it was

    The last time (a few minutes ago) it was the driver_irql_not_less_or_equal. Now the crashes keeps happening when I'm "surfing" my Harddisk in trhough the folders.
    I hope someone can look at this Dump File, and if there is a requirement to see other Dump Data, I have plenty.
    The IRQL error dump is:

     
  11. 2006/05/31
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Hi Vegeta,

    Probably the best thing to do is to go to Microsoft Support Services, and select an option to "open" a support request.

    You can use the log file (debuglog.txt) generated to supply the needed information to start your support request.

    Our "resident" debug troubleshooter seems to be unavailable.

    You are facing most likely a hardware failure, although I can't tell you what.
     
  12. 2006/05/31
    cpc2004

    cpc2004 Inactive

    Joined:
    2005/07/08
    Messages:
    366
    Likes Received:
    0
    Faulty RAM

    Hi,

    The first memory is crashed with code corruption and it is the sign of faulty ram. Some faulty ram can pass memtest. Reseat the memory module to another another memory slot and clean up the dust inside the computer may resolve the blue screen problem. If it still crashes, replace the ram.
     
  13. 2006/05/31
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Seems he just came back :D
     
  14. 2006/05/31
    Vegeta

    Vegeta Inactive Thread Starter

    Joined:
    2006/05/29
    Messages:
    7
    Likes Received:
    0
    Hi,
    Actually I've have tried to put the RAM block in a different slot, and remove dust from the block, but that didn't help.

    The reason why I got 5 crashes today, was because I reinstalled the OS, and the crashes happend much frequent and random when I went through different folders. I didn't have this problem before the reinstall. When I installed Spy-Bot S/D and Ad-Aware SE, and Registry Cleaner and ran them, plus there were some startups (in msconfig) that didn't even have a name which I removed, after all of this, I haven't got a crash yet. Not that the crashes stopped, but probably only the frequency that decreased.
    At time where the crash frequency was high, I tried the Safe Mode, and tried to run through folders like when I did before and got the crashes, but this time, I didn't got any crashes in Safe Mode.
    Therefore I now think that this may be software problem. But that maybe conflicts with the fact that I still had the crashes even after formating and reinstalling the OS.
    Is there a need to post other and different Dump logs, with different errors?
     
  15. 2006/05/31
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    99% sure not. If its a software problem it would crash at the same location/module every time. Random locations/modules generally point to hardware.
     

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.