Okay, we've had some more BSOD's so I've enclosed a new package with the latest dumps.
Whilst I've been away from the thread I've also removed both memory sticks 2 x 4GB and reinstalled stick 1 into slot A - BSOD - moved it to B - BSOD - stick 2 into slot A - BSOD - moved to B - BSOD - so it's happening with both sticks in both locations so does this rule out memory as a possible cause?
Once again, any help you can offer to resolve it would be very welcome.
Thanks,
Shaun
Well, excellent troubleshooting indeed. Though, if you could do it with Memtest86+ it'll be perfect. Your method is also included here, a bit different though.
Combining your crash dumps and the general view of BSODs culprits, I'd suggest you to have a look at your memory, the sticks. Through decades people have been using the bootable tool called Memtest86+ and it's basically very unique in these manners.
Be sure to check your warranty rules and regulations before opening your case.
* Memtest86+ is USB-ready, and can be booted directly from it. Download the flashdrive wizard.
* To ensure that either your sticks OR your motherboard slots are broken, it's necessary to do the below procedure-
* Pull out all sticks except ONE, scan it.
* If no errors, pull the scanned stick into another slot.
* Proceed like this until you've scanned all sticks individually, and all the slots.
Best Regards,
Frederik.
Thanks for the prompt reply Frederik - I'll give that a go tomorrow night (presumably it's an exhaustive test and will take most of the evening?).
Okay, I've run one stick through both slots (7 passes and no errors for each test).
It took flippin' hours and hours though so I'll do the other stick tomorrow night and report back. :)
<hick> Schall memories teshted h'okay wurth ner h'errorz <hick>
He he ... seriously though both sticks in both slots tested and passed with flying colours (no errors).
So ... what's next? :)
Oh, I've also updated the Nvidia drivers this evening and the Intel wireless driver/s.
I've run SFC /scannow and it didn't find any integrity violations.
Last edited by Clickfinity; 13 Sep 2012 at 17:59.
Great, it isn't your memory at this moment definitely. I just looked upon this post, and I thought it'll be a great time to confirm that it has actually worked. Therefore, are you able to get me a new msinfo32 (nfo)?
- A nfo file
Best Regards,
Frederik.
Hi Frederik,
I've uploaded a full package so you can see the latest dumps, devices and drivers, as well as the latest .nfo file.
Cheers,
Shaun
Quote