BSOD death problem please help

#1
hi all have had a couple of crashes today and i cant figure out why, i put new ram in 2 days ago and having been using the computer fine, seems when i open cubase now it wants too crash, everything im sure is updated, i maily use this computer for audio work
windows 7 64
amd a8-3850 processor View attachment 010712-12355-01.dmp View attachment 010812-13119-01.dmp View attachment 010812-13525-01.dmp
 


Trouble

Noob Whisperer
#2
Two memory management;
Code:
BugCheck 1A, {41201, fffff683ff758108, 7c3000001d83b005, fffffa800748bac0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+14382 )
Followup: MachineOwner
[U][B][COLOR=#ff0000]MEMORY_MANAGEMENT (1a)[/COLOR][/B][/U]
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff683ff758108
Arg3: 7c3000001d83b005
Arg4: fffffa800748bac0
Code:
BugCheck 1A, {41790, fffffa800059be30, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
Followup: MachineOwner
[B][U][COLOR=#ff0000]MEMORY_MANAGEMENT (1a)[/COLOR][/U][/B]
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa800059be30
Arg3: 000000000000ffff
Arg4: 0000000000000000
And one Memory Corruption:
Code:
BugCheck 4E, {99, 398b4, 2, 39cf3}
[COLOR=#ff0000][U][B]Probably caused by : memory_corruption[/B][/U][/COLOR] ( nt!MiBadShareCount+4c )
Followup: MachineOwner
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000000398b4, page frame number
Arg3: 0000000000000002, current page state
Arg4: 0000000000039cf3, 0
Please;
Download Memtest86+ from this location here. Burn the ISO to a CD and boot the computer from the CD.
Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.
See this Guide to using Memtest 86+
And since PFN was identified and associated with memory corruption you should also run chkdsk on your system drive
Open an elevated command prompt and type
chkdsk C: /R
hit enter
answer yes "Y" to the prompt
reboot
let it complete all five stages and if you miss the summary at the end you can examine the log file in Event Viewer.
Regards
Randy
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.