Thanks again,
Good idea, tonight I will check out the IDE/ACHI setup, before attempting anything else.
BTW I don't get any beeping.
I suspect POST does not even get started in any meaningful way!
My problem, I have just enough knowledge to be dangerous!!
Q-Wave BSOD's
Re: Q-Wave BSOD's
I know the feeling. There's enough on the web to confuse too...
If you're not getting to post, not sure if you'll be able to boot into an os.
Sounds like you bricked your motherboard?
I truly hope not.
Hope you find a solution man. All the best..
If you're not getting to post, not sure if you'll be able to boot into an os.
Sounds like you bricked your motherboard?
I truly hope not.
Hope you find a solution man. All the best..
Not because it is easy, but because it is hard...
Re: Q-Wave BSOD's
a failed bios upgrade can surely brick a motherboard. i'd check with the maker to see if they have a solution. if not, there's ebay. if you jusdt replace the motherboard with the same, there won't be any big resets for your programs, probably just a reauthorization for windows.
Re: Q-Wave BSOD's
Yeah Gary,
Thats what I was thinking.
The MOBO isn't that old so there should be some around.
Anyway I'll know tonight.
maus
Thats what I was thinking.
The MOBO isn't that old so there should be some around.
Anyway I'll know tonight.
maus
Re: Q-Wave BSOD's
Not conveniently. They are on all 4 of my Scope hardware instances and Ive no idea which one connects my Reason and Cubase dongle, which I need to play QWave :Eanna wrote:Dante, the 64 bit version of the zarg synths use a different device driver for managing stuff probably to do with memory or dma. Can you disable the usb host controller, even temporarily, and retest on 64 bit?
- Dante-IRQ
- Dante-IRQ.jpg (151.55 KiB) Viewed 2810 times
Re: Q-Wave BSOD's
@Dante, for those devices sharing IRQ with Scope in msinfo32, you can check exactly what hardware items are connected to those ports, by going thru Device Manager's Connections by Type view (see my first post on the matter). Any element sharing IRQ with Scope that doesn't have connected hardware is eligible for disablement. And you may be able to reconnect some items too, move them to different connectors, and then disable those items you've freed up.
One thing I know can certainly cause DPC latency, which may or may not be associated with your problems, is Wifi dongles. If you need it, try to move it off to a separate USB host, or disable that port when using Scope.
Me, I had a 4-port USB hub where I had some other USB bits hanging off. I now have Ableton Push connected to that USB hub, and it's working well. Three USB ports on my PC, two of which had items connected, and some PCIe slots that I don't use, no longer actually function, since I disabled the Host Controllers in the Device Manager.
Like GaryB has always said, I'm now pretty confident that it's IRQ sharing that's the main culprit for Scope misbehaving. My system is now purring like its never done before.
@Maus, if you can see the BIOS screens, then you've done a successful POST, and you should be able to check IDE/AHCI, and boot into an OS. If however you cannot get to the BIOS screens, then the BIOS update may well have bricked your motherboard, meaning you may need to source another motherboard. Hopefully, MSI will come good with a workaround, or possibly your motherboard is still under warranty - if it's a failure in their BIOS update software that's bricked your mobo, then you may have a different type of discussion with their support crew...
Just throwing this out there - if you do need another motherboard, maybe you could consider one with a few PCIe slots, so you can move your Xite host card to a different slot, with a view to having options for ensuring your IDE channels aren't sharing IRQ interrupts with Scope. There are a few threads where some folk have indicated stability for particular mobo models here on planetz too. Obviously, that decision is yours...
One thing I know can certainly cause DPC latency, which may or may not be associated with your problems, is Wifi dongles. If you need it, try to move it off to a separate USB host, or disable that port when using Scope.
Me, I had a 4-port USB hub where I had some other USB bits hanging off. I now have Ableton Push connected to that USB hub, and it's working well. Three USB ports on my PC, two of which had items connected, and some PCIe slots that I don't use, no longer actually function, since I disabled the Host Controllers in the Device Manager.
Like GaryB has always said, I'm now pretty confident that it's IRQ sharing that's the main culprit for Scope misbehaving. My system is now purring like its never done before.
@Maus, if you can see the BIOS screens, then you've done a successful POST, and you should be able to check IDE/AHCI, and boot into an OS. If however you cannot get to the BIOS screens, then the BIOS update may well have bricked your motherboard, meaning you may need to source another motherboard. Hopefully, MSI will come good with a workaround, or possibly your motherboard is still under warranty - if it's a failure in their BIOS update software that's bricked your mobo, then you may have a different type of discussion with their support crew...
Just throwing this out there - if you do need another motherboard, maybe you could consider one with a few PCIe slots, so you can move your Xite host card to a different slot, with a view to having options for ensuring your IDE channels aren't sharing IRQ interrupts with Scope. There are a few threads where some folk have indicated stability for particular mobo models here on planetz too. Obviously, that decision is yours...
Not because it is easy, but because it is hard...
Re: Q-Wave BSOD's
I'm BACK!!!
Was able to boot from USB.
Used RUFUS to get a bootable drive and the loaded Bios DOS file onto it.
Magic happened.
Thanks so much to Eanna for the great help and hanging in there for me.
That was a couple of hairy days.
I owe you a beer when you come out to Australia.
Now what was I doing two days ago.........
Was able to boot from USB.
Used RUFUS to get a bootable drive and the loaded Bios DOS file onto it.
Magic happened.
Thanks so much to Eanna for the great help and hanging in there for me.
That was a couple of hairy days.
I owe you a beer when you come out to Australia.
Now what was I doing two days ago.........
Re: Q-Wave BSOD's
Delighted for yiz buddy!!
Well done on sticking with it!
Time to backup BIOS and HD now methinks?!
Well done on sticking with it!
Time to backup BIOS and HD now methinks?!
Not because it is easy, but because it is hard...
Re: Q-Wave BSOD's
Oh yeah its backup time!!
Re: Q-Wave BSOD's
Good to hear.mausmuso wrote:I'm BACK!!!.
@Eanna, I'll read your instruction post later, try stuff out then post your guide to Scoperise along w/ the Modular Prowave correction.
Re: Q-Wave BSOD's
Dante let me know how you get on. Feel free to fire on any questions to make the article as good as we can make it.. 
Maus, let me know how you get on too on your quest to banish the bsod..
Maus, let me know how you get on too on your quest to banish the bsod..
Not because it is easy, but because it is hard...
Re: Q-Wave BSOD's
Ive updated a section here under "Reassign IRQs So Scope Gets Its Own" link.
http://www.hitfoundry.com/tsg/tsg_mast.htm
Haven't tried it out yet, will wait until I get myself a decent USB hub. A Rack Mount one WOULD be nice !!!!
But it looks like I can find out the actual devices I know I can disable safely by using device manager (devices by connection) alone by expanding all the nodes within APCI node, without getting the hex numbers from MSINFO32.EXE first - from the below screenshot.
http://www.hitfoundry.com/tsg/tsg_mast.htm
Haven't tried it out yet, will wait until I get myself a decent USB hub. A Rack Mount one WOULD be nice !!!!
But it looks like I can find out the actual devices I know I can disable safely by using device manager (devices by connection) alone by expanding all the nodes within APCI node, without getting the hex numbers from MSINFO32.EXE first - from the below screenshot.
- Win 8 Device Manager
- device manager.jpg (108.9 KiB) Viewed 2761 times
Re: Q-Wave BSOD's
actually Scope cards are ok with a shared irq involving a system resource like an ide bus or a pci or pcie controller. these devices almost always play nice. firewire, lan ports, usb and to some degree, video cards should be avoided. you can probably get away with a video card or a lan port that wasn't connected while using Scope, but usb must be disable if it's sharing an irq with a Scope card. firewire is best disabled too(when it shares an irq with a Scope card), unless you can use a different slot.
Re: Q-Wave BSOD's
Dante, you really just need to make sure that the USB devices connected to USB host controllers that are share IRQ with Scope are moved to other ports.
Then you can disable those USB host controllers.
I.e. it's only important to disable those USB Host Controllers that are shared with Scope.
And it's better to disable the Host Controller nodes, rather than the Devices connected to the Host Controllers. If you disable the device, you won't be able to use it on different ports. And the IRQ for the Host Controller will still be shared with Scope... Disabling the Host Controllers themselves will mean that the IRQ sharing goes away...
Gary's the most experienced head on what's OK for sharing, but in general, do as much as you can is the best advice...
As for USB hubs, I got mine for like 4 euros in a magazine shop. It's externally powered...
Then you can disable those USB host controllers.
I.e. it's only important to disable those USB Host Controllers that are shared with Scope.
And it's better to disable the Host Controller nodes, rather than the Devices connected to the Host Controllers. If you disable the device, you won't be able to use it on different ports. And the IRQ for the Host Controller will still be shared with Scope... Disabling the Host Controllers themselves will mean that the IRQ sharing goes away...
Gary's the most experienced head on what's OK for sharing, but in general, do as much as you can is the best advice...
As for USB hubs, I got mine for like 4 euros in a magazine shop. It's externally powered...
Not because it is easy, but because it is hard...
Re: Q-Wave BSOD's
I hear ya Gary,
But for me IRQ 19 (1 * PCIe + 1 * 1394 slot) = Can't move/can't disable
Solution get rid of Firewire M-Audio ProjectMixIO and get a new controller me thinks.
On the BSOD front
I have run MEMTest86 on my 12Gb RAM - no errors.
Cross that off.
I have a 650GB HDD and I only have 32GB left on the disk.
Could that be contributing?
I note they suggest having at least 100MB free for Windows.
I'm way over that but maybe there is something else?
maus
But for me IRQ 19 (1 * PCIe + 1 * 1394 slot) = Can't move/can't disable
Solution get rid of Firewire M-Audio ProjectMixIO and get a new controller me thinks.
On the BSOD front
I have run MEMTest86 on my 12Gb RAM - no errors.
Cross that off.
I have a 650GB HDD and I only have 32GB left on the disk.
Could that be contributing?
I note they suggest having at least 100MB free for Windows.
I'm way over that but maybe there is something else?
maus
Re: Q-Wave BSOD's
Temporarily remove your ProjectMix from the Firewire port, and disable the OCHI 1394 controller, and restart.
If it fixes BSODs, then yes you can consider whether you wish to move the ProjectMix on...
As for disk space, can you see what you can temporarily move off to an external hard drive? A Sample Library you can choose to not fire up while testing maybe?
You could even pop the case of an external HD, and add it as a second internal drive, as the majority of external HD's are SATA, and will happily live inside your PC case, directly connected to the motherboard via SATA rather than going thru a USB bridge.
If it fixes BSODs, then yes you can consider whether you wish to move the ProjectMix on...
As for disk space, can you see what you can temporarily move off to an external hard drive? A Sample Library you can choose to not fire up while testing maybe?
You could even pop the case of an external HD, and add it as a second internal drive, as the majority of external HD's are SATA, and will happily live inside your PC case, directly connected to the motherboard via SATA rather than going thru a USB bridge.
Not because it is easy, but because it is hard...
Re: Q-Wave BSOD's
I have done the disable firewire trick and I still got BSOD's.
I think it probably worth doing anyway longer term to ensure SCOPE get priority everytime/all the time.
Also I am thinking about what I can move off the C:\.
I have two other drives for projects and sample libraries, also I have a server backup connected with a couple of TB's available so I should be able to free up some space.
Regards
I think it probably worth doing anyway longer term to ensure SCOPE get priority everytime/all the time.
Also I am thinking about what I can move off the C:\.
I have two other drives for projects and sample libraries, also I have a server backup connected with a couple of TB's available so I should be able to free up some space.
Regards
Re: Q-Wave BSOD's
There's a free program call TreeSize free edition. Its great for finding big dirs
Not because it is easy, but because it is hard...
Re: Q-Wave BSOD's
you saw the post about samples right?
it took me a minute, but if you are loading presets that use samples, that's the problem. the sample players based on the STS don't work in 64bit windows...
it took me a minute, but if you are loading presets that use samples, that's the problem. the sample players based on the STS don't work in 64bit windows...