TechSpot

PC randomly restarting, please look at my minidumps?

By TheGlow
Jul 29, 2005
  1. I just put this pc together July 1st and was working squeaky clean till yesterday. Since ive had about 5-6 restarts.
    1 I didnt notice a bluescreen, one when I wasnt home, and 3 more BSODs i recall looking at.

    And another 10 secs after this posting.
     

    Attached Files:

  2. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Run chkdsk /r may resolve your problem. If it still crashes, boot into recovery console and run chkdsk /r. Please feedback your result and your feedback will help us to resolve similar problem.

    Debug report of your minidumps

    BugCheck 77, {1, 6c0069, 0, b9e50ca0}
    Probably caused by : memory_corruption ( nt!MmInPageKernelStack+173 )
    STACK_TEXT:
    f7a4bd58 8050f1d5 00000077 00000001 006c0069 nt!KeBugCheckEx+0x1b
    f7a4bd8c 8053b28c 0007c4c0 00000000 865bfb30 nt!MmInPageKernelStack+0x173
    f7a4bda4 8053b767 8507c520 805c4a28 00000000 nt!KiInSwapKernelStacks+0x16
    f7a4bdac 805c4a28 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x89
    f7a4bddc 80540fa2 8053b6de 00000000 00000000 nt!PspSystemThreadStartup+0x34
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
     
  3. TheGlow

    TheGlow TS Rookie Topic Starter

    OK, It said disk locked in windows so I went to recovery. Took a while but finished, said it repaired one or more errors.
    So Ill have to mess around and see if it restarts cuz it was always random. gaming, chatting etc.
     
  4. TheGlow

    TheGlow TS Rookie Topic Starter

    No dice, had another BSOD,
    0x0000008E, 0xC0000005, 0xBFA33500, 0xB3697B60, 0x00000000
    and something about nv4_disp.dll, so trying to put new drivers in now for vid card
     
  5. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

  6. TheGlow

    TheGlow TS Rookie Topic Starter

    No wasnt the nvidia because I had turned on Azureus to dl a file and when the checking on the file would hit 100% it would BSOD. if i had a game open, it blamed nv4_disp.dll. If i had it open alone, it blamed ntfs.sys at 0x00000024.
    Swapped video drivers anyways, but still had a bsod when looking for a system restore point. Which I have none.
    getting ready to just reinstall windows, only been up a month so no real loss.
     
  7. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    It may be caused by bad RAM. Reseat the memory stick if you have only one memory stick. Take out one memory stick if you have more than one memory stick. If your windows does not crash, the removed RAM is faulty.
     
  8. TheGlow

    TheGlow TS Rookie Topic Starter

    I did a memtest for 40 mins, no problems. I have 2 sticks, i had them dual channel and switched them around to single channel and just had one a moment ago. ill try em 1 at a time next
    heres some more minidumps if you want a peek
     
  9. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Two of your latest dump has memory corruption at load module ntfs. Over 4000 bytes are corrupt. It may be corrupt by software driver or hardware. As you know it is very hard to determine the root cause if it is software problem.

    Suggestion
    1. De-install symantec
    2. Reseat memory stick
    3. Run memtest

    Mini073005-04.dmp
    BugCheck 1000008E, {c0000005, f737775a, ba2b2889, 0}

    *** WARNING: Unable to verify timestamp for SYMEVENT.SYS
    *** ERROR: Module load completed but symbols could not be loaded for SYMEVENT.SYS
    Probably caused by : memory_corruption
    STACK_TEXT:
    ba2b2954 f7341ae3 864fbce0 865eb710 804eec60 Ntfs!NtfsCommonFlushBuffers+0x7f
    ba2b29b8 804eddf9 84f84770 865eb710 866b1870 Ntfs!NtfsFsdFlushBuffers+0x92
    ba2b29c8 f73ba459 ba2b2a68 804eddf9 864ac498 nt!IopfCallDriver+0x31
    ba2b29d0 804eddf9 864ac498 865eb710 ba2b2a28 sr!SrPassThrough+0x31
    ba2b29e0 eb28f074 00000000 ba2b2a28 864d9ce8 nt!IopfCallDriver+0x31
    WARNING: Stack unwind information not available. Following frames may be wrong.
    ba2b2a68 8056afb9 8631af10 865eb710 864e1620 SYMEVENT+0xb074
    ba2b2ae4 8053c808 80000610 ba2b2b84 ba2b2dac nt!NtFlushBuffersFile+0x1c1
    ba2b2ae4 804fd889 80000610 ba2b2b84 ba2b2dac nt!KiFastCallEntry+0xf8
    ba2b2b64 805bc901 80000610 ba2b2b84 8653ca98 nt!ZwFlushBuffersFile+0x11
    ba2b2dac 805c4a28 ed8e25f0 00000000 00000000 nt!PopFlushVolumeWorker+0xf9
    ba2b2ddc 80540fa2 805bc808 ed8e25f0 00000000 nt!PspSystemThreadStartup+0x34
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    CHKIMG_EXTENSION: !chkimg -lo 50 -d !Ntfs
    f7377000-f737701d 30 bytes - Ntfs!NtfsSetAllocationInfo+b6
    [ a7 fc ff 89 45 c8 85 c0:15 70 de 32 f7 8b 4e 28 ]
    f737701f-f7377048 42 bytes - Ntfs!NtfsSetAllocationInfo+173 (+0x1f)
    [ 48 6a 00 68 02 01 00 c0:26 f6 46 04 80 74 12 ff ]
    f737704a-f7377062 25 bytes - Ntfs!NtfsSetAllocationInfo+1ea (+0x2b)
    [ 75 08 e8 45 93 fc ff 8d:15 f4 de 32 f7 83 7f 18 ]
    f7377064-f7377088 37 bytes - Ntfs!NtfsSetAllocationInfo+204 (+0x1a)
    [ 8b 45 e0 3b 46 1c 7f 12:3c 02 75 35 57 ff 15 50 ]
    f737708a-f73770b7 46 bytes - Ntfs!NtfsSetAllocationInfo+22a (+0x26)
    [ 00 00 8b 45 e0 89 86 0c:ff 75 10 53 57 8b 45 e0 ]
    f73770b9-f73770e0 40 bytes - Ntfs!NtfsSetAllocationInfo+3b1 (+0x2f)
    [ 4d d0 1b c8 51 57 50 52:03 3b c1 72 0f 8b 45 1c ]
    f73770e3-f7377110 46 bytes - Ntfs!NtfsSetAllocationInfo+400 (+0x2a)
    [ d0 89 46 1c 3b 46 24 7f:1c 83 20 00 c6 45 e7 00 ]
    f7377112-f7377134 35 bytes - Ntfs!NtfsSetAllocationInfo+42b (+0x2f)
    [ 01 00 00 0f 83 7b b9 fd:ff 30 ff 15 d8 da 32 f7 ]
    f7377136-f737714a 21 bytes - Ntfs!NtfsSetAllocationInfo+4b4 (+0x24)
    [ 89 4d ac 8b 80 10 01 00:ff 15 18 db 32 f7 eb 04 ]
    f737714c-f7377159 14 bytes - Ntfs!NtfsSetAllocationInfo+4ca (+0x16)
    [ 89 8d 6c ff ff ff 8b 4d:15 e0 de 32 f7 56 e8 eb ]
    f737715b-f7377168 14 bytes - Ntfs!NtfsSetAllocationInfo+4d9 (+0x0f)
    [ 8b 95 6c ff ff ff 0f ad:15 f4 de 32 f7 8b 4e 0c ]
    f737716a-f73771b1 72 bytes - Ntfs!NtfsSetAllocationInfo+4e8 (+0x0f)
    [ ff ff 89 85 38 ff ff ff:15 14 db 32 f7 8a 45 e7 ]
    f73771b4-f73771fb 72 bytes - Ntfs!NtfsFlushAndPurgeScb+91 (+0x4a)
    [ 50 57 e8 89 40 fa ff 90:6a 50 8d 46 08 50 56 ff ]
    f73771fe-f7377244 71 bytes - Ntfs!NtfsFlushVolume+38 (+0x4a)
    [ c0 57 e9 5a 03 00 00 80:00 8d 45 b4 50 ff 75 08 ]
    f7377246-f7377255 16 bytes - Ntfs!NtfsFlushVolume+13b (+0x48)
    [ 01 53 57 56 e8 b6 f3 fb:0c 59 33 c0 8d 7d 84 f3 ]
    f7377257-f737727e 40 bytes - Ntfs!NtfsFlushVolume+23d (+0x11)
    [ e9 00 03 00 00 68 e9 00:53 53 53 53 53 6a 10 8d ]
    f7377280-f73772d9 90 bytes - Ntfs!NtfsFlushVolume+28c (+0x29)
    [ ac ff 75 ac 51 ff 75 08:8c 0f b7 70 14 03 f0 6a ]
    f73772db-f73772df 5 bytes - Ntfs!NtfsFlushVolume+2e2 (+0x5b)
    [ 75 0c ff 75 08:e8 14 00 00 00 ]
    f73772e1-f7377304 36 bytes - Ntfs!NtfsFlushVolume+2e8 (+0x06)
    [ 7f 0a 02 00 89 5d ac 89:9b 80 f9 ff c2 0c 00 90 ]
    f7377306-f7377337 50 bytes - Ntfs!NtfsFlushVolume+309 (+0x25)
    [ 48 0c 39 19 0f 95 45 de:45 84 50 ff 75 08 e8 08 ]
    f7377339-f7377352 26 bytes - Ntfs!NtfsFlushVolume+338 (+0x33)
    [ 15 20 dc 32 f7 84 c0 0f:75 10 57 ff 15 4c da 32 ]
    f7377354-f7377377 36 bytes - Ntfs!NtfsFlushVolume+34b (+0x1b)
    [ 00 c0 e9 13 46 fe ff 80:81 7d 10 00 00 01 00 0f ]
    f7377379-f737738f 23 bytes - Ntfs!NtfsFlushVolume+386 (+0x25)
    [ 39 5d ac 0f 85 10 46 fe:15 1c db 32 f7 89 5d bc ]
    f7377391-f73773e9 89 bytes - Ntfs!NtfsFlushVolume+39e (+0x18)
    [ fe ff 39 58 40 0f 84 f6:bc 89 45 cc 8b 07 89 45 ]
    f73773eb-f7377401 23 bytes - Ntfs!NtfsFlushVolume+3e4 (+0x5a)
    [ 08 e8 40 1f fb ff c3 90:06 83 65 e0 00 eb 07 c7 ]
    f7377404-f737742f 44 bytes - Ntfs!NtfsFlushVolume+3f8 (+0x19)
    [ 60 05 fe 89 5d ac 39 58:39 47 04 7f 12 7c 04 39 ]
    f7377431-f7377460 48 bytes - Ntfs!NtfsFlushVolume+492 (+0x2d)
    [ 45 ec 8b 08 ff 31 50 ff:4e 1c 89 55 c0 89 4d c4 ]
    f7377462-f7377463 2 bytes - Ntfs!NtfsFlushVolume+4be (+0x31)
    [ 5d fc:46 1c ]
    f7377465-f73774e9 133 bytes - Ntfs!NtfsFlushVolume+4c1 (+0x03)
    [ 7d d8 e9 84 45 fe ff 83:4e 28 ff 15 f4 de 32 f7 ]
    f73774eb-f7377530 70 bytes - Ntfs!NtfsFlushVolume+614 (+0x86)
    [ e9 68 46 fe ff 6a 01 53:75 10 8d 45 d0 50 57 8b ]
    f7377533-f737762a 248 bytes - Ntfs!NtfsFlushVolume+69f (+0x48)
    [ 56 ff 75 08 e8 09 e8 fe:8d 4d d0 51 50 57 ff 15 ]
    f737762c-f7377657 44 bytes - Ntfs!NtfsFlushVolume+836 (+0xf9)
    [ d0 1b 00 00 c0 e9 73 46:e7 e8 4e 7d f9 ff c2 1c ]
    f7377659-f7377672 26 bytes - Ntfs!NtfsFlushVolume+8b7 (+0x2d)
    [ 46 28 3b c3 74 23 6a 01:91 b4 00 00 00 33 f6 66 ]
    f7377674-f7377719 166 bytes - Ntfs!NtfsFlushVolume+8d2 (+0x1b)
    [ 8b 46 28 ff 70 48 ff 75:66 09 70 0e 8b 91 80 00 ]
    f737771b-f7377765 75 bytes - Ntfs!NtfsFlushVolume+984 (+0xa7)
    [ 75 d8 ff 75 08 e8 2d f1:8b 55 08 56 75 0c 66 8b ]
    f7377767-f73777f9 147 bytes - Ntfs!NtfsCommonFlushBuffers+8c (+0x4c)
    [ 8b 45 d4 3b c3 74 05 0f:55 8b ec 66 8b 55 0c 8b ]
    f73777fb-f737783f 69 bytes - Ntfs!NtfsCommonFlushBuffers+2fa (+0x94)
    [ c4 0f 85 cc a3 fc ff e9:d4 3b c3 0f 84 0a 02 00 ]
    f7377841-f7377873 51 bytes - Ntfs!NtfsCommonFlushBuffers+37a (+0x46)
    [ 53 53 ff 75 e0 56 e8 f8:15 64 de 32 f7 53 53 53 ]
    f7377875-f73778b8 68 bytes - Ntfs!NtfsFsdFlushBuffers+80 (+0x34)
    [ 75 e4 e8 29 86 01 00 e9:89 86 78 07 00 00 8d 86 ]
    f73778ba-f737794a 145 bytes - Ntfs!NtfsFsdFlushBuffers+cc (+0x45)
    [ 00 c0 74 ae 81 ff 88 01:c0 e9 88 00 00 00 8b 4e ]
    f737794c-f7377961 22 bytes - Ntfs!NtfsSetAndGetVolumeTimes+da (+0x92)
    [ 08 e8 12 04 02 00 e9 00:09 38 5d e7 74 04 80 4e ]
    f7377964-f73779a5 66 bytes - Ntfs!NtfsInitializeSecurityFile+73 (+0x18)
    [ ff 15 50 de 32 f7 8d 45:90 90 90 90 90 33 db 8b ]
    f73779a7-f73779d3 45 bytes - Ntfs!NtfsUpgradeSecurity+138 (+0x43)
    [ ff ff ff 83 c7 42 89 bd:de 32 f7 38 5d e5 74 0c ]
    f73779d5-f7377a0b 55 bytes - Ntfs!NtfsUpgradeSecurity+166 (+0x2e)
    [ 8c 50 56 ff 77 10 6a 01:08 f6 40 0a 04 74 11 8b ]
    f7377a0d-f7377a18 12 bytes - Ntfs!NtfsUpgradeSecurity+204 (+0x38)
    [ ff ff 50 53 53 53 53 53:c3 be 22 00 00 c0 56 ff ]
    f7377a1a-f7377a58 63 bytes - Ntfs!NtfsUpgradeSecurity+211 (+0x0d)
    [ 50 56 ff 75 88 e8 ef 4d:e8 99 7c f9 ff 8b c6 e8 ]
    f7377a5a-f7377a7b 34 bytes - Ntfs!NtfsUpgradeSecurity+251 (+0x40)
    [ ff ff 50 6a 50 56 ff 75:8b 45 0c 85 c0 74 19 f6 ]
    f7377a7e-f7377a81 4 bytes - Ntfs!NtfsUpgradeSecurity+275 (+0x24)
    [ 00 f6 46 05:c0 57 ff 75 ]
    f7377a83-f7377a90 14 bytes - Ntfs!NtfsUpgradeSecurity+27a (+0x05)
    [ 75 09 56 ff 75 88 e8 0b:e8 30 7c f9 ff b8 22 00 ]
    f7377a92-f7377bd4 323 bytes - Ntfs!NtfsUpgradeSecurity+289 (+0x0f)
    [ 00 00 8b 07 39 58 08 75:90 90 90 90 90 8b ff 55 ]
    WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view entire output.
    4005 errors : !Ntfs (f7377000-f7377fff)

    MODULE_NAME: memory_corruption
    IMAGE_NAME: memory_corruption
    FOLLOWUP_NAME: memory_corruption
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    MEMORY_CORRUPTOR: LARGE_4096
    STACK_COMMAND: .trap ffffffffba2b2889 ; kb
    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE_4096
    BUCKET_ID: MEMORY_CORRUPTION_LARGE_4096

    Followup: memory_corruption
     
  10. TheGlow

    TheGlow TS Rookie Topic Starter

    Ill try the symantec.
    I did reset the rams.
    I put Stick1 was in bank 1, stick 2 in bank2, I moved stick 2 to bank1, and stick 1 to bank3, disabling dual channel. It then did it on that last one.
    And i just ran memtest, 3 and half hours, 8 passes, 0 errors.

    Ah just turned off symantec, played a game, finished with game, closed game, desktop pops up, BSOD.
     
  11. urbandragon

    urbandragon TS Rookie Posts: 231

    did you try removing 1 stick of ram. your problem may be due to a single faulty memory module... and as you will see in some of the other posts memtest is not 100% accurate.

    try removing both sticks and trying them 1 at a time.
     
  12. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    The latest dump is also has 4077 bytes corruption at !ks
     
  13. TheGlow

    TheGlow TS Rookie Topic Starter

    Well I made another partition to xfer some files to before I reinstall windows.
    Now when I copy files over from C: to G: it ALWAYS BSOD's within 4 minutes.
    I did it with mem stick 1 alone, it BSOD. I did mem stick 2 alone and BSOD.
    So Unless both sticks are bad, I guess we can rule that out.
     
  14. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Your windows has over 4000 bytes are overlaid. Maybe it is device driver error. It is impossible to trace which device driver is bad as the overlay pattern is random. Re-install Windows may resolve the problem
     
  15. TheGlow

    TheGlow TS Rookie Topic Starter

    Im in the middle of that now. I went through 9 more BSODs to xfer my files over. But now im done, formatted C long version, and setup is up to stage 4 : installing windows.
    Im at work tonight, overnight shift, nice n slow. as long as I can have it up n functional by 11 to play games, i dont mind.

    All up n running, copied files and BSOD again...
     
  16. TheGlow

    TheGlow TS Rookie Topic Starter

    From what I can now tell my 2nd hdd is corrupted. Chkdsk fails each time. I have pagefile set to use that drive as well. Since ive left paging onto the other drive, no bsods.
     
  17. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Maybe bad pagegfile is the culprit as you have three mnidumps crashed with bugcheck code 77
    Bug Check 0x77: KERNEL_STACK_INPAGE_ERROR
    The KERNEL_STACK_INPAGE_ERROR bug check has a value of 0x00000077. This indicates that the requested page of kernel data from the paging file could not be read into memory.

    Mini072805-02.dmp 77 (00000001, 00000000, 00000000, ee82595c) nt!Mini072905-01.dmp 77 (00000001, 00000000, 00000000, b500ac70) nt!
    Mini072905-02.dmp 77 (00000001, 006c0069, 00000000, b9e50ca0) nt!
     
  18. puree

    puree TS Rookie

    Kernel_stack_inpage_error

    hi everyone! i'm new here.

    my PC needs a doctor. please help.

    blue screen always appear. either PAge_fault_in_nonpaged_arae or kernel_stack_inpage_error.

    and disk read error occured
    press Ctrl+alt+del


    i'm having difficulty restarting my PC....on the screen.....we appologize for inconvenience, but windows did not start succesfully. A recent hardware or software changes might have caused this.

    then several choices follows such sa Safe mode, start windows normally etc.

    my friend will just reformat the whole thing and then when i start insatlling applications, things will happen again.

    what should i do?

    i really dont know anything about PC.thanks. hope you can help me.

    please write the step by step procedure.thanks again
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...