I. #%&*$#. Hate. Computers.

New OS install. New hard drive installed it on. Mobo replacement. Plenty of power.

Maybe a month after that reinstall, these #%&*$# blue screen of death issues are back.

Kernel data inpage error
Stop: 0x0000007a

NTSC.sys address ffffff8800150f054 base at fffff8800141dooo datatestamp


Could it be another drive, not my OS drive, that is going bad and casui these errors?

These errors don't happen when resuming the computer, but while I am in the middle of list ding to music, photo editing, game g, or watching a movie.

Etc etc

Wtf is up.

If I were rich I would have smashed my entire system to bits and then pissed on the wreckage.

I've unplugged all drives except the OS drive, but computer refuses to boot to windows

Start Button, in Search Type Event Viewer

Launch it, windows logs, System.

If ANY Drive is having reading problems, it would report bad blocks in this event log. from there

Either a Yellow or Red Icon for Disk and NTFS (They usually show up together).

should say:

HardDiskX = Drive Number in Computer Manager/Disk Management (ie Harddisk0)
DRX = Drive Paritition Data.


So For Example, when I plug my 1TB Seagate in USB Port, It's Drive Number is 2 (Windows Drive 0, Other Drive 1, etc)
I get a Rash of
When I unplug it the errors stop.

That should help narrow down which drive is physically damage or just has a bad format ("Quick Format" Typically causes these issues).

NTFS.sys can cause a Halt State if Windows has Page Files on one of those drives.
If you want, you can post the entire BSOD MiniDump file and I can open it and see if it's hardware or driver related.

Thanks skate. If I can ever boot to windows then I will try that and will see if I can get you the mini dump (ha ha)

Is the anything I can do to prod my system into booting up? It refuses to do so.

if you installed windows with another drive present, it likely put the boot partition on one of the other drives.

I had that problem twice, when I Had Dual Operating systems, it stuck the boot manager on the other drive, while Windows 7 was on another, When I pulled the XP Drive, I was Unable to boot Win 7 etc etc.

what's it doing?
BOOTMGR MISSING or CORRUPT?

or booting windows then crashing before it's done?


Windows Taking a Dump Randomly is why I still have a 4GB USB Stick with Ubuntu Live on it (boots right from the USB Stick).

Saved me so many times, as I can access my data to recover to another drive/usb drive or replace missing or corrupted system files when windows refuses to boot.

He didn't type ntfs, he typed NTSC. I don't know what that might be other than some TV tuner program?



The Jedi Master

I'm dead in the water here. No boot to windows

Sounds like your HD crapped out on you, IMO.
First, I'd switch the SATA cables for one you know to be good, to make sure it isn't that. It happens.
Second, I'd throw the W7 disc in there and try to reinstall to the questionable drive to see if it's recognized.
If so, you could try a windows repair instead of reinstall, but I can't remember a time when that actually worked for me.

Then, try to fix the master boot record.

http://www.sevenforums.com/general-discussion/17521-how-fix-mbr-through-command-prompt.html


Ignore the guy talking about msconfig, try the instructions:
after selecting repair>cmd prompt, enter
BootRec.exe /fixmbr

machine decided to reboot...for how long it will work, I don't know.

more #%&*$#, of course:

found a link to a M$ hotfix for the issue:

http://support.microsoft.com/kb/977178

downloaded it and when I run it, even though it's for Windows 7/Server 2008, I get this #%&*$# message:


This update is not applicable to your computer

No other info, such as whethher it's already been installed as part of Windows 7 updates.



Skate, I ran Event Viewer and indeed see a bunch of Warning and Error Levels for the System tab, but they are from around June 10th.

Stuff like this:
The device, \Device\Harddisk1\DR1, is not ready for access yet.
An error was detected on device \Device\Harddisk1\DR10 during a paging operation.
The device, \Device\Harddisk7\DR7, is not ready for access yet.





More recent errors, from 7/21:

The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_APPLE&PROD_IPOD&REV_1.62#000A2700213475EF&0#.

The previous system shutdown at 10:40:21 PM on ‎7/‎20/‎2014 was unexpected.

