New
#11
PFN_LIST_CORRUPT was the what I got this time, MSE wouldn't install, I ended up doing malewarebytes (free version), I removed Norton before I tried installing MSE.
Last edited by morezozy; 03 Jul 2014 at 09:50.
PFN_LIST_CORRUPT was the what I got this time, MSE wouldn't install, I ended up doing malewarebytes (free version), I removed Norton before I tried installing MSE.
Last edited by morezozy; 03 Jul 2014 at 09:50.
Still too many memory corruption errors.Code:Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Debug session time: Thu Jul 3 19:31:09.736 2014 (UTC + 6:00) System Uptime: 0 days 1:50:18.564 BugCheck 4E, {99, 1f0b16, 2, 1d2b17} Probably caused by : memory_corruption ( nt!MiBadShareCount+4c ) BUGCHECK_STR: 0x4E_99 PROCESS_NAME: SearchProtocol ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Debug session time: Thu Jul 3 09:56:36.306 2014 (UTC + 6:00) System Uptime: 1 days 9:08:36.134 BugCheck 1A, {41201, fffff680000057c8, c7b00001a75c4867, fffffa800b7b1650} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13702 ) BUGCHECK_STR: 0x1a_41201 PROCESS_NAME: SearchProtocol ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Debug session time: Wed Jul 2 00:47:36.287 2014 (UTC + 6:00) System Uptime: 0 days 8:59:58.114 BugCheck 1A, {41201, fffff680007fc7c8, b7b0000124de1867, fffffa800a62d2e0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13702 ) BUGCHECK_STR: 0x1a_41201 PROCESS_NAME: SearchProtocol ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Debug session time: Tue Jul 1 15:46:49.697 2014 (UTC + 6:00) System Uptime: 0 days 22:03:14.524 BugCheck 3B, {c000001d, fffff80003ebe402, fffff88012a92d60, 0} Probably caused by : memory_corruption BUGCHECK_STR: 0x3B PROCESS_NAME: SearchProtocol ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Could you follow this part for memtest:
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.InformationErrors are sometimes found after 8 passes.
TipMemtest should be done overnight.