Print

[xboxdawg]

This is an odd problem, hope someone can help.

I have a Toshiba SH-D162C in a Windows XP Svc pack 3 PC.

I can read the game in fine using Xbox Backup Creator. But when I go to burn it, it gets to the Optimum Power Calibration or whatever, then says writing, it sits there about a minute or two and does nothing. Then my computer reboots.

I was using v2.8 so I downloaded v2.9. Now I get an error message something about DMI when I start the program and it does the same thing.

One key point, I have changed out the motherboard in my PC and the hard drive. So I'm wondering if there is some setting I need to change/check or what? Any ideas? It's an old ASUS K8U-X socket 754 motherboard and I mentioned the windows/drive setup above. The drive I'm writing with is a Pioneer DVD-RW that works fine for DVD burning.

It apparently writes just enough to the blank DVD-R DL that its not recognized as a blank. So I've wasteda bout 3 or 4 of them. Any ideas?

Thanks,

XBD

[armyof1ne]

QUOTE(xboxdawg @ Jun 16 2009, 05:27 PM)

This is an odd problem, hope someone can help.

I have a Toshiba SH-D162C in a Windows XP Svc pack 3 PC.

I can read the game in fine using Xbox Backup Creator. But when I go to burn it, it gets to the Optimum Power Calibration or whatever, then says writing, it sits there about a minute or two and does nothing. Then my computer reboots.

I was using v2.8 so I downloaded v2.9. Now I get an error message something about DMI when I start the program and it does the same thing.

One key point, I have changed out the motherboard in my PC and the hard drive. So I'm wondering if there is some setting I need to change/check or what? Any ideas? It's an old ASUS K8U-X socket 754 motherboard and I mentioned the windows/drive setup above. The drive I'm writing with is a Pioneer DVD-RW that works fine for DVD burning.

It apparently writes just enough to the blank DVD-R DL that its not recognized as a blank. So I've wasteda bout 3 or 4 of them. Any ideas?

Thanks,

XBD

Believe it or not, this is more of a pc question... most of the time installing new hardware doesnt do squat, in some rare cases, it can cuase instability in all windows platforms becuase resources that were once dedicated to certain pieces on your old mother are no longer.... your registry is probably screwed up a little along with other things, I hate to tell you this but it would be best when replacing a whole motherboard to reformat windows xp, back up all your data and do a clean install of windows so that   1. you have a completely clean registry  2. you have the right chipset resources allocated with no chance of having "the old motherboard's resouce conflict".

This is the easiest solution, otherwise you would be tinkering for days with the registry as well as killing a shitton of dl's

[xboxdawg]

I guess you misunderstood me. I replaced the Motherboard AND Hard Drive. Installed Windows XP from scratch and reinstalled everything as I needed it.

So pretend this is a new PC cause that's basically what it is.

So any other ideas as far as what to check?

Thanks,

MC

[majinsoftware]

My computer does the same thing, strange thing is that imgburn works fine for burning, its just XBC that BSOD my computer even tho it uses imgburn engine.

So I just have to close xbc and open the dvds files with imgburn its self.

[armyof1ne]

QUOTE(xboxdawg @ Jun 17 2009, 05:53 PM)

I guess you misunderstood me. I replaced the Motherboard AND Hard Drive. Installed Windows XP from scratch and reinstalled everything as I needed it.

So pretend this is a new PC cause that's basically what it is.

So any other ideas as far as what to check?

Thanks,

MC

i reread and sure enough... was too early in the morning i guess, lol.... Ok, i read and didnt notice media type that you were using, That plays a major factor, Have you checked latest firmware? have you disabled Imapi service when burning DL's(Run services.msc, disable imapi only when your burning dvd+r DL's, make sure you reboot after you disable) 90% of the time this fixes the problem, the other 10% is the drive is becoming faulty(i have killed 2 drives over the life of me making backups of almost $4000 dollars in games)
these are for the calibration problem, which you do have, as far as your rebooting run scandisk, you may have a damaged .dll or .sys file that could be cuasing the crash... normally you will see a blue screen at a crash, not just it rebooting

another thing would be make sure you have SP3 and all windows updates availible, being that its a clean install(hoping) it may be SP2 or earlier

