Solved Memory Management BSOD while surfing the internet - Win 7 64bit

[x BlueRobot]

[COLOR="Red"]BugCheck 1A[/COLOR], {[COLOR="Blue"]41790[/COLOR], [COLOR="SeaGreen"]fffffa80008fa0f0[/COLOR], [COLOR="Orange"]ffff[/COLOR], 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

Usual causes:  Device driver, memory, kernel

I would run Driver Verifier again, and try this:

Scan for any missing, modified or corrupted protected Windows files with:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[stg07]

Thanks for the quick reply, x BlueRobot. Will try out the steps now and get back to you later.

 

[stg07]

Have just enabled driver verifier and run scannow.

For scannow (1 run), there is a file it could not repair.

The sfcdetails text file is attached for your reference.

 

[x BlueRobot]

2013-08-10 13:11:47, Info                  CSI    00000300 [SR] Cannot repair member file [l:22{11}]"mighost.exe" of Microsoft-Windows-MigrationEngine, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-08-10 13:11:48, Info                  CSI    00000302 [SR] Cannot repair member file [l:22{11}]"mighost.exe" of Microsoft-Windows-MigrationEngine, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-08-10 13:11:48, Info                  CSI    00000303 [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
2013-08-10 13:11:48, Info                  CSI    00000306 [SR] Could not reproject corrupted file [ml:62{31},l:60{30}]"\??\C:\Windows\SysWOW64\migwiz"\[l:22{11}]"mighost.exe"; source file in store is also corrupted

2013-08-10 13:10:08, Info                  CSI    00000298 [SR] Cannot repair member file [l:22{11}]"mighost.exe" of Microsoft-Windows-MigrationEngine, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-08-10 13:10:11, Info                  CSI    0000029c [SR] Cannot repair member file [l:22{11}]"mighost.exe" of Microsoft-Windows-MigrationEngine, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-08-10 13:10:11, Info                  CSI    0000029d [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
2013-08-10 13:10:11, Info                  CSI    000002a0 [SR] Could not reproject corrupted file [ml:62{31},l:60{30}]"\??\C:\Windows\SysWOW64\migwiz"\[l:22{11}]"mighost.exe"; source file in store is also corrupted

The file also seems to be corrupted within the store too, therefore Windows will unlikely able to repair the file itself, even if we run the command three separate times, as a result I would suggest running a Repair Install.

 

[stg07]

The file also seems to be corrupted within the store too, therefore Windows will unlikely able to repair the file itself, even if we run the command three separate times, as a result I would suggest running a Repair Install.

Finally done with running a Repair Install as instructed in the link you gave me. What do I need to do now? Run both driver verifier and scannow again?

 

[x BlueRobot]

I'll run the System File Checker again to see if everything has been repaired

 

[stg07]

My 1st run of SFC after the repair install gave me this message: "Windows Resource Protection did not find any integrity violations". Driver Verifier was not enabled before running the SFC.

 

[x BlueRobot]

Okay that's good, use your system as you normally would for a few days, and then report back on how things are

 

[stg07]

No BSODs so far for the past week. So I will mark this as solved for now. Thanks again, x BlueRobot.

 

[x BlueRobot]

Glad to able to help