motherbaords and windows7

bubbletopspoon

Honorable
Sep 14, 2013
91
0
10,630
Hi guys
Recently i have been getting the blue screen of death and i have been looking around and apparently it can happen if all yours drivers arent up to date.
Was looking around at all my components and the only thing that is out of date is the motherboard BIOS, is there a chance that can cause it, because apparently it can, mine is four versions too old.

Also if the BIOS can cause this can anyone tell em how to update it, because on there website (msi) there is a link so i click it extract it, run it and then it says cant execute command.

Motherboard- B75MA-P33
Thanks, any help would be greatly appreciated
 
Solution
Hey bubble, download the latest BIOS for your board from MSI. Put it on a USB flash drive, leave it plugged into a USB slot. Restart your PC, hit the DELETE key when the BIOS Flash screen comes up. (The screen that says the name and model of your MB, down on the bottom of that same screen it should say something like, "Hit DEL to enter the bios.") Once in the UEFI BIOS, on the top of the screen there should be a tab that says TOOLS. Go to that, in that it should have a utility that says "Flash Utility" Click on that. Once there find the slot where the USB Flash drive is located that has your newly downloaded BIOS file. Once found, hit ENTER on it. It should tell you something like "Would you like to read this file?" Hit ENTER. Then it...
ok will download this who crashed and try it but i recently upgraded to a I5 which is an ivy bridge and in the description of the newer BIOS version it say update for Ivy bridge processors so i think i just need to update my BIOS, but dont know how and im scared i will screw the system up.
 
so i did the scan and this is what the report was:

On Mon 27/01/2014 17:06:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012714-19765-01.dmp
This was probably caused by the following module: hal.dll (hal+0x5472)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
 
also this was shown for the same time:

On Mon 27/01/2014 17:06:01 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: iusb3xhc.sys (iusb3xhc+0x6424B)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\iusb3xhc.sys
product: USB 3.0 Device Driver
company: Intel Corporation
description: Intel(R) USB 3.0 eXtensible Host Controller Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iusb3xhc.sys (Intel(R) USB 3.0 eXtensible Host Controller Driver, Intel Corporation).
Google query: Intel Corporation KMODE_EXCEPTION_NOT_HANDLED
 
where exactly do i find the update for those drivers, also is there a chance you could tell me step by step how to update my BIOS or should i jsut look online (bit of a PC noob even though i built this 😛 )
 
Hey bubble, download the latest BIOS for your board from MSI. Put it on a USB flash drive, leave it plugged into a USB slot. Restart your PC, hit the DELETE key when the BIOS Flash screen comes up. (The screen that says the name and model of your MB, down on the bottom of that same screen it should say something like, "Hit DEL to enter the bios.") Once in the UEFI BIOS, on the top of the screen there should be a tab that says TOOLS. Go to that, in that it should have a utility that says "Flash Utility" Click on that. Once there find the slot where the USB Flash drive is located that has your newly downloaded BIOS file. Once found, hit ENTER on it. It should tell you something like "Would you like to read this file?" Hit ENTER. Then it says "Would you like to update?" After its complete you'll have to restart.
 
Solution
also geek jed, once i click on the file from, the MSI webiste, it downloads and then i can drag it into the USB drive, but it goes in as an EXE file and if i double click on it to run it doesn't let me and says it not compatible with my version of 64bit windows, am i not meant to run it until i hit the BIOS menu?
 


You don't run it from within windows, you run it from the BIOS.
What you should have downloaded from MSI was a .zip file, and then you extract the contents of the .zip onto the USB.
http://us.msi.com/service/biosupdate/
You're doing a "Flash AMI UEFI BIOS by MFLASH"
 
thank you very much geek jed, james mason, and scout. Just did it all went well, wasnt as hard as i thought it would be, got scared over nothing, will report back ion here to see if that solves the blue screen error for me :)
 
hi guys, so it seemed the BIOS didn't help the blue screen, i ran the whocrashed test and this message appeared:

On Tue 28/01/2014 20:06:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012814-22698-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EC9AC5, 0xFFFFF8800A1BCCD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


Any1 have any ideas of what could be causing this crash then??
 
Sorry bubble, I ran off on you. I'm thinking its registry errors. I would download a good registry repair app. to do some fixing. And while your at it get a good defrag. app. as well. You should always defrag. and optimize your HD every week.