LIGHTNING UK!

I believe this is a 'Read' queue rather than a 'Write' queue. It's not something I'll be doing though, soz.

Time for a new drive me thinks

That text is (will be) available in the next release. It's just 'normal' text, not 'extended' - which I assume is better known as 'debug' to me

Change the filesystem selection to include 'Joliet'.

Oh and btw, is this any good to ya? I 19:31:59 Link Size: Auto I 19:31:59 Test Mode: No I 19:31:59 BURN-Proof: Enabled I 19:32:00 Advanced Settings: Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes I 19:32:00 Filling Buffer... (40 MB) I 19:32:01 Writing LeadIn... I 19:32:01 Writing Session 1 of 1... (1 Track, LBA: 0 - 1307916)

If it can still recognise the old (burnt) ones, although you say they're not, the new discs MUST be different somehow. That or it's just lost the ability to initialise blank ones - which would be a little odd. If you've tried 2 spindles, the next logical step is to try another drive with said discs.

Unless you actually go in and change one of the settings inthe 'Advanced Settings' screen, they're not touched from whatever the drive defaults to when it's switched on, or whatever you've enabled / disabled in any other software since that time. The settings are on a drive by drive basis, so really whatever's set in the Smartburn util should be mirrored in ImgBurn - and vice versa - they both just query the drive to see what the current setting is. Are you sure the two don't match up? The wording is slightly different in both programs so don't get caught out! From my own testing, it's certainly ok with my 20A1H (LL0B) drive.

And you're sure the disc are exactly the same as the last lot you had? They're not the newer 8x ones or anything? Can the drive still recognise the DL ones you've burnt in the past? The drives firmware is STILL up-to-date yeah? Please be aware that 'ImgBurn' doesn't do any recognising of media, this is a drive issue - plain and simple.

What's it saying the statusbar when you insert the discs? i.e. open ImgBurn without anything in the drive, then insert a disc. Watch the statusbar messages and note what it says until it finally stops on something. If the drive won't recognise and initialise the media, no software can do anything with it.

The first error is the real one. In your case, the drive is simply returning the error codes that, when put in english, mean 'Write Error'. Ditch the Ricoh DL discs and buy Verbatims instead. The 2.4x DVD+R DL ones work best.

Just for giggles, go back to the 7600 for a while. See if you still get the BSOD's. That might give us more of a clue about the PSU being a potential issue. I don't know why you'd have the wrong HAL. Vista's not gonna install the wrong one, so unless you've installed on a totally different machine, I very much doubt that's the issue.

