Constant crashes

Page 2 of 2 FirstFirst 12

  1. Posts : 8
    Windows 7 HomePremium 64 bit
    Thread Starter
       #11

    Now i've got a real problem; I can't login to any of my Windows installs now (currently in my Linux distro). Bluescreens after the splash screen, just before windows actually loads. I am getting an odd notice at the bottom of the screen at that point, something about a ROM error I believe the exact wording was: "Warning: Have option ROM cannot be invoke", whatever the hell that means. Basically I'm screwed here: I can't access my system in normal or safe mode which means I can;t even get to the dump files to offer them as a tool to diagnose the problem. I'm desperate here, any help at all would be amazing, thanks.
      My Computer


  2. Posts : 13,354
    Windows 7 Professional x64
       #12

    Try a system restore from the repair or install disc.
      My Computer


  3. Posts : 263
    Dual boot XP Pro SP3x86 and Win7 Pro x64
       #13

    At this point I am not clear as to what you are able to access and is it the issue related to your OS, BIOS (ROM error), or ODD (ROM error). It appears that you would like to avoid a clean install.

    Again, not knowing what works and does not, one route you can take, if only as a diagnostic step, is to boot to the BIOS setup, select you other ("storage") HDD as the boot drive and boot from the Windows disc. Then install Windows on that HDD.

    Once accomplished you have full access to your original boot drive which you can check for errors, read log/dmp files, etc. as a means of trying to figure out what is going on. If all else fails, you can recover (copy) files that are not part of the OS per se (e.g., FF profile, IE bookmarks, Outlook *.pst, DT files, saved games, etc.) which would be lost if you have to accomplish a clean install. I used this technique for many years dual booting 2000/XP much to my relief. Another less precise option would be to boot with a Linux boot disc (I'm thinking primarily of Knoppix which is based on the Debian platform). If you are able to repair you present OS, then go back to the BIOS, reset it as the boot disk and then delete the trial install from your storage disk.

    I mention this only because I ask myself, "Why not just do a clean install?" Perhaps I am missing something.

    Monk
      My Computer


  4. Posts : 8
    Windows 7 HomePremium 64 bit
    Thread Starter
       #14

    So, now I had manged to reinstall Windows, again, and had it running for a few days with no issues. By the way, I flashed the BIOS to the latest version provided by XFX. I have installed all the most up to date drivers for my components directly from the manufacturers. Now I'm getting a bluescreen immediately after boot, right before the Windows login appears (page fault in non paged area) this time. It also failed to boot at all once, presenting 5 beeps at POST and crashing right away without presenting a bluescreen at all. At this point I am at a complete and total loss; it HAS to be the windows install somehow as there are absolutely zero issues when I am using Linux. Beyond that, I haven't got a clue. I hate to say this but I think I'll just go back to Vista, that ran for 2 years without this crap happening.
      My Computer


  5. Posts : 8
    Windows 7 HomePremium 64 bit
    Thread Starter
       #15

    HMonk said:
    At this point I am not clear as to what you are able to access and is it the issue related to your OS, BIOS (ROM error), or ODD (ROM error). It appears that you would like to avoid a clean install.

    Again, not knowing what works and does not, one route you can take, if only as a diagnostic step, is to boot to the BIOS setup, select you other ("storage") HDD as the boot drive and boot from the Windows disc. Then install Windows on that HDD.

    Once accomplished you have full access to your original boot drive which you can check for errors, read log/dmp files, etc. as a means of trying to figure out what is going on. If all else fails, you can recover (copy) files that are not part of the OS per se (e.g., FF profile, IE bookmarks, Outlook *.pst, DT files, saved games, etc.) which would be lost if you have to accomplish a clean install. I used this technique for many years dual booting 2000/XP much to my relief. Another less precise option would be to boot with a Linux boot disc (I'm thinking primarily of Knoppix which is based on the Debian platform). If you are able to repair you present OS, then go back to the BIOS, reset it as the boot disk and then delete the trial install from your storage disk.

    I mention this only because I ask myself, "Why not just do a clean install?" Perhaps I am missing something.

    Monk
    I have done this already, on 2 other discs that I know to be functional and the problem repeats on all of them. As for the Linux idea: I already use Kubuntu fairly often and have it installed on another drive. When I wok from there I have had none of the problems that Windows have shown.
      My Computer


  6. Posts : 263
    Dual boot XP Pro SP3x86 and Win7 Pro x64
       #16

    If you are able to do a clean install of Windows, do so, first reformatting the install partition. Once the reinstall is accomplished, DO NOT upgrade any drivers. Next launch the mobo install disc and let it install the mobo drivers. Then use the computer for a while to see if the BSOD recurs. If not, I think you may rightfully assume yours is a driver issue. Then, one-by-one, upgrade drivers, saving any graphics drivers for last. Pause between each upgrade to observe performance for a while. Lastly, using your install disc, install your gfx drives/software. DO NOT upgrade the gfx driver at this point other than that which is on the original install disc. Observe performance for a while. Lastly, if there is a driver upgrade available, uninstall your current gfx driver, then install the upgrade, i.e., NEVER overwrite an existing gfx driver with an upgrade. If the system is still stable after all of this, one-by-one, start reinstalling any apps and endure the wait-and-see strategy after each.

    I appreciate your frustration but I think it fair to say that there is no inherent incompatibility between Windows 7 and your system. So it remains to tweak the BIOS, OS, drivers, and other SW until you ID the culprit.

    Go back to Vista? Nah. You've crossed the Rubicon, lad: there's no turning back now.

    Monk
      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 12:57.
Find Us