Memory Management BSOD

**redblade8** · 13 Jul 2012

Hallo, I'm on my bosses computer right now, and he got a bsod saying 'memory management'. I have a few files attached, any help is appreciated. Thanks. ^_^

A few q & a...
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? yes
- an OEM or full retail version? oem
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? 3 Years.
- What is the age of OS installation (have you re-installed the OS?) Since new, 2009.

**usasma** · 14 Jul 2012

The memory dump blames Norton. Please do this:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: http://us.norton.com/support/kb/web_...080710133834EN
- IMMEDIATELY install and update the free antivirus, then check to ensure that the Windows Firewall is turned on.
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

If the above steps don't stop the BSOD's, please zip up and upload any new memory dumps with your next post - and we'll see what we can figure out from there.

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


BHDrvx64.sys            Wed May 16 22:16:36 2012 (4FB45F84)
CamDrL64.sys            Sat Feb 03 13:17:27 2007 (45C4D1B7)
ENG64.SYS               Wed Apr 25 05:29:25 2012 (4F97C3F5)
EX64.SYS                Wed Apr 25 05:27:28 2012 (4F97C380)
EraserUtilRebootDrv.sys Tue May 15 20:36:03 2012 (4FB2F673)
GEARAspiWDM.sys         Mon May 18 08:17:04 2009 (4A1151C0)
IDSvia64.sys            Thu May 24 20:08:33 2012 (4FBECD81)
Ironx64.SYS             Mon Nov 14 21:00:53 2011 (4EC1C7D5)
LVMVDrv.sys             Fri Jul 20 03:18:17 2007 (46A061B9)
LVPr2M64.sys            Wed Jul 18 20:21:21 2007 (469EAE81)
PS2.sys                 Thu Sep 07 18:49:03 2006 (4500A1DF)
RTKVHD64.sys            Thu Jul 03 04:56:41 2008 (486C9449)
SRTSP64.SYS             Thu Mar 15 14:09:13 2012 (4F623049)
SRTSPX64.SYS            Thu Mar 15 14:09:21 2012 (4F623051)
SYMDS64.SYS             Mon May 16 18:15:03 2011 (4DD1A1E7)
SYMEFA64.SYS            Tue Nov 22 19:49:28 2011 (4ECC4318)
SYMEVENT64x86.SYS       Mon Jan 23 13:57:54 2012 (4F1DADB2)
SYMTDIV.SYS             Sat Nov 12 16:08:01 2011 (4EBEE031)
ccSetx64.sys            Fri Nov 04 18:05:25 2011 (4EB461A5)
dump_nvstor64.sys       Fri Jun 06 22:08:11 2008 (4849ED8B)
eeCtrl64.sys            Tue May 15 20:36:03 2012 (4FB2F673)
nvlddmkm.sys            Thu May 22 19:17:52 2008 (4835FF20)
nvmfdx64.sys            Wed May 21 13:48:06 2008 (48346056)
nvraid.sys              Wed Jun 06 16:34:01 2007 (46671A39)
nvstor64.sys            Fri Jun 06 22:08:11 2008 (4849ED8B)
pnarp.sys               Tue Oct 28 01:57:00 2008 (4906A9AC)
processr.sys            Sat Jan 19 00:52:45 2008 (4791902D)
purendis.sys            Tue Oct 28 00:31:28 2008 (490695A0)

