Nope nothing. Also, could this problem have anything to do with me using Ethernet connection because I started using Ethernet instead of wireless connection at our school just couple of weeks ago and that's around the time this problem started occurring?
Oh I see. Well could be since such stuff never happened until you got that installed.. Try keeping it away and see if the problem occurs?
I've tried that by not using ethernet at all past two weeks but it hasn't solved the problem yet.
Guess you should take some hardware tests:
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
The goal is to test all the RAM sticks and all the motherboard slots.
Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.
If you get errors, stop the test and continue with the next step.
1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.
2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.
If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.
In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.Errors are sometimes found after 8 passes.
There is only the one serious problem with the CBS.log (there is a minor one, that I suspect may be fixed as part of the repair I'll post later).
This shouldn't present any problem.Code:Info CSI 0000041d [SR] Cannot repair member file [l:24{12}]"MFC90FRA.DLL" of Microsoft.VC90.MFCLOC, Version = 9.0.30729.1, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral in the store, hash mismatch
CheckSUR found and fixed one problem - with a catalog file for a policy setting....
It's interesting to not that thse two problems are related to the same component - VC 2008Code:(f) CSI Catalog Corrupt 0x800B0003 winsxs\Catalogs\fe0fac4e315b16deed38f335d82d54236d1dddb87577f2cadc062421a1e828a3.cat policy.9.0...vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.1_39e222e84b9e7e6f (fix) CSI Catalog Corrupt CSI File Replaced Deleted CatalogThumbprint
I think that a second run of SFC may be a good idea to confirm that replacing the catalog file hasn't either fixed the problem or brought more to light, before attempting to solve it manually.
Quote