Frequent BSOD: Memory_Management (CUSTOM BUILT)

[Whalen207]

If you have a USB Flash drive the link below requires a USB Flash drive. Save the contents of your flash drive onto your Computer then once you're done with the Memory test move them back to the flash drive

:ar: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

If you have any errors . Take a look at Part 3. But you have a Dual Channel memory kit so if you get any errors . Stop the Test and check with the memory manufacture to see if you're still under warranty and RMA both of the memory sticks .

I will run that test later today, once I have more time.
I've learned they tend to take quite some time.

 

[VistaKing]

Best result is to leave it run over night.

 

[Whalen207]

Just having it run and let every single test (0-9) run at least three times have me ~>10,000 Error reports, having reports pop up for almost every single test.

Could that still be attributed to a shotty memory controller / bent pins / bad memory ports? Or is it definitively going to be the RAM Sticks themselves? I could try switching ports, but if the Memtest points to it definitely being the sticks I'll RMA them.

 

[VistaKing]

Test each RAM stick on every slot now . That will tell you if its the RAM or the slot

If the memory passes on one slot and fails in another it could mean you might have a bad slot so test it on the next slot if it passes then you could rule out the slot to be the issue. But If you get error messages on one slot and and error on the other slot that's a bad ram .

Dual Channel memory kits is replacing both RAM sticks even if one of the sticks is good .

 

[tom982]

Hello Whalen207, welcome to the forums

I have reviewed your CBS log and think it's safe to say the corruption found by SFC is causing your computer to freeze:

2013-05-28 13:50:46, Info                  CSI    0000027b [SR] Beginning Verify and Repair transaction
2013-05-28 13:50:47, Info                  CSI    0000027c Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-videosamples_31bf3856ad364e35_6.1.7600.16385_none_51a21f033003affd\Wildlife.wmv do not match actual file [l:24{12}]"Wildlife.wmv" :
  Found: {l:32 b:t1OnvzNjTEApf/B1H5fBcCnQQiR9GCcVLGW+mgxhHjg=} Expected: {l:32 b:Ba78lQJTTKxpaiXlAgrkCrvCoryRipkCpgZzhJoIV7Q=}
2013-05-28 13:50:47, Info                  CSI    0000027d [SR] Cannot repair member file [l:24{12}]"Wildlife.wmv" of Microsoft-Windows-VideoSamples, 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
2013-05-28 13:50:47, Info                  CSI    0000027e Hashes for file member \SystemRoot\WinSxS\amd64_nv_lh.inf_31bf3856ad364e35_6.1.7600.16385_none_4a5c7d78e486512b\nvlddmkm.sys do not match actual file [l:24{12}]"nvlddmkm.sys" :
  Found: {l:32 b:NXBNcvqSnZo6VAz41N/pyPTXBZB/ERYh8v/DForV784=} Expected: {l:32 b:Ft9NlkUjjRAU+pGJ/xcdz3t8dXP3WbWscwJVGBOdhrE=}
2013-05-28 13:50:47, Info                  CSI    0000027f [SR] Cannot repair member file [l:24{12}]"nvlddmkm.sys" of nv_lh.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-05-28 13:50:47, Info                  CSI    00000280 Hashes for file member \SystemRoot\WinSxS\amd64_prnep00b.inf_31bf3856ad364e35_6.1.7600.16385_none_ad2d68ddc89d49d5\Amd64\EP0NRE8M.DLL do not match actual file [l:36{18}]"Amd64\EP0NRE8M.DLL" :
  Found: {l:32 b:qLrdjMQw3IYPTzHxGf0CR/iSMwFzKXt7oB01vQphzLE=} Expected: {l:32 b:OjoI3UTrBcgOFifLKMgy2du18n5bO+n5XZMmnBG9W+o=}
2013-05-28 13:50:47, Info                  CSI    00000281 [SR] Cannot repair member file [l:36{18}]"Amd64\EP0NRE8M.DLL" of prnep00b.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-05-28 13:50:47, Info                  CSI    00000282 Hashes for file member \SystemRoot\WinSxS\amd64_nv_lh.inf_31bf3856ad364e35_6.1.7600.16385_none_4a5c7d78e486512b\nvlddmkm.sys do not match actual file [l:24{12}]"nvlddmkm.sys" :
  Found: {l:32 b:NXBNcvqSnZo6VAz41N/pyPTXBZB/ERYh8v/DForV784=} Expected: {l:32 b:Ft9NlkUjjRAU+pGJ/xcdz3t8dXP3WbWscwJVGBOdhrE=}
