Constant BSOD when analyzing MP3 files. Crash Dumps not written out

[LiquidStool]

Hey all

Some time ago i installed windows 10 using an iso, i immediately hated it and came back to 7. Ever since then, i've suffered with almost daily BSOD and it mainly seems to be when i'm using processor heavy audio programs, mainly Serato.

When I analyze the audio files, it has an processor load display and within a few seconds, this stays at critical. Now if i had a 2gb of ram, i could understand but my pc far exceeds minimum specs for all programs i use so i'm not sure it's ram related - ramcheck didn't show any problems either.

anyhow, i've tried using Whoscrashed and it tells me that there are no dumps and they are enabled. When the PC bluescreens, it rarely restarts on it's own, just shows its collecting info for the dump, after 2 hours i figured it's probably not doing anything, reboot and all is fine until the next bsod event.

I've replaced the HDD and checked voltages etc and they all seem pretty rock steady, likewise with temps. Somebody mentioned the page file but i have no idea how to check it, to increase it or anything else related - and given that i believe it's recommended that it's double the size of the installed ram, I'm gonna need 64gb of HDD space just for that!

At a bit of a crossroads, i'm pretty sure it's driver related hence the whoscrashed purchase but without the pagefile i'm not sure where to go from here.

Any help be much appreciated.

Stool

 

[Arc]

We need at least some info to know what is going on there.

Post a reply following the Blue Screen of Death (BSOD) Posting Instructions and as you are saying that the dumps are not being recorded, take a camera snap of the next BSOD screen and let us see it. The on-screen codes might give some idea.

 

[LiquidStool]

Sorry, missed the request for information upload....

Thinks it's attached.

Will attach a BSOD snap as soon as i can replicate the crash. Thanks.

 

[Arc]

Nice. Now we have the data. Whenever we will get the hints about the bugcheck codes, we will start the troubleshooting process.

 

[LiquidStool]

Cool, thanks for your help

 

[LiquidStool]

Hope this helps!

 

[Arc]

Well, a stop 0x101 is CLOCK_WATCHDOG_TIMEOUT. So we dont have dumps that is not a big loss, dumps are generally silent for this bugcheck.

As far as we have seen, the causes of this BSOD generally are ....

• BIOS failure
• Driver failure
• Hardware failure.

So pretty much anything and everything.

Let us start from the top. As it is seen that your BIOS version is .....

BIOS Version/Date    American Megatrends Inc. 1104, 10/04/2012

There are updates available for motherboard Asus P9X79. Version 4701 would be a good try. Get it from https://www.asus.com/in/Motherboards/P9X79/HelpDesk_Download/ and apply it. See if there is any change. Let us know.

   Warning

BIOS updates are risky. If it is not done properly or aborted during the process, it will brick the motherboard. So if you dont have any prior experience with this, dont do it yourself. Get it done by someone who can do it, it may be a paid professional too.

 

[LiquidStool]

I'm on it, thank you man

 

[LiquidStool]

Hey Arc

So I've looked at the procedure for flashing the bios and it's something that i really am not comfortable with so I've called 4 local computer repair shops and none of them want to do it either!

It's probably a stupid question and will make things more difficult but can we miss this step out??

I never had this issue with an earlier version of Serato DJ (the program i'm certain is causing the issue, i'm going to go back to the earlier version to try to force a BSOD but as the newer version is much improved this will only be to confirm the issue so i'll still need to upgrade)

 

[Arc]

It's probably a stupid question and will make things more difficult but can we miss this step out??

Yes, you may skip it for the time being.

Proceed with the steps as mentioned in http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html, as much as it is needed to identify and stop the issue.

If even the clean reinstall (the last resort) is even not enough to solve the issue, then you might need to rethink about it again.

If you plan for a clean reinstall at any particular point of time, please drop a post here. Dont proceed with it till you get a reply to it.

 

[LiquidStool]

great. Will come back ASAP. thanks man.