Minidump 04 Microsoft (R) Windows Debugger Version 6.7.0005.1 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Documents and Settings\Administrator\Desktop\Mini071507_04.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: C:\Windows\Symbols Executable search path is: Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 6000.16386.x86fre.vista_rtm.061101-2205 Kernel base = 0x82000000 PsLoadedModuleList = 0x82111db0 Debug session time: Sun Jul 15 10:15:49.209 2007 (GMT+1) System Uptime: 0 days 0:13:01.937 Loading Kernel Symbols ................................................................................ ................................................................................ Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, 864ba440, b2000000, 70f0f} Unable to load image \SystemRoot\system32\PSHED.dll, Win32 error 0n2 *** WARNING: Unable to verify timestamp for PSHED.dll *** ERROR: Module load completed but symbols could not be loaded for PSHED.dll Probably caused by : hardware Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 00000000, MCA_ASSERT Arg2: 864ba440, Address of WHEA_ERROR_RECORD structure Arg3: b2000000, High 32 bits of MCi_STATUS MSR for the MCA bank that had the error Arg4: 00070f0f, Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error Debugging Details: ------------------ WHEA_ERROR_RECORD: !errrec ffffffff864ba440 BUGCHECK_STR: 0x124_AuthenticAMD CUSTOMER_CRASH_COUNT: 4 DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT PROCESS_NAME: ImgBurn.exe CURRENT_IRQL: 4 STACK_TEXT: 820eef84 823a6e93 00000124 00000000 864ba440 nt!KeBugCheckEx+0x1e 820eefa0 820cecb6 864ba440 864bbad8 00000001 hal!HalBugCheckSystem+0x37 820eefc0 823a6e52 864bbad8 864bbbf0 820eeff4 nt!WheaReportHwError+0x10c 820eefd0 823a6f73 00000003 864bbad8 00000000 hal!HalpReportMachineCheck+0x28 820eeff4 823a389f 80159000 00000000 00000000 hal!HalpMcaExceptionHandler+0xc3 820eeff4 00000000 80159000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x77 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: 0x124_AuthenticAMD BUCKET_ID: 0x124_AuthenticAMD Followup: MachineOwner --------- Minidump 03 Loading Dump File [C:\Documents and Settings\Administrator\Desktop\Mini071507_03.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 6000.16386.x86fre.vista_rtm.061101-2205 Kernel base = 0x82000000 PsLoadedModuleList = 0x82111db0 Debug session time: Sun Jul 15 09:04:23.067 2007 (GMT+1) System Uptime: 0 days 0:04:40.831 Loading Kernel Symbols ................................................................................ ................................................................................ Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, 8607fd18, b2000000, 70f0f} Probably caused by : hardware Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 00000000, MCA_ASSERT Arg2: 8607fd18, Address of WHEA_ERROR_RECORD structure Arg3: b2000000, High 32 bits of MCi_STATUS MSR for the MCA bank that had the error Arg4: 00070f0f, Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error Debugging Details: ------------------ WHEA_ERROR_RECORD: !errrec ffffffff8607fd18 BUGCHECK_STR: 0x124_AuthenticAMD CUSTOMER_CRASH_COUNT: 3 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: dwm.exe CURRENT_IRQL: 0 STACK_TEXT: 820eef84 823a6e93 00000124 00000000 8607fd18 nt!KeBugCheckEx+0x1e 820eefa0 820cecb6 8607fd18 864bfad8 00000001 hal!HalBugCheckSystem+0x37 820eefc0 823a6e52 864bfad8 864bfbf0 820eeff4 nt!WheaReportHwError+0x10c 820eefd0 823a6f73 00000003 864bfad8 00000000 hal!HalpReportMachineCheck+0x28 820eeff4 823a389f 80159000 00000000 00000000 hal!HalpMcaExceptionHandler+0xc3 820eeff4 00000000 80159000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x77 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: 0x124_AuthenticAMD BUCKET_ID: 0x124_AuthenticAMD Followup: MachineOwner --------- Looks like some issue with your hardware?! It keeps pointing to your chip too. Are you overclocking or anything? Done any motherboard bios updates? If not, do some!

Find the mini memory dump file - probably in c:\windows\minidump and attach it in your next post. I'll tell you which driver is causing the problem.

ok, look in the tools menu and go into the 'filter drivers' bit. Click the 'clipboard' button and then 'paste' the info into a reply here on the forum.

Does it fail like that on *every* disc you put in the drive? i.e. cds, dvds, originals + blanks. It's difficult to say why it won't process the command, it should be pretty basic functionality! Do the other drives work ok with ImgBurn?

http://www.touslesdrivers.com/index.php?v_...amp;v_code=8956 click on the picture of the drive just under 'T

Your drive is probably connected to a USB 1.0 port. You need USB 2.0 to get any sort of decent speeds.

Put it in the drive and look in the little info panel on the right of imgburn's main window. Copy + paste all that info if you're not sure what you're looking for.

Either it's just given up and not burning anything correctly or there's some other issue with your machine. Have you tried a cleaning disc in the drive? Oh and try burning at 8x or 12x As you can see, 2x isn't even supported by the drive / firmware. If it's still doesn't work, throw the drive in the bin! (maybe try it in a different pc first though, or another drive in yours)

Happy Birthday! (probably too late now - doh!)

Different media is indeed the way forwards! Well, that and firmware - but yours is already 'current'.

When you read a disc, it's read sector by sector. i.e. what goes in is what comes out. If you need compression of some sorts, you need to look elsewhere. ImgBurn is a burning program, not a compression / transcoding /re-encoding tool.

Learn how the program works, read the guides.

If you're already using MKM-001 discs, stop wasting any more and just buy a new drive.

I never said levels were the problem