rt64.sys Blue Screen

[AbsoluteGuardian]

This is just one of many in a long string of BSODs my computer has experienced that I still haven't been able to crack down on. This happened while watching videos on youtube and downloading a game so nothing particularly strenuous.

If anyone can shed some light on this I'd be eternally grateful because this is honestly beyond me at this point.

https://www.dropbox.com/s/q8mxcgphhx7b1n2/011618-34531-01.dmp?dl=0

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://pste.eu/p/nO1t.html

File: 052618-34937-01.dmp (May 26 2018 - 14:37:18)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
Probably caused by: ntkrnlmp.exe (Process: Agent.exe)
Uptime: 0 Day(s), 3 Hour(s), 36 Min(s), and 12 Sec(s)

I can't help you with this. Wait for additional replies. Good luck.

 

[AbsoluteGuardian]

I ran the dump file through the debugger and got the following information: https://pste.eu/p/nO1t.html

File: 052618-34937-01.dmp (May 26 2018 - 14:37:18)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
Probably caused by: ntkrnlmp.exe (Process: Agent.exe)
Uptime: 0 Day(s), 3 Hour(s), 36 Min(s), and 12 Sec(s)

I can't help you with this. Wait for additional replies. Good luck.

Agent.exe being the process that caused it means it happened while I was patching Overwatch which is handy. Shame it's not the root of the problem, I don't even know what is anymore.

 

[Colif]

How old is the PC? I know you have the newest BIOS from 2016 but motherboard itself was released in 2011. errors could be caused by newer drivers sending commands the older bios doesn't understand,

I probably asked this already but have you tried a clean install of win 10? it might be an old driver that I can't see running.

Sending you to Tenforums sure didn't help. We think ntkrnlmp stands for NT Kernal Multi Processor, we had to work it out ourselves.

is that latest version of Synapse?

I am starting to run out of guesses myself, hence wondering about age of PC being reason above.

 

[AbsoluteGuardian]

How old is the PC? I know you have the newest BIOS from 2016 but motherboard itself was released in 2011. errors could be caused by newer drivers sending commands the older bios doesn't understand,

I probably asked this already but have you tried a clean install of win 10? it might be an old driver that I can't see running.

Sending you to Tenforums sure didn't help. We think ntkrnlmp stands for NT Kernal Multi Processor, we had to work it out ourselves.

is that latest version of Synapse?

I am starting to run out of guesses myself, hence wondering about age of PC being reason above.

I've had this PC since 2013 and the issues started ~2015 though I vaguely recall getting a couple of BSODs before that.

As for the clean install, this PC was initially running Windows 7 all the way until Windows 10 came out, that was a fun experience too. Installing Windows 10 from the installation media failed. Routinely. It would make no progress, some progress or a lot of progress then throw up and error and revert everything back to the way it was. So what I had to do was do a clean install of Windows 7 and THEN do a clean install of Windows 10, I don't think I could get a cleaner install once Windows 10 was installed by that point.

I just updated Synapse though I'd like to know how it made its way back on my PC after I uninstalled it. I guess Win10 downloaded it as a driver for a product it recognised?

 

[Colif]

I wonder if its that AMD SATA driver from 2012 that is reason you couldn't fresh install win 10, and had to go the long way. I assume you mean you clean installed win 7 and then upgraded it to 10, as installing 7 and then clean installing 10 wouldn't make any sense (clean installs wipe all partitions off the drive whereas the upgrade would have used any win 7 drivers win 10 didn't have)

You could always reinstall win 7 if it worked fine without errors, you still have that license even if you upgraded it to 10, it will still work on 7.

 

[AbsoluteGuardian]

I wonder if its that AMD SATA driver from 2012 that is reason you couldn't fresh install win 10, and had to go the long way. I assume you mean you clean installed win 7 and then upgraded it to 10, as installing 7 and then clean installing 10 wouldn't make any sense (clean installs wipe all partitions off the drive whereas the upgrade would have used any win 7 drivers win 10 didn't have)

You could always reinstall win 7 if it worked fine without errors, you still have that license even if you upgraded it to 10, it will still work on 7.

I just mean I selected the clean install option when I was upgrading to Windows 10, it's not like it would've gotten rid of much beyond that point.

These problems existed on Windows 7 too.

 

[Colif]

Blink... stop making it difficult 😀

Sorry, every fix I can think of you throw back at me

I guess that clean is best you can do. It likely used the AMD driver I mentioned which has no win 10 version.

I don't know what to suggest apart from driver verifer but you already said why you don't want to run it.
A new PC comes to mind but thats the expensive fix.

 

[AbsoluteGuardian]

Blink... stop making it difficult 😀

Sorry, every fix I can think of you throw back at me

I guess that clean is best you can do. It likely used the AMD driver I mentioned which has no win 10 version.

I don't know what to suggest apart from driver verifer but you already said why you don't want to run it.
A new PC comes to mind but thats the expensive fix.

I'm sorry about that, this has been going on for long enough to the point where I've tried most things. I went as far as upgrading the PSU on a whim in 2016 because someone suggested this could be a hardware issue and I got a BSOD the day after for my efforts.

Student life so as much as I'd like to I can't even resort to a new PC. I appreciate everyone here trying to help.

 

[Colif]

I can't read dump files, I just read patterns. I helped enough people on here to normally figure these things out. Usually the drivers responsible will show themselves eventually.

Its why I suggested Tenforums as there are people there who can read them. Another thought is ask on here, they another name I see a lot on my searches for answers - https://www.bleepingcomputer.com/forums/f/233/windows-crashes-bsod-and-hangs-help-and-support/

I am sorry I can't figure this out. I hate it when threads go for months without resolution.

 

[AbsoluteGuardian]

I can't read dump files, I just read patterns. I helped enough people on here to normally figure these things out. Usually the drivers responsible will show themselves eventually.

Its why I suggested Tenforums as there are people there who can read them. Another thought is ask on here, they another name I see a lot on my searches for answers - https://www.bleepingcomputer.com/forums/f/233/windows-crashes-bsod-and-hangs-help-and-support/

I am sorry I can't figure this out. I hate it when threads go for months without resolution.

I'll give BC a bash, maybe something else will pop up here too 😀