do i need mobo drivers if my pc bsod

techhead122 · Aug 7, 2016

hey there, I have an ibuypower and its mobo is a gigabyte ga-78lmt-usb3. it recently bsod when I went to shut the system done and also when I was watching a video to study for my A+ certification ironically lol. I performed chkdsk with no errors, checked bios for abnormal temperatures and everything was good, and also performed all windows updated that were available. Ithen also went to the mobo website and checked to see if there were any driver updates for it, which there are a few that were released from 2010-2014. at the top of the screen though it gives and option to click (rev.4.1) (rev.5.0) or (rev.6.0). not sure what that means and could use some help troubleshooting what my systems problem is!!!

Thanks

!

jsmithepa · Aug 7, 2016

I've doing this for like forever and I NEVER investigate nothing, seldom the problem is obvious. To me is very simple, SOMETHING changed and that's causing it. If you think about it, there are tons of stuff happening in your PC and everything must *almost* be flawless, but perfection don't exist, all software have bugs.

So what do I do? I maintain OS Image backups. Those are my known-to-be-good system "states." I restore the dang thing, which takes 15 minutes and am guaranteed am back to a good place, sans hardware problem, mind you but hardware issues are rare. Software not playing nicely is typically 95%+ of issue. No OS Image Backup? (think about it in the future), Windows may have already been doing this for you, go into Restore and see if has saved CHECKPOINTS, you may be able to "go back" using those, no as nice as OS Image backups.

Colif · Aug 7, 2016

download and run who crashed: http://www.resplendence.com/whocrashed
it will create a summary of your errors and might give name of driver

copy/paste results here

techhead122 · Aug 7, 2016

Colif :

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 8/7/2016 8:45:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080716-23821-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800030C3E3C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.

On Sun 8/7/2016 8:45:47 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: scmndisp.sys (scmndisp+0x16D1)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800030C3E3C)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\scmndisp.sys
product: SerComm® Neutral Wireless Solution
company: Windows (R) Win 7 DDK provider
description: SerComm NDIS User mode I/O Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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: scmndisp.sys (SerComm NDIS User mode I/O Driver, Windows (R) Win 7 DDK provider).
Google query: Windows (R) Win 7 DDK provider IRQL_NOT_LESS_OR_EQUAL

On Mon 7/25/2016 12:20:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072516-15100-01.dmp
This was probably caused by the following module: usbhub.sys (usbhub+0x17FA)
Bugcheck code: 0xFE (0x8, 0x6, 0x6, 0xFFFFFA8008C66160)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbhub.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Default Hub Driver for USB
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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.

On Wed 7/20/2016 12:16:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072016-18018-01.dmp
This was probably caused by the following module: usbhub.sys (usbhub+0x17FA)
Bugcheck code: 0xFE (0x8, 0x6, 0x6, 0xFFFFFA8008782160)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbhub.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Default Hub Driver for USB
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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.

On Fri 2/12/2016 6:25:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021316-15693-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x743C0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800030D616C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.

On Fri 2/5/2016 3:09:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020516-14726-01.dmp
This was probably caused by the following module: usbhub.sys (usbhub+0x17FA)
Bugcheck code: 0xFE (0x8, 0x6, 0x6, 0xFFFFFA8008EA1B20)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbhub.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Default Hub Driver for USB
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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.

On Wed 2/3/2016 3:31:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020316-15038-01.dmp
This was probably caused by the following module: usbhub.sys (usbhub+0x17FA)
Bugcheck code: 0xFE (0x8, 0x6, 0x6, 0xFFFFFA8008D6F000)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbhub.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Default Hub Driver for USB
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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.

On Thu 12/31/2015 5:35:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123115-16177-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80001E9225C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.

On Mon 11/30/2015 4:34:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\113015-19047-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80001EC425C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.

On Wed 11/18/2015 4:15:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111815-18938-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80001ED925C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

13 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

scmndisp.sys (SerComm NDIS User mode I/O Driver, Windows (R) Win 7 DDK provider)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.

Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

techhead122 · Aug 7, 2016

Colif :

I just installed this driver off gigabytes website since the dump files had to do with my usb for some of the crashes

VIA USB 3.0 Driver

V4.90A 11.61 MB 2015/03/18

im still confused on the rev 4.1 rev5.0 rev6.0 though

also when I try to download the drivers from the website it downloads and I have to click extract. its putting it into windows temp files as a zip I think. what do I do to actually download the driver?? im sorry I'm a noob at the computer tech stuff and trying to learn. thanks!