Code:


Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\Mini071212-04.dmp]
Built by: 6002.18607.amd64fre.vistasp2_gdr.120402-0336
Debug session time: Thu Jul 12 20:36:31.043 2012 (UTC - 4:00)
System Uptime: 0 days 3:39:06.964
BugCheck 1E, {ffffffffc0000005, fffffa600cb478f0, 0, 0}
*** WARNING: Unable to verify timestamp for SYMDS64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMDS64.SYS
Probably caused by : SYMDS64.SYS ( SYMDS64+59f7 )
BUGCHECK_STR:  0x1E_c0000005_R
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
PROCESS_NAME:  SearchIndexer.e
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_SYMDS64+59f7
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffffa60`0cb478f0 00000000`00000000 00000000`00000000
BiosVersion =  5.14
BiosReleaseDate = 06/20/2008
SystemManufacturer = HP-Pavilion
SystemProductName = FK791AA-ABA a6650f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

**redblade8** · 17 Jul 2012

Hi,

My Boss is currently paying $80 a year for Norton, so he doesn't want to uninstall it at this time. :\

Is Avast better than Norton? I'm using Avast free on my system, but I'm just wondering Avast free vs Norton Internet Security, and Avast Internet Security vs Norton Internet Security..? I'm pretty sure that Avast is better, maybe not the free version, but I could be wrong.

I've also been getting error messages when uninstalling java & the cisco media center if this is related to any bsod, and he got another bsod, which I've ran another scan with your bsod tool.

I tried installing the windows installer 4.5 to fix the 1719 & 1722 error messages I was getting when uninstalling, but I was got the 'this update does not apply to your system' error.

Ah, sorry I didn't attach the .cbs log file from the sfc/scannow I did in the last post..I was tired and only did a screenshot for some reason. :S
I did another sfc/scannow now, and have attached the new log file I got from it.

Thanks for your help so far. ^_^

**usasma** · 17 Jul 2012

So your boss wants to pay $80 a year for something that's known to be causing problems on his system?
Does he run his business the same way?

In my previous post I stated that you can (if you so choose) reinstall a fresh copy of Norton once the troubleshooting is completed.

IMO - the differences between antivirus' and internet security apps aren't all that much.
At work when a customer comes in with a virus, their first question is invariably - "How could I get a virus, I have an antivirus installed?" If someone is bound and determined to get infected, no amount of software is going to stop that.

FYI - I've had 3 infections on my systems since 1988.
The first was the Joshi virus in 1990 while serving in Gulf War I - it took out a lot of military computers because no one had antivirus at that time.
The other 2 infections were files that I had downloaded - but hadn't yet opened. So the infection didn't affect my system.
Two ironclad rules for surfing the web:
- Don't click on anything if you don't know what it's going to do. If you don't know what to do, shut the system off without trying to close anything.
- Don't open anything that you've downloaded without scanning it for viruses first.

There is a slight chance that you may get further BSOD's after uninstalling Norton. If so, please zip up the memory dumps and upload them with your next post so we can figure out what's going on.

From the number of other errors that you're getting, there's either a corruption in Norton or an infection that's contributing to these other errors. Please perform some of free anti-malware scans here: Free Online AntiMalware Resources

**redblade8** · 24 Jul 2012

Originally Posted by usasma

So your boss wants to pay $80 a year for something that's known to be

causing problems on his system?
Does he run his business the same way?

In my previous post I stated that you can (if you so choose) reinstall a fresh copy of

Norton once the troubleshooting is completed.

IMO - the differences between antivirus' and internet security apps aren't all that much.
At work when a customer comes in with a virus, their first question is invariably - "How

could I get a virus, I have an antivirus installed?" If someone is bound and determined to

get infected, no amount of software is going to stop that.

FYI - I've had 3 infections on my systems since 1988.
The first was the Joshi virus in 1990 while serving in Gulf War I - it took out a lot of

military computers because no one had antivirus at that time.
The other 2 infections were files that I had downloaded - but hadn't yet opened. So the

infection didn't affect my system.
Two ironclad rules for surfing the web:
- Don't click on anything if you don't know what it's going to do. If you don't know what

to do, shut the system off without trying to close anything.
- Don't open anything that you've downloaded without scanning it for viruses first.

There is a slight chance that you may get further BSOD's after uninstalling Norton. If so,

please zip up the memory dumps and upload them with your next post so we can figure out

what's going on.

From the number of other errors that you're getting, there's either a corruption in Norton

or an infection that's contributing to these other errors. Please perform some of free

anti-malware scans here: Free Online AntiMalware

Resources

...Hmm ._. At least look at my previous posts attachments to see if anything is new
please..? .-. I'm sorry to bother, but I'm just wondering. ^^

Also, what about the uninstalling errors I was getting..? Do you know anything about this..?
Or should I make a separate post on another part of the forum for this..?

He doesn't want to uninstall/cancel his Norton subscription at this time...He wants to get
his whole $80's worth of money out of the year that it has left. Norton isn't going to re-
fund him partially for the time the subscription has left if he decides to cancel it
now...And he is considering other products. I was surprised myself too when I saw he was
using Norton, so I told him about Avast..He is considering it, and I never said that he will
never uninstall Norton. Just not at this time. He wants his $80 dollars worth.

How does he run his business..? Quite smoothly, and the food there is great. Maybe stop by
sometime and try it out..? ^_^

He doesn't go to any suspicious websites as far as I know..Just mostly online banking..and
then his kids use it too. I ran a scan with malware bytes, and spybot search and destroy,
and removed some malware they found, which there weren't many of. The spybot search and
destroy had finished, and I removed a few items, but I stopped the malware bytes scan and
removed 2 infections before it had finished. I then started another scan later just to make
sure..

I'm not sure what your point was on your sarcastic bit about the gulf war...What was it..?
:\

The two rules, I do know these. ^^ But I'll be sure to pass it along to them, thanks for the
advice. ^_^

What about the sfc/scannow I did..? It was saying that there are system files that are
corrupt that could be contributing to this. :\

New information:

I was defragging the disk, as well as running a scan with spybot search and destroy and
malware bytes. I left the room for a bit...and came back to a bsod. I then restarted the
computer, and icons, and some few other things were displayed weirdly, and not correctly as
they should. Most other things were noticeably not working as they should either. Typing
into the start menu made it go to not responding.. When I went to internet explorer to try
to get to this forum, it also went to not responding and didn't work. Same with other
programs & stuff, so I shutdown the computer.

When I started the computer back up, I promtly got another bsod. I finally got it running
again, but the loading time this time was very slow. The desktop went white, and
explorer.exe not responding which I got back up manually via the task manager. I then went
to system restore to try to restore it to an earlier point in time, but this also was half
not responding & not seeming like it was doing anything after a while..Other things gave me
the error 'pipeline is not valid,' and 'windows is not geneine & the key is invalid' or
something like that..I tried opening a word document, but got another bsod, so I then shut
down the computer. Everything seemed to be running normally after that, but I'm just
wondering about these bsod error logs & such I have attatched.

Thanks for your help, it's much appriciated. =)

**usasma** · 24 Jul 2012

My only attempt at sarcasm was this:

So your boss wants to pay $80 a year for something that's known to be causing problems on his system?
Does he run his business the same way?

The Gulf War thing was me relating my experiences with viruses - and showing that even someone who knows what he's doing (presumably) can get infected. No sarcasm intended there.

Can we compromise with an uninstall and an immediate reinstall of a fresh copy of Norton? Norton is a very complex program and it may be causing issues simply because it's so complicated.

We have many problems with Norton (even more with McAfee recently) at work - and rarely do they give us notice that they're messing up. In one case I spent over 5 hours diving through the registry and monitoring Process Explorer in order to find a hint that Norton was misbehaving. Removing Norton fixed that one.

But, enough of that - let's move on to other issues.....

It's no bother for me to look through the reports again - especially since you've had further BSOD's. More to follow on that after I finish responding to your last post.

As for the uninstalling errors - it's possible that they're related to the problems that you're having. So let's see what fixing the BSOD's does for you (sometimes there are underlying problems - but they're revealed once the BSOD's are fixed).

I'm not real well versed with reading the logfiles from SFC.EXE. I was hoping to have a friend look at them, but he's no longer able to help out - so I may have to wing it!

What sort of malware did you find? Was it cookies - or was it Trojans (or something else - like Adware)? I ask because the more severe forms of malware can damage the operating system - and those problems will remain even after the virus is removed.

Just FYI, here's how I help "fix" BSOD's:
- first we rule out any 3rd party driver problems (the most common reason for BSOD's). This is done by using the dump reports, the age of the 3rd party drivers, and my experience (and the DRT table) to identify previously seen problem drivers.
- after that we rule out hardware problems (the next most common issue) - but that's a long, tedious process of testing. So some people opt to try the next step instead. For testing we use these free diagnostics: Hardware Diagnostics . If that doesn't find anything, then we suggest this procedure: Hardware Stripdown Troubleshooting
- the final step is a "clean" install of Windows (I use this link: Canned Speeches )

After that there's nothing else that can be wrong. So any problems that continue are from something that was missed - most likely in the hardware stripdown. That's because the clean install of Windows should also have fixed any 3rd party driver problems. But, to even throw a monkey wrench into that, we've been experiencing errors with restore disks at work recently - and don't have a firm handle on why it's happening.

More to follow after having a detailed look at all the reports. Just FYI - the last 3 memory dumps are all different errors (STOP 0x1E; 0x7A; 0x1A). This usually indicates a hardware problem. They (hardware problems) are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues (3rd party hardware/drivers)
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

Have you done any temperature monitoring on this system? I suggest this free tool: HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools
Is this a desktop computer? If so you can sometimes rule out overheating by opening up the case and pointing a house fan (on high) at it. Overheating can occur in devices with temp sensors, or in devices without them. The house fan trick is a low-tech solution to cool all the devices.

Will be right back after reviewing the reports.......

**usasma** · 24 Jul 2012

The first BSOD was a STOP 0x1E (KMODE_EXCEPTION_NOT_HANDLED) and it directly blamed SYMDS64.SYS which performed a memory access operation which was denied (0xc0000005). More info on this error here: BSOD Index SYMDS64.SYS is a Symantec/Norton NIS/N360 driver (from this link: Driver Reference Table - SYMDS64.SYS )

The second BSOD was a STOP 0x7E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED). It was caused by code corruption (in memory) due to a memory access operation. In other words, something messed up a section of memory (virtual memory, not necessarily physical memory) by improperly writing to it - and that caused the BSOD. The BSOD didn't identify the faulting driver here.

The third BSOD was a STOP 0x1A (MEMORY_MANAGEMENT) error. Again Windows was not able to identify the cause of it.

So, we've got memory access errors. These sort of errors can be caused both by 3rd party drivers - and by hardware problems (overheating, overclocking, or bad hardware).

It's easiest to rule out the hardware in this instance, so please run MemTest86+ if you haven't already. Here's a link to the diagnostic procedure that I use: Memory Diagnostics
If that passes, then try the Prime95 and the video tests on this page: Additional Hardware Diagnostics
Also try the hard drive diagnostics here (as the pagefile.sys is where virtual memory's contents are stored when not being used): Hard Drive Diagnostic Procedure

This doesn't preclude the overheating tests - but Prime95 will stress the memory (and will overheat it) if it's a problem. If there's no overheating problem with the RAM, then Prime95 won't cause overheating. In other words, if you get BSOD's while running Prime95 - point the house fan at the memory and then try Prime95 again to see if it goes longer before erroring out.

Norton drivers continue to be present in the memory dumps - but that's no surprise since it was blamed in one of them.

The only other (IMO) notable driver issue(s) are the chipset drivers dating from 2007. I'd suggest updating these from the nVidia website ( World Leader in Visual Computing Technologies | NVIDIA ) - in the Downloads section under either nForce or Legacy (depending on the age of the chipset). If you can't figure out the chipset, post back with the exact make and model of the HP system and we can point you to the latest version.

And, as long as you're at the nVidia website, please update your video drivers - as they date from 2008.

perfmon /report shows configuration issues with a USB card reader device. Please uninstall the current drivers, and download/install a fresh copy. Check Device Manager to ensure that they are fixed.

No evidence of EventID 41 errors in the event log. This indicates that there's less likelyhood of a problem causing reboots that's out of Windows ability to detect. You'll sometimes see these in conjunction with overheating of a component that doesn't have a temp sensor (such as your RAM).

There's several instances of this error. I believe that it's significant as the error code appears to have been trashed (0xFFFFFFFF):

Event[73]:
Log Name: System
Source: Service Control Manager
Date: 2012-07-17T02:48:55.000
Event ID: 7024
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Owner-PC
Description:
The Norton Internet Security service terminated with service-specific error 4294967295 (0xFFFFFFFF).

This is not the "smoking gun". It's an error that I believe supports my contention that this may be a Norton issue.

Beyond that I cannot see any other patterns. I believe that the problems are related to one or more of the following:
- Norton
- Memory
- Overheating

FYI - I had an HP system at work several years ago that was overheating - but there was no sign of it on any of the sensors. I accidentally brushed my hand against the video card and got a 2nd degree burn. That proved to use that the video card was overheating - despite the sensor telling us that the card wasn't overheating!

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


BHDrvx64.sys            Wed May 16 22:16:36 2012 (4FB45F84)
CamDrL64.sys            Sat Feb 03 13:17:27 2007 (45C4D1B7)
ENG64.SYS               Wed Apr 25 05:29:25 2012 (4F97C3F5)
EX64.SYS                Wed Apr 25 05:27:28 2012 (4F97C380)
EraserUtilRebootDrv.sys Tue May 15 20:36:03 2012 (4FB2F673)
GEARAspiWDM.sys         Mon May 18 08:17:04 2009 (4A1151C0)
IDSvia64.sys            Thu May 24 20:08:33 2012 (4FBECD81)
Ironx64.SYS             Mon Nov 14 21:00:53 2011 (4EC1C7D5)
LVMVDrv.sys             Fri Jul 20 03:18:17 2007 (46A061B9)
LVPr2M64.sys            Wed Jul 18 20:21:21 2007 (469EAE81)
LVUSBS64.sys            Wed Jul 18 20:23:07 2007 (469EAEEB)
PS2.sys                 Thu Sep 07 18:49:03 2006 (4500A1DF)
RTKVHD64.sys            Wed Feb 11 07:39:19 2009 (4992C6F7)
SRTSP64.SYS             Thu Mar 15 14:09:13 2012 (4F623049)
SRTSPX64.SYS            Thu Mar 15 14:09:21 2012 (4F623051)
SYMDS64.SYS             Mon May 16 18:15:03 2011 (4DD1A1E7)
SYMEFA64.SYS            Tue Nov 22 19:49:28 2011 (4ECC4318)
SYMEVENT64x86.SYS       Mon Jan 23 13:57:54 2012 (4F1DADB2)
SYMTDIV.SYS             Sat Nov 12 16:08:01 2011 (4EBEE031)
ccSetx64.sys            Fri Nov 04 18:05:25 2011 (4EB461A5)
dump_nvstor64.sys       Fri Jun 06 22:08:11 2008 (4849ED8B)
eeCtrl64.sys            Tue May 15 20:36:03 2012 (4FB2F673)
nvlddmkm.sys            Thu May 22 19:17:52 2008 (4835FF20)
nvmfdx64.sys            Fri Aug 01 14:38:28 2008 (48935824)
nvraid.sys              Wed Jun 06 16:34:01 2007 (46671A39)
nvstor64.sys            Fri Jun 06 22:08:11 2008 (4849ED8B)
processr.sys            Sat Jan 19 00:52:45 2008 (4791902D)

Code:


Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\Mini071712-01.dmp]
Built by: 6002.18607.amd64fre.vistasp2_gdr.120402-0336
Debug session time: Tue Jul 17 04:55:11.858 2012 (UTC - 4:00)
System Uptime: 0 days 1:05:32.434
BugCheck 1E, {ffffffffc0000005, fffffa600bc83d30, 0, 0}
*** WARNING: Unable to verify timestamp for SYMDS64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMDS64.SYS
Probably caused by : SYMDS64.SYS ( SYMDS64+59f7 )
BUGCHECK_STR:  0x1E_c0000005_R
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  mbam.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_SYMDS64+59f7
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffffa60`0bc83d30 00000000`00000000 00000000`00000000
BiosVersion =  5.14
BiosReleaseDate = 06/20/2008
SystemManufacturer = HP-Pavilion
SystemProductName = FK791AA-ABA a6650f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\Mini071712-02.dmp]
Built by: 6002.18607.amd64fre.vistasp2_gdr.120402-0336
Debug session time: Tue Jul 17 05:24:26.944 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:15.865
BugCheck 1000007E, {ffffffffc0000005, fffffa6003467fed, fffffa6001bc23a8, fffffa6001bc1d80}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BYTE
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffffa60`03467fed fffffa60`01bc23a8 fffffa60`01bc1d80
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\Mini071712-03.dmp]
Built by: 6002.18607.amd64fre.vistasp2_gdr.120402-0336
Debug session time: Tue Jul 17 05:45:34.718 2012 (UTC - 4:00)
System Uptime: 0 days 0:18:07.639
BugCheck 1A, {41790, fffffa8001ed7250, ffff, 0}
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`01ed7250 00000000`0000ffff 00000000`00000000
BiosVersion =  5.14
BiosReleaseDate = 06/20/2008
SystemManufacturer = HP-Pavilion
SystemProductName = FK791AA-ABA a6650f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

