Please help, multiple Stop Errors and MFR/MBR Errors

[leeingrove]

Hi and thanks for looking, it seems if i fix one error another replaces it. though Stop Code 0x3B I have had 5 times yet not continuous. (Sorry if it looks a muddle Head is about to explode)

Yesterday after running sfc /scannow and dskchk /f my computer managed a full hour before freezing. Then it was back to normal blue screens I mean...

I ran dskchk earlier and in USN journal the master file tables BITMAP attributes are incorrect, thus the volume Bitmap is incorrect windows also found problems with the file system. Yet running chkdsk with the "f" attribute does not fix it like it says it will.

Because I have a Sony systems recovery Win 7 disk I cannot do a repair instal, also my d/l speed is slow so can't d/l win 7 iso.

Going to microsoft is no help all there hot fixes wont run in safe mode. This I find stupid as hot fixes are for stop errors.

Now for something else (which is why i am here)... After running defrag and normal boot I let it stay at login screen after 30 mins it froze, on restart normal mode, and before login box came up my windows is not activated etc etc. Then when I logged in told me my copy is not genuine. Before could do anything about it got a stop 0x3B. Tried again after restart got as far as activation checker when it crashed again. Previously before the defrag this was not an issue.

All my troubles started when my "ex" d/l a program called windows loader (this is what happens when you beleive a person who says they know all about computers) was installed (she said meant to just d/l to put on her lappy)...

Some how this prog has managed to corrupt the MBR and files in the system32 folder.


Below are the stop error reports and any help will be greatly appreciated.

Before anyone asks have thought about starting over with a clean format, but where is the fun in that.

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: VGN-N31S_W, Sony Corporation, VAIO
CPU: GenuineIntel Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2137186304 total
VM: 2147352576, free: 1971314688



On Mon 23/12/2013 16:35:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122313-24398-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003991A9B, 0xFFFFF88002C77120, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


On Sun 22/12/2013 18:08:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122213-21559-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0x2A7FFFFFFF98, 0x2, 0x0, 0xFFFFF800037587E5)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 22/12/2013 14:20:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122213-21200-01.dmp
This was probably caused by the following module: clfs.sys (CLFS+0x4FF8C)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF88000CCDF8C, 0x0, 0xFFFFFA800181D100)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\clfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Common Log File System Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 18/12/2013 21:07:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121813-21325-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800207E568, 0xFFFFF8800207DDC0, 0xFFFFF800037C3147)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 17/12/2013 23:50:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121813-21169-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003671B05, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 16/12/2013 23:29:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121613-25194-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x50 (0xFFFFF7FFD320EB9D, 0x8, 0xFFFFF7FFD320EB9D, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[leeingrove]

Sorry should point out that the BSOD is not the real problem I can handle that have added just for reference, it's the MBR and MFR that is the real problem.

Cheers

 

[gregrocker]

Work through the Troubleshooting Steps for Windows 7
starting with the hardware tests.

I'd also borrow a connection to download the Win7 ISO to invest in a Clean Reinstall - Factory OEM Windows 7 once you confirm the hardware conditions if the problems aren't quickly resolved. There's no point in fighting a ruined install when you are at the HQ for reinstalls of Win7 with us to help you get it perfect.

 

[matts6887]

+1 to gregrocker for those troubleshooting tips he published in that link. Every one of those steps is a valuable tool(s) in solving computer problem(s).

 

[matts6887]

also, try doing a sfc /scannow and or dskchk /f to scan for and possibly fix errors.