TechSpot

BSOD after shutting down abd rebooting hours later - Windows 7

By quickshotuk
Mar 3, 2011
Post New Reply
  1. quickshotuk

    quickshotuk TS Rookie Topic Starter Posts: 20

    it seems so, i booted it up this morning and same problems arose, but this time I didn't have my Nvidia Geforce card connected, I just used the intergrated graphics. Also, I took out all the USB cables and hard drives to see if I still get the error, and I still do. When using just one hard drive with Windows, there aren't as many BSOD's, more a blank screen and a problem with the graphics as the monitor goes back into standby. When loading Windows startup repair, it booted in, but middle way gave an unable to use memory error, 2nd time, I just failed with a 'send or don't send' windows error, and third time in a row, the PC just shut down.

    I know 400w is probably not the best PSU to use, but my old one seems to be working fine in another PC. I thought maybe this would've ruled out a faulty motherboard but that doesn't seem confirmed.
     
  2. quickshotuk

    quickshotuk TS Rookie Topic Starter Posts: 20

    ok, just thought I'd keep you updated, a replaced brand new PSU does not change a thing, still the same problems arise, I think that the MOBO maybe a problem, but I've googled this model and there doesn't seem to be one person having the same issues. The RAM is the only thing that I can test/replace, if it doesn't work still, its definitely got to be a faulty mobo. Annoying because I didn't want to take out the heatsink, buy new thermal paste and spend money sending it off!! There's another minidump file, just in case its sommhing different
     

    Attached Files:

  3. Route44

    Route44 TechSpot Ambassador Posts: 12,168   +37

    Your error code is 0x6B: PROCESS1_INITIALIZATION_FAILED
    This bug check indicates that the initialization of the Microsoft Windows operating system failed.

    Cause

    Any part of the disk subsystem can cause the PROCESS1_INITIALIZATION_FAILED bug check, including bad disks, bad or incorrect cables, mixing different ATA-type devices on the same chain, or drives that are not available because of hardware regeneration.

    This bug check can also be caused by a missing file from the boot partition or by a driver file that a user accidentally disabled in the Drivers tab.

    * In Post #4 I suggested doing a Windows Repair and in Post #23 I suggested that you run a harddrive diagnostics in light of error code 0x24. Have you already done either?
     
  4. quickshotuk

    quickshotuk TS Rookie Topic Starter Posts: 20

    yes, I've done a hard drive diagnostic, but I did this after I unplugging it, left it 10 mins and let it boot up normally. There were no errors from the program, for either hard drive. Windows repair, I couldn't do because I kept getting BSOD's whenever booting that up, I have a mix of problems booting up anything from a CD or from the hard drive when the PC is in that state. The one thing I forgot to do was run the windows repair after unplugging/plugging then rebooting. I will do that now and report back if I get any errors.
     
  5. quickshotuk

    quickshotuk TS Rookie Topic Starter Posts: 20

    windows startup repair thinks I have a USB device connected, it won't work for some reason. I can confirm I have absolutely no USB devices connected, even the mouse and keyboard are not USB.
     
  6. quickshotuk

    quickshotuk TS Rookie Topic Starter Posts: 20

    ok i used a usb startup repair drive, booted it up and while it was searching for 'windows installations' it found a startup error which it will fix when rebooted. I'm not totally convinced this solved the problem, but we'll see.
     


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.