Main Area and Open Discussion > Living Room
Annoying error/issues at shutdown/restart and startup
Carol Haynes:
OK - another wrinkle in the problem. I tried to run a game, the system crashed (no BSOD) and then wouldn't start.
Startup repair said it couldn't fix and in safe mode I ran SFC /SCANNOW again.
Now I get an error saying SFC cannot repair a corrupt file. I run:
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"c:\sfc_output.txt"
to find the issue but there are no files reported (see log below - trucated because all the entries are the same).
log2012-06-08 20:42:54, Info CSI 0000009a [SR] Verifying 100 (0x0000000000000064) components
2012-06-08 20:42:54, Info CSI 0000009b [SR] Beginning Verify and Repair transaction
2012-06-08 20:42:55, Info CSI 0000009d [SR] Verify complete
2012-06-08 20:42:55, Info CSI 0000009e [SR] Verifying 100 (0x0000000000000064) components
2012-06-08 20:42:55, Info CSI 0000009f [SR] Beginning Verify and Repair transaction
2012-06-08 20:42:56, Info CSI 000000a1 [SR] Verify complete
...
2012-06-08 20:51:31, Info CSI 0000037e [SR] Verifying 56 (0x0000000000000038) components
2012-06-08 20:51:31, Info CSI 0000037f [SR] Beginning Verify and Repair transaction
2012-06-08 20:51:33, Info CSI 00000381 [SR] Verify complete
2012-06-08 20:51:33, Info CSI 00000382 [SR] Repairing 0 components
2012-06-08 20:51:33, Info CSI 00000383 [SR] Beginning Verify and Repair transaction
2012-06-08 20:51:33, Info CSI 00000385 [SR] Repair complete
--- End quote ---
Earlier today I had another issue with these sfc errors:
log 22012-06-08 18:49:57, Info CSI 000000e8 [SR] Cannot repair member file [l:80{40}]"Microsoft-Windows-IE-HTMLRendering.ptxml" of Microsoft-Windows-IE-HTMLRendering, Version = 8.0.7601.17573, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2012-06-08 18:50:02, Info CSI 000000e9 [SR] Cannot repair member file [l:80{40}]"Microsoft-Windows-IE-HTMLRendering.ptxml" of Microsoft-Windows-IE-HTMLRendering, Version = 8.0.7601.17573, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2012-06-08 18:50:02, Info CSI 000000ea [SR] This component was referenced by [l:156{78}]"Package_4_for_KB2497640~31bf3856ad364e35~amd64~~6.1.1.2.2497640-16_neutral_GDR"
2012-06-08 18:50:02, Info CSI 000000ec [SR] Verify complete
2012-06-08 18:50:03, Info CSI 000000ed [SR] Verifying 100 (0x0000000000000064) components
2012-06-08 18:50:03, Info CSI 000000ee [SR] Beginning Verify and Repair transaction
2012-06-08 18:50:04, Info CSI 000000f0 [SR] Verify complete
...
2012-06-08 18:53:10, Info CSI 000001e4 [SR] Verifying 100 (0x0000000000000064) components
2012-06-08 18:53:10, Info CSI 000001e5 [SR] Beginning Verify and Repair transaction
2012-06-08 18:53:12, Info CSI 000001e7 [SR] Verify complete
2012-06-08 18:53:12, Info CSI 000001e8 [SR] Verifying 100 (0x0000000000000064) components
2012-06-08 18:53:12, Info CSI 000001e9 [SR] Beginning Verify and Repair transaction
2012-06-08 18:53:14, Info CSI 000001ea [SR] Cannot repair member file [l:92{46}]"wow64_Microsoft-Windows-IE-HTMLRendering.ptxml" of Microsoft-Windows-IE-HTMLRendering, Version = 8.0.7601.17573, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2012-06-08 18:53:15, Info CSI 000001eb [SR] Cannot repair member file [l:92{46}]"wow64_Microsoft-Windows-IE-HTMLRendering.ptxml" of Microsoft-Windows-IE-HTMLRendering, Version = 8.0.7601.17573, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2012-06-08 18:53:15, Info CSI 000001ec [SR] This component was referenced by [l:156{78}]"Package_4_for_KB2497640~31bf3856ad364e35~amd64~~6.1.1.2.2497640-16_neutral_GDR"
2012-06-08 18:53:16, Info CSI 000001ee [SR] Verify complete
2012-06-08 18:53:16, Info CSI 000001ef [SR] Verifying 100 (0x0000000000000064) components
2012-06-08 18:53:16, Info CSI 000001f0 [SR] Beginning Verify and Repair transaction
2012-06-08 18:53:23, Info CSI 000001f5 [SR] Verify complete
...
2012-06-08 18:55:26, Info CSI 000002f2 [SR] Beginning Verify and Repair transaction
2012-06-08 18:55:27, Info CSI 000002f4 [SR] Verify complete
2012-06-08 18:55:27, Info CSI 000002f5 [SR] Repairing 2 components
2012-06-08 18:55:27, Info CSI 000002f6 [SR] Beginning Verify and Repair transaction
2012-06-08 18:55:27, Info CSI 000002f7 [SR] Cannot repair member file [l:80{40}]"Microsoft-Windows-IE-HTMLRendering.ptxml" of Microsoft-Windows-IE-HTMLRendering, Version = 8.0.7601.17573, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2012-06-08 18:55:28, Info CSI 000002f8 [SR] Cannot repair member file [l:92{46}]"wow64_Microsoft-Windows-IE-HTMLRendering.ptxml" of Microsoft-Windows-IE-HTMLRendering, Version = 8.0.7601.17573, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2012-06-08 18:55:28, Info CSI 000002f9 [SR] Cannot repair member file [l:80{40}]"Microsoft-Windows-IE-HTMLRendering.ptxml" of Microsoft-Windows-IE-HTMLRendering, Version = 8.0.7601.17573, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2012-06-08 18:55:28, Info CSI 000002fa [SR] This component was referenced by [l:156{78}]"Package_4_for_KB2497640~31bf3856ad364e35~amd64~~6.1.1.2.2497640-16_neutral_GDR"
2012-06-08 18:55:29, Info CSI 000002fb [SR] Cannot repair member file [l:92{46}]"wow64_Microsoft-Windows-IE-HTMLRendering.ptxml" of Microsoft-Windows-IE-HTMLRendering, Version = 8.0.7601.17573, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2012-06-08 18:55:29, Info CSI 000002fc [SR] This component was referenced by [l:156{78}]"Package_4_for_KB2497640~31bf3856ad364e35~amd64~~6.1.1.2.2497640-16_neutral_GDR"
2012-06-08 18:55:29, Info CSI 000002fe [SR] Repair complete
2012-06-08 18:55:29, Info CSI 000002ff [SR] Committing transaction
2012-06-08 18:55:29, Info CSI 00000303 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
--- End quote ---
But the only fix I could find to replace the file was rejected from Windows 7. The errors seem to relate to an IE 8 file - but I have IE 9 installed.
Also I tried to reinstall Windows 7 SP1 but it wouldn't let me (said it was already installed) - is this the only version of windows where you can't reinstall a service pack? I figured if I could reinstall SP1 I could apply updates again from a known base. Previous versions of Windows have let you do this.
Stoic Joker:
I recently set up Windows SBS 2011 and connected my computer to the domain. Not an easy job as none of the methods suggested from the NEw User wizard on the server actually worked! It suggests opening http://connect on the machine you want to connect but there is absolutely no response from that address anywhere on the network. Installed the server 4 times without result - in the end I used a thumb drive and carried the connection software to the machine. Even so I had to manually establish a domain connection before it would let me run the proper connection software! What a bunch of crap. It also confirms why I never want to get involved in Windows servers for work! Could they produce more obscure software if they tried - it is 100% jargon and incredibly confusing wizards - and SBS 2011 is supposed to be the easiest server to set up in recent years.-Carol Haynes (June 08, 2012, 02:51 PM)
--- End quote ---
While I haven't played with SBS11 I do "play" with servers on an (all) daily basis ... I never use the wizards. Much of that sounds like a DNS issue as it's critical to have it configured properly on a Windows domain. the http://connect is most likely a host header entry in/for the default IIS server ... So it should (probably) be http://connect.ServerName.TLD. ...Assuming you have a TLD - Please tell me you didn't pick a single label domain name...that always gets messy.
SoldierByte:
Ms Carol,
Over a year and a half ago I had a similar issue setting up
my win7 ultimate 32 AND 64 bit 12 core system...ssd, etc., etc.
Specially the connection, crashing, and access stuff with ie9..
Here is my assistance with others in regards to the delima..
Possibly some info there may help you..
SPECIALLY about sharing the links between 32 and 64 bit..
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
||||||||||||||||||||||||||||||||||||||||||||||||Begin copied post|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
I had the EXACT SAME problem... Freeze and could not do games, work, browse, surf or run anything..
I tried EVERYTHING on all these pages TWICE and stuff from ALL over the net.. FINALLY I found a cure..
Although I checked, re-checked, and even visited all the manufacture's sites and
even got the same answers at Window's update where I was ASSURED all my drivers were " up to date"..
Anyways, I downloaded "" slimdrivers "" ( from http://www.slimwareutilities.com/ )
that I got from the MajorGeeks site/domain.. ( http://majorgeeks.com/ )
I was SHOCKED to find my that ( among NUMEROUS other stuff )
my pci slots, and a BUNCH of other drivers that I was told were good..
were either outdated or not SPECIFIC for win 7 64..!! The software is free and pretty clean..
ONLY " con " is that when you get the software it wants to instal Yahoo crap
( i.e. toolbar and search to your browser ) and you got to delete it..!!
( do THAT AFTER you run the slimdriver program ) They want you to " register " but what the hell..
the software is FREE.. it WORKS, and a LOT of headaches and hassles now gone...!!
I have monkeyed in my BIOS, installed, reinstalled, deleted, added, edited registry,
restored and almost took a hammer to my machine.. I had just about given up....
But finally (as by this time I was willing to try ANYthing )
I now see that it IS a driver problem and NOT Win 7 64..
Hope this works for all yous..
May the God of your choice smile upon you and yours,
Take Care Stay Safe..
\\- SoldierByte -//
Note: MotherBoard is GIGABYTE G1.Guerrilla
Chipset is IntelCore i7-990X Gulftown 6x32 + 6x32 + 6x256 + 12M
I'm running with: Microsoft Windows 7 Ultimate (x64) Build 7601 ( SP1)
24 GB RAM Graphics are EVGA e-GeForce GTX 590 nVIDIA GeForce GTX 590 (GF110)
TWO dual Cards meaning FOUR PHYSICAL cards so I actually have 6 more GB of dedicated graphics memory..
utilizing PCIe v2.0 x16 (2.5 Gb/s) @ x16 (2.5 Gb/s) ............. Good Luck.. \\- SB -//
<<< ------------------- UPDATE ------------------- >>>
My crashing ( monm dsod), " freezing non-responsive " , no connecting,
etc., etc., etc.. problems started
approximately a month after original set-up of my computer system..
I instituted the above post solution 24 hours prior to
THAT ( the above ) post...
Since then I have run EXTENSIVE testing to
ascertain the problem HAS BEEN resolved..
I have had my computer on CONTINUOUSLY since
prior posting with NUMEROUS HARD and soft reboots..
I have done countless stress testing
both on CPU and GPU...
I have had NO FURTHER problems...
EVERYTHING works fine....
Now....
I am through testing and am now outta this forum..
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=---->>> If any
of yous need me... Ya know how to contact me..
Till then..........
Take Care & Stay Safe....
\\\ -- SoldierByte -- //
Solving the problem.....
Here is a quick fix for the computer illiterate..
( the problem lies within the dll's that are shared between both the 32bit and 64bit modes..)
Since modifying ANYthing within the dll files is both extremely difficult and dangerous..
Do the following.... Go to control panel.. Go to device manager..
now UNINSTALL your ( ALL of em )) graphics adapter ( s ).. ( NOT disable... UNINSTALL..!! )
now close all windows.. Turn off computer...
now re-start computer ( hard re-boot ) go into SAFE MODE ( pressing F-8 during BIOS )
again.. control panel.. device manager.. and choose Graphics Adapter.. and choose INSTAL ( for all of em )
when done now again close all windows...
SHUT DOWN computer .... NOW...
Start computer ( hard re-boot ) and just start Windows normally and access your account as you generally would..
What you have done is gotten rid of the old corrupted dll's and sharing links by providing brand new links...
To ascertain the validity and stability of the GPU in both 32 and 64 bit mode
you can run a registry scan and clean out the old crap....
All should work fine....
Yous all Take care Stay Safe...
\\-- SoldierByte --//
As I explained previously..
the problem lies with SHARED dll's being corrupted..!!!
MY freeze and hang-up occurrences have
been resolved by COMPLETELY uninstalling the said drivers
while in normal mode ( 64 bit )...
then REINSTALLING in safe mode ( 32 bit )..
Updating drivers and such has shown no occurrence..
Hope this is helpful to others..
\\\-- SoldierByte --///
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-END copied posting-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Maybe this will save you frustration, time, aggravation, and hell..!!
I hope I have been able to help..
SB
Carol Haynes:
I recently set up Windows SBS 2011 and connected my computer to the domain. Not an easy job as none of the methods suggested from the NEw User wizard on the server actually worked! It suggests opening http://connect on the machine you want to connect but there is absolutely no response from that address anywhere on the network. Installed the server 4 times without result - in the end I used a thumb drive and carried the connection software to the machine. Even so I had to manually establish a domain connection before it would let me run the proper connection software! What a bunch of crap. It also confirms why I never want to get involved in Windows servers for work! Could they produce more obscure software if they tried - it is 100% jargon and incredibly confusing wizards - and SBS 2011 is supposed to be the easiest server to set up in recent years.-Carol Haynes (June 08, 2012, 02:51 PM)
--- End quote ---
While I haven't played with SBS11 I do "play" with servers on an (all) daily basis ... I never use the wizards. Much of that sounds like a DNS issue as it's critical to have it configured properly on a Windows domain. the http://connect is most likely a host header entry in/for the default IIS server ... So it should (probably) be http://connect.ServerName.TLD. ...Assuming you have a TLD - Please tell me you didn't pick a single label domain name...that always gets messy.
-Stoic Joker (June 08, 2012, 03:38 PM)
--- End quote ---
Machine name is DCS-Server
Domain Name is DCS.local
The DNS works fine for all other purposes. I can use http://companyweb OK but http://connect just isn't there - and that is precisely what SBS11 tells you to type in a browser on a client machine. There is the option to connect to the domain by using a thumbdirve and running the connect software from that on each client but it doesn't work either. I have to first connect the computer to the domain via System properties and then it will run - which rather seems to defeat the object of the software. In SBS11 the connect software does more than the normal System Properties connection method (it installs extra software).
Carol Haynes:
Thanks SoldierByte for the info. Actually I don't think those are the issues I am experiencing. The system has been up and running for well over a year and it is only in the last few weeks that the problems have started happening.
My thought is that there are so many crap drivers on my system from installing games via Steam with numerous DRM-crapware methods I was expecting it to collapse at some point.
I haven't installed a new system since I changed the hardware as I move from an AMD SB890 to AMD SB990 system with AM3 processors and kept the same graphics and sound cards so the drivers are identical and they installed without a squeak. (AMD still recommend using AMD 8-series drivers for AMD-9 series motherboards - which is odd and perhaps says something about how little they have changed). Oddly the new board wasn't supplied with either SB or NB drivers! I have since clean uninstalled all AMD software, run Driver Sweeper to delete all the dregs left behind and installed the full Catalyst 11.12 drivers (I have had a lot of bad experiences since Catalyst 12 was released and so I am avoiding those, along with many other people, until the dust settles).
I did find loads of unuplugged/unused devices in device manager and deleted them. I have also run a Driver Verify test - it came up with Stream.sys as causing problems so I removed webcam software and anything else that was unneccssary and used WDM drivers - I also updated DirectX and Sound Drivers.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version