No worries Lars.  Getting the right memory in a high spec machine is a bit of a minefield and despite outward appearances it is not always as clear cut as it may first appear.  MEMtest86 is a pretty good free memory test utility that runs independently of Windows and it should pick up any faults - if they exist - after about TEST 5 or so or maybe before - it's a while since I used it, but there's about 15 or so tests that it does and it may take a couple of hours to go through all 15 tests a couple of times.  Obviously you're looking for any errors at all.  Hey - I may be wrong and I hope I am - I'm not too proud to admit being wrong.  It's just that all the signs are there and I've seen very similar signs enough times to strongly suspect memory issues from what you've said.  For all I know perhaps the HD500 XP driver may need a bit of a tweak too.  There's usually a limited lifetime guaranteee on RAM by companies like Crucial and Corsair.  I once had some fairly expensive Crucial RAM - 3 sticks as it happens in an old Pentium III machineand I was getting lots of instability.  I ran MEMtest86 with all the RAM installed and it crapped out at about test 3. I then tested all three sticks individually.  One was perfectly OK, but the other two sticks were well below par.  I got an RMA from Crucial who simply swapped it out within two days, and my problems were solved.  what i'm saying here is that just because you got good quality RAM it doesn't necessarily mean it doesn't have a genuine fault.

Nick

Hmmm.   Strange.  Must admit I haven't used it on my i7 system.  Will try and give it a go this weekend.  There are as I recall a few different versions intended for different hardware platforms, so obviously you need to use the right one - but i will look into it tomorrow - I have day job work to do in the morning and an amp power transformer to swap out in the afternoon, but after that i will probably have some time.

Nick

Santuzzo wrote:

 

Thanks Nick!

 

I ran rthe extended tests of the  Windows Memory Diagnostics test, though, and it found no errors in 2  passes of the complete test (I had it run overnight).

 

I just had another blue screen, but this one was kind of different, since I connected my HD500 while Cubase was loading a project, 
so RAM was being used heavily at the moment. Also in this case the blue screen message was a different one.
After rebooting I tried again, this time I waited until the project was loaded in Cubase, and then nothing happened. 

I know that normally I would wait for a project to load until I connect the HD500 OR I would connect it BEFORE I have Cubase loading the project.

So, this was kind of a forced blue screen, which in my opinion does not represent the blue screens I had previously.

Does this make any sense?

Yes - possibly not related to the main problem at all.  It's never a good idea to plug in the audio device the program is going to use whilst the program is loading

Hey Lars

Still struggling with this one eh

It seems to me that it possibly is rather more stable than it first was though as it now seems to be days between BSODs rather than minutes or hours like it was initially.  You seem to be making some progress at least.  I can't offer much more than I've already said, but appearing here now just to offer some moral support.

Good luck - well done for hanging in there -  I'm sure you'll get there in the end.

Nick