📎 AI Summary:
This WindowsForum thread discusses consolidating multiple BSOD-related sticky posts into a single, comprehensive post to improve clarity and ease of reference. Participants agree that merging the threads is a good idea and suggest focusing on essential diagnostic tools and instructions, such as running the SF Diagnostic Tool and collecting dump files. The overall sentiment is positive, with efforts made to simplify troubleshooting procedures, though there’s also a humorous acknowledgment of challenges in encouraging users to follow guidelines.
This WindowsForum thread discusses consolidating multiple BSOD-related sticky posts into a single, comprehensive post to improve clarity and ease of reference. Participants agree that merging the threads is a good idea and suggest focusing on essential diagnostic tools and instructions, such as running the SF Diagnostic Tool and collecting dump files. The overall sentiment is positive, with efforts made to simplify troubleshooting procedures, though there’s also a humorous acknowledgment of challenges in encouraging users to follow guidelines.
Trouble
Noob Whisperer
I actually think that this is a wonderful idea.
By consolidating the following three
Link Removed
Link Removed
Link Removed
just the pertinent data and some attention to instructions
like Captain Jack's tool = run as administrator
CPUz = all SPD tabs
RAMMon = export html report and zip
I think it would be very helpful and simplify any reference that might be needed by either OPs or helpers.
Maybe preserve the name "Every Thread Starter, Please Read":
Then unstick the old ones to save any confusion.
Good thinking Elmer!
By consolidating the following three
Link Removed
Link Removed
Link Removed
just the pertinent data and some attention to instructions
like Captain Jack's tool = run as administrator
CPUz = all SPD tabs
RAMMon = export html report and zip
I think it would be very helpful and simplify any reference that might be needed by either OPs or helpers.
Maybe preserve the name "Every Thread Starter, Please Read":
Then unstick the old ones to save any confusion.
Good thinking Elmer!
Trouble
Noob Whisperer
Actually there is a bit of redundancy built into this approach, since I think if we can Just get everyone to run the SF Diagnostic Tool, I believe it goes out and gets the contents of the C:\Windows\MiniDump folder as part of its' process. So maybe we could concentrate on an emphasis on that and the Memory (CPU-z / RAMMon) stickys and that might be sufficient. Although it's probably still a good idea for the OP to know where and how to get his latest (most recent) dumps so he's not re-running the tool everytime just to add his latest file(s).
Captain Jack
Former Moderator
Ok all three thread merge into one Link Removed 🙂
Trouble
Noob Whisperer
Thanks Shyam, nice job, much easier to reference now.
If only we can get folks to follow it and quit attaching their dump files Link Removed and maybe even get them to fill out their system specs in their profile.
What? I can dream can't I? My glass is alway half something.
If only we can get folks to follow it and quit attaching their dump files Link Removed and maybe even get them to fill out their system specs in their profile.
What? I can dream can't I? My glass is alway half something.