**usasma** · 24 Jul 2012

Finally, here's what I believe is significant about the SFC.EXE scan:

Code:

2012-07-17 03:30:42, Info                  CSI    00000217 [SR] Verify complete
2012-07-17 03:30:43, Info                  CSI    00000218 [SR] Verifying 100 (0x0000000000000064) components
2012-07-17 03:30:43, Info                  CSI    00000219 [SR] Beginning Verify and Repair transaction
2012-07-17 03:30:54, Info                  CSI    0000021a Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-o..iadisc-style-sports_31bf3856ad364e35_6.0.6000.16386_none_bfbb2c7163d2e329\SportsNotesBackground.wmv do not match actual file [l:50{25}]"SportsNotesBackground.wmv" :
  Found: {l:32 b:NL3iAn0KqTuLafiDNe6Fcp2UBykCdETr5FRxr96bh/Q=} Expected: {l:32 b:P4UBkuj7CRNMy5QSxD5o+oAlgsD+5+5VqOV0k9nAEfM=}
2012-07-17 03:30:54, Info                  CSI    0000021b [SR] Cannot repair member file [l:50{25}]"SportsNotesBackground.wmv" of Microsoft-Windows-OpticalMediaDisc-Style-Sports, Version = 6.0.6000.16386, 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
2012-07-17 03:30:57, Info                  CSI    0000021c Hashes for file member \??\C:\Windows\System32\networkmap.dll do not match actual file [l:28{14}]"networkmap.dll" :
  Found: {l:32 b:bG8fd7y159vqe7djYfcrDTvrBLWH9cLa2azYn+Ncw9s=} Expected: {l:32 b:wZ4F9gI3kkaApJEhxAK+4JarxWWRHBJC9pvEuWoiqLY=}
