Random BSOD crashes periodically

Page 1 of 3 123 LastLast

  1. Posts : 12
    MS Windows 7 Ultimate 64-bit
       #1

    Random BSOD crashes periodically


    After upgrading from Visa 64bit to Windows 7 64bit, I average 3-4 BSODs a week. I have ran memory tests and a disk check, both of which completed with no issue.
    Last edited by jdbkrb; 08 Mar 2010 at 21:54. Reason: forgot to attach BSOD dump files
      My Computer


  2. Posts : 5,705
    Win7 x64 + x86
       #2

    What memory test did you run - and what sort of disk check?
    Please run the following free diagnostics if you haven't run these tests:
    H/W Diagnostics:
    Please start by running these bootable hardware diagnostics:
    Memory Diagnostics (read the details at the link)
    HD Diagnostic (read the details at the link)

    Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
    23 memory dumps uploaded, all appear to be STOP 0x50's (more info on the error here: BSOD Index )
    They were generated between 8 Feb and 27 Feb 2010
    They blame NTFS.sys for causing the problem - so running the hard drive diagnostic described above is essential. Also, run CHKDSK /R if you haven't run it already:
    CHKDSK /R /F:
    Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
    When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

    Elevated Command Prompt:
    Go to Start and type in "cmd.exe" (without the quotes)
    At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

    CHKDSK LogFile:
    Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
    Expand the Windows logs heading, then select the Application log file entry.
    Double click on the Source column header.
    Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
    Copy/paste the results into your next post.
    Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
    Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:
    How To Find Drivers:
    - search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
    - - The most common drivers are listed on this page: Driver Reference
    - - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

    Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:
    Code:
    agrsm64.sys  Mon Nov 10 10:01:35 2008 - Agere Systems Soft Modem - http://www.carrona.org/dvrref.html#agrsm64.sys
    RTL85n64.sys Fri May 09 03:30:24 2008 - Realtek 8185 Extensible 802.1b/g driver - http://www.carrona.org/dvrref.html#RTL85n64.sys
    Summary of the BSOD's:
    Code:
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Feb  9 00:44:10.339 2010 (GMT-5)
    System Uptime: 0 days 0:47:53.430
    BugCheck 50, {fffff8a114619538, 0, fffff8800122d2bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  wmplayer.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Mon Feb  8 21:25:57.622 2010 (GMT-5)
    System Uptime: 0 days 17:07:34.486
    BugCheck 50, {fffff8a10e32fcc8, 0, fffff880012262bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  wmplayer.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Feb  9 08:32:48.434 2010 (GMT-5)
    System Uptime: 0 days 7:26:23.151
    BugCheck 50, {fffff8a11a693968, 0, fffff880012132bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  wmplayer.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Feb  9 15:08:21.693 2010 (GMT-5)
    System Uptime: 0 days 1:05:55.410
    BugCheck 50, {fffff8a11c95f462, 0, fffff880010562bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  ehshell.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Feb  9 14:00:51.081 2010 (GMT-5)
    System Uptime: 0 days 5:19:39.172
    BugCheck 50, {fffff8a11b6f44b8, 0, fffff8800120c2bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  wmplayer.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Feb  9 15:13:10.339 2010 (GMT-5)
    System Uptime: 0 days 0:03:30.430
    BugCheck 50, {fffff8a10c1100a2, 0, fffff8800121f2bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  ehshell.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Feb  9 01:04:45.795 2010 (GMT-5)
    System Uptime: 0 days 0:18:51.512
    BugCheck 50, {fffff8a10b5ef6e8, 0, fffff8800122e2bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  wmplayer.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Thu Feb 11 20:41:37.778 2010 (GMT-5)
    System Uptime: 0 days 4:12:30.870
    BugCheck 50, {fffff8a121e3ec08, 0, fffff880012242bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  wmplayer.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sat Feb 13 14:54:55.931 2010 (GMT-5)
    System Uptime: 1 days 10:29:28.813
    BugCheck 50, {fffff8a1039e4cd8, 0, fffff8800123c2bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  wmplayer.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sat Feb 13 23:55:38.585 2010 (GMT-5)
    System Uptime: 0 days 8:57:35.403
    BugCheck 50, {fffff8a10f08a7b8, 0, fffff880012122bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  wmplayer.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sun Feb 14 15:03:41.499 2010 (GMT-5)
    System Uptime: 0 days 14:21:16.723
    BugCheck 50, {fffff8a1191e2a68, 0, fffff8800121e2bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  wmplayer.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Mon Feb 15 06:16:12.100 2010 (GMT-5)
    System Uptime: 0 days 15:11:01.817
    BugCheck 50, {fffff8a1181de4b8, 0, fffff8800120b2bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  wmplayer.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Wed Feb 17 22:02:44.455 2010 (GMT-5)
    System Uptime: 0 days 9:54:05.546
    BugCheck 50, {fffff8a11550c608, 0, fffff8800123d2bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  wmplayer.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Feb 16 16:25:13.126 2010 (GMT-5)
    System Uptime: 0 days 0:04:34.217
    BugCheck 50, {fffff8a10a1b9aa8, 0, fffff880012142bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  wmpnetwk.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Thu Feb 18 15:49:19.757 2010 (GMT-5)
    System Uptime: 0 days 2:35:44.849
    BugCheck 50, {fffff8a10fdb4828, 0, fffff8800125f2bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  wmplayer.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Thu Feb 18 21:15:59.068 2010 (GMT-5)
    System Uptime: 0 days 5:24:55.785
    BugCheck 50, {fffff8a1090a5be8, 0, fffff8800124a2bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  wmplayer.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Thu Feb 18 13:11:23.155 2010 (GMT-5)
    System Uptime: 0 days 15:06:35.262
    BugCheck 50, {fffff8a1139b7828, 0, fffff880012182bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  wmplayer.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Thu Feb 25 20:59:55.949 2010 (GMT-5)
    System Uptime: 0 days 0:06:57.666
    BugCheck 50, {fffff8a10d7b75b8, 0, fffff8800101f2bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  wmplayer.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Thu Feb 25 20:51:03.999 2010 (GMT-5)
    System Uptime: 1 days 0:53:50.716
    BugCheck 50, {fffff8a10de57d68, 0, fffff880012242bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  wmplayer.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Fri Feb 26 15:53:51.811 2010 (GMT-5)
    System Uptime: 0 days 4:26:47.903
    BugCheck 50, {fffff8a10f653188, 0, fffff8800121d2bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  wmplayer.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Fri Feb 26 16:06:20.445 2010 (GMT-5)
    System Uptime: 0 days 0:10:29.162
    BugCheck 50, {fffff8a10ff79588, 0, fffff880010652bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  wmpnetwk.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sat Feb 27 21:54:33.161 2010 (GMT-5)
    System Uptime: 0 days 0:28:31.252
    BugCheck 50, {fffff8a10d8be744, 0, fffff880012212bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  ehshell.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sat Feb 27 21:24:12.642 2010 (GMT-5)
    System Uptime: 0 days 3:10:08.733
    BugCheck 50, {fffff8a10ac50d68, 0, fffff8800121d2bd, 5}
    Probably caused by : Ntfs.sys ( Ntfs!memmove+2d )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  wmplayer.exe
      My Computer


  3. Posts : 12
    MS Windows 7 Ultimate 64-bit
    Thread Starter
       #3

    Hey John,

    I really appreciate all the assistance. I am in the process of running all the tests and performing recommended fixes. I will let you know what I find.


    Thanks Again,

    Jb
      My Computer


  4. Posts : 5,705
    Win7 x64 + x86
       #4

    Not a problem - I'll get notified when you post to this thread so I can come back to see what's going on.
      My Computer


  5. Posts : 12
    MS Windows 7 Ultimate 64-bit
    Thread Starter
       #5

    Here is the results from the CHKDSK, I am working through the other possible solutions at this time.

    Log Name: Application
    Source: Microsoft-Windows-Wininit
    Date: 3/12/2010 9:19:55 PM
    Event ID: 1001
    Task Category: None
    Level: Information
    Keywords: Classic
    User: N/A
    Computer: JBsPowerPc
    Description:


    Checking file system on C:
    The type of the file system is NTFS.
    Volume label is OS.

    WARNING! C parameter specified.
    Your drive may still be corrupt even after running CHKDSK.

    A disk check has been scheduled.
    Windows will now check the disk.

    CHKDSK is verifying files (stage 1 of 5)...
    329472 file records processed.

    File verification completed.
    368 large file records processed.

    0 bad file records processed.

    4 EA records processed.

    132 reparse records processed.

    CHKDSK is verifying indexes (stage 2 of 5)...
    444918 index entries processed.

    Index verification completed.
    0 unindexed files scanned.

    0 unindexed files recovered.

    CHKDSK is verifying security descriptors (stage 3 of 5)...
    329472 file SDs/SIDs processed.

    Cleaning up 75 unused index entries from index $SII of file 0x9.
    Cleaning up 75 unused index entries from index $SDH of file 0x9.
    Cleaning up 75 unused security descriptors.
    Security descriptor verification completed.
    57724 data files processed.

    CHKDSK is verifying Usn Journal...
    36377640 USN bytes processed.

    Usn Journal verification completed.
    CHKDSK is verifying file data (stage 4 of 5)...
    329456 files processed.

    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
    159868494 free clusters processed.

    Free space verification is complete.
    Windows has checked the file system and found no problems.

    961399807 KB total disk space.
    321296108 KB in 266741 files.
    167108 KB in 57725 indexes.
    0 KB in bad sectors.
    462615 KB in use by the system.
    65536 KB occupied by the log file.
    639473976 KB available on disk.

    4096 bytes in each allocation unit.
    240349951 total allocation units on disk.
    159868494 allocation units available on disk.

    Internal Info:
    00 07 05 00 78 f3 04 00 a1 27 09 00 00 00 00 00 ....x....'......
    cc 17 00 00 84 00 00 00 00 00 00 00 00 00 00 00 ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

    Windows has finished checking your disk.
    Please wait while your computer restarts.

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-03-13T03:19:55.000000000Z" />
    <EventRecordID>4185</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>JBsPowerPc</Computer>
    <Security />
    </System>
    <EventData>
    <Data>

    Checking file system on C:
    The type of the file system is NTFS.
    Volume label is OS.

    WARNING! C parameter specified.
    Your drive may still be corrupt even after running CHKDSK.

    A disk check has been scheduled.
    Windows will now check the disk.

    CHKDSK is verifying files (stage 1 of 5)...
    329472 file records processed.

    File verification completed.
    368 large file records processed.

    0 bad file records processed.

    4 EA records processed.

    132 reparse records processed.

    CHKDSK is verifying indexes (stage 2 of 5)...
    444918 index entries processed.

    Index verification completed.
    0 unindexed files scanned.

    0 unindexed files recovered.

    CHKDSK is verifying security descriptors (stage 3 of 5)...
    329472 file SDs/SIDs processed.

    Cleaning up 75 unused index entries from index $SII of file 0x9.
    Cleaning up 75 unused index entries from index $SDH of file 0x9.
    Cleaning up 75 unused security descriptors.
    Security descriptor verification completed.
    57724 data files processed.

    CHKDSK is verifying Usn Journal...
    36377640 USN bytes processed.

    Usn Journal verification completed.
    CHKDSK is verifying file data (stage 4 of 5)...
    329456 files processed.

    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
    159868494 free clusters processed.

    Free space verification is complete.
    Windows has checked the file system and found no problems.

    961399807 KB total disk space.
    321296108 KB in 266741 files.
    167108 KB in 57725 indexes.
    0 KB in bad sectors.
    462615 KB in use by the system.
    65536 KB occupied by the log file.
    639473976 KB available on disk.

    4096 bytes in each allocation unit.
    240349951 total allocation units on disk.
    159868494 allocation units available on disk.

    Internal Info:
    00 07 05 00 78 f3 04 00 a1 27 09 00 00 00 00 00 ....x....'......
    cc 17 00 00 84 00 00 00 00 00 00 00 00 00 00 00 ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

    Windows has finished checking your disk.
    Please wait while your computer restarts.
    </Data>
    </EventData>
    </Event>
      My Computer


  6. Posts : 12
    MS Windows 7 Ultimate 64-bit
    Thread Starter
       #6

    Also it might be important to know, I have a 1TB WD MyBook essentials external hard drive that stays connected to the pc. Is there anything on it that could be causing the problem?
      My Computer


  7. Posts : 12
    MS Windows 7 Ultimate 64-bit
    Thread Starter
       #7

    Ok, here is an update:

    I was able to find and install update for Realtek 8185 Extensible 802.1b/g driver I deleted the original driver and installed the new one from the downloaded file.

    I did not see any update for
    Agere Systems Soft ModemSo I left driver as is.

    I will try out PC over the next couple of days and report if the problem persist. Hopefully you have solved all my problems and frustrations.


    Thank you very much.

    I'll keep you informed.
      My Computer


  8. Posts : 5,705
    Win7 x64 + x86
       #8

    No problems with the chkdsk.
    If the tests don't point anything out we've still got a few more tricks up our sleeves.
    Good luck!
      My Computer


  9. Posts : 12
    MS Windows 7 Ultimate 64-bit
    Thread Starter
       #9

    Seems like something is still wrong, here is the latest BSOD dump
      My Computer


  10. Posts : 28,845
    Win 8 Release candidate 8400
       #10

    jdbkrb said:
    Seems like something is still wrong, here is the latest BSOD dump

    Sorry but the BSOD file is corrupt. try uploading it again. BTW it should be in the form of *.dmp NOT a text file


    Ken
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 19:52.
Find Us