PlanetZ forums - scopeusers.com

Hello everybody,

I have big problems with my new system:

setup:
A8V deluxe
AMD64 3500+
2 GB Kingston DDR400 RAM
Creamware Pulsar 1
TerraTec DMX6fire
WinXP pro & Nuendo 3

As a last step, I installed Nuendo 3 today and wanted to switch the ASIO setting to ASIO SCOPE - but everytime I do so I get a blue screen and have to restart the system. The Pulsar 1 does not share its IRQ (18). In my old Pentium4 system that was never a problem. It doesn't work wether I try this in XTC mode or in standalone mode. I don't know how I can solve this problem. Thank you in advance for your help!

Best wishes,
Ulrich

I think your problem my be related not to your system, but to Nuendo "3". I have read lots of complains about the "3" version. Many have gone back till they fix a bit better some serious problems. Perhaps you should content yourselve with going back to Nuendo 2.1, which is still a quite stable version, then when the "3" version becomes a truly stable one, you install it again.

Any way, just a point.

On 2005-05-12 00:31, Nestor wrote:
I think your problem my be related not to your system, but to Nuendo "3". I have read lots of complains about the "3" version. Many have gone back till they fix a bit better some serious problems. Perhaps you should content yourselve with going back to Nuendo 2.1, which is still a quite stable version, then when the "3" version becomes a truly stable one, you install it again.

Any way, just a point.

Hi Nestor,

many thanks for your reply! Personally I don't suspect Nuendo 3 because everything worked fine with my old setup:

Soyo P4I 845PE ISA Board
Pentium 4 2.8 MHz
Kingston 2 GB DDR 400 RAM
Creamware Pulsar 1
TerraTec DMX 6fire
WinXP pro & Nuendo 3

That lets me think about a hardware problem - can anyone help?

Best wishes,
Ulrich

<font size=-1>[ This Message was edited by: RockEngineer on 2005-05-12 08:09 ]</font>

Hello again,

I did once again a clean install of Windows and changed the PCI slot - but it doesn't solve my problem: Everytime I want to switch the ASIO driver to ASIO SCOPE in Nuendo, I get a Bluescreen with "MACHINE-CHECK-EXCEPTION" and I have to restart. Please help! I tried out BIOS versions 1011 and 1009. What does this exception mean?

Best wishes,
Ulrich

Update: I turned Cool'n'Quiet off, I disabled ASPI 2.0 support, I disabled USB 2.0 support - it doesn't change anything!!!

I made a research on google and many say that it's an error due to hardware faults of cpu due to overheating, or related to a too small power supply.

anyway I found this discussion:
http://reviews.cnet.com/5208-6142-0.htm ... ID=1151969

others report graphic driver problems or drivers generally...
uninstall and reinstall all drivers, maybe Scope drivers first...

Anyway if you search on google or such you can find lot of infos.

On 2005-05-12 12:03, alfonso wrote:
I made a research on google and many say that it's an error due to hardware faults of cpu due to overheating, or related to a too small power supply.

anyway I found this discussion:
http://reviews.cnet.com/5208-6142-0.htm ... ID=1151969

others report graphic driver problems or drivers generally...
uninstall and reinstall all drivers, maybe Scope drivers first...

Anyway if you search on google or such you can find lot of infos.

Hi Alfonso,

thanks for your reply. I already used Google - as a consequence I changed my graphic card -> same problem!
I turned on my computer maybe half an hour ago - this can't be a cpu overheating?!
My power supply is a Q-TEC 400W (not a cheap one) Is it too weak?? I don't know but the same components worked well in my previous system (different mobo + cpu)

The problem only arises if I want to switch the ASIO driver within Nuendo (sometimes as well in the case I wanted to load XTCproject.pro within SFP)

Is there anyone among you running a Pulsar 1 on a ASUS A8V deluxe with AMD64 cpu without problems???

Best wishes,
Ulrich

<font size=-1>[ This Message was edited by: RockEngineer on 2005-05-12 12:39 ]</font>

have you tried installing XP in standard Mode? since you gave it all. I would try reinstalling the OS in standard mode and put the Pulsar and the VGA on one of these IRQ's 5/9/10/or 11


you need to disable lots here to get to the core problem,

1. hyper threading off
2. usb
3. on board sound

you may have to start with only the Pulsar and video card to see what causes this machine to blue screen on you.

<font size=-1>[ This Message was edited by: antar on 2005-05-12 13:01 ]</font>

this is a motherboard with ALL the topings:

did you try disabling ALL those extra stuff including your sound card.

Quote:
The specs
A quick look at the A8V Deluxe's spec sheet hints at what makes this board so Deluxe.

CPU support Socket 939-based Athlon 64 processors
Form factor ATX
Chipset VIA K8T800 Pro
North bridge VIA K8T800 Pro
South bridge VIA VT8237
Interconnect Ultra V-Link (1.06GB/sec)
PCI slots 5 32-bit/33MHz
AGP slots 1 AGP 4X/8X (1.5V only)
Memory 4 184-pin DIMM sockets
Maximum of 4GB of DDR266/333/400 SDRAM
Storage I/O Floppy disk
2 channels ATA/133
2 channels Serial ATA 150 via VT8237 south bridge with RAID 0,1 support
1 channel ATA/133 via Promise PDC20378 with RAID 0, 1, 0+1 support
2 channels Serial ATA 150 via Promise PDC20378 RAID with RAID 0, 1, 0+1 support
Audio 8-channel audio via VT8237 integrated audio and ALC850 codec
Ports 1 PS/2 keyboard
1 PS/2 mouse
1 serial
1 parallel
headers for 1 game port
4 USB 2.0 with headers for 4 more
1 Firewire via VIA VT6307 with headers for one 1 more
1 RJ45 10/100/1000 Gigabit Ethernet via Marvell 88E8001