2012-07-17 03:30:57, Info                  CSI    0000021d [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:28{14}]"networkmap.dll" from store
2012-07-17 03:30:59, Info                  CSI    0000021e Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-o..iadisc-style-sports_31bf3856ad364e35_6.0.6000.16386_none_bfbb2c7163d2e329\SportsNotesBackground.wmv do not match actual file [l:50{25}]"SportsNotesBackground.wmv" :
  Found: {l:32 b:NL3iAn0KqTuLafiDNe6Fcp2UBykCdETr5FRxr96bh/Q=} Expected: {l:32 b:P4UBkuj7CRNMy5QSxD5o+oAlgsD+5+5VqOV0k9nAEfM=}
2012-07-17 03:30:59, Info                  CSI    0000021f [SR] Cannot repair member file [l:50{25}]"SportsNotesBackground.wmv" of Microsoft-Windows-OpticalMediaDisc-Style-Sports, Version = 6.0.6000.16386, 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
2012-07-17 03:30:59, Info                  CSI    00000220 [SR] This component was referenced by [l:196{98}]"Microsoft-Windows-OpticalMediaDisc-Package~31bf3856ad364e35~amd64~~6.0.6000.16386.OpticalMediaDisc"
2012-07-17 03:30:59, Info                  CSI    00000221 Hashes for file member \??\C:\Program Files\Movie Maker\Shared\DvdStyles\Sports\SportsNotesBackground.wmv do not match actual file [l:50{25}]"SportsNotesBackground.wmv" :
  Found: {l:32 b:NL3iAn0KqTuLafiDNe6Fcp2UBykCdETr5FRxr96bh/Q=} Expected: {l:32 b:P4UBkuj7CRNMy5QSxD5o+oAlgsD+5+5VqOV0k9nAEfM=}
