Intermittant Machine_Check_Exception BSOD
Full error msg : stop 0x0000009C, 0x 0000000000000002, 0xFFFFF80000137BC0, 0x00000000B2000000, 0x0000000000010005 Specs:Intel i7875k cpu Intel DP55KG MB (Latest Bios dated May 2010) ATI 5770 GPU Noctua DP-14 HS Assembly Windows XP x64 SP2 8Gb 1332 CL9 1000W PS 1TB Hitachi HDD Memtest84 says ram is fine (5 passes no errors) Prime95 craps out 1 core in 3 minutes (repeatably) and the rest run for 16 plus hours Core temps never get above 51C Can fire up in safe mode every time, but will get BSOD 1 in 3 with normal startup Cant figure out what XP doesn't like I apologize if this post is not on the correct forum1 person needs an answerI do too
September 7th, 2010 6:06am

Please provide additional information about your system:Describe your current antivirus and anti malware situation: McAfee, Norton, Spybot, AVG, Avira!, MSE, Defender, ZoneAlarm, PC Tools, Comodo, etc.Click Start, Run and in the box enter:msinfo32Click OK, and when the System Summary info appears, click Edit, Select All, Copy and then paste the information back here.There will be some personal information (like System Name and User Name), and whatever appears to be private information to you, just delete it from the pasted information.For video driver information, expand the Components, click Display, click Edit, Select All, Copy and then paste the information back here.For audio information, expand the Components, click Sound Device, click Edit, Select All, Copy and then paste the information back here. This will minimize back and forth Q&A and eliminate guesswork.Download BlueScreenView from here:http://www.nirsoft.net/utils/blue_screen_view.htmlUnzip and run it (BSV installs nothing) and let it finish scanning all your dump files. If you double click on of the dumps, you will get some information about it (including the Caused By Driver field) and you may be able to spot the problem right away - especially if you see a pattern in the dumps where the Caused by Driver field is the same (start with that driver).Select (highlight) one or more of the most recent dump files by clicking them and holding down the Ctrl key to select multiples files. Try to select just the most recent ones that relate to your issue (maybe five or so dump files to get started).Click File, Save Selected Items and save the information from the dumps to a text file on your desktop called BSOD.txt. Open BSOD.txt with a text editor, copy all the text and paste it into your next reply.Here is an example of the BSV report from a single BSOD that I initiated on purpose that shows the cause of the crash as the i8042prt.sys driver belonging to Microsoft Corporation:==================================================Dump File : Mini062110-01.dmpCrash Time : 6/21/2010 11:51:31 AMBug Check String : MANUALLY_INITIATED_CRASHBug Check Code : 0x000000e2Parameter 1 : 0x00000000Parameter 2 : 0x00000000Parameter 3 : 0x00000000Parameter 4 : 0x00000000Caused By Driver : i8042prt.sysCaused By Address : i8042prt.sys+27fbFile Description : i8042 Port DriverProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 5.1.2600.5512 (xpsp.080413-2108)Processor : 32-bitComputer Name : Full Path : C:\WINDOWS\minidump\Mini062110-01.dmp==================================================Send the information from the last 5 memory dumps.While you are waiting, test your system RAM. Here is how to do that:Run a test of your RAM with memtest86+ (I know it is boring and will cost you a CD). Memtest86+ is a more up to date version of the old memtest86 program and they are not the same.The memtest86+ will not run under Windows, so you will need to download the ISO file and create a bootable CD, boot on that and then run the memtest86+ program. If even a single error is reported that is a failure and should make you suspicious of your RAM.If you have multiple sticks of RAM you may need to run the test on them one at a time and change them out to isolate the failure to a particular single stick.Always keep at least the first bank of RAM occupied so the test will find something to do and there is enough to boot your system.Sometimes, reseating the RAM in the slots will relieve the error but a failure is still cause for suspicion.The file and instructions are here:http://www.memtest.org/Here is a link that shows you have to create and use the memtest86+ CD:http://www.geekstogo.com/forum/topic/246994-guide-to-using-memtest86/If someone says to run memtest86, you can tell them to go pound sand and that you know memtest86+ supercedes memtest86 and here's why: http://en.wikipedia.org/wiki/Memtest86Do you really think suggestions that begin with the words try, might or maybe are going to be helpful?I need YOUR votes and points for helpful replies and Propose as Answers. I am saving up for a pony!
Free Windows Admin Tool Kit Click here and download it now
September 7th, 2010 12:50pm

Fixed it.......I thinkThe Intel Bios is not that good. It recognizes the 875k cpu but will not let me increase multiplier past 22 (thats what i paid the premium for), In addition the "auto" settings were wrong for my ram. It set it at 1600 Mhz and 11-11-11-29. In addition the cpu core voltage was wrong. I manually set the ram to 1332 at 9-9-9-24 and ran memtest86+ no ram errors after 3 passes. Still get BOSD once in a while. Set the cpu voltage up one notch and everything became stable. Ran prime95 for 16 hours with no errors and max temp of 54CThanks for the helpIan
September 9th, 2010 2:27am

Others have suggested that I run Windows7 on my system. Is there a benefit other than ongoing support and DirectX 11? Both are 64 bit os's and will access all ram.
Free Windows Admin Tool Kit Click here and download it now
September 9th, 2010 2:35am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics