Windows 7: System File Checker

I am trying to use system file checker tool (sfc.exe) and I am running Windows 7 ult 64bit. I am CERTAIN that I have corrupted files in windows. When I try to use any of the programs like Windows Experience, Generate a system health report, or look at files in Event Log(event log is unable to give me proper codes says performance diag unavailable), i get error messages. When I try to use SFC.EXE through the command prompt i get an error message stating that I need a 64bit version of SFF.EXE. I DONT WANT TO DO A CLEAN INSTALL.

Have you tried a repair install?

when i installed the disk the install button came up, i clicked it and what should happen next, should i automaticly get the other options or will it create a temp folder first, etc..?

Are you following the tutorial step by step?

Put the disk in, click on setup, click on install, follow the rest of the instructions in the tutorial.

after doing this all seems well, except, so far the only thing im finding that won't work is my printer, i tried updating from samsung and uninstalling the printer then reboot and auto installed. the installer comes up with no errors(in fact it says device installed successfully, ready to use). But when i try to print something, anything, the spooler crashes and an error report is sent to ms. thank you for your help previously.

You're welcome. Have you run another elevated sfc/scannow to see if there's still corrupted files? Might do that.
Not sure about your printer, might look in Services, make sure the Print Spooler service is set to Automatic and Started. Also, might look in the Event Viewer and see if there is any information about it crashing under the event types that you could post, maybe someone will have an idea.

Log Name: Microsoft-Windows-PrintService/Admin
Source: Microsoft-Windows-PrintService
Date: 10/20/2009 2:19:51 PM
Event ID: 315
Task Category: Sharing a printer
Level: Error
Keywords: Classic Spooler Event,Printer
User: SYSTEM
Computer: James-PC
Description:
The print spooler failed to share printer Samsung ML-2010 Series with shared resource name Samsung ML-2010 Series. Error 2114. The printer cannot be used by others on the network.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-PrintService" Guid="{747EF6FD-E535-4D16-B510-42C90F6873A1}" />
<EventID>315</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>30</Task>
<Opcode>12</Opcode>
<Keywords>0x8000000000000820</Keywords>
<TimeCreated SystemTime="2009-10-20T18:19:51.109375000Z" />
<EventRecordID>53</EventRecordID>
<Correlation />
<Execution ProcessID="1212" ThreadID="2628" />
<Channel>Microsoft-Windows-PrintService/Admin</Channel>
<Computer>James-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<ShareFailed xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2...er/core/events">
<Param1>2114</Param1>
<Param2>Samsung ML-2010 Series</Param2>
<Param3>Samsung ML-2010 Series</Param3>
</ShareFailed>
</UserData>
</Event>

this was an auto fix that windows used, for the following error;

Log Name: Microsoft-Windows-PrintService/Admin
Source: Microsoft-Windows-PrintService
Date: 10/20/2009 2:19:51 PM
Event ID: 315
Task Category: Sharing a printer
Level: Error
Keywords: Classic Spooler Event,Printer
User: SYSTEM
Computer: James-PC
Description:
The print spooler failed to share printer Samsung ML-2010 Series with shared resource name Samsung ML-2010 Series. Error 2114. The printer cannot be used by others on the network.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-PrintService" Guid="{747EF6FD-E535-4D16-B510-42C90F6873A1}" />
<EventID>315</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>30</Task>
<Opcode>12</Opcode>
<Keywords>0x8000000000000820</Keywords>
<TimeCreated SystemTime="2009-10-20T18:19:51.109375000Z" />
<EventRecordID>53</EventRecordID>
<Correlation />
<Execution ProcessID="1212" ThreadID="2628" />
<Channel>Microsoft-Windows-PrintService/Admin</Channel>
<Computer>James-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<ShareFailed xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2...er/core/events">
<Param1>2114</Param1>
<Param2>Samsung ML-2010 Series</Param2>
<Param3>Samsung ML-2010 Series</Param3>
</ShareFailed>
</UserData>
</Event>

also found this one;

Log Name: Application
Source: Application Error
Date: 10/21/2009 2:16:10 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: James-PC
Description:
Faulting application name: splwow64.exe, version: 6.1.7100.0, time stamp: 0x49eea123
Faulting module name: SUGS2UM.DLL, version: 0.3.8.0, time stamp: 0x45a6fbc5
Exception code: 0xc0000005
Fault offset: 0x0000000000015eb2
Faulting process id: 0xd0c
Faulting application start time: 0x01ca527a8d53e0fe
Faulting application path: C:\Windows\splwow64.exe
Faulting module path: C:\WINDOWS\SYSTEM32\SPOOL\DRIVERS\X64\3\SUGS2UM.DLL
Report Id: ceb7b71e-be6d-11de-994c-00242112a29d
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-10-21T18:16:10.000000000Z" />
<EventRecordID>15305</EventRecordID>
<Channel>Application</Channel>
<Computer>James-PC</Computer>
<Security />
</System>
<EventData>
<Data>splwow64.exe</Data>
<Data>6.1.7100.0</Data>
<Data>49eea123</Data>
<Data>SUGS2UM.DLL</Data>
<Data>0.3.8.0</Data>
<Data>45a6fbc5</Data>
<Data>c0000005</Data>
<Data>0000000000015eb2</Data>
<Data>d0c</Data>
<Data>01ca527a8d53e0fe</Data>
<Data>C:\Windows\splwow64.exe</Data>
<Data>C:\WINDOWS\SYSTEM32\SPOOL\DRIVERS\X64\3\SUGS2UM.DLL</Data>
<Data>ceb7b71e-be6d-11de-994c-00242112a29d</Data>
</EventData>
</Event>

James

this app crash was caused by splwow64.exe. this is the print spooler WOW (meaning so 32 bit can run in 64bit)


Ken

i kinda got that, any ideas on how to fix it?