Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Randomly occuring "Memory Management" BSODs?


25 Jun 2013   #21

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

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.


My System SpecsSystem Spec
.

25 Jun 2013   #22

Windows 7 Home Premium x64
 
 

No "new" dumps in the minidump folder.

... and ok, I'll switch on the verifier again.
My System SpecsSystem Spec
25 Jun 2013   #23

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

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

Dump Files - Configure Windows to Create on BSOD
My System SpecsSystem Spec
.


25 Jun 2013   #24

Windows 7 Home Premium x64
 
 

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

... then I'll just wait and "hope" for a BSOD :-P
My System SpecsSystem Spec
25 Jun 2013   #25

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

Quote   Quote: Originally Posted by PelleK63 View Post
Oh, the errors found with SFC /SCANNOW were repaired on the first run/reboot. I just ran the test a second time and there were no errors found.

Clarification concerning driver verifier - it could very well be that it was driver verifier that induced the last two BSODs. Problem is just that the PC never continued with a reboot from those BSODs. I had to physically reset the PC and then there were never any dump files created? Not any that the SF Diag tool found anyway.
Please post the CBS.log file anyhow - it contains a lot more than just the SFC results!.
My System SpecsSystem Spec
25 Jun 2013   #26

Windows 7 Home Premium x64
 
 

That was already appended to post #18. Attaching again.
My System SpecsSystem Spec
25 Jun 2013   #27

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

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
My System SpecsSystem Spec
25 Jun 2013   #28

Windows 7 Home Premium x64
 
 

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

Quote   Quote: Originally Posted by NoelDP View Post
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
My System SpecsSystem Spec
25 Jun 2013   #29

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

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.
My System SpecsSystem Spec
25 Jun 2013   #30

Windows 7 Home Premium x64
 
 

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

Quote   Quote: Originally Posted by NoelDP View Post
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.
My System SpecsSystem Spec
Reply

 Randomly occuring "Memory Management" BSODs?




Thread Tools



Similar help and support threads for2: Randomly occuring "Memory Management" BSODs?
Thread Forum
Recently having this BSOD called "Memory Management" BSOD Help and Support
BSOD Randomly Occuring MEMORY MANAGEMENT BSOD Help and Support
Random BSODS (mostly "memory management"), often on startup BSOD Help and Support
Solved BSODs occuring randomly and increasingly more frequent. BSOD Help and Support
Random "Bad Pool Header" and "System Service Exception" BSODs BSOD Help and Support
Randomly occuring 7f BSoDs BSOD Help and Support
"Random" sproadic BSODs - Memory or video? BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 09:04 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33