Last but not leastly, Run a malware/spyware/viral scan... i would recommend you use malwarebyte's Anti-Malware, That shit is the best on the market, and its free... you dont have a rootkit i dont think, free version doesnt tackle rootkits, Anyway, Ill give you a rundown

so this is what i suggest
1. Upgrade firmware for you drive
2. Disable imapi when burning DL's(Services.msc, disable service reboot, reactivate/reboot when done)
3. Get better media
4. Run recovery console for windows xp and execute command "chkdsk /f /r" without quotes
5. Make sure windows is 100% updated
6. Run a viral scan using malwarebyte's antimalware

When done please respond back to know how it went, i monitor threads that i tackle, i dont monitor everything(being that im not an admin or mod or anything else for that matter)
Good luck!

[xboxdawg]

I'll give it a try and report back.

Thanks for the great suggestions!

XBD

[xboxdawg]

OK, I did everything you mentioned, Windows XP was already updated to svc pk 3.  Pioneer DVR-110D is at firmware 1.41 which is most current. It works fine for burning DVD-R and worked fine for DL with my old motherboard.

I ran the chkdsk /p/r from the windows xp disc recovery mode. It fixed a few problems.

Downloaded and ran the malwarebyte antimalware (thanks! I like it!) It found 2 minor things.

Next I did the services.msc, imapi was on manual so it wasn't running anyway. I set it to disable and rebooted.

I also have norton systemworks so I've run that and cleaned up Windows.

Xbox backup creator 2.9 does the power calibration, sync and says it's gonna write layer 1, then gives a blue screen with machine check.

I tried it again and selected imgburn  to burn it (instead of XBC) and it worked perfectly.

So now I don't know what the deal is. I can continue to use the Imgburn option but am still curious as to what's going on. I'm wondering if I'm missing some driver or something for the motherboard. I've installed everything that was on the CD that came with it. I checked the ASUS website and what I've got on the CD looks newer than what they had on there.

Any other ideas? I know I found a workaround but it would be nice to know whats going on.

I really appreciate the time you took Army to answer me.

Thanks,

XBD

This post has been edited by xboxdawg: Jun 19 2009, 01:09 AM

[armyof1ne]

QUOTE(xboxdawg @ Jun 18 2009, 06:08 PM)

OK, I did everything you mentioned, Windows XP was already updated to svc pk 3.  Pioneer DVR-110D is at firmware 1.41 which is most current. It works fine for burning DVD-R and worked fine for DL with my old motherboard.

I ran the chkdsk /p/r from the windows xp disc recovery mode. It fixed a few problems.

Downloaded and ran the malwarebyte antimalware (thanks! I like it!) It found 2 minor things.

Next I did the services.msc, imapi was on manual so it wasn't running anyway. I set it to disable and rebooted.

I also have norton systemworks so I've run that and cleaned up Windows.

Xbox backup creator 2.9 does the power calibration, sync and says it's gonna write layer 1, then gives a blue screen with machine check.

I tried it again and selected imgburn  to burn it (instead of XBC) and it worked perfectly.

So now I don't know what the deal is. I can continue to use the Imgburn option but am still curious as to what's going on. I'm wondering if I'm missing some driver or something for the motherboard. I've installed everything that was on the CD that came with it. I checked the ASUS website and what I've got on the CD looks newer than what they had on there.

Any other ideas? I know I found a workaround but it would be nice to know whats going on.

I really appreciate the time you took Army to answer me.

Thanks,

XBD

