BSOD Memory management

miketmt69

Distinguished
Oct 28, 2011
59
0
18,630
0
Okay I have been getting these for quite some time. like almost 6 months now. I have totally redone windows. ran memtest86 for 5 passes. I regularly run advance system care and smart defrag 3. I saw on another forum to run sfc /scannow on cmd to fix files. I did this and got back "Windos resource protection found corrupt files but was unable to fix some of them.

Now I dont know what you guys will need so just let me know. like I dont really know about the event viewer logs or anything. Any and all help will be greatly appreciated cause I have been going on with this for a very long time. And I just dont have the money for a computer technician.
 

miketmt69

Distinguished
Oct 28, 2011
59
0
18,630
0


Thanks for the help I will try this and report back.
 

miketmt69

Distinguished
Oct 28, 2011
59
0
18,630
0
okay so I tried this and no luck. But here is an error report that I kept getting.

Log Name: System
Source: Service Control Manager
Date: 7/27/2014 2:25:42 PM
Event ID: 7026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: joe-PC
Description:
The following boot-start or system-start driver(s) failed to load:
papycpu2
papyjoy
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7026</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2014-07-27T18:25:42.920799900Z" />
<EventRecordID>82743</EventRecordID>
<Correlation />
<Execution ProcessID="752" ThreadID="756" />
<Channel>System</Channel>
<Computer>joe-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">
papycpu2
papyjoy</Data>
</EventData>
</Event>
 
you need to start cmd.exe as a admin then run the command
sfc.exe /scannow

otherwise the program will run and exit and you can not see the results (you can still look for the log though)

most times when it can not do the repair it is caused because the backup copy of the file it is trying to repair is also corrupted. (common with malware/ pirate programs that hack activation)

windows 8.x added an new switch to the command to allow a repair from a trusted online copy but with windows 7 you have to find a good original cd to fix the problems.




 

miketmt69

Distinguished
Oct 28, 2011
59
0
18,630
0
yeah johnbl I did that and it gives me the corrupted file error and tells me where my log file is. but when I try to open the log file I and a file failed to open
 
that bugcheck is in a graphics driver.
if you put your memory .dmp file on a cloud server with public access I can take a quick look.

most often it is just a buggy 3rd party driver that is corrupting memory. Windows will load the drivers in different orders on each boot and the bad driver will corrupt different drivers kernel memory data structures on each boot.

basically, you want to update as many drivers as you can. I would start with the chipset drivers because of common issues with memory corruption due to usb drivers and netcards. for the last bugcheck you would update the nvidia driver.

basically, update all the drivers you can, delete all of the old memory dump files and post any new memory dumps.
you might also want to do a malwarebytes scan.





 

ASK THE COMMUNITY