After updating drivers I have regular BSOD

[billyray]

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

 

[Paul Black]

Hi billyray,

Welcome to SevenForums!

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 and then upload the results for us to look at.

I hope this helps!

 

[Vineet Garg]

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. ...

 

[Paul Black]

Hi billyray,

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 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!

 

[billyray]

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

 

[RolandJS]

. 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.

 

[Vineet Garg]

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. ...

 

[RolandJS]

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.

 

[Vineet Garg]

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.

 

[axe0]

Hi Bilyray,

Sorry for the delay, do you still need help?

 

[billyray]

Hi,


Yes I really need help still, I was wondering if the thread had died!




Let me know what you think of the logs from my last post?


Billy

 

[billyray]

That would be great thanks

 

[axe0]

Which test in P95 do you get a crash?

 

[billyray]

yes I still need help please

 

[Paul Black]

Hi billyray,

Yes I still need help please.

You didn't answer axe0 question!

 

[billyray]

Which test in P95 do you get a crash?

sorry missed it, Small FFTS. It runs for about 10-20 secs before BSOD.

 

[billyray]

Cpu test

I just ran IntelBurnTest, almost immediately (5 seconds) one of the cores on my CPU hits 83 degrees C when running the test in Standard mode. No doubt this isn't good. Does it mean my CPU is knackered or is there something I could try in the BIOS?



I've attached a screenshot.


Thanks

 

[axe0]

The max safe temperature for your CPU is 66 degrees.

Do the temperatures get high when you're using the computer normally?

 

[wither 2]

All the temperatures seem to be on the high side. Have you checked the fan on the CPU to see if it's clean (and also running).