Solved

BSOD on a new windows install! (crash dump files included)

Hello people of Tom's hardware

I have had 2 BSOD'S in one day! one happened when i was AFK and the other when i was playing GTA V (game). As I have know clue what to do i thought i would upload the dump files here and hope some one can help.
Crash dump files: https://www.dropbox.com/sh/yrccp4qkx2oqpn8/AAAECv4wG93CVaLbSbPF9Wnja?dl=0

Thanks for any help

*NOTE* i have been having hard drive errors but this is on a E: drive not my main drive with the drivers and such
5 answers Last reply Best Answer
More about bsod windows install crash dump files included
  1. use this it wil read bsod in plain text http://www.resplendence.com/whocrashed also you e drive give error i would test it with the maker software and if you unplug it do you have bsod .
  2. scout_03 said:
    use this it wil read bsod in plain text http://www.resplendence.com/whocrashed also you e drive give error i would test it with the maker software and if you unplug it do you have bsod .


    I will try unplugging it and reading the dump thanks for the quick reply :)
  3. Best answer
    the first bugcheck was in a custom usb driver but you have two overclocking software drivers installed.
    driver was \SystemRoot\system32\DRIVERS\ViaHub3.sys Sun Jan 19 18:19:55 2014

    both bugchecks were called because of a bad memory address passed to viahub3.sys
    I would remove the overclocking drivers and see if you can still get the bugcheck.
    if you do, then change the memory dump to a kernel memory dump and reboot. the new memory.dmp file will contain info to help debug USB issues.

    remove:
    C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys Tue Sep 06 00:11:44 2011
    and
    C:\Program Files (x86)\MSI\Super Charger\NTIOLib_X64.sys Thu Oct 25 03:27:58 2012
  4. johnbl said:
    the first bugcheck was in a custom usb driver but you have two overclocking software drivers installed.
    driver was \SystemRoot\system32\DRIVERS\ViaHub3.sys Sun Jan 19 18:19:55 2014

    both bugchecks were called because of a bad memory address passed to viahub3.sys
    I would remove the overclocking drivers and see if you can still get the bugcheck.
    if you do, then change the memory dump to a kernel memory dump and reboot. the new memory.dmp file will contain info to help debug USB issues.

    remove:
    C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys Tue Sep 06 00:11:44 2011
    and
    C:\Program Files (x86)\MSI\Super Charger\NTIOLib_X64.sys Thu Oct 25 03:27:58 2012


    will do thanks
  5. johnbl said:
    the first bugcheck was in a custom usb driver but you have two overclocking software drivers installed.
    driver was \SystemRoot\system32\DRIVERS\ViaHub3.sys Sun Jan 19 18:19:55 2014

    both bugchecks were called because of a bad memory address passed to viahub3.sys
    I would remove the overclocking drivers and see if you can still get the bugcheck.
    if you do, then change the memory dump to a kernel memory dump and reboot. the new memory.dmp file will contain info to help debug USB issues.

    remove:
    C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys Tue Sep 06 00:11:44 2011
    and
    C:\Program Files (x86)\MSI\Super Charger\NTIOLib_X64.sys Thu Oct 25 03:27:58 2012


    THANKS THIS FIXED IT
Ask a new question

Read More

Windows Crash Blue Screen Tom's Hardware Crash dump files