BSoD at startup

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by cristi92b, Aug 2, 2011.

  1. cristi92b

    cristi92b New Member

    Joined:
    Aug 2, 2011
    Messages:
    44
    Likes Received:
    0
    Btw, I know a friend who has the same CPU, same mobo, same graphic card, same PSU, same bios version, and he has no problem, no bsod.
     
    #21 cristi92b, Aug 4, 2011
    Last edited: Aug 4, 2011
  2. zigzag3143

    zigzag3143 Honorable Member
    Microsoft MVP

    Joined:
    Jun 2, 2009
    Messages:
    812
    Likes Received:
    115


    Most recent crash was Related to VMparport.sys parallel port driver from VMware Inc, Inc.



    I would remove the vmware at least to test.
     
  3. cristi92b

    cristi92b New Member

    Joined:
    Aug 2, 2011
    Messages:
    44
    Likes Received:
    0
    I think I will install Windows 7 again.
     
  4. zigzag3143

    zigzag3143 Honorable Member
    Microsoft MVP

    Joined:
    Jun 2, 2009
    Messages:
    812
    Likes Received:
    115
    Great idea, it usually will fix software problems and may in fact be faster.
     
  5. cristi92b

    cristi92b New Member

    Joined:
    Aug 2, 2011
    Messages:
    44
    Likes Received:
    0
    I won't be at home for the next week so I will post again when I will return.
     
  6. zigzag3143

    zigzag3143 Honorable Member
    Microsoft MVP

    Joined:
    Jun 2, 2009
    Messages:
    812
    Likes Received:
    115

    Understood let us know.
     
  7. cristi92b

    cristi92b New Member

    Joined:
    Aug 2, 2011
    Messages:
    44
    Likes Received:
    0
    I returned and I have new minidumps.
     

    Attached Files:

  8. zigzag3143

    zigzag3143 Honorable Member
    Microsoft MVP

    Joined:
    Jun 2, 2009
    Messages:
    812
    Likes Received:
    115
    This is a very unusal BCC. I have only seen it one other time. As a first step I suggest you upgrade to SP-1. If SP-1 doesnt fix the problem I would run CHKDSK as described below. If that doesnt help you may want to start thinking about a clean install.

    This bug check results from a serious error in a driver or other system file. The file header checksum does not match the expected checksum.
    This can also be caused by faulty hardware in the I/O path to the file (a disk error, faulty RAM, or a corrupted page file).


    To remedy this error, run the Emergency Recovery Disk (ERD) and allow the system to repair or replace the missing or damaged driver file on the system partition.

    You can also run an in-place upgrade over the existing copy of Windows. This preserves all registry settings and configuration information, but replaces all system files. If any Service Packs and/or hotfixes had previously been applied, you need to reinstall them afterward in the appropriate order (latest Service Pack, then any post-Service Pack hotfixes in the order in which they were originally installed, if applicable).

    If a specific file was identified in the bug check message as being corrupted, you can try replacing that individual file manually. I


    If you want to replace the file on a single-boot system with an NTFS partition, you need to restart the system, press F8 at the operating system Loader menu, and choose Safe Mode with Command Prompt. From there, copy a fresh version of the file from the original source onto the hard disk. If the file is used as part of the system startup process in Safe Mode, you need to start the computer using the Recovery Console in order to access the file. If these methods fail, try reinstalling Windows and then restoring the system from a backup.

    Note If the original file from the product CD has a filename extension ending in an _ (underscore), the file needs to be uncompressed before it can be used. The Recovery Console's Copy command automatically detects compressed files and expands them as they are copied to the target location. If you are using Safe Mode to access a drive, use the Expand command to uncompress and copy the file to the target folder. You can use the Expand command in the command line environment of Safe Mode.
    Resolving a disk error problem: Disk errors can be a source of file corruption. Run Chkdsk /f /r to detect and resolve any file system structural corruption. You must restart the system before the disk scan begins on a system partition.
    Resolving a RAM problem: If the error occurred immediately after RAM was added to the system, the paging file might be corrupted or the new RAM itself might be either faulty or incompatible.
    To determine if newly added RAM is causing a bug check


    1. Return the system to the original RAM configuration.
    2. Use the Recovery Console to access the partition containing the paging file and delete the file pagefile.sys.
    3. While still in the Recovery Console, run Chkdsk /r on the partition that contained the paging file.
    4. Restart the system.
    5. Set the paging file to an optimal level for the amount of RAM added.
    6. Shutdown the system and add your RAM. The new RAM must meet the system manufacturer's specifications for speed, parity, and type (that is, fast page-mode (FPM) versus extended data out (EDO) versus synchronous dynamic random access memory (SDRAM)). Try to match the new RAM to the existing installed RAM as closely as possible. RAM can come in many different capacities, and more importantly, in different formats (single inline memory modules -- SIMM -- or dual inline memory modules -- DIMM). The electrical contacts can be either gold or tin and it is not wise to mix these contact types.
    If you experience the same error message after reinstalling the new RAM, run hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer.
    When you can log on to the system again, check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error.
    Disabling memory caching of the BIOS might also resolve this error.
     
    #28 zigzag3143, Aug 14, 2011
    Last edited: Aug 14, 2011
    2 people like this.
  9. cristi92b

    cristi92b New Member

    Joined:
    Aug 2, 2011
    Messages:
    44
    Likes Received:
    0
    Thank you very much!
     
  10. zigzag3143

    zigzag3143 Honorable Member
    Microsoft MVP

    Joined:
    Jun 2, 2009
    Messages:
    812
    Likes Received:
    115
    My pleasure and let us know if you are still having problems.
     
  11. cristi92b

    cristi92b New Member

    Joined:
    Aug 2, 2011
    Messages:
    44
    Likes Received:
    0
    Do you think that replacing the memory could solve this?
     
  12. nmsuk

    nmsuk Windows Forum Admin
    Staff Member Premium Supporter

    Joined:
    Sep 7, 2009
    Messages:
    2,694
    Likes Received:
    194
    It could do you know anyone you could borrow some off to test with?
     
  13. cristi92b

    cristi92b New Member

    Joined:
    Aug 2, 2011
    Messages:
    44
    Likes Received:
    0
    No... I will buy new RAM.
     
  14. nmsuk

    nmsuk Windows Forum Admin
    Staff Member Premium Supporter

    Joined:
    Sep 7, 2009
    Messages:
    2,694
    Likes Received:
    194
    Check the mobo page for your manufacturer for compatible ram before buying :) Good luck
     

Share This Page

Loading...