ripken204 Posted November 27, 2005 Posted November 27, 2005 (edited) the comp i just built has randomly reboots every few hrs or so, the event viewer gives me this:The computer has rebooted from a bugcheck. The bugcheck was: 0x10000050 (0xf000e819, 0x00000000, 0xbf8b480a, 0x00000002). A dump was saved in: C:\WINDOWS\Minidump\Mini112605-08.dmp. Edited November 27, 2005 by ripken204
ripken204 Posted November 27, 2005 Author Posted November 27, 2005 thats almost all hardware tho, my hardware is top notch and so is my cooling.
tom_vilsack Posted November 27, 2005 Posted November 27, 2005 Try different ram...i had same thing happen to me,ram was fine just didn't get along with mb i put it in...i swaped it with another comps ram i have,and now no more reboots...and other box gets along with that ram no problems...
MHz Posted November 27, 2005 Posted November 27, 2005 To strengthen on what tom_vilsack is saying. If your top notch ram is not JEDEC compliant ram, then it could be a compatiblity issue between the motherboard and the ram. Changing the timings of the ram will possibly prove useless if it not compatible with your mobo. Corsair makes some good ram but it goes outside JEDEC standards. I went through a 3 month ordeal to discover the problem and to get it resolved. Had the ram sent away for a month to be tested, but it returned as passed. Matching pair of ram modules yet my mobo could tell them apart! Finally the supplier exchanged it for cheaper Kingston ram which is JEDEC standard and now runs like a dream.Don't kid yourself. Download Memtest86 and test your ram. The quicker you can positively identify the problem, the sooner it will be fixed.
cluberti Posted November 28, 2005 Posted November 28, 2005 If you could change your dump options to do a full dump and set your pagefile size to RAM+50MB, you'd get a full memory dump that I could debug for you. Would it be possible for you to post the (compressed) dump here, or PM or email it to me? That's usually a memory error, but it's now always a physical memory error - it could be a kernel pool memory error as well. I can tell for sure by looking at the dump...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now