New
#11
I have 2 versions - problems started when I loaded 64 bit windows 7 onto a new SSD and hooked it up alongside my old 32bit windows 7.
I have 2 versions - problems started when I loaded 64 bit windows 7 onto a new SSD and hooked it up alongside my old 32bit windows 7.
I have both the 32bit and 64bit versions of Windows 7 installed. The problems started when I installed 64bit onto a new SSD and added it to my existing set-up.
Well I guess it's a dual-boot. I'm getting BSODs with both but I'm trying to fix the 64 bit version at the moment.
Stick with the 64 bit installation only.
Re-run the SPTD steps, but be sure to use the 64 bit of SPTD.
I ran the SPTD steps for both versions before the last BSOD. Should I do that again?
I hope this is the right one!
OK. WinDBG reports a different error than earlier, but unfortunately its inconclusive at this stage. We can try a few things. Firstly, lets check that memory is behaving OK.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80002da6a20, fffff8800b198080, 0} Probably caused by : ntkrnlmp.exe ( nt!ObDereferenceSecurityDescriptor+20 ) Followup: MachineOwner ---------
Run a minimum of 8 passes, preferably overnight to get a few more passes in, or until errors occur using MemTest86+.
Use this tutorial to help you use MemTest86+:
RAM - Test with Memtest86+
Report back on the results and we will take it from there.
I got some errors on the 7th test (I think) but when I took out one stick of RAM and ran it again, memtest seemed to crash.
Any idea how to stop that from happening? I used the USB version and some forums mentioned disabling USB legacy in the BIOS but that just stopped the USB memory stick from being recognised.