2012-07-17 03:30:59, Info                  CSI    00000222 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-o..iadisc-style-sports_31bf3856ad364e35_6.0.6000.16386_none_bfbb2c7163d2e329\SportsNotesBackground.wmv do not match actual file [l:50{25}]"SportsNotesBackground.wmv" :
  Found: {l:32 b:NL3iAn0KqTuLafiDNe6Fcp2UBykCdETr5FRxr96bh/Q=} Expected: {l:32 b:P4UBkuj7CRNMy5QSxD5o+oAlgsD+5+5VqOV0k9nAEfM=}
2012-07-17 03:30:59, Info                  CSI    00000223 [SR] Could not reproject corrupted file [ml:520{260},l:112{56}]"\??\C:\Program Files\Movie Maker\Shared\DvdStyles\Sports"\[l:50{25}]"SportsNotesBackground.wmv"; source file in store is also corrupted
2012-07-17 03:31:01, Info                  CSI    00000224 Repair results created:

I believe that C:\Program Files\Movie Maker\Shared\DvdStyles\Sports\SportsNotesBackground.wmv is corrupted and cannot be repaired. I didn't see any other items that weren't able to be repaired. Try deleting that file (and it's stored copy and then rerun SFC.EXE

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
memory management bsod	diehardmosh	Crashes and Debugging	28	24 Apr 2012
BSOD Memory Management	kmart020	Crashes and Debugging	1	11 Jan 2011
Vista runs out of physical memory when working with files > 1GB - memory management issue?	Robert Janik	Vista performance & maintenance	2	21 Apr 2010
Memory Management	Brad	Vista hardware & devices	6	23 Oct 2007
BSOD Memory Management and latest was with no reason	qUAan	Vista hardware & devices	8	26 Jul 2007

Memory Management BSOD

Re: Memory Management BSOD

Re: Memory Management BSOD

Re: Memory Management BSOD

Re: Memory Management BSOD

Re: Memory Management BSOD

Re: Memory Management BSOD

Re: Memory Management BSOD

Posting Permissions