BSOD with new install of WIN7 Pro 64, error 0x00000101

Page 2 of 2 FirstFirst 12
  1.    #11

    They're fine, and upload the Minidumps, they will be suffice with any BSODs caused by Driver Verifier.

    Code:
    C:\Windows\Minidump
    You can upload these in a zipped folder straight to the forum.
      My Computer


  2. Posts : 10
    Windows 7 Professional 64
    Thread Starter
       #12

    Ahh thank you very much. I've attached all the minidumps from the 14th until now. There are more if needed but the 13th is when I re-enabled the verifier.
      My Computer

  3.    #13

    The dumps didn't reveal much, apart from almost all being Stop 0x4Es:


    Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

    Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

    Test each RAM stick and every motherboard DIMM slot available.

    Arc said:
    No code has to be inserted here. It is a RAM, a bad RAM.

    But if you have got a result like that:
    No code has to be inserted here. It is a motherboard issue. The particular slot is bad.
      My Computer


  4. Posts : 10
    Windows 7 Professional 64
    Thread Starter
       #14

    DO you need me to run it again? I ran it for 13 passes with no errors just a few days ago.
      My Computer

  5.    #15

    No sorry I forgot that, and this may be a more viable option:

    Run some hard-drive diagnostics and follow these steps:

    Find your hard-drive manufacturer and run their tests.

    Additional Tests:

    Post a screenshot of Crystal Disk Info summary:

    writhziden said:
    If you have an SSD, make sure the following are up to date:
    • SSD firmware
    • BIOS Version
    • Chipset Drivers
    • Hard disk controller drivers/SATA drivers
    • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
    Check for any file system errors and bad sectors using Option #2 of:

    Use this command with Disk Check:

    Code:
    chkdsk C: /f /r
      My Computer


  6. Posts : 10
    Windows 7 Professional 64
    Thread Starter
       #16

    Well I finally finished running the hard drive tests. There were no errors on any of them. Frustrated, I reloaded Windows XP. Odd that it doesn't crash when I run XP. Do you have any thoughts on that? Is it something wrong with Windows 7 itself? If so is there a patch for that?
      My Computer

  7.    #17

    It's most likely not actually Windows 7, but most likely how something is interacting with the operating system.

    You could have ran this (see below) with Windows 7 -

    Scan for any missing, modified or corrupted protected Windows files with:
      My Computer


  8. Posts : 10
    Windows 7 Professional 64
    Thread Starter
       #18

    Well I ran the sfc /scannow. The first 4 times I tried to run it, I got the BSOD. That was using "Option 2." Then I put my install disk and tried "Option 1." The first try resulted in a BSOD. The second returned "Windows Resource Protection did not find any integrity violations."
      My Computer

  9.    #19

    Could you please upload the new BSODs?
      My Computer


 
Page 2 of 2 FirstFirst 12

  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 07:08.
Find Us