locked
Windows 7 Home Premium OEM PC build problems RRS feed

  • Question

  • I recently built another pc and things went together fine much like the first time. Windows 7 Home Premium OEM installed fine and booted up quickly. After booting I found out that I could not install programs to the pc, I always get random errors such as registry corruption, hkey error, or just "no". Also I got the windows update failure error. Then after fixing that and updating, the BSOD was there to greet me. So happily after spending 4 wonderful days with my buddy BSOD and numerous clean installs with drivers installed before and after windows 7, I am about to give up. I have never had a problem like this and have no idea what to do. I have run memtest, checked for HDD errors, tested videocard, tested cpu, tried a registry repair. I even found out that the Marvell raid controller is not supposed to be compatible with Win7 so that's good. I finally got 2 programs to install, but then windows wouldn't boot at all so I loved on my BIOS.

    BSOD: 0x000000f4 (0x0000000000000003, 0xFFFFFAB007749B30, 0xFFFFFAB007749E10, 0xFFFFF8002D93500)

    The pc has:

    Intel core i7 950

    Asus Sabertooth x58

    3x2gb corsair dominator 1866

    evga gtx 465 1gb

    thermaltake black widow 950w

    cheap combo read/write drive

    WD 1tb 6gb/s HD, connected with sata 3

     

    Any help is appreciated, thanks.

     

    • Moved by Carey FrischMVP Tuesday, December 7, 2010 12:48 AM Moved to proper forum category (From:Windows Vista Service Packs/Windows Server 2008 Service Packs)
    Monday, December 6, 2010 10:44 AM

Answers

  • Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION - . This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

    http://msdn.microsoft.com/en-us/library/ff560372%28VS.85%29.aspx

     

    Cause

    Several processes and threads are necessary for the operation of the system. When they are terminated for any reason, the system can no longer function.


    To see the cause I have to take a look at the dumps with the Debugging Tools for Windows.

    Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your public Skydrive [1] folder and post a link here.

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65

     


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Cloud_TS Tuesday, December 14, 2010 7:08 AM
    Tuesday, December 7, 2010 2:17 PM
  • On Tue, 7 Dec 2010 11:08:18 +0000, rockstar1996 wrote:
     
    > Have you ran registry scans? Your program problem could be that windows installer may be corrupted? Comment back If you have any questions!
     
     
     
    Registry cleaning programs are *all* snake oil. Cleaning of the
    registry isn't needed and is dangerous. Leave the registry alone and
    don't use any registry cleaner. Despite what many people think, and
    what vendors of registry cleaning software try to convince you of,
    having unused registry entries doesn't really hurt you.
     
    The risk of a serious problem caused by a registry cleaner erroneously
    removing an entry you need is far greater than any potential benefit
    it may have.
     
     
     
    and also
     
    Let me point out that neither I nor anyone else who warns against the
    use of registry cleaners has ever said that they always cause
    problems. If they always caused problems, they would disappear from
    the market almost immediately. Many people have used a registry
    cleaner and never had a problem with it.
     
    Rather, the problem with a registry cleaner is that it carries with it
    the substantial *risk* of having a problem. And since there is no
    benefit to using a registry cleaner, running that risk is a very bad
    bargain.
     
     

    Ken Blake
    • Marked as answer by Cloud_TS Tuesday, December 14, 2010 7:08 AM
    Tuesday, December 7, 2010 10:12 PM

All replies

  • Have you ran registry scans? Your program problem could be that windows installer may be corrupted? Comment back If you have any questions!
    Tuesday, December 7, 2010 11:08 AM
  • Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION - . This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

    http://msdn.microsoft.com/en-us/library/ff560372%28VS.85%29.aspx

     

    Cause

    Several processes and threads are necessary for the operation of the system. When they are terminated for any reason, the system can no longer function.


    To see the cause I have to take a look at the dumps with the Debugging Tools for Windows.

    Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your public Skydrive [1] folder and post a link here.

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65

     


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Cloud_TS Tuesday, December 14, 2010 7:08 AM
    Tuesday, December 7, 2010 2:17 PM
  • On Tue, 7 Dec 2010 11:08:18 +0000, rockstar1996 wrote:
     
    > Have you ran registry scans? Your program problem could be that windows installer may be corrupted? Comment back If you have any questions!
     
     
     
    Registry cleaning programs are *all* snake oil. Cleaning of the
    registry isn't needed and is dangerous. Leave the registry alone and
    don't use any registry cleaner. Despite what many people think, and
    what vendors of registry cleaning software try to convince you of,
    having unused registry entries doesn't really hurt you.
     
    The risk of a serious problem caused by a registry cleaner erroneously
    removing an entry you need is far greater than any potential benefit
    it may have.
     
     
     
    and also
     
    Let me point out that neither I nor anyone else who warns against the
    use of registry cleaners has ever said that they always cause
    problems. If they always caused problems, they would disappear from
    the market almost immediately. Many people have used a registry
    cleaner and never had a problem with it.
     
    Rather, the problem with a registry cleaner is that it carries with it
    the substantial *risk* of having a problem. And since there is no
    benefit to using a registry cleaner, running that risk is a very bad
    bargain.
     
     

    Ken Blake
    • Marked as answer by Cloud_TS Tuesday, December 14, 2010 7:08 AM
    Tuesday, December 7, 2010 10:12 PM
  • @KenBlake

    thank you for the advice but what about windows registry why would windows have that if it was a scam?

    Wednesday, December 8, 2010 12:26 AM
  • Windows doesn't have a registry cleaner. tjhose are all 3rd party tools.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Wednesday, December 8, 2010 2:41 PM