perkster
07-17-2007, 06:55 PM
new build had another BSOD restart and then "windows recovered from a serious error" message again, happened at 2am according to event view, computer was idling.
someone mentioned that the CAS 4 RAM i have may be causing instability with the P5B and should change it for CAS5 or above.
however before i do that i want to debug and make sure the ram is the prob.
i ran memtest and no problems.
i installed miscrosoft debgging tools and opened the most recent dumpfile but it said my kernal didnt have the right symbols or symbol path to display the analysis, so i am no nearer to finding problem.
in event view it is showing as error code: 1000008b. any advice on how to proceed in debugging why the critical restart would be welcome. I have all recent drivers for everything installed. specs in sig (says building now but was finished last week). how can i get more useful info from the minidump and what does it mean about these symbols?
Thanks in advance, you are all so helpful.
someone mentioned that the CAS 4 RAM i have may be causing instability with the P5B and should change it for CAS5 or above.
however before i do that i want to debug and make sure the ram is the prob.
i ran memtest and no problems.
i installed miscrosoft debgging tools and opened the most recent dumpfile but it said my kernal didnt have the right symbols or symbol path to display the analysis, so i am no nearer to finding problem.
in event view it is showing as error code: 1000008b. any advice on how to proceed in debugging why the critical restart would be welcome. I have all recent drivers for everything installed. specs in sig (says building now but was finished last week). how can i get more useful info from the minidump and what does it mean about these symbols?
Thanks in advance, you are all so helpful.