Randomly occuring "Memory Management" BSODs?

It's good to know that the system files have been repaired, and that's a good point about Driver Verifier, I was wondering that myself earlier.

Have you checked the Minidump directory?

Code:

%systemroot%\Minidump

It may be good idea to run Driver Verifier again.

No "new" dumps in the minidump folder.

... and ok, I'll switch on the verifier again.

Thanks, and just to make sure, ensure your settings are set to create Minidumps upon BSOD.

Dump Files - Configure Windows to Create on BSOD

It was set on creating a full dump. Changed it to a minidump.

... then I'll just wait and "hope" for a BSOD :-P

That was already appended to post #18. Attaching again.

No problem. I AM thankful for the support :)

Already ran SFC /SCANNOW an extra time after the first run/reboot. It reported no errors.

The log file from that run is attached.

Cheers // PelleK63

NoelDP said:

Sorry - musta missed it

Some interesting results in there...

Code:

2013-06-25 16:37:59, Error                 CSI    00000306 (F) c0000243 [Error,Facility=(system),Code=579 (0x0243)] #6273907# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation|AllowAccessDenied), handle = {provider=NULL, handle=0}, da = (FILE_GENERIC_READ|DELETE|WRITE_DAC|WRITE_OWNER|FILE_WRITE_ATTRIBUTES|FILE_WRITE_EA|FILE_APPEND_DATA|FILE_WRITE_DATA|0x00000040), oa = @0xeadc40->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[126]"\SystemRoot\WinSxS\amd64_microsoft-windows-font-truetype-gulim_31bf3856ad364e35_6.1.7600.16385_none_a1815c1476403b50\gulim.ttc"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0xeadc70, as = (null), fa = (FILE_ATTRIBUTE_NORMAL), sa = (FILE_SHARE_READ|FILE_SHARE_WRITE), cd = 5, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
[gle=0xd0000243]
2013-06-25 16:37:59, Error                 CSI    00000307@2013/6/25:14:37:59.789 (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(2057): Error c0000243 [Error,Facility=(system),Code=579 (0x0243)] originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
[gle=0x80004005]
2013-06-25 16:38:00, Error                 CSI    00000308 (F) c0000243 [Error,Facility=(system),Code=579 (0x0243)] #6273906# from Windows::Rtl::SystemImplementation::CDirectory::CreateNewFile(...)[gle=0xd0000243]
2013-06-25 16:38:00, Error                 CSI    00000309 (F) c0000243 [Error,Facility=(system),Code=579 (0x0243)] #6273901# from RtlRunPrimitiveOperationsFromCallbacksAgainstSil(...)[gle=0xd0000243]
2013-06-25 16:38:00, Info                  CSI    0000030a [SR] Unable to complete Verify and Repair transaction because some of the files that need to be repaired are in use. A reboot is required to complete this operation.

Code:

 Line 3537: 2013-06-25 16:38:00, Info                  CSI    0000030b [SR] Repairing 1 components
 Line 3538: 2013-06-25 16:38:00, Info                  CSI    0000030c [SR] Beginning Verify and Repair transaction
 Line 3541: 2013-06-25 16:38:00, Info                  CSI    0000030e [SR] Cannot repair member file [l:18{9}]"gulim.ttc" of Microsoft-Windows-Font-TrueType-Gulim, Version = 6.1.7600.16385, 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
 Line 3542: 2013-06-25 16:38:00, Info                  CSI    0000030f [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[l:18{9}]"gulim.ttc" by copying from backup
 Line 3545: 2013-06-25 16:38:01, Info                  CSI    00000311 [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:18{9}]"gulim.ttc" from store
 Line 3556: 2013-06-25 16:38:01, Info                  CSI    00000313 [SR] Repair complete

I'd recommend running SFC again - I'm not convinced that the repair worked as advertised :)

Yes, I ran chkdsk C: /f /r earlier today.

Apparentely there were some "damaged attribute posts" (?) (Don't know how to translate)

Chkdsk event log attached ... I hope you can read Swedish

Regards // PelleK63

NoelDP said:

That does appear to have worked.
The question arises why it caused the errors in my first clip - normally such errors would be the result of disk corruption.
Have you run CHKDSK C: /R to check the disk status (it could take a few hours to run!)
If not, please do so.

If/when you have, please post the results - they can be found in the Event Viewer, under Windows Logs\Application, as a Wininit event.