![]() It's the MOTU pcie 424 with four 24 i/o devices hanging off it. I have a firewire cabled, but not firewire interface (they use the cables just for data). Your email went right to spam, but I found it tonight after reading this. Another possibility is it could have dried up thermal compound on whatever cooling solution (blocks and pipes out to a fan, I assume) is over the GPU.ĭo you get the same thing if you hook up an external monitor?ĭo you have a CPU in there with Intel graphics? If so, can you select it in the BIOS (F2 on boot) and disable the nvidia graphics for now? Is it reasonable for you to open it up to clean out the fan? Sometimes it's just insufficient cooling that causes GPU issues. Given that this is LTSC, it's not an update issue. 'That's Windows 10? I swear I can see the Windows 7 taskbar at the bottom of that noise. So any ideals or am I doomed to the dungeon of hell. I don't have sleep cause something apparently is wrong with my video card, it won't work with it's driver, so I've been using the MS basic display driver and that has worked fine for longer than when the video card quit working (runs cooler). I've found that if I wait for the OS select page, then click the other options line followed by clicking the shut down option it will then start up normally. At first I removed the power and battery, then held the power button down for 10 seconds. Comes up with the first screen when bios boots. So this is What I get after about every 4th startup/ power up or out of hibernation. I'll check your email tomorrow after some meetings. Not saying that's your issue (totally different device), just that I've seen that type of behavior before. I've also had it happen when I had a bad firewire cable (too long, so out of spec). They cycle exactly like that when the PC is first powering up, before they get clock sync. Pete, have you received my e-mail on that matter?Your email went right to spam, but I found it tonight after reading this. ![]() I also borrowed an USB interface that does not exhibit any of this behaviour, so this indeed is confined to Firewire devices. It was going through 44, 48, 88, 96, 176 and 192 and back again. What I observed though, by accident, keeping Saffire's MixControl open, is that the interface is not cycling between some two sampling rates but rather goes through all available ones in a loop. Only after once again reinstalling everything I was able to get it back to usable condition. The issue reappeared randomly without any particular reason yesterday, and hit hard, as none of my usual mumbo jumbo was helping. ![]() Bad news is that the solution worked more or less flawlessly just for a few days.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |