Machine_Check_Exception
- Thread starter Hassan
- Start date
My fathers HDD went funny with some BSOD action like this but it happened much more randomly fortunately i found i could save most the data and use the freezer trick to get rest off very slower and then bought a new one and its fine.
Well i say fine what i mean is his GPU fan went and it is epoxy to the GPU so we bought a new card and NOW its fine again. Honestly that man could break a fork by eating with it.
Well i say fine what i mean is his GPU fan went and it is epoxy to the GPU so we bought a new card and NOW its fine again. Honestly that man could break a fork by eating with it.
Rastalovich
New member
Put the hard drive in your pc as a slave to your drives.
Machine_Check_Exception was the error I got when my mobo pwm went south.
Machine_Check_Exception was the error I got when my mobo pwm went south.
Rastalovich
New member
Just plug it into a free port.
Rastalovich
New member
I mean take it out of your sisters and put it in yours. U`ll be able to see if the drive is alive or not.
RollerCam540
New member
Memtest is a decent diagnostic tool if you apply it correctly. To test 1GB of ram, it should complete at least 32 passes of test #5, which can generally take up to or beyond 48 hours. before you run test #5, you want to run a standard test loop (1-7) for 12-24 hours. Failures during different test numbers generally have different meanings.
Re-run memtest as directed. This will at the very least allow you to remove all but one stick of RAM. I would then recommend stripping everything from the computer but the CPU, one stick of RAM, video card, and hard drive -- this will allow you to narrow down your sources of error by focusing on the bare essentials.
If you really think the hard drive is a problem, visit the manufacturer's website because they have OS-independent diagnostic tools that should help determine whether something along "the hard drive chain" is the source of error.
You need to ensure that (a) your PSU is strong enough to supply ample power to your components (b) your PSU is from a "reliable" manufacturer because PSUs can output 66% less power when they run hot or get dusty (c) your CPU heatsink makes proper contact with the IHF (d) each screw within the computer is properly fastened and grounded
Re-run memtest as directed. This will at the very least allow you to remove all but one stick of RAM. I would then recommend stripping everything from the computer but the CPU, one stick of RAM, video card, and hard drive -- this will allow you to narrow down your sources of error by focusing on the bare essentials.
If you really think the hard drive is a problem, visit the manufacturer's website because they have OS-independent diagnostic tools that should help determine whether something along "the hard drive chain" is the source of error.
You need to ensure that (a) your PSU is strong enough to supply ample power to your components (b) your PSU is from a "reliable" manufacturer because PSUs can output 66% less power when they run hot or get dusty (c) your CPU heatsink makes proper contact with the IHF (d) each screw within the computer is properly fastened and grounded
RollerCam540
New member
The point I tried to make with my last response is that you're not checking the integrity of your components properly! Why do I say this? How can you test the integrity of your HD when you can't account for the integrity of the parts that carry the information from the hard drive to the visual representation of it on your monitor? You need to work your way down the component chain -- one by one -- generally without skipping links.
How do you test your PSU? One should test their PSU when the computer is under load. To do that one needs a digital multimeter and the comfort to work with "live" wires while the computer runs PRIME95, or the likes, over the course of several hours. Now you could test it in a different unit but that computer must have power demands that meet or exceed your computer's.
From there I would recommend booting into a preinstallation enviornment of some sort -- an OS-like enviornment that does not require a hard drive. you might be able to use UBUNTU or BartPE but I'm not sure because I don't use either. The premise: booting into a PE will theoretically allow one to exclude the software from the potential sources of error. That's why memtest, seatools, and other diagnostics boot straight from the CD. Make sure you disconnect your hard drive and any other component that would be unnecessary for the computer to operate during this period -- the more parts you have connected the less likely you are to pin point the source of error.
Memtest tests more than just RAM, certain errors that occur during a memtest have been shown to be a result of something directly unrelated to RAM.
You have a Venice processor, meaning the memory controller is on the processor's die itself, so one may receive a memory error when it's really the processor... or one may receive a processor error when it's really the memory.
Frankly, at the moment, I don't have the time walk you through a diagnostic procedure. I'd like to help but school and work have me pinned down. I'm sure someone here will be more than happy to help you. Remember to properly traverse the chain of command, as you cannot blame one component if it depends on another.
How do you test your PSU? One should test their PSU when the computer is under load. To do that one needs a digital multimeter and the comfort to work with "live" wires while the computer runs PRIME95, or the likes, over the course of several hours. Now you could test it in a different unit but that computer must have power demands that meet or exceed your computer's.
From there I would recommend booting into a preinstallation enviornment of some sort -- an OS-like enviornment that does not require a hard drive. you might be able to use UBUNTU or BartPE but I'm not sure because I don't use either. The premise: booting into a PE will theoretically allow one to exclude the software from the potential sources of error. That's why memtest, seatools, and other diagnostics boot straight from the CD. Make sure you disconnect your hard drive and any other component that would be unnecessary for the computer to operate during this period -- the more parts you have connected the less likely you are to pin point the source of error.
Memtest tests more than just RAM, certain errors that occur during a memtest have been shown to be a result of something directly unrelated to RAM.
You have a Venice processor, meaning the memory controller is on the processor's die itself, so one may receive a memory error when it's really the processor... or one may receive a processor error when it's really the memory.
Frankly, at the moment, I don't have the time walk you through a diagnostic procedure. I'd like to help but school and work have me pinned down. I'm sure someone here will be more than happy to help you. Remember to properly traverse the chain of command, as you cannot blame one component if it depends on another.
