stimpy   10 #13 Posted September 11, 2011 (edited) just download bluescreenview and see what the dumps say.  It will be easy to work out what is causing the crash from that. Edited September 11, 2011 by stimpy Share this post Link to post Share on other sites Share this content via...
TaxiBaz   10 #14 Posted September 11, 2011 just download bluescreenview and see what the dumps say. It will be easy to work out what is causing the crash from that.  A better link for downloading bluescreenview. http://www.nirsoft.net/ No nag screens. Share this post Link to post Share on other sites Share this content via...
Mikes10 Â Â 10 #15 Posted September 11, 2011 running something like memtest x86 or pc-check is a lot better than running the microsoft tool. Â 2 or 3 years ago whilst in conversation with a field service engineer of a computer supplier to corporate and public sector businesses, the reasons for recommending Microsoft Memory Diagnositc were: Â 1) its a tool written and provided by Microsoft. 2) All the instructions for downloading, installing and using the tool are provided by Microsoft. Â Now if the end user (customer) could not follow the instructions provided by Microsoft for using the Memory Diagnostic tool then there was a good chance that the customer was 'Technically Challenged' and the field engineer had to be careful not to upset him/her for fear of getting bad feedback. Share this post Link to post Share on other sites Share this content via...
sccsux   10 #16 Posted September 11, 2011 1) its a tool written and provided by Microsoft  And that's a good reason for using something?  I'd not trust a M$ tool to fix an M$ OS issue. Share this post Link to post Share on other sites Share this content via...