Jump to content

Xbox 360 game fails to verify


Gandy

Recommended Posts

Hi I tried to burn a 360 game and imgburn finds errors in the verify stage. The burn goes through fine, but it fails in multiply places when it tries to verify. Is this normal? I'm using verbatim media and recording at 2.4x There were about three errors when I got to 21% or so so I just stopped the verify. Here's a log

 

I 15:14:45 ImgBurn Version 2.4.2.0 started!

I 15:14:45 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

I 15:14:45 Total Physical Memory: 2,096,620 KB - Available: 1,557,016 KB

I 15:14:45 Initialising SPTI...

I 15:14:45 Searching for SCSI / ATAPI devices...

I 15:14:45 Found 1 DVD

Link to comment
Share on other sites

Try burning one at 4x then :)

 

Just tried another at 4x I got one error this time around 75%, and a few others later so it's still a decent number of errors. Like I said before I don't know if this is normal for xbox discs or what. I think I've made 3 coasters, which kinda sucks considering it's verbatim. Here's the log again if you need it. There's a time gap in the log just because I let it running for a bit and came back to it a few hours later. I tried burning a different img this time for your reference.

 

I 23:20:23 ImgBurn Version 2.4.2.0 started!

I 23:20:23 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

I 23:20:23 Total Physical Memory: 2,096,620 KB - Available: 1,356,372 KB

I 23:20:23 Initialising SPTI...

I 23:20:23 Searching for SCSI / ATAPI devices...

I 23:20:23 Found 1 DVD

Link to comment
Share on other sites

No, miscompares are not 'normal'.

 

It's weird that you should be getting them at all to be honest. You expect to see errors reading back dodgy burns, not miscompares.

 

It almost looks like corruption - either in memory (test your system with memtest) or with the controller running the hdds/optical drives.

Link to comment
Share on other sites

No, miscompares are not 'normal'.

 

It's weird that you should be getting them at all to be honest. You expect to see errors reading back dodgy burns, not miscompares.

 

It almost looks like corruption - either in memory (test your system with memtest) or with the controller running the hdds/optical drives.

 

All right I just ran memtest for about 8.5 hours and it didn't find an error while scanning. I thought it might be a memory issue just because everyone once in a while(maybe once or twice a month) I'll get a BSOD. Is there anyway to test out the controller for my hdd/optical drives?

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.