Solved Validation of Windows 7 problem after updates.

[NoelDP]

AV=Anti-Virus

Woops - you uploaded the CBS.log file, rather than the CheckSUR.log file I asked for.
Please look again for the file, and upload that one..

 

[lady]

Sorry for the delay. Is this it attached?

 

[NoelDP]

That's the one - and at least that worked, and the result is clear - which means that we don't have to start doing complex hardware tests

We'd probably better run the SFC /SCANNOW command again, and then upload the new CBS.log file - things may have changed a little,

 

[lady]

I didn´t do that SFC/SCANNOW part yesterday as too scary for a novice to attempt. Just had another look at it and feel the same. All seems to be okay at the moment, so I´ll leave it at that for now. Thank you very much for your patience and hope you can enjoy a well deserved pint!

 

[NoelDP]

Believe me - there's nothing scary about SFC! - the worst it can do is give us a long list of problems - then comes the scary bit

Go ahead with it and post the new CBS.log - we'll have you programming next week

 

[lady]

Sfc/scannow

Option 1 looks too complicated from Boot??? Should I use option 2 that checks and repairs files or one that just scans to see if there is a problem without changing anything. Already got over one problem this morning after PC shut down on it´s own with a load of text on screen but I caught the last bit and it said it was "dumping physical memory to disc. Done this before but perhaps we can deal with this in a separate thread some other time.

Still very nervous about doing the scan.. Sorry

 

[NoelDP]

Yeah - it's the easiest way.
Here's my own boilerplate on the subject...

SFC -System File Checker - Instructions
Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.
At the Command prompt, type
SFC /SCANNOW
and hit the Enter key
Wait for the scan to finish - make a note of any error messages - and then reboot.

Doesn't sound so scary now, huh?

 

[lady]

By reboot do you mean close down PC and re-open or something different?

 

[lady]

Okay Googled reboot and have done as you asked. The scan report said " Windows Resource Protection found corrupt files but was unable to fix some of them. Detail included in CBS.Log". The log should be attached. Thanks for giving me the courage to venture into the unknown.

 

[NoelDP]

That's what I was expecting/hoping for...
Now all I have to do is work out actually what it all means!
back soon...

 

[lady]