a kernel power critical message, likely due from when my system blue screened:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_APPLE&PROD_IPOD&REV_1.62#000A2700213475EF&0#.

The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_APPLE&PROD_IPOD&REV_1.62#000A2700213475EF&0#.

Could this be applicable? From yesterday when it blue screened. There are a bunch of these:
The driver detected a controller error on \Device\Ide\IdePort0.

Get some of these, too, from the day before:
The driver detected a controller error on \Device\Ide\IdePort1.

Also, where would I find the SOD MiniDump file to post it? I googled the issue and was directed to look in C:Windows/minidump. I have no such folder in C:Windows.

My Startup and Recovery>Debugging information was set to Kernel MEmory Dump, but there's no %SystemRoot%\MEMORY.DMP location or file anywhere on my comp, according to Windows search.

Thanks again, folks.

And when this #%&*$# happens again, which I'm certain it will, how in hell's name can I boot?

I'd back everything up while you can, save your bookmarks, email, docs, photos and prepare for that drive to die. Even if its new.
Still check the SATA cable and power to the drve.

Another BSOD after about 15 min.

I have 8 internal drives and 3 external ones. How can I figure out which one(s) are causing the issue if it is a drive issue?

For Mini Dumps
http://support.microsoft.com/kb/315263

Run just the OS drive. After a while, if no issues, add another and so on.
Enable SMART on your motherboard, it might catch something.
If you had just the OS drive earlier and it wouldn't boot, it seems that would be the bad one, if there's a bad one.

Check all connections, exchange the SATA cables, try another power plug from the PSU.

-Check all SATA Cables arent worn/frayed.
-Check HDD Modes in Bios are correct (UDMA Mode 5 or 6)
-Enable SMART in BIOS if it's Disabled.
-Make Sure Chipset Drivers are Up to date for SATA Controller.
Both Intel's and Marvells
2 Red Ports are 6GB Intel, 4 Gray Ports are 3GB Intel, and 2 Red are 6GB Marvel

-Almost every Occurrence of that Specific Error on Intel Chip sets is resolved by installing the Intel RST and AHCI Driver and GUI
https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=24006&lang=eng&ProdId=2101 (F6FLPY-x64)


If you've done all that.
It might be the Controller Chip itself faulting, Mainboard RMA.

The way to ensure it's not the drives is the run Them with SMART on, one or 2 at a time, and run the diagnostics software provided by the Manufacturer.
(JUST RUN SMART TESTS, Extended Tests Will Erase DATA, BE VERY CAREFUL WITH WHICH TEST YOU CHOOSE)
-WD Data Lifegaurd Tools for Windows (Western Digital)
-HGST Device Manager (HDM) (Hitachi)
-Seagate Dashboard

This is where once again, Booting a Ubuntu Live USB Stick comes in handy, Booting directly to linux from the USB Stick, You can run SMART Tests on all the drives without any Windows Drivers getting in the Way.

Thanks. Step 2 doesn't work for me. CMD doesn't recognize that address as valid when I type it.


To open the dump file after the installation is complete, follow these steps:
Click Start, click Run, type cmd, and then click OK.
Change to the Debugging Tools for Windows folder. To do this, type the following at the command prompt, and then press ENTER:
cd c:\program files\debugging tools for windows
To load the dump file into a debugger, type one of the following commands, and then press ENTER:
windbg -y SymbolPath -i ImagePath -z DumpFilePath
kd -y SymbolPath -i ImagePath -z DumpFilePath

Step 2 being the cd c:\program. Etc

Re that UBUNTUl live USB stick, is that something that I can make?

Ps what is the best way to determine which drive is causing these BSOD errors?

A problem has been detected and windows has been shut down to prevent damage to your computer.
A process of thread crucial to system operation has unexpectedantly exited or been terminated.

Unplugged all drives but e three most recent ones, my comp ran for about 30 mon then BSOD with a different error:

Stop: 0x000000F4


When I rebooted I got:

reboot and select proper boot device
Or insert boot media in selected boot device and press a key


Tried again and see BOOTMGR missing


#%&*$#




I don't have any more patience for this #%&*$#. I might ditch PC and go to Mac.