After updating drivers I have regular BSOD

Page 1 of 2 12 LastLast

  1. billyray
    Posts : 7
    Windows 7 pro 64bit
       New #1

    After updating drivers I have regular BSOD


    Hello,


    The Desktop PC I'm having BSOD on is my DAW which I use for recording and mixing music with Pro Tools 12.

    This has been very stable for the past 4 years until I bought a new audio interface from Audient ID-44.

    I've worked with Audient's support to get it stable and that involved updating drivers for graphics card, networking, and also the BIOS.
    At some point in this process I updated from Windows 7 Home to Windows 7 Pro, mainly as I was going to add some more RAM and Win 7 Home will only support the 16GB I have.
    The Audient interface is way more stable since all the updates but now I get BSOD at least once a day, sometimes more.

    I've tried removing the Audient drivers and reverting to my old Digidesign interface and drivers which was really stable before all the updates but now I get BSOD with that too!
    Reverting to the old interface isn't a long term option as it's very old and has poor sound compared to the Audient.
    I'd really appreciate any help in diagnosing this, I have dmp files from the last few BSOD but you can't attach them in this forum so I used bluescreenviewer to create some txt files from the last 2.


    I have already run a memtest overnight and the memory is report as fine. I did try running a CPU test with Prime95 but it seems to crash within 30 seconds, not sure if I'm using the correctly.



    The main issue I can see in them is:


    ntoskrnl.exe BSOD



    Thanks in advance


    Billy
      My Computer
    Quote Quote

  3. Paul Black
    Posts : 6,021
    Win 7 HP SP1 64-bit Vista HB SP2 32-bit Linux Mint 18.3
       New #2

    Hi billyray,

    Welcome to SevenForums!

    billyray said:
    I've worked with Audient's support to get it stable and that involved updating drivers for graphics card, networking, and also the BIOS.
    Please run MS_Info32_Find_Problem_Devices.bat Option [2] from here => BATCH PROGRAMS [Standalone] and then upload the results using the tutorial at the bottom of the above link [Upload to SevenForums . . .] and someone will look at it for you.

    INFORMATION: I have written quite a few batch scripts in order to streamline processes, avoid possible typing errors, and save time hunting around for specific Windows and tabs etc. It is just quicker and easier for users to run the batch script[s] and then upload the results for us to look at.

    I hope this helps!
      My Computer
    Quote Quote

  4. Vineet Garg
    Posts : 565
    Windows 7 Ultimate x32 With Sp1 + Vista Ultimate x32 with Sp1 & Sp2 !!
       New #3

    Hi & Greets to both of you!

    1.
    I have dmp files from the last few BSOD but you can't attach them in this forum
    @billyray : You may also follow here BSOD - Posting Instructions

    2. WhoCrashed came better for me than BlueScreenView but our masters use more advanced utilities.

    Thanks & Regards. ...
      My Computer
    Quote Quote

  6. Paul Black
    Posts : 6,021
    Win 7 HP SP1 64-bit Vista HB SP2 32-bit Linux Mint 18.3
       New #4

    Hi billyray,


    billyray said:
    I have dmp files from the last few BSOD but you can't attach them in this forum so I used bluescreenviewer to create some txt files from the last 2.
    If the file size is above the upload limit, you can zip the file[s] FIRST and then try and upload it . . .

    Screenshots And Files - Upload And Post In SevenForums

    This tutorial [Published by Brink] will show you how to upload the file =>
    Screenshots and Files - Upload and Post in SevenForums.

    I hope this helps!
      My Computer
    Quote Quote

  7. billyray
    Posts : 7
    Windows 7 pro 64bit
    Thread Starter
       New #5

    msinfo problem bat


    Thanks for the replies.


    I ran MS_Info32_Find_Problem_Devices.bat but it didn't find any problems. see attached screenshot.


    Next I'm going to have a look at the BSOD posting instructions.




    Here are the logs from the dm log collector aswell.


    Thanks
      My Computer
    Quote Quote

  8. RolandJS
    Posts : 2,774
    Windows 7 Professional 64-bit
       New #6

    Vineet Garg said:
    . WhoCrashed came better for me than BlueScreenView but our masters use more advanced utilities
    Ahhhh, a resplendent fellow tech after me own heart! For me. because of slimming trimming pc, Who Crashed, is now relative, once removed.
      My Computer
    Quote Quote

  10. Vineet Garg
    Posts : 565
    Windows 7 Ultimate x32 With Sp1 + Vista Ultimate x32 with Sp1 & Sp2 !!
       New #7

    RolandJS said:
    Ahhhh, a resplendent fellow tech after me own heart! For me. because of slimming trimming pc, Who Crashed, is now relative, once removed.
    Sir,
    I am confused what you mean ? Is WhoCrashed good to use ?

    Thanks & Regards. ...
      My Computer
    Quote Quote

  11. RolandJS
    Posts : 2,774
    Windows 7 Professional 64-bit
       New #8

    Vineet, I was having some fun alongside you, yes, WhoCrashed utility is useful, it can point to the last thing that was running just before a BSOD. Before uninstalling it, I did consult it. Another source indicated that just because X is the last active thing, does not always mean X caused a BSOD, something running in the background can be the real cause.

    Now, it is possible this utility or anything similar just might be of great help to the OP.
      My Computer
    Quote Quote

  12. Vineet Garg
    Posts : 565
    Windows 7 Ultimate x32 With Sp1 + Vista Ultimate x32 with Sp1 & Sp2 !!
       New #9

    RolandJS said:
    Vineet, I was having some fun alongside you, yes, WhoCrashed utility is useful, it can point to the last thing that was running just before a BSOD. Before uninstalling it, I did consult it. Another source indicated that just because X is the last active thing, does not always mean X caused a BSOD, something running in the background can be the real cause.
    Good Stuff Sir, Thanks.
      My Computer
    Quote Quote

  13. axe0
    Posts : 7,050
    Windows 10 Pro
       New #10

    Hi Bilyray,

    Sorry for the delay, do you still need help?
      My Computer
    Quote Quote

 
Page 1 of 2 12 LastLast

  Related Discussions
Since recently i've been getting regular BSOD with error code 0x109. Earlier threads have led me to try Driver Verifier but it came up with no errors. My specs are as follows; Computer type: PC/Desktop Computer Manufacturer/Model Number: Custom built OS: Windows 7 Ultimate x64 CPU: AMD FX-8350...
Hi experts, I was working on video project, I got a notification about new GPU drivers so i updated it, after that im getting this Blue screen error frequently like 3-4 times a day, I have attached all files needed in a zip below please help me with this, Just help me to find wat is the real...
New BSOD after updating drivers
in BSOD Help and Support

Running fresh install of 7 x64 ultimate. Was having lots of BSOD. Was told they were driver issues. Updated drivers and computer was running fine. Shut down computer for a couple hours and when I turned it back on I got another BSOD. Can someone please debug this dump and let me know what caused...
Hello All. So I am working with Toshiba Satellite A205-S5855. It is about 2 years old. Originally I purchased this laptop with the OS Vista on it. Had several issues with it over the past two years that included getting two hard drives and a mother board replaced under warranty. This warranty...
Went from XP to 7 in January and have had numerous crashes since. Have made 2 fresh instals and 2 repair/upgrade instals but still crashing. The events seem random and log files are not helpful although Firefox, Thunderbird and Iolo System Shield crash but do not result in a BSOD. Have run...
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 12:58.
Find Us