Solved Copy of Windows not genuine, Build 7601

[derekimo]

OK, let's just forget about that tool then.

Try this tool just so we get an idea,

Download CrystalDiskInfo - MajorGeeks

You'll get a screen like this if it's good,



Or one like this, on my Hitachi,



Which ever it is, post back a screenshot.

If it is like my Hitachi you can reset the sectors back to good health but it may be time to get a new drive.

 

[derekimo]

Also, you don't have any dump files in your uploads.

Can you make sure it is set for small memory dumps,

http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

It will help if you get another one.

 

[tzxlyd]

Derekimo,
OK, that tool worked and I have changed the startup and recovery for small dump files. So now I have no idea what to think -- I could probably try to force a BSOD since it tends to happen whenever I move the computer (could there be a loose connection somewhere internally?). I am even more confused than I was before all of this -- earlier today it crashed repeatedly in normal and safe modes reorting the disk read error messages and it would not let me logon with my password.

 

[derekimo]

OK, at least we have some idea on your drive now. It's possible there's a loose connection but it's more likely some corruption or conflicts with drivers.

Forcing a crash won't do any good in troubleshooting, we want the actual cause to show.

I don't remember if you ran this already,

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

You said disk check came back fine so it's worth checking for file corruption.

 

[ICIT2LOL]

Now in msinfo there is a problem device and there is some references to it being an AV problem see this
http://www.sevenforums.com/bsod-help-support/85581-windows-7-randomly-freezes.html

 

[derekimo]

Now in msinfo there is a problem device and there is some references to it being an AV problem see this
http://www.sevenforums.com/bsod-help-support/85581-windows-7-randomly-freezes.html

What is that device?

I must not be seeing it.

 

[tzxlyd]

Derekimo,
I ran the SFC twice just to make sure -- nothing found.

 

[derekimo]

OK, at this point I think we just wait and see if it BSOD's.

 

[ICIT2LOL]

Now in msinfo there is a problem device and there is some references to it being an AV problem see this
http://www.sevenforums.com/bsod-help-support/85581-windows-7-randomly-freezes.html

What is that device?

I must not be seeing it.

In post #7 files Derek see pic however nothing in the others

Sorry should have expanded that

 

[derekimo]

OK, he did a recovery (Post #24) since that log was posted, that's why it isn't in the other two.

Thanks for the screenshots.

 

[tzxlyd]

Derekimo,
Just BSOD' twice -- the second time it crashed immediately after restarting -- before I was able to open IE. Both IE and WE crashed the second time and had to restart them. I cancelled the disk check that was starting so I could get the BSOD file sent to you.

 

[derekimo]

OK, there still aren't any dump files but there are a string of these,

The device, \Device\Harddisk0\DR0, is not ready for access yet.

Followed by this,

The device, \Device\Ide\iaStor0, did not respond within the timeout period.

Which is the storage driver.

Let's try this,

Remove Intel Rapid Storage Technology applications.

1. Uninstall it from Control Panel > Programs and Features.

2. Uninstall the driver from device manager:
- Right click on "my computer" icon and click "manage" on the context menu.
- In the "Computer Management" window that opens:
- Select "Device Manager" in the left pane, It will list all the existing devices.
- Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
- Select one Intel device item under it, right click, then uninstall.
- Repeat the process for all Intel items under "IDE ATA/ATAPI controllers"

3. Now restart the computer.

4. Once booted, Windows will auto configure the appropriate native system driver.

 

[tzxlyd]

Derekimo,
Done. This time I let the disk check run at startup and there were messages of items it had to repair and it did not takes hours as it has been to run the check. Now that you told me to do that I remember that I had to reconfigure my internet drivers after MCC worked on it the first time but I used services.msc to uninstall the WLAN, then let windows update/reconfigure from there. Perhaps, I may need to let windows update/reconfigure all of my drivers at some point to make sure they are configured correctly?

 

[tzxlyd]

Do you think I should change the Startup and Recover so BSOD does a complete dump instead of a small dump?

 

[derekimo]

Derekimo,
Done. This time I let the disk check run at startup and there were messages of items it had to repair and it did not takes hours as it has been to run the check. Now that you told me to do that I remember that I had to reconfigure my internet drivers after MCC worked on it the first time but I used services.msc to uninstall the WLAN, then let windows update/reconfigure from there. Perhaps, I may need to let windows update/reconfigure all of my drivers at some point to make sure they are configured correctly?

Let's not do anything else right now. There is no reason to start messing with any other drivers at this point.

Do you think I should change the Startup and Recover so BSOD does a complete dump instead of a small dump?

It's possible you already have a folder for those if you haven't been cleaning your computer.

Changing it back will just mean you have to upload those files to something like OneDrive because they are too large to upload here, and the DMlog collector doesn't look for those.

For the time being just leave it at small memory dumps.

You can look to see if there are any folders related to dumps in the C:\Windows folder. (MemoryDump, MiniDump, Etc.)

 

[tzxlyd]

OK. I will leave as is. So far the computer speed is much better -- I was waiting a long time on internet windows to load and that has gotten back to normal.

 

[ICIT2LOL]

Ok no probs

 

[tzxlyd]

Derekimo,
Another BSOD but I am sure there is nothing in the file because this time I saw the message that the dumped failed just before it restarted -- still I ran the file collector just in case.

 

[derekimo]

Well the first thing I can see is it is still using the driver we intended to get rid of.

Can you follow these instructions again.

Remove Intel Rapid Storage Technology applications.

1. Uninstall it from Control Panel > Programs and Features.

2. Uninstall the driver from device manager:
- Right click on "my computer" icon and click "manage" on the context menu.
- In the "Computer Management" window that opens:
- Select "Device Manager" in the left pane, It will list all the existing devices.
- Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
- Select one Intel device item under it, right click, then uninstall.
- Repeat the process for all Intel items under "IDE ATA/ATAPI controllers"

3. Now restart the computer.

4. Once booted, Windows will auto configure the appropriate native system driver.

Do not reboot until you have done both step 1 and 2.

After it reboots and installs the driver, run the log collector again so we can see if it installed the correct Microsoft driver.

 

[tzxlyd]

Derekimo,
I did exactly that the 1st time but there is only one Intel Chip set under IDE, so I am attaching a capture of all of the controllers under the Device Manager. You will notice that most of the Intel Controllers are listed under the System Devices not DM.