Colif · Aug 7, 2016

(rev.4.1) (rev.5.0) or (rev.6.0) are versions of your motherboard, it means Gigabyte have updated the motherboard twice and you sort of need to know which one you have or can get wrong drivers.

Download https://www.piriform.com/speccy and run it. On the right hand column are headers, one is for Motherboard - click this and it shows a detailed view
the 3rd heading down is version, what does yours show?

One you know revision number, click it and then dl any Win 7 drivers that match your motherboard.

Once you get the drivers, you need to extract them, but you can choose the location it sends them too by clicking browse next to the proposed save location. I normally extract them to the downloads folder. Then you have to click the driver in that folder to actually install.

You need might need new WiFi drivers as well.

techhead122 · Aug 8, 2016

Colif :

Motherboard
Manufacturer Gigabyte Technology Co. Ltd.
Model GA-78LMT-USB3 (Socket M2)
Version x.x
Chipset Vendor AMD
Chipset Model 780G
Chipset Revision 00
Southbridge Vendor AMD
Southbridge Model SB700
Southbridge Revision 00
System Temperature 30 °C
BIOS
Brand Award Software International Inc.
Version FA
Date 4/23/2013
Voltage
CPU CORE 1.104 V
DRAM 1.500 V
+5V 5.040 V
+12V 9.864 V
+3.3V 3.312 V
CMOS BATTERY 1.572 V
PCI Data
Slot PCI
Slot Type PCI
Slot Usage Available
Bus Width 32 bit
Slot Designation PCI
Characteristics 5V, 3.3V, PME, SMBus
Slot Number 0
Slot PCI
Slot Type PCI
Slot Usage Unknown
Data lanes x16
Slot Designation PCI Express x16
Characteristics 3.3V
Slot Number 1
Slot PCI
Slot Type PCI
Slot Usage Unknown
Data lanes x1
Slot Designation PCI Express x1
Characteristics 3.3V
Slot Number 2

techhead122 · Aug 8, 2016

Colif :

(rev.4.1) (rev.5.0) or (rev.6.0) are versions of your motherboard, it means Gigabyte have updated the motherboard twice and you sort of need to know which one you have or can get wrong drivers.

Download https://www.piriform.com/speccy and run it. On the right hand column are headers, one is for Motherboard - click this and it shows a detailed view
the 3rd heading down is version, what does yours show?

One you know revision number, click it and then dl any Win 7 drivers that match your motherboard.

Once you get the drivers, you need to extract them, but you can choose the location it sends them too by clicking browse next to the proposed save location. I normally extract them to the downloads folder. Then you have to click the driver in that folder to actually install.

You need might need new WiFi drivers as well.

so my chipset revision is 00 and there is no option for that on their website.

Colif · Aug 9, 2016

No, its just not recorded in the location speccy expected. Try opening PC case and see if its written on the board itself, or it might be in your manual.

techhead122 · Aug 10, 2016

Colif :

ok so I opened it up and see that it is a rev 5.0. I also took notice that two of my USB ports on the mobo are labeled LAN_USB and two others are labeled KB_MS_USB and was wondering if I didn't have my wireless nic connected to the LAN_USB if that could be creating some conflict? when I powered the pc back up it automatically downloaded a USB driver which I thought was ironic. Also noticed that this pc came with a WEAK PSU, 300W! but im still left with one last question if you could help me, what is the other software problem besides the USB driver listed in the dump file program that you had me run?

On Thu 12/31/2015 5:35:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123115-16177-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80001E9225C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.

Thanks again you have been a huge help!!!!

Paul NZ · Aug 10, 2016

If you installed Easytune or Charge on/off, uninstall them. Charge on/off maybe causing the USB stop errors

The revision will be etched on this mobo. Make sure you download / install the right drivers for the revision of the mobo you've got

The only mobo thats got BIOS FA is revision 5. It's the only BIOS for the revision 5 mobo

Search

do i need mobo drivers if my pc bsod

techhead122

Commendable

Paul NZ

jsmithepa

Polypheme

Colif

Win 11 Master

techhead122

Commendable

techhead122

Commendable

Colif

Win 11 Master

techhead122

Commendable

techhead122

Commendable

Colif

Win 11 Master

techhead122

Commendable

Paul NZ

Polypheme

TRENDING THREADS

Latest posts

Moderators online

Share this page