HD health and more

Not sure if this will help but you may like to try these mem testers, particularly the first three. (All Free) They use different methods of testing and may find something that the Win 7 diagnostic couldn't. They run from a bootable CD.

http://pcsupport.about.com/od/toolsofthetrade/tp/memorytest.htm


Have you looked at your error logs? They may just give you a clue, perhaps a common program that is always running when the fault occurs or a driver issue.

 

yes I tried upgrade adviser no problems there, and no apologies needed, i can use all the help i need.

i saw a few red and yellows in the logs but have no idea what they mean, ill post a few here.

im assuming swapping ram modules is a better "test" (correct me if im wrong) so ill follow PeteCs advice on that.

 

Event viewer / windows logs / Applications (warnings)
=========
Log Name: Application
Source: Microsoft-Windows-Security-SPP
Date: 10/2/2010 12:20:02 PM
Event ID: 1021
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: HomeMaster
Description:
sppuinotify service has failed to start. 0x80070426
Event Xml:

===============
Log Name: Application
Source: Microsoft-Windows-Search
Date: 10/2/2010 11:59:30 AM
Event ID: 3036
Task Category: Gatherer
Level: Warning
Keywords: Classic
User: N/A
Computer: HomeMaster
Description:
The content source <csc://{S-1-5-18}/> cannot be accessed.

Context: Windows Application, SystemIndex Catalog

Details:
(HRESULT : 0x80004005) (0x80004005)

Event Xml:
Context: Windows Application, SystemIndex Catalog

Details:
(HRESULT : 0x80004005) (0x80004005)
===========
Log Name: Application
Source: Microsoft-Windows-Search
Date: 10/2/2010 11:59:30 AM
Event ID: 3036
Task Category: Gatherer
Level: Warning
Keywords: Classic
User: N/A
Computer: HomeMaster
Description:
The content source <csc://{S-1-5-18}/> cannot be accessed.

Context: Windows Application, SystemIndex Catalog

Details:
(HRESULT : 0x80004005) (0x80004005)

Event Xml:
Context: Windows Application, SystemIndex Catalog

Details:
(HRESULT : 0x80004005) (0x80004005)

================
Log Name: Application
Source: Microsoft-Windows-Search
Date: 10/2/2010 11:51:15 AM
Event ID: 1008
Task Category: Search service
Level: Warning
Keywords: Classic
User: N/A
Computer: HomeMaster
Description:
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Index Corruption}.

Event Xml:

 

Event viewer / windows logs / Applications (errors)

Log Name: Application
Source: Microsoft-Windows-Search
Date: 10/2/2010 11:50:44 AM
Event ID: 7042
Task Category: Gatherer
Level: Error
Keywords: Classic
User: N/A
Computer: HomeMaster
Description:
The Windows Search Service is being stopped because there is a problem with the indexer: The catalog is corrupt.

Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

Event Xml:


Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

==========
Log Name: Application
Source: Microsoft-Windows-Search
Date: 10/2/2010 11:50:44 AM
Event ID: 7040
Task Category: Gatherer
Level: Error
Keywords: Classic
User: N/A
Computer: HomeMaster
Description:
The search service has detected corrupted data files in the index {id=4400}. The service will attempt to automatically correct this problem by rebuilding the index.

Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

Event Xml:

Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

=========
Log Name: Application
Source: Microsoft-Windows-Search
Date: 10/2/2010 11:50:44 AM
Event ID: 7010
Task Category: Gatherer
Level: Error
Keywords: Classic
User: N/A
Computer: HomeMaster
Description:
The index cannot be initialized.

Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

Event Xml:


Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)

=======

lots of "search" errors.

 

are those helpful in any way? or am i looking in the wrong places?

 

i already started removed 3 modules I am on 2 GB at the moment.

here is a newbie question, since my problems (freeze or BSOD) are random how would i know i have bad ram (when swapping them around)

 

np petec, have fun in US

 

thx for confirming that

 

I am far from experienced at reading error logs but the windows indexing service is mentioned. From a search for a solution to that error I found this. Just running sfc /scannow may do the job, watch and see if it finds any problems.

 

edit: actually i think i should wait a day or 2 and see if anything changed before i continue.

but will post results of scan when its done

ty

 

You have not run the scan, try this.

When cmd appears in the box above search, right click on it and select 'run as administrator' then type in sfc /scannow at the command prompt (observe the space before slash) and hit enter, it should then perform the scan.

If that finds nothing you may have to delete the indexing service and reinstall it, meanwhile you could disable it and see if the problem persists.

 

i noticed the typo in the command that's why i edited my previous post.

its done found errors but couldn't fix them, log is 3.23 MB.

2010-09-29 13:16:05, Info CBS SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
2010-09-29 13:16:05, Info CBS SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
2010-09-29 13:16:05, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
2010-09-29 13:16:05, Info CBS SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]

those were part of the 1st 15 lines of Log.

looked into the registry and SetupCompleted is still set to 1.

going to try to disable indexing as per your instructions

Edit: Windows Search disabled

Edit: found how to delete and rebuild index
control panel / indexing options / Advanced / rebuild
i think this would be a better (permanent) solution if it works.

id like to keep this thread open to add updates for any error logs related to search plus I am still checking my RAM modules and slots.

 

OK, best of luck, hope you find the cause which will be useful for future reference.

 

if its the indexing thing, then i believe i know what the cause is.
if you noticed the thread where we found the sfc /scannow command.

the guy with the problem said he had recently upgraded from an OS to an other, my problems started when i upgraded from vista 32 to vista 64.

when I installed win 7 i noticed an "invalid user" while moving my personal folders from drive C to drive D.

so im thinking the indexing corruptions are caused by invalid user permission (if that makes sense to any1) i think those were users from previous windows installations that no longer exist.



ill know for sure if the logs return more search/indexing related errors.

 

Ummm, not sure about that, but I would not have thought that previously set permissions could cause a problem, but perhaps someone with more knowledge of this could shine more light on the issue.

Looking back throught the posts I noticed something:

This comment:

Does this mean you have some 64bit programs still running.

You then you said:

This is where I am confused as the first comment says that it is 64bit systems that are freezing.

As you are back on a 32bit OS you should have all your software and drivers back to 32bit. Your comments suggest you still have something running on 64bit


Further confusion you have now just said:

So just to clarify, you then changed Vista 64 to Win 7 64bit and then onto Win 7 32bit. Did you also change all your drivers and software to match the OS and 32 or 64 bit

 

here is the detailed history of the PC.
- Bought the hardware in august 2009.
- Installed vista ultimate 32 (thinking that the SP1 that would allow vista to recognize the 8gb of ram would actually let it use the 8 gb of ram. I was actually content with vista had no problems with it once i got used to the new OS)
- In October or November I upgraded to vista ultimate 64, (that's when the random freezing and very rare BSOD's started) I reformatted several times and started a few threads about it in here with no solution.
- 2 weeks ago (week end of the 17th, i decided ill test win 7 64, thinking if it works ill buy it if not ill go back to XP)
5 or 6 days after installation PC started having BSOD after BSOD (PC restarts as soon as windows loaded got a new BSOD).
I reformatted and installed win 7 Ultimate 32, and that's where we are right now: trying to figure out what is wrong with my system. (when i mentioned my PC doesn't play well with 64 its cause i hadn't experience any trouble with win 7 32 either, but I had spoken too soon.

I didnt think that was possible either and id think if that was the case lots more ppl would be experiencing that issue, that was just a shot in the dark