BSOD - Machine Check Exception

[GoNz0]

was this a pre built package ? if so and scan built it they should test it, and feel free to trawl the forums, i am not going to do it for you

i have seen posts in the past of scan selling high end systems with stability issues.

[Carlh]

My RAM was installed by Scan, so it should be right shouldn't it.

i have seen plenty of posts on here to prove otherwise.



if they installed it i suggest you contact them.

Gonzo,

Your post above implies that the memory hasnt been installed correctly I was just asking you to point out where this has happened.

I am not trying to be awkward as I am aware that some systems especially when overclocked can have stability issues however I am sure we shall be able to sort this issue out for the OP.

Regards

[Rookie1986]

was this a pre built package ? if so and scan built it they should test it, and feel free to trawl the forums, i am not going to do it for you

i have seen posts in the past of scan selling high end systems with stability issues.

The system shipped with an OC bundle (i3570k @ 4.5Ghz, 8GB Vengeance RAM, H100 Cooler, Fatal1ty Z77 Pro) and then I installed the remaining parts myself.

I've loaded the default BIOS settings just to see if this can solve the problem but TBH this bundled with the Mrs going on is starting to get me down a bit

Preying for a resolution ,
Rookie

[kalniel]

The system shipped with an OC bundle (i3570k @ 4.5Ghz, 8GB Vengeance RAM, H100 Cooler, Fatal1ty Z77 Pro) and then I installed the remaining parts myself.

I've loaded the default BIOS settings just to see if this can solve the problem but TBH this bundled with the Mrs going on is starting to get me down a bit

Preying for a resolution ,
Rookie

Did the chkdsk come up with anything?

[Rookie1986]

Did the chkdsk come up with anything?

I get this message when I try to run CHKDSK

Access Denied as you do not have sufficient privileges.
You have to invoke this utility running in elevated mode.

I'm set as Admin so not sure what else could be wrong, I've got to go to work now anyway but I'm only their until 7:30 tonight so if anyone has any ideas for me to try once I get home it would be much appreciated if you could post them on here ready for when I return,

Thanks a lot,
Steve

[Rookie1986]

Sorry, double post - Its just not my month lol!!

Rookie

[bluepumpkin]

I feel for you man. I doubt GoNz0 meant physically not installing it correctly, surely he was just suggesting that perhaps they did not set the correct values in the BIOS (maybe the wrong timings)

Presuming this system is the one in your system details you are using an SSD (presumably) as you OS drive, did you install Windows 7 from scratch? Do you know if the SSD is set-up in AHCI mode? I ask because you could easily get similar BSOD errors if the HDD is not working quite right and the most important driver for the HDD will be the AHCI. Because of this an older installation of Windows (based on different MB) is likely to not be using the correct AHCI drivers and so could generate issues like this. I think someone earlier suggested it but I would perhaps try using native IDE mode and if you have not done so a fresh windows 7 install (on another HDD to test perhaps)

[Rookie1986]

I feel for you man. I doubt GoNz0 meant physically not installing it correctly, surely he was just suggesting that perhaps they did not set the correct values in the BIOS (maybe the wrong timings)

Presuming this system is the one in your system details you are using an SSD (presumably) as you OS drive, did you install Windows 7 from scratch? Do you know if the SSD is set-up in AHCI mode? I ask because you could easily get similar BSOD errors if the HDD is not working quite right and the most important driver for the HDD will be the AHCI. Because of this an older installation of Windows (based on different MB) is likely to not be using the correct AHCI drivers and so could generate issues like this. I think someone earlier suggested it but I would perhaps try using native IDE mode and if you have not done so a fresh windows 7 install (on another HDD to test perhaps)

Hey,

Yeah its the system in my side bar. Windows 7 was a full fresh install on the SSD. I'm not sure about AHCI but I haven't manually done this in the registry or the BIOS so I'm going to say its in IDE mode at present (will check when I finish work). After the first crashes last Saturday Windows 7 has had a full fresh install again, I also re-installed the drivers/utilities from my motherboard disk but the computer does not like this for some reason and gets constant BSOD when the utilities are installed so I have had to remove them for now. Maybe the motherboard has a problem?? IDK I'm just guessing here, clearly I'm in over my head!

Rookie.

[GoNz0]

I feel for you man. I doubt GoNz0 meant physically not installing it correctly, surely he was just suggesting that perhaps they did not set the correct values in the BIOS (maybe the wrong timings)

i would have expected most people to have assumed that but i missed the reply being a scan rep. i guess i should have expected that sort of an answer.

[kalniel]

I'm set as Admin so not sure what else could be wrong, I've got to go to work now anyway but I'm only their until 7:30 tonight so if anyone has any ideas for me to try once I get home it would be much appreciated if you could post them on here ready for when I return,

Thanks a lot,
Steve

Open an elevated command prompt - the instructions should be on that page, but if not, type run into the search bar, right click on the run icon it finds and run as administrator. Then run the full (/r) chkdsk for each volume - volumes not in use can be taken offline for the scan, but if it's in use it'll want to schedule for the next time you reboot.

Don't forget to check the cables and sata/ahci drivers.

[Rookie1986]

Open an elevated command prompt - the instructions should be on that page, but if not, type run into the search bar, right click on the run icon it finds and run as administrator. Then run the full (/r) chkdsk for each volume - volumes not in use can be taken offline for the scan, but if it's in use it'll want to schedule for the next time you reboot.

Don't forget to check the cables and sata/ahci drivers.

Hey,

When I right click on the run icon and go to the shortcut tab, open advanced properties the option to change over to admin is greyed out.

[kalniel]

Sorry, try 'cmd'. Then right click that and 'run as administrator'

[Rookie1986]

Sorry, try 'cmd'. Then right click that and 'run as administrator'

Again, this is also grayed out when I try to change it over to admin, I have checked my account settings and I'm set as the computer admin so I'm'm not sure whats going on

[kalniel]

Maybe you're already admin so it doesn't allow you to change it. I don't know about logging in with admin privileges over the whole account as it should never be needed and isn't advised.

Maybe log in with a normal account then do the above?

[Rookie1986]

Maybe you're already admin so it doesn't allow you to change it. I don't know about logging in with admin privileges over the whole account as it should never be needed and isn't advised.

Maybe log in with a normal account then do the above?

I'm sorry I dont follow, there are only two accounts on my system, mine (admin) and then Guest Account. Or am I'm looking at something totally different here? Either way the admin box is not ticked in either the "Run" or "CMD" settings window.

So far since resetting the BIOS back to default I havent had another crash but its still to early to tell. What should I do if I find that having the system not overclocked means it works because I paid scan to overclock it for me and TBH I don't want it non-overclocked because I've spent a lot of money on cooling and parts to make sure it could be overclocked.

Rookie

[kalniel]

If it's 100% stable at stock then it's almost certainly voltage/timing related, not hard disk/cables. If you've paid for it to be overclocked then discuss it with Scan and they will either give you some configuration options to improve stability, or replace parts that are not stable when overclocked (assuming they were guarenteed to be).