Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I recently built my own PC from parts and installed Windows 7 and I have been getting BSODs with various different stop codes.

The latest was 0x24, but I've also had 0xd1 and 0x1e. However, Windows does not let me know where the fault occurred, so I have no idea how to go about resolving this.

I know the cause is likely a hardware driver, but I don't know which and cannot find information about how to use the minidumps to troubleshoot my problem.

I've uploaded the last three minidumps in case someone can make sense out of them and let me know what could be causing my BSODs.

Thanks, Ben

share|improve this question
All three mini dumps point to different causes, suspect a bad memory module. – Moab Jul 9 '10 at 20:30

Not sure if this is still an issue for you but I would also run MemTest86+ on the system to verify that RAM is ok. Often random BSOD's like this are from a bad stick somewhere.

share|improve this answer
Had a very similar issue back in 2001 with Win2K on custom built hardware (purchased and assembled by yours truly). Twas then I learned about memtest86, and the usefulness of pre-assembled, burn-tested hardware (ie, it's sometimes worth the markup if your time is valuable) – r00fus Aug 13 '10 at 5:36

blue screen view looks super useful. Blackbeagle recommended it under this post:

If that does not help, I would try some of the recommendations made under this post:

share|improve this answer
Thanks for the pointers. I have more info now thanks to BlueScreenView, I'll post another question with more specifics if I can't get this system working. – Ben S May 30 '10 at 13:42

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .