travelingjunk84
Active Member
- Joined
- Aug 20, 2015
- Messages
- 69
- Thread Author
- #1
Here is all the files i think i need. Thanks again for the help in advance!
Yes, you can now test the sticks individually to determine which is bad.i guess now i take half the sticks out and re run to figure out what memory stick it is righ
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41201, fffff68000001850, af000001f504f867, fffffa80073720d0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13702 )
Followup: MachineOwner
Yes, you can now test the sticks individually to determine which is bad.i guess now i take half the sticks out and re run to figure out what memory stick it is righ
Ok, so the past couple days I've tested each stick in one slot ranging from 5-16 hrs each test with no errors.If you ran Memtest86 and found errors then I wouldn't worry about the other stuff as you have probably found the main culprit.
Yes, you can now test the sticks individually to determine which is bad.
This is a possible I guess but there may also be other reasons as to why when used together they error out and singularly they don't.Guess that leads me to believe that one of the memory slots is bad right?
Your RAM settings don't look quite right like the voltage for example. Try going into the bios and choosing 'optimised defaults' which will set everything to it's default setting.At one point in time i did try overclocking and adjusting voltages
Ok.. Well things look fine and especially as you hit optimised defaults then hopefully Memtest86 won't error out.