After a windows update again yesterday I am back to square one with message on screen "Windows 7 Build 7601 This copy of windows is not genuine. I have not tried to reactivate it yet but thought I should produce the same report for you as last time before reactivating to see if it shows the problem better for you. Hope you can sort this as it´s driving me nuts. Thanks

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 50
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-YJTVC-MD29W-F8RDX
Windows Product Key Hash: SWep1ZWtFYLyTGKT8V8Egqk6mT8=
Windows Product ID: 00371-OEM-9044882-48560
Windows Product ID Type: 3
Windows License Type: OEM System Builder
Windows OS version: 6.1.7601.2.00010100.1.0.048
ID: {3FAF6361-E866-449B-AE4F-DFE500DBDD07}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Professional
Architecture: 0x00000000
Build lab: 7601.win7sp1_gdr.140303-2144
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Users\User\AppData\Local\Google\Chrome\Application\chrome.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{3FAF6361-E866-449B-AE4F-DFE500DBDD07}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-F8RDX</PKey><PID>00371-OEM-9044882-48560</PID><PIDType>3</PIDType><SID>S-1-5-21-1226978661-57905391-1268580119</SID><SYSTEM><Manufacturer>To Be Filled By O.E.M.</Manufacturer><Model>To Be Filled By O.E.M.</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>P1.30</Version><SMBIOSVersion major="2" minor="4"/><Date>20091118000000.000000+000</Date></BIOS><HWID>D21A3E07018400F2</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Romance Standard Time(GMT+01:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7601.17514

Name: Windows(R) 7, Professional edition
Description: Windows Operating System - Windows(R) 7, OEM_COA_NSLP channel
Activation ID: e120e868-3df2-464a-95a0-b52fa5ada4bf
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00371-00180-448-848560-02-3082-7601.0000-2412014
Installation ID: 010050712912520692235043583095987566422190943444038653
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: F8RDX
License Status: Notification
Notification Reason: 0xC004F009 (grace time expired).
Remaining Windows rearm count: 4
Trusted time: 29/08/2014 21:14:24

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 8:9:2014 20:11
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: OAAAAAIABgABAAEAAAACAAAAAQABAAEA6GEmUfAdPp1q4Kp2SOT04zRI9HMYhq7n0Jh+rMZzqPA=

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information: 
  ACPI Table Name	OEMID Value	OEMTableID Value
  APIC			A_M_I 		OEMAPIC 
  FACP			A M I 		OEMFACP 
  MCFG			A_M_I 		OEMMCFG 
  OEMB			A_M_I 		AMI_OEM 
  AAFT			A_M_I 		OEMAAFT

 

[NoelDP]

License Status: Notification
Notification Reason: 0xC004F009 (grace time expired).
Remaining Windows rearm count: 4

Odd - Windows must have decided a few days ago that your hardware had changed significantly, and gone to re-activation mode.
The 3-day grace period for such re-activations has now expired.

Let's see if we can find out what tripped it.
The most common cause of such problems is the Ethernet networking card - either switching it off, or changing the MAC address, but that seems unlikely here.


Open Event Viewer
click on the Windows logs entry in the left pane to expand it.
Now click on the Application entry - wait while it loads.
Click on 'File' in the menu bar and select Save...
Save the file as Appevt.evtx
Repeat for the System log
then zip both, and upload them.

 

[lady]

Took me a while to find "Events Viewer" and then save option not in file so a little daunting for me but hope this is it attached. Thanks for helping. I have not changed any hardware but we do get power cuts in this part of Spain and if the PC is on it sometimes causes me problems. Had one the other day and just telling you in case this is significant. I do turn off the router at night due to the heat here and I also have to run my PC with the side panel off in the summer with a fan blowing directly into it. Earlier in the week my pc went off and the message I could catch was "Dumping physical memory to disc. It closes down my machine and then froze on restart, so I had to physically turn it off on the switch at back and re-start. Then it said "Windows has recovered from an unexpected shutdown". Been ok until update. Hope the extra info helps.

 

[NoelDP]

There's only the one event in each log - interestingly, one of the events captured is a BSOD.
I'm going to call for some help on this, as BSOD's (forced shutdowns) are not my forte.
While we wait for the cavalry, please read and follow the I nstructions here ... http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html
- but post the files and other data in this thread to keep things tidy.

 

[essenbe]

Hi Lady, I'm just subscribing so I can help you and Noel when you upload the BSOD posting instructions file.

 

[lady]

Scary stuff but hope that this is what you want. For some reason a few times on shutdown there was a message to wait or force shutdown as it was waiting for windows log-off sound. This is what I remember but didn´t write it down. I waited the first time but nothing happened so I clicked on force shut down. When it happened several times more I went into sounds and set it again to no sounds, which is my normal setting. Why it had changed from that I have no idea. Hope this info helps, sorry for the delay and thank you for your support.

 

[Arc]

Hi lady.

All your recent crash dumps are showing a possibility of memory corruption. the versatility of the bugcheck codes and the probable causes in a short range of time also indicate to it.

In this situation the first thing you should is to test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 subsequent passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result. Further troubleshooting/actions will be needed depending on this result.

Edit, Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus, egui (ESET).
5. Apply > OK
6. Accept then restart.

_____________________________________

BugCheck 50, {89bc8fe8, 1, 8c4c5bed, 0}


Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!NtfsInsertCachedRun+12b )

Followup: MachineOwner
---------

BugCheck 1A, {5003, c0402000, a5c4, 163dc76}

Probably caused by : memory_corruption ( nt!MiAllocateWsle+6f )

Followup: MachineOwner
---------

BugCheck 19, {3, baf0ade0, eb11cb97, baf0ade0}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+312 )

Followup: Pool_corruption
---------

 

[lady]

I have dealt with your edit and taken everything out of start menu except ESET and restarted. I have read through the notes of the other test and it´s far too complicated for me as I don´t know how to boot from CD or how to get it back to normal afterwards and certainly know nothing about disconnecting ram from the motherboard. For me that would be a shop job but the guy we use only speaks Spanish so it´s hard for us to communicate. When the screen went black before and showed the message "This copy of windows in not genuine" I first took the PC to him and he cleared it for me. It happened again after a few weeks so I took it back and he called Microsoft helpline in Spain and he appeared to be entering numbers into the phone. The problem was cleared again but some updates cause this problem. Should I try and reactivate it myself again as it has worked before? I left it with the fault so that you could see it. Thanks

P.S. Not so concerned about the crash dump, more about windows not being genuine, when it is.

 

[Arc]

When NoelDP is with you, and you are following his instructions, then "This copy of windows in not genuine" issue is not an issue at all.

You should be concerned about the crash dumps, too. That might be a more fatal issue, as it is appearing.

If you wnat, NoelDP or essenbe or me, anybody can guide you in memtest. You need not to remove the RAMS at this moment. Initially you run the test with all the RAM modules connected.

 

[NoelDP]

When NoelDP is with you, and you are following his instructions, then "This copy of windows in not genuine" issue is not an issue at all.

<chuckle>

Thin is that it's very likely that it's the BSOD problems that are causing the non-genuine issue. Unless we can solve the root cause, they are just going to keep returning.

By the time Arc, Steve and I have finished with you, you'll be teaching the rest of the street how to fix their PC problems, lady