BSOD after installing Windows 7 Professional


  1. Posts : 2
    Windows 7 professsional
       #1

    BSOD after installing Windows 7 Professional


    Hi,

    I have installed Windows 7 professional on my daughters laptop, it seems to have installed ok, then its comes up with a blue screen with the following code STOP 0x0000007, and then restarts, I have tried system restore, reinstallation, but nothing seems to help

    many thanks

    carol
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

    Boot in safe mode with networking and run this tool
    https://www.sevenforums.com/crashes-d...tructions.html
      My Computer


  3. Posts : 2
    Windows 7 professsional
    Thread Starter
       #3

    Hi,

    I did the first part of the instructions, and then did the perfmon /report and the following happened Error An error occured while attempting to generate the report - the system cannot find the path specified

    :-(
      My Computer


  4. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #4

    Bettyboop1966 said:
    Hi,

    I did the first part of the instructions, and then did the perfmon /report and the following happened Error An error occured while attempting to generate the report - the system cannot find the path specified

    :-(
    Skip this step and upload the zip file generated by the tool
      My Computer


  5. Posts : 137
    Windows 7 Ultimate x64 / OS X Snow Leopard 10.6.8
       #5

    To the OP, your situation may be different than what I'm about to post but I hope it helps to narrow down your search for the cause.

    First of all, that stop code indicates hardware failure. This does not necessarily mean a piece of hardware is completely dead or useless (however it can), it simply means Windows was unable to initialize and use it correctly. For new computers, the most common cause is improper/inadequate hardware installation, something like a card, memory module or CPU not being seated fully. Another common cause is power supply not being sufficient.

    For an older computer that's been running a while that just underwent a Windows 7 installation, it could mean the same thing as above or hardware that's actually failing. This could mean a faulty memory module, bad or failing video card, etc. One of the key things I inspect is to see if anywhere with a fan is covered with a layer of dust. More dust would indicate longer use. Sometimes I'm able to fix issues involving dust with a thorough cleaning, sometimes it needs replacement.

    Now let's get back to a few simple things you can do. First of all when troubleshooting computers, the very first thing you need to look at is hardware before software. It makes no sense to troubleshoot Windows (software) when a piece of hardware is faulty.

    - First, think about what your computer needs at a bare minimum to boot into Windows. It doesn't need a USB printer, webcam, 2nd hard drive, or even an optical drive to boot in Windows. You don't need any cards installed other than the video card, etc. Disconnect all of that and just make sure you use 1 stick of memory in the first slot, video card, only the hard drive with Windows on it, NO additional drives physically connected. The rest that you'll need is a monitor, keyboard and mouse.

    - Now that you've configured your machine to use only the bare minimum of hardware, boot your machine into Windows. See if you get that same stop code. If you do, then at least now you know all the "disconnected" hardware has nothing to do with the cause and you can focus on what's in the machine now.

    - Do the simple things first. Shut down the machine, re-seat all the hardware all while inspecting it carefully. Look for any signs of circuits being burnt out or having an obvious burnt smell. If the hardware is dusty, take precautions necessary to protect yourself from inhaling it. Put the memory module back in the same slot and restart the machine. If the machine boots without the stop code, restart the machine a few times to see if you can get the stop code to re-occur. If it doesn't, install/connect 1 piece of hardware at a time and boot back into Windows. If the stop code comes up again, shut down the machine, go back to what you recently did/changed, undo it and try again. If you've tried every RAM slot with the same module and still receiving the stop code, remove that module and try a different one and retry all slots again. What you're doing here is to confirm whether 1 RAM module creates a different result when the system boots into Windows. At the same time you're also testing the RAM slots. If you find success in 3 out of 4 RAM slots, it's very possible that 1 slot is bad, so naturally you should avoid using that slot until you get a new motherboard.

    - If you are finding good success after re-seating everything and now the machine is booting into Windows 7 without BSOD, then continue to connect 1 hardware at a time. What you're watching for is to see at what point a BSOD will occur again. If you're lucky then you'll be able to reattach every device and you can continue on with using Windows.

    Keep in mind that like I said earlier, the key to troubleshooting is involving the least amount of variables/factors as much as possible. It's better to have to search through 9 possibilities than 24. After you find success, always go 1 step at a time regarding connecting/reinstalling hardware.

    Good Luck and sorry for long post.
      My Computer


  6. Posts : 11,408
    ME/XP/Vista/Win7
       #6
      My Computer


 

  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 22:54.
Find Us