 | |
| |
| 10 May 2009 | #1 |
| | How to find culprit of BSOD I was refered here by Jacee in an attempt to diagnose and hopefully avoid another BSOD. Sooooo, where do I start looking? Hopefully the info contained in this link will give most of the neccessary info about my hardware. http://pcpitstop.com/betapit/sec.asp...report=Summary Grassy, Tx |
My System Specs | |
| 11 May 2009 | #2 |
| | Attach only the bare minimum hardware when troubleshooting, i.e remove all usb devices, bluetooth, secondary monitors etc and try again. |
| My System Specs |
| 11 May 2009 | #3 |
| | Stupid me, I was worse for wear when I posted that last night and left out necessary info. It only BSOD'ed on the first boot/run. I've since run it approx. 10hrs. w/ out issue if that makes any difference. Tx. |
| My System Specs |
| . |
| |
| 12 May 2009 | #4 |
| | Try locating your memory dump files from the BSOD. They're usually located in the C:\Windows\Minidump folder (it may be hidden). If you find them there, zip them up and include them in your next post. If they're not there, they may be in a file located here: C:\Windows\Memory.DMP This file is usually too large to upload, so I'd suggest following the steps at this link to run an analysis and post it here: Diagnosing Bsod's (originally posted 02Oct08) - Vox |
| My System Specs |
 |
How to find culprit of BSOD problems?
| Thread Tools | |
| Similar help and support threads for: How to find culprit of BSOD | ||||
| Thread | Forum | |||
| BSOD - HTPC - Can WMC be the culprit? | BSOD Help and Support | |||
| Trying to find the culprit in boot failure twice the past month | General Discussion | |||
| BSOD (ntoskrnl.exe the culprit?) | BSOD Help and Support | |||
| BSOD - assuming the video cards the culprit | BSOD Help and Support | |||
| BSOD Stop 0124 with a possible culprit | BSOD Help and Support | |||
All times are GMT -5. The time now is 11:09 AM.