2013-05-28 13:50:47, Info                  CSI    00000283 [SR] Cannot repair member file [l:24{12}]"nvlddmkm.sys" of nv_lh.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-05-28 13:50:47, Info                  CSI    00000284 [SR] This component was referenced by [l:178{89}]"Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.INF_nv_lh"
2013-05-28 13:50:47, Info                  CSI    00000285 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-videosamples_31bf3856ad364e35_6.1.7600.16385_none_51a21f033003affd\Wildlife.wmv do not match actual file [l:24{12}]"Wildlife.wmv" :
  Found: {l:32 b:t1OnvzNjTEApf/B1H5fBcCnQQiR9GCcVLGW+mgxhHjg=} Expected: {l:32 b:Ba78lQJTTKxpaiXlAgrkCrvCoryRipkCpgZzhJoIV7Q=}
2013-05-28 13:50:47, Info                  CSI    00000286 [SR] Cannot repair member file [l:24{12}]"Wildlife.wmv" of Microsoft-Windows-VideoSamples, 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
2013-05-28 13:50:47, Info                  CSI    00000287 [SR] This component was referenced by [l:194{97}]"Microsoft-Windows-SampleContent-Music-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.MusicSamples"
2013-05-28 13:50:47, Info                  CSI    00000288 Hashes for file member \SystemRoot\WinSxS\amd64_prnep00b.inf_31bf3856ad364e35_6.1.7600.16385_none_ad2d68ddc89d49d5\Amd64\EP0NRE8M.DLL do not match actual file [l:36{18}]"Amd64\EP0NRE8M.DLL" :
  Found: {l:32 b:qLrdjMQw3IYPTzHxGf0CR/iSMwFzKXt7oB01vQphzLE=} Expected: {l:32 b:OjoI3UTrBcgOFifLKMgy2du18n5bO+n5XZMmnBG9W+o=}
