davefromlondon
I thought my ibuypower.com gaming pc (quad core, 2gb corsair, asus pl5 sli mobo, 640mb nvidia ge force 8800gts vista ult, vdj 5.0) was running without freeze crash.......i recently tested it for over 24 hours and it finally froze and gave me the funny face error message.. it recovered without boot but the music video stopped. i use automix, all vista is tunes and all setting on vdj as per message boards.
am I asking too much to go over 24 hours non stop. I'll never gig that much, at most 6 hours or so.but it was a test. Maybe I'll test multiple 8 hour overnight tests and reboot every time.
Any thoughts on why I crashed after so much success ?
am I asking too much to go over 24 hours non stop. I'll never gig that much, at most 6 hours or so.but it was a test. Maybe I'll test multiple 8 hour overnight tests and reboot every time.
Any thoughts on why I crashed after so much success ?
geposted Tue 22 Jan 08 @ 4:07 pm
djcel
Can you copy paste here the data of your "crashguard report.txt" file
geposted Tue 22 Jan 08 @ 6:29 pm
Paz75
no guesses, but when i mix and then leave vdj open overnight and try to play something in the morning, it doesnt crash, but it also doesnt work. probably something went to sleep.
when you tested it 24 hours, you werent acutally using the software for 24 hours, thus you werent an operator at the controls. maybe something went to sleep as well cuz you were moving the mouse and keyboard to keep it awake? i seriously doubt the abilities of Microsuck to manage sleep modes on hardware because all versions of windows that have it are able to mess it up somehow. you dont know how many times an 'asleep' machine (by closing the lid and waiting for all activity and power to stop) comes alive in my back from the office and then i either forget about it and it kills itself from the heat or it runs out of batteries, or i open it an hour later and find a machien cooking the bag....
when you tested it 24 hours, you werent acutally using the software for 24 hours, thus you werent an operator at the controls. maybe something went to sleep as well cuz you were moving the mouse and keyboard to keep it awake? i seriously doubt the abilities of Microsuck to manage sleep modes on hardware because all versions of windows that have it are able to mess it up somehow. you dont know how many times an 'asleep' machine (by closing the lid and waiting for all activity and power to stop) comes alive in my back from the office and then i either forget about it and it kills itself from the heat or it runs out of batteries, or i open it an hour later and find a machien cooking the bag....
geposted Wed 23 Jan 08 @ 4:43 am
davefromlondon
Crashguard - I found this under user/documents/virtualdj
if date=801220055 means 22 jan 2008 , midnightish then that sounds about right time it crashed last
CRASHGUARD
date=708300048
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=708300447
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=708300452
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=708300531
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=708300829
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=708300903
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=708301008
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=709132118
version=5.0
build=500
thread=Scan
address=006b94f5
ins=66892b83
excode=c0000005 (1,ce77000)
CRASHGUARD
date=709210851
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=709220234
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=709221548
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=709231322
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=709231443
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=709231455
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=801220055
version=5.0
build=500
thread=Scan
address=006b94f5
ins=66892b83
excode=c0000005 (1,fdd7000)
if date=801220055 means 22 jan 2008 , midnightish then that sounds about right time it crashed last
CRASHGUARD
date=708300048
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=708300447
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=708300452
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=708300531
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=708300829
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=708300903
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=708301008
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=709132118
version=5.0
build=500
thread=Scan
address=006b94f5
ins=66892b83
excode=c0000005 (1,ce77000)
CRASHGUARD
date=709210851
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=709220234
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=709221548
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=709231322
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=709231443
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=709231455
version=5.0
build=500
thread=Main
address=00438e8b
ins=8b481089
excode=c0000005 (0,10)
CRASHGUARD
date=801220055
version=5.0
build=500
thread=Scan
address=006b94f5
ins=66892b83
excode=c0000005 (1,fdd7000)
geposted Wed 23 Jan 08 @ 8:33 pm
djcel
All these crashes are with the old version 5.0
You can now delete this file on your computer.
You can now delete this file on your computer.
geposted Thu 24 Jan 08 @ 2:31 pm
A Man and His Music
I don't get it, That's the version he's using. Does the report give an indication what went wrong?
geposted Thu 24 Jan 08 @ 3:21 pm
davefromlondon
djcel wrote :
All these crashes are with the old version 5.0
You can now delete this file on your computer.
You can now delete this file on your computer.
yes, I'm using 5.0 because, up till recently, it was working for tens of hours with no crash. I read issues with 5.0 rel 6 so i'm reluctant to upgrade. I'd appreciate a response on why 5.0 crashed
geposted Thu 24 Jan 08 @ 10:14 pm
cstoll
The only real issue with ver5.0.6 is that if you are using the DAC-2 controller.
And the point about ver 5.0 being OLD is the in the subsequent revision releases it is very possible that the bug you encountered was 'fixed'.
I agree a better explanation is do to what your crash codes represent.
And the point about ver 5.0 being OLD is the in the subsequent revision releases it is very possible that the bug you encountered was 'fixed'.
I agree a better explanation is do to what your crash codes represent.
geposted Fri 25 Jan 08 @ 2:41 pm
djcel
There are 2 different crashes
This one is a crash during the scan ([Any music] or [techno/house]) of a song. Maybe a corrupted file.
davefromlondon wrote :
CRASHGUARD
date=801220055
version=5.0
build=500
thread=Scan
address=006b94f5
ins=66892b83
excode=c0000005 (1,fdd7000)
date=801220055
version=5.0
build=500
thread=Scan
address=006b94f5
ins=66892b83
excode=c0000005 (1,fdd7000)
This one is a crash during the scan ([Any music] or [techno/house]) of a song. Maybe a corrupted file.
geposted Fri 25 Jan 08 @ 6:45 pm
davefromlondon
cstoll wrote :
The only real issue with ver5.0.6 is that if you are using the DAC-2 controller.
And the point about ver 5.0 being OLD is the in the subsequent revision releases it is very possible that the bug you encountered was 'fixed'.
I agree a better explanation is do to what your crash codes represent.
And the point about ver 5.0 being OLD is the in the subsequent revision releases it is very possible that the bug you encountered was 'fixed'.
I agree a better explanation is do to what your crash codes represent.
if I upgrade and have problems then what is the best way to re-instate the current version. do I use vista restore point or do I de-install and re install
geposted Mon 28 Jan 08 @ 1:19 pm
davefromlondon
djcel wrote :
There are 2 different crashes
This one is a crash during the scan ([Any music] or [techno/house]) of a song. Maybe a corrupted file.
davefromlondon wrote :
CRASHGUARD
date=801220055
version=5.0
build=500
thread=Scan
address=006b94f5
ins=66892b83
excode=c0000005 (1,fdd7000)
date=801220055
version=5.0
build=500
thread=Scan
address=006b94f5
ins=66892b83
excode=c0000005 (1,fdd7000)
This one is a crash during the scan ([Any music] or [techno/house]) of a song. Maybe a corrupted file.
is there any way to define exactly what happened ?
geposted Mon 28 Jan 08 @ 1:21 pm