At this point we know its XBC... its possible that you got a bad install(package and all) becuase to my knowledge they use the same .sys files to burn(though i believe they are compiled in the program itself)
Try getting on xbins ftp and redownload XBC remove install and install to a new folder(not the one it was originally set to) when you recieve a blue screen, 90% of the time it does a physical memory dump which means a small list of things...
1. computer memory is bad and is failing to store items(unstable),
2. Hard drive file system is unstable or corrupt(either on its way to death or file system is literally corrupting itself meaning low level format is in order)
3. The items you are using(programs/.vxd's,.dll's,.sys are damaged and need replaced)
4. Northbridge(CPU/Memory Backbone controller as well as on some boards the Sata controller) on your motherboard is unstable(can be cuased by heat or damaged northbridge..... Depending on your motherboard, some boards run your sata/ide on your southbridge which normally controll PCI... PCI-E, this means it could be a combination of both northbridge and southbridge.(This is so rare its not even funny, But i have come across it... being that its new i doubt it, but it could have been damaged in manufacture)

So as stated... Your options are now...

1. Download a new install package of XBC(latest of course) off xbins(google autoxbins... its a quick and fast way instead of getting a irc client)
2. I didnt state this before, but there might command conflicts(this never occured to me before) Try seeing if your motherboard is completely up to date as far as the bios goes.... Before you upgrade make sure that in the release notes your problem is defined... if its not defined... no bios update is needed(your more than welcome to update to please the computer gods though)
3.Try switching in XBC from SPTI to ASPI after everything else is done... SPTI is an admin only scsi translation API..... ASPI is a any-user style scsi translation API

Another question... this pertains to the SPTI/ASPI fix...  Are you running as an administrator or User? Being that its a blue screen, i doubt this is the problem... in all my time working on computers ive seen some real wierd crap that shouldnt be doing what its doing but does anyways... lol..

Last question...  Press Windowskey+Pausebreak-->HardwareTab-->Device manager and open up your IDE ATA/ATAPI entry and see if you have a certain chipset install correctly... for me its VIA, for some its Nforce... (Via Serial ATA Controller) Make sure its install, if not, since you obviously looked at the site and they havent updated in a while, you might have the wrong disc, try and use the drivers availible off the site.

Let me know how it goes!

This post has been edited by armyof1ne: Jun 19 2009, 02:25 AM

[xboxdawg]

I was using XBC 2.8 and getting same thing. So I downloaded 2.9. ASPI is grayed out. I suspect a driver/motherboard program. I will delete the drivers and try the ones from the website.
I am the only user and as such I am the administrator so that's not an issue.

I appreciate your support and I'll report back after I try the things you suggested.

Thanks,

XBD

[armyof1ne]

QUOTE(xboxdawg @ Jun 18 2009, 09:13 PM)

I was using XBC 2.8 and getting same thing. So I downloaded 2.9. ASPI is grayed out. I suspect a driver/motherboard program. I will delete the drivers and try the ones from the website.
I am the only user and as such I am the administrator so that's not an issue.

I appreciate your support and I'll report back after I try the things you suggested.

Thanks,

XBD

That could be that no viable ASPI driver is available...I personally have had good luck with nero... they created there own ASPI driver instead of adaptecs one(nero's is more recent)
i think just picking up a trial version should get it installed correctly and it will then be able to be used

[TheDemonIII]

one thing u might wanna just do is use the option in xbc to choose ur burn engine, and point it towards your imgburn directory. that's what i do because i like using imgburn and xbc makes sure all of the settings are correct (layerbreak and whatnot).

[xboxdawg]

Demon I did that and it works. But still I'd like to know why my PC is failing when I try to it the other way. I'm getting a machine_check_exception blue screen.

[armyof1ne]

QUOTE(xboxdawg @ Jun 19 2009, 09:17 AM)

Demon I did that and it works. But still I'd like to know why my PC is failing when I try to it the other way. I'm getting a machine_check_exception blue screen.

If it wasnt any of those things posted... its either memory or hard drive damage... try updating... reinstalling driver... thats about all thats left

[majinsoftware]

Samsung drives just dont like the xbc burn engine. Something to do with the aspi.

[xboxdawg]

OK I deleted the drivers for everything associated with the motherboard that I could find. Downloaded the drivers from the website and installed.

It detected them and seemed to install fine. It did fix a problem I was having with my Sansa Mp3 player. Whenever I attached it with the PC on it would reboot. It works fine now.

However I cannot burn using XBC 2.8 or 2.9. I think it is something on the Northbridge or something. I just don't know. I will use the Imgburn option in XBC 2.9 as a workaround in the meantime.

It does the syncing, power optimization and then says it's starting to write. However it never does anything. HD spins a few times then after like a minute or two the MACHINE_CHECK_EXCEPTION blue screen of death appears. So something in that program is looking for a status or something that it can't get and it crashes the whole system. Everything else that I know of that I am using works fine. So it's quite the mystery.

And you are right, on my old motherboard I did have the optiion to select ASPI. Maybe something is not installed properly for that. I should research that next I suppose.

Thanks for everyone's assistance. If you have any other ideas let me know. I would like to get this fixed but I do have a workaround for backing up my games.

Thanks,

XBD