New
#1
1st BSOD then Windows 7 freezes after random time (30 min to 1 hour)
I first experiment a BSOD as computer freezes. Windows rebooted automatically and then it enters a dialog to re-install Windows 7 automatically, no devices detected.
I reboot again and then everything works fine but after random period of time windows completely freezes ( like main browser, either Firefox or chrome appears out of response). If none of these are open, the File Explorer freezes one time but mainly freezes on explorer applications.
While this happens, i can still move mouse wherever i want, however no click works nor Ctrl+Alt+Del. I think no specific program cause this because in the afternoon i felt asleep and when i wake up, computer was with black screen freezing.
Run Memory Test and Chkdsk tests, everything is fine. Sfc reports corrupted system files but i don't think it's relevant as a quick google search has reported it as a false positive, it's the following :
2012-10-12 13:58:42, Info CSI 000000e6 [SR] Cannot repair member file [l:22{11}]"PINTLGB.IMD" of Microsoft-Windows-IME-Simplified-Chinese-Core, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-10-12 13:58:42, Info CSI 000000e7 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2012-10-12 13:58:42, Info CSI 000000ea [SR] Could not reproject corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:22{11}]"PINTLGB.IMD"; source file in store is also corrupted
2012-10-12 13:58:42, Info CSI 000000ec [SR] Verify complete
-----------
Main Things I changed in my system.
- I tweek my SSD hardware w a guide like 4-5 days ago. No problem with that afterwards
- Windows update ran 24 hours ago. Since then i always have like 2 updates pending. After updating successfully, Windows still recommend an update.
- There are many PostgresSQL errors but they don't match with freezing times in the event logs.
That's all i can think for now.
Thanks for your help