2013-05-28 13:50:47, Info                  CSI    00000289 [SR] Cannot repair member file [l:36{18}]"Amd64\EP0NRE8M.DLL" of prnep00b.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-05-28 13:50:47, Info                  CSI    0000028a [SR] This component was referenced by [l:186{93}]"Microsoft-Windows-Printer-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.INF_prnep00b

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download the attached file, SFCFix.txt, and save this to your Desktop. Ensure that this file is named SFCFix.txt - do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.txt.
5. Drag the file SFCFix.txt onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
8. Copy (Ctrl + C) and Paste (Ctrl + V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

https://dl.dropboxusercontent.com/u/16537616/SFCFix/Scripts/Whalen207/SFCFix.txt

But this corruption isn't why SFC failed to complete. If we look towards the end of the CBS log, you will see this:

2013-05-28 13:50:46, Error                 CSI    00000276 (F) Invalid attribute name found: [l:42{21}]"ProcessorArchitucture"[gle=0x80004005]
2013-05-28 13:50:46, Error                 CSI    00000277@2013/5/28:18:50:46.207 (F) d:\win7sp1_gdr\base\wcp\identity\id_baseidentity.cpp(1263): Error STATUS_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME originated in function Windows::Identity::Rtl::Implementation::CRtlIdentityBase::CRtlIdentityBase_Initialize expression: pBAI != 0
[gle=0x80004005]
2013-05-28 13:50:46, Error                 CSI    00000278 (F) STATUS_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME #5179054# from Windows::Identity::Rtl::Implementation::CRtlIdentityAuthority::IRtlIdentityAuthority_Parse(flags = 0, string = [l:312{156}]"Microsoft-Windows-extrac32.Resources, Culture=en-US, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitucture=x86, versionScope=NonSxS")
[gle=0xd0150017]

What's happened here is known as a bitflip, where one bit in a binary byte flips from a 0 to a 1, or vice versa.

What you have: ProcessorArchitucture=x86
What it should be: ProcessorArchitecture=x86

u: 01110101
e: 01100101

As you can see, these characters differ by just one byte. To fix this I will have to manually repair your COMPONENTS registry hive:

Upload a file to Dropbox

Note: If you prefer, the same techniques can be applied to your Skydrive however these instructions may not necessarily work for Skydrive.

1. If you haven't already created a Dropbox account, please do so Here
2. Although this procedure can be done directly through the website, it is much easier to do so via the Windows client which can be downloaded from the Dropbox website:
   
   https://www.dropbox.com/install
3. After you have downloaded and installed that, you should now see Dropbox in your Favourites box in Windows Explorer. This is the folder that will be synchronised with the Dropbox servers, anything that you wish to back up online can be put in here, but today we will be using it to transfer files.
   
   
   
   
4. To access your Dropbox folder, just click on the link in the top left hand corner of Windows Explorer (accessible from any location - Documents etc.). Alternatively, you can double click on the icon
   
   found in your system tray (next to the time). If you are still having issues locating this folder, unless otherwise specified, it can be found under this location: C:\Users\{Your username}\Dropbox
5. Copy all of the following files to the Public folder in your Dropbox:
   • C:\Windows\system32\config\components (it has no file extension)
6. Select all files by pressing Ctrl+A then right-click and select Send to > Compressed (zipped) folder
7. This will create a .zip
   
   file in your Public folder.
8. Right-click on this file and select Dropbox > Copy Public Link then Paste (Ctrl + V) this link into your next post for me please

Tom

 

[Whalen207]

Thanks for all the advice, but dragging 'SFCFix.txt' to 'SFCFix.exe' rapidly opens a cmd-esque window then quickly closes it, returning this text:

SFCFix version 1.5.5.0 by niemiro.
Start time: 2013-05-29 02:09:04.628
Using .txt script file at C:\Users\Jack\Desktop\SFCFix.txt




Successfully processed all directives.
SFCFix version 1.5.5.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2013-05-29 02:09:04.628
----------------------EOF-----------------------

EDIT: I'm stupid, give me a second to download the actual SFCFix.txt from dropbox and drag it >.<
EDIT2: Okay, here's the dump after a restart and an odd chkdsk during startup:

SFCFix version 1.5.5.0 by niemiro.
Start time: 2013-05-29 02:12:20.051
Using .txt script file at C:\Users\Jack\Desktop\SFCFix.txt




PowerCopy::
Successfully took permissions for file or folder C:\Windows\Sysnative\drivers\nvlddmkm.sys
Successfully took permissions for file or folder C:\Users\Public\Videos
Successfully took permissions for file or folder C:\Windows\System32\DriverStore\FileRepository\prnep00b.inf_amd64_neutral_2e6b718b2b177506\Amd64\EP0NRE8M.DLL

Successfully created directory tree \\?\C:\Users\Public\Videos\SampleVideos.

Successfully copied file \\?\C:\Windows\winsxs\amd64_nv_lh.inf_31bf3856ad364e35_6.1.7600.16385_none_4a5c7d78e486512b\nvlddmkm.sys to \\?\C:\Windows\Sysnative\drivers\nvlddmkm.sys.
Successfully copied file \\?\C:\Windows\WinSxS\amd64_microsoft-windows-videosamples_31bf3856ad364e35_6.1.7600.16385_none_51a21f033003affd\Wildlife.wmv to \\?\C:\Users\Public\Videos\SampleVideos\Wildlife.wmv.
The file \\?\C:\Windows\System32\DriverStore\FileRepository\prnep00b.inf_amd64_neutral_2e6b718b2b177506\Amd64\EP0NRE8M.DLL is in use and must be replaced over a reboot.

Successfully pended file for replace over reboot: \\?\C:\Windows\System32\DriverStore\FileRepository\prnep00b.inf_amd64_neutral_2e6b718b2b177506\Amd64\EP0NRE8M.DLL

Successfully restored ownership for C:\Windows\Sysnative\drivers\nvlddmkm.sys
Successfully restored permissions on C:\Windows\Sysnative\drivers\nvlddmkm.sys
Successfully restored ownership for C:\Users\Public\Videos
Successfully restored permissions on C:\Users\Public\Videos
PowerCopy:: directive completed successfully.




Reboot:: directive completed successfully.




PostRebootCorruptionDetection::
No hash verification failures detected.
PostRebootCorruptionDetection:: directive completed successfully.




PostRebootRestorePermissions::
Successfully restored ownership for C:\Windows\System32\DriverStore\FileRepository\prnep00b.inf_amd64_neutral_2e6b718b2b177506\Amd64\EP0NRE8M.DLL
Successfully restored permissions on C:\Windows\System32\DriverStore\FileRepository\prnep00b.inf_amd64_neutral_2e6b718b2b177506\Amd64\EP0NRE8M.DLL
PostRebootRestorePermissions:: directive completed successfully.




Successfully processed all directives.
SFCFix version 1.5.5.0 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2013-05-29 02:16:00.325
----------------------EOF-----------------------

 

[Whalen207]

Even after running that script, another BSOD. Got it when I started install a new game (Arma III L) onto my E: drive via Steam.

 

[Whalen207]

And yes, I do realize the script was intended only to demonstrate that it couldn't fix something, and it's very odd that it completed. Instead of being incomplete as you implied it would end up as.

 

[tom982]

And yes, I do realize the script was intended only to demonstrate that it couldn't fix something, and it's very odd that it completed. Instead of being incomplete as you implied it would end up as.

Huh? It successfully fixed three problems so I'm not sure what you're on about. I would appreciate it if you could follow all of my instructions:

http://www.sevenforums.com/bsod-hel...ry_management-custom-built-3.html#post2414766


Tom

 

[Whalen207]

But this corruption isn't why SFC failed to complete. If we look towards the end of the CBS log, you will see this: *CODECODECODE*

I assumed, due to this part of your message, that your intention of sending me the SFC file and having me run it was to demonstrate something not operating correctly, something that would be fixed in the large second part of your message regarding DropBox files and me sending you detailed logs, etc etc.

Hence when SFC compiled and executed flawlessly I mistakenly thought something was wrong, and that it was not supposed to operate in such a manner.

So where does that leave us... I suppose the next step is to upload the files you requested, yes?

 

[tom982]

But this corruption isn't why SFC failed to complete. If we look towards the end of the CBS log, you will see this: *CODECODECODE*

I assumed, due to this part of your message, that your intention of sending me the SFC file and having me run it was to demonstrate something not operating correctly, something that would be fixed in the large second part of your message regarding DropBox files and me sending you detailed logs, etc etc.

Hence when SFC compiled and executed flawlessly I mistakenly thought something was wrong, and that it was not supposed to operate in such a manner.

So where does that leave us... I suppose the next step is to upload the files you requested, yes?

Hi Whalen207,


Oh, sorry for the confusion! While the two issues I identified are both SFC related, they are at completely different ends of the spectrum and aren't linked at all. Windows is helpless when this sort of registry corruption happens and requires people like me to come along and tidy up the mess So yes, if you could upload the components file, that would be great. After downloading it, it is a 30 second fix at my end and I'll have it re-uploaded as soon as possible.


Tom

 

[Whalen207]

Okay, I'll get the file to you asap. You don't mind if I use filesmelt instead of dropbox, do you? I just find the latter to be a much bigger hassle (you can use dropbox if you want).

Of course since it is a System file we're talking about I'll either need to boot up in Safemode or another OS entirely to mess with it (copy it, in this case), so let me finish what I'm working on atm.

 

[tom982]

Nope, any website is fine with me! Either way, make sure you zip it up before uploading - I've got to live with a 2MB/s connection here!

You don't have to boot into safe mode or anything like that, copy it to your Desktop, compress it and upload it. Simple

 

[Whalen207]

Nope, any website is fine with me! Either way, make sure you zip it up before uploading - I've got to live with a 2MB/s connection here!

You don't have to boot into safe mode or anything like that, copy it to your Desktop, compress it and upload it. Simple

For some reason it wasn't working, but I got it to work.
System was using the file when I first tried to copy it, but wasn't the second time.

Here it is.

 

[Whalen207]

Also here's a nifty Paint.NET crash that might point to some relevant (or irrelevant) problem with Memory.

 

[tom982]

Hi Whalen207,

Thanks for uploading it. I have managed to repair the registry corruption so all there's left to do now is to replace your hive with mine.

Could you download this file please:

https://dl.dropboxusercontent.com/u/16537616/Fixes/COMPONENTS/components.zip

Extract the contents to your Desktop, there should be one file, components (it has no file extension).

Navigate to C:\Windows\system32\config\ and rename the components file found in that folder to components.old as a backup. Now copy and paste the components file located on your Desktop into this folder. Should you run into any error about the file being in use etc., reboot and try again.

SFC Scan

1. Click on the Start
   
   button and in the search box, type Command Prompt
2. When you see Command Prompt on the list, right-click on it and select Run as administrator
3. When command prompt opens, copy and paste the following commands into it, press enter after each
   
   sfc /scannow
   
   Wait for this to finish before you continue
   
   copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Tom

 

[Whalen207]

Ran it.

 

[Whalen207]

Updated OCZ Agility 3 (C:\) to the latest firmware version. Will report any problems as they come, but none so far.

 

[VistaKing]

Whalen207

Do you still have Kaspersky and MSE still installed ?

 

[centaur78]

oh well

Ding Ding Ding

We are back on track Johnny !!!!