New
#31
There seems to be a trend here. I just can't imagine that so many burns on 2 different drives have resulted in failures. The odds don't support it being the burning software.
In instances like this, the most common fault is the hard drive, but this could also be a memory issue.
So, I'd first suggest that you perform a bootable memory diagnostic. Use this free tool (rather than the built in memory tool): Bootable Memory Test Diagnostics - Vox
Then try a bootable hard drive diagnostic ( Bootable Hard Drive Diagnostics - Vox )
The BSOD's don't point to anything in particular, but here's the summary:
Code:Built by: 6000.16386.amd64fre.vista_rtm.061101-2205 Debug session time: Thu Jun 18 18:56:02.750 2009 (GMT-4) System Uptime: 0 days 0:18:13.721 BugCheck A, {fffffaafd0821760, 2, 0, fffff80001c8bddd} Probably caused by : win32k.sys ( win32k!memset+80 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: iexplore.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 6000.16386.amd64fre.vista_rtm.061101-2205 Debug session time: Thu Jun 18 19:18:19.793 2009 (GMT-4) System Uptime: 0 days 0:21:45.763 BugCheck 50, {fffffa80ff11a5f0, 0, fffff80001c59f54, 5} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+119 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 6000.16386.amd64fre.vista_rtm.061101-2205 Debug session time: Thu Jun 18 19:35:38.757 2009 (GMT-4) System Uptime: 0 days 0:16:48.727 BugCheck 50, {fffff90000852230, 0, fffff960000443a9, 0} Probably caused by : win32k.sys ( win32k!xxxInternalDoPaint+19 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: explorer.exe