1 analog front out
1 analog bass/center out
1 analog rear out
1 analog surround out
1 analog line in
1 analog mic in
2 digital S/PDIF outputs (RCA and TOS-Link)
BIOS AMI
Bus speeds CPU: 200-300MHz in 1MHz increments
Bus dividers CPU:MEM: 1:1, 4:3, 3:2, 5:3, 2:1
Voltages CPU: 0.8-1.8V in 0.025V increments
AGP: 1.5-1.6V in 0.1V increments
DRAM: 2.6-2.8V in 0.1V increments
V-Link: 2.5-2.6V in 0.1V increments
Monitoring Voltage, fan status, and temperature monitoring



<font size=-1>[ This Message was edited by: antar on 2005-05-12 12:57 ]</font>

Hi Antar,

thanks for your reply - no I didn't try standard mode yet (I remember that ASPI wasn't a problem on my old board..)

I disabled almost everything like onboard sound, Raid, S-ATA etc. I only use onboard LAN.

Which mobo with socket 939 do you prefer?

Best wishes,
Ulrich


<font size=-1>[ This Message was edited by: RockEngineer on 2005-05-12 13:06 ]</font>

check this link about the
msi neo2 platinum 939

http://www.planetz.com/forums/viewtopic ... forum=19&1


I don't have this mainboard but I may upgrade to it later on.



<font size=-1>[ This Message was edited by: antar on 2005-05-12 14:11 ]</font>

On 2005-05-12 14:08, antar wrote:
check this link about the
msi neo2 platinum 939

http://www.planetz.com/forums/viewtopic ... forum=19&1


I don't have this mainboard but I may upgrade to it later on.



<font size=-1>[ This Message was edited by: antar on 2005-05-12 14:11 ]</font>

Thank you very much! I will change the board. There is another interesting one which includes nvideas:
Gigabyte GA-K8NSC-939

This one has got S-ATA connectors as well.
Best wishes,
Ulrich

hello RockEngineer,

I suggest you change your nickname to "HardwareEngineer"after you managed to solve your problems (just kidding)
cheers
tom

hopefully we'll soon start again making music together!!!

HELP!!!
I have the same problem...
As I swith to pulsar drivers the system crashes and blue screen comes.
Any suggestions???
---------------------
Athlon 64 3000+
MB ASUS A8V DELUXE
PSU GSP 400W
AGP RADEON 9200
IDE + SATA HD

This might seem like a silly question, but are there asio drivers loaded in your project?

of course they are...
I tried with both asio and wave and had the same blue screen.
s

it's a problem with your computer.

*edit* i shouldn't be so flip...
can either of you blue screeners describe the EXACT steps taken in installing your software? if the problem is not there, then there's faulty hardware in your case. i wouldn't be a bit surprised if it was the motherboard you chose. via chipset plus bleeding edge technology equals potential trouble(the nforce4 chipsets may be trouble as well). the scope driver and nuedo/sx works GREAT in most cases, multiple computers here as well....

personally, i'd have gotten an all intel solution myself and skipped 64bit for the moment(there's really no software anyway), but i prefer function and stability over blazing speed anyway.

all that said, assuming proper drivers, latest bios etc, and proper software setup still should work imho, but not if you have a hardware fault. i would guess that it's memory related. i'd bet that the memory you used is not optimal and that you may need to manually set timings. memory may be faulty. also, you may have over-over-clocked your machine.

just guesses, but here's a microsoft page about the machine check exception:
http://support.microsoft.com/default.as ... -us;329284

since this message seems to originate with a feature in p4 processors, there may be some problem with 64bit amd processors as relates to windows(faulty error messages), but again this is strictly conjecture and not knowledge....

<font size=-1>[ This Message was edited by: garyb on 2005-06-05 03:03 ]</font>

I think it's a problem with CREAMWARE and the arrival of the new technology.Creamware should update pulsar's I drivers in order to work with newer chipsets and cpus.So,it's not our's computer problem (we are two persons whith the same setup in this forum)but Creamware's business...

On 2005-06-05 01:26, garyb wrote:
it's a problem with your computer.

*,
i would guess that it's memory related. i'd bet that the memory you used is not optimal and that you may need to manually set timings. memory may be faulty. also, you may have over-over-clocked your machine.
....

<font size=-1>[ This Message was edited by: garyb on 2005-06-05 03:03 ]</font>

The memory I used is a branded one , Kingston DDR 400 MHZ and works fine with other systems like mine...So it's not a hardware fault.Don't forget that we are two persons with the same setup in this thread and with the same problem...(so how it could be hardware fault?)

some links about the machine check exception:
http://lists.debian.org/debian-amd64/20 ... 00348.html
http://forums.amd.com/index.php?showtopic=47121
http://www.planetamd64.com/lofiversion/ ... t7084.html
http://www.aoaforums.com/forum/archive/ ... 11181.html
http://www.hardwareforumz.com/-SY-KT400 ... 40222.html