![](https://forum.imgburn.com/uploads/set_resources_1/84c1e40ea0e759e3f1505eb1788ddf3c_pattern.png)
Raptor88
-
Posts
41 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Raptor88
-
-
Not necessarily, your drive could just be messing up the burn and its firmware isn't handling it very well, reporting that error when it should be reporting something else.
Thanks for sharing your analysis. I need to figure out why:
- The original optical drive in the Dell XPS 8500 had the problem.
- A new Liteon drive updated to the latest firmware has the problem.
- A Sony Optiarc drive has the problem.
- Replaced the SATA cable and plugged into a different SATA II header on the motherboard has the problem.
I'm testing in safe mode now and will do that all day to see what happens. One thing I notice is that using the Win8 resource monitor, the network "TCP Connections" graph is maxing out when the normal Win8 is running. But when in safe mode, the "TCP Connections" drops down to horizontal line number 2 (out of 10 horizontal lines) after about 30 seconds and stays there. Think that the TCP Connections maxing out in normal Win8 could be the problem?
-
That isn't an error you normally get first. It typically follows a 'write error' of some sort and I wonder if that initial error isn't being lost somewhere in your system.
The error comes directly from the drive and basically means you're trying to write to somewhere you can't.
On most discs, sectors need to be written to in sequential order. You can't write sectors 0-15 and then 32-47 or whatever. If you try, you'll get an 'invalid address for write' error back when submitting the command to write 32-47.
Something is messing up somewhere but you can't do much to troubleshoot when all you've got is an intermittent issue.
Oh, just knowing that the error comes directly from the drive is very helpful. That means the address Imgburn sends to the drive is getting corrupt between the CPU > Southbridge chip that has the SATA controller > SATA cable > optical drive. I have replaced the optical drive plus tried an Optiarc drive, and I replaced the SATA cable and plugged the SATA cable into a different SATA port on the motherboard. So would you say that the problem is probably in the Southbridge chip on the motherboard? Your best guess is fine.
Thanks,
Raptor88
-
Haven't tried the test burns in safe mode yet since the problem is not happening in normal mode no matter how many times I've tried it till now. That's the intermittent nature of my problem.
The log from a previous error shows: Failed to write sectors xxxxxx - xxxxxx. Reason: Invalid address for write. (where xxxxxx are numbers)
What exactly causes an invalid address to be created in the first place?
... 1. Is the correct address generated by Imgburn and then gets corrupted somehow?
... 2. How does Imgburn know the address is invalid? (if it created the address in the first place)
Trying to understand what could cause an invalid address for write in test mode to help me troubleshoot this problem.
Thanks,
Raptor88
-
Also forgot to mention that this problem is intermittent. When it's working, it can complete the test burns successfully many times. When it's having the problem, it can happen consecutively.
All fans in the PC working. Problem can happen anytime during the day.
Also restored a Dec 2014 backup that was done when Imgburn was working fine and before this problem started happening. Invalid address for write problem started in about March 2015, so I doubt that it is an infection or Windows 8 problem.
-
Also forgot to mention that this problem is intermittent. When it's working, it can complete the test burns successfully many times. When it's having the problem, it can happen consecutively.
All fans in the PC working. Problem can happen anytime during the day.
-
Which controller is that drive attached to?
Right click the drive selection drop down box when you're in Write mode and select 'Family Tree'. Close the prompt that comes up and then copy + paste everything from the Log window.
Try booting up in safe mode and see if you have the same problem.
Thank you very much for your quick reply! Here's the result of the Family Tree:
I 12:01:08 ImgBurn Version 2.5.8.0 started!
I 12:01:08 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200)
I 12:01:08 Total Physical Memory: 8,348,672 KiB - Available: 6,300,176 KiB
I 12:01:08 Initialising SPTI...
I 12:01:08 Searching for SCSI / ATAPI devices...
I 12:01:09 -> Drive 1 - Info: ATAPI iHAS124 E 4L0A (M:) (SATA)
I 12:01:09 Found 1 DVD±RW/RAM!
I 12:03:01 Device: [0:0:0] ATAPI iHAS124 E 4L0A (M:) (SATA)
I 12:03:01 Family Tree:
I 12:03:01 -> ACPI x64-based PC
I 12:03:01 -> Microsoft ACPI-Compliant System
I 12:03:01 -> PCI Express Root Complex
I 12:03:01 -> Intel® 7 Series/C216 Chipset Family SATA AHCI Controller (VEN_8086&DEV_1E02 - Intel - iaStorA - v9.3.0.1011)
I 12:03:01 -> CD-ROM Drive (ATAPI iHAS124 E) (Bus Number 5, Target Id 0, LUN 0)
I will try in safe mode.
BTW, this PC has worked with Imgburn for years. Could be overheating since when I opened my friend's PC (this one), it was full of dust and the heatsinks were clogged with dust. The optical drive was replaced with the new Liteon drive for this problem. Running Windows 8 with the Classic Shell.
Thanks,
Raptor88
-
Dell XPS 8500, i5, 8GB ram, new Lite-on iHAS124 drive. Upgraded the drive's firmware from 4L08 to 4L0A.
Running Imgburn in test mode, doing a pseudo burn of a VIDEO_TS folder using the "Write files/folders to disc" option. Getting an I/O Error! ScsiStatus: 0x02 Interpretation check condition. Here's one burn log that shows the "Invalid address for write" errors:
I 14:41:24 ImgBurn Version 2.5.8.0 started!
I 14:41:24 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200)
I 14:41:24 Total Physical Memory: 8,348,672 KiB - Available: 6,392,640 KiB
I 14:41:24 Initialising SPTI...
I 14:41:24 Searching for SCSI / ATAPI devices...
I 14:41:24 -> Drive 1 - Info: ATAPI iHAS124 E 4L0A (M:) (SATA)
I 14:41:24 Found 1 DVD±RW/RAM!
I 14:41:49 Operation Started!
I 14:41:49 Building Image Tree...
I 14:41:51 Checking Directory Depth...
I 14:41:51 Calculating Totals...
I 14:41:51 Preparing Image...
I 14:41:52 Checking Path Length...
I 14:41:52 Contents: 18 Files, 2 Folders
I 14:41:52 Content Type: DVD Video
I 14:41:52 Data Type: MODE1/2048
I 14:41:52 File System(s): ISO9660, UDF (1.02)
I 14:41:52 Volume Label: Slave Hunters Chuno Eps 1, 2, 3
I 14:41:52 IFO/BUP 32K Padding: Enabled
I 14:41:52 Region Code: 1, 2, 3, 4, 5, 6, 8
I 14:41:52 TV System: NTSC
I 14:41:52 Size: 3,781,277,696 bytes
I 14:41:52 Sectors: 1,846,327
I 14:41:52 Image Size: 3,781,885,952 bytes
I 14:41:52 Image Sectors: 1,846,624
I 14:41:54 Operation Successfully Completed! - Duration: 00:00:04
I 14:41:54 Operation Started!
I 14:41:54 Source File: -==/\/[bUILD IMAGE]\/\==-
I 14:41:54 Source File Sectors: 1,846,624 (MODE1/2048)
I 14:41:54 Source File Size: 3,781,885,952 bytes
I 14:41:54 Source File Volume Identifier: Slave Hunters Chuno Eps 1, 2, 3
I 14:41:54 Source File Volume Set Identifier: 46AF7538001C2D57
I 14:41:54 Source File Application Identifier: IMGBURN V2.5.8.0 - THE ULTIMATE IMAGE BURNER!
I 14:41:54 Source File Implementation Identifier: ImgBurn
I 14:41:54 Source File File System(s): ISO9660, UDF (1.02)
I 14:41:54 Destination Device: [0:0:0] ATAPI iHAS124 E 4L0A (M:) (SATA)
I 14:41:54 Destination Media Type: DVD-R (Disc ID: MCC 03RG20)
I 14:41:54 Destination Media Supported Write Speeds: 6x, 8x, 12x, 16x
I 14:41:54 Destination Media Sectors: 2,298,496
I 14:41:54 Write Mode: DVD
I 14:41:54 Write Type: DAO
I 14:41:54 Write Speed: 8x
I 14:41:54 Link Size: Auto
I 14:41:54 Lock Volume: Yes
I 14:41:54 Test Mode: Yes
I 14:41:54 OPC: No
I 14:41:54 BURN-Proof: Enabled
I 14:41:54 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x)
I 14:41:54 Advanced Settings - Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes
I 14:41:54 Filling Buffer... (80 MiB)
I 14:41:55 Writing LeadIn...
I 14:42:20 Writing Session 1 of 1... (1 Track, LBA: 0 - 1846623)
I 14:42:20 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 1846623)
W 14:45:52 Failed to Write Sectors 920480 - 920511 - Reason: Invalid Address For Write
W 14:45:52 Retrying (1 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (2 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (3 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (4 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (5 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (6 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (7 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (8 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (9 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (10 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (11 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (12 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (13 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (14 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (15 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (16 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (17 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (18 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (19 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
W 14:45:53 Retrying (20 of 20)...
W 14:45:53 Retry Failed - Reason: Invalid Address For Write
E 14:50:31 Failed to Write Sectors 920480 - 920511 - Reason: Invalid Address For Write
E 14:50:32 Next Writable Address: 0
I 14:50:32 Synchronising Cache...
W 14:50:45 User opted to skip the 'Close Track/Session/Disc' functions.
I 14:50:45 Cycling Tray after Test Write...
E 14:50:47 Failed to Write Image!
I 14:50:47 Exporting Graph Data...
I 14:50:47 Graph Data File: C:\Users\HarrietK\AppData\Roaming\ImgBurn\Graph Data Files\ATAPI_iHAS124_E_4L0A_FRIDAY-MAY-15-2015_2-41_PM_MCC_03RG20_8x.ibg
I 14:50:47 Export Successfully Completed!
E 14:50:47 Operation Failed! - Duration: 00:08:53
I 14:50:47 Average Write Rate: 3,749 KiB/s (2.8x) - Maximum Write Rate: 10,995 KiB/s (8.1x)
Source drive with the VIDEO_TS folder was either the C: spinner or a spinner in a USB3 docking station. Same error. Cannot be the media since the burn was in "Test" mode.
I also tried a known working Optiarc drive and it gets the same type of error.
Any ideas?
-
The real option is on the layer break selection window that pops up.
Thanks a lot for that info. Will look for it on my next DL burn.
Raptor
-
I see that the seamless option in ImgBurn is checked by default.
My impression is that it's not enabled by default.
I see now that the "seamless layer break" checkmark is in the GENERAL > DISPLAY WARNING section. I can't seem to find it elsewhere. Could you tell me what the path is to that option?
-
(Speeds: 4x, 6x, 8x, 10x)
You can't burn at 2.4x, your drive only sees the quoted speeds.
Try faster burning and cleaning the drive.
Well that makes perfect sense. I'll try to burn on 4x speed.
FWIW, my drive is the same as yours, a LG GH22NP20 running firmware 1.04, and it burned a DL Verbatim 2.4 DVD+R disc perfect. I did use the 2.4 burn speed setting and got the same "W 14:22:26 Write Speed Miscompare! - Wanted: 3,324 KB/s (2.4x), Got: 5,540 KB/s (4x)" entry in the ImgBurn log. I used the verify option and the disc verified with no errors and the disc plays back perfect.
Raptor
-
...snip... I used Verbatim but now I am using a PHILIPS Double Layer DVD +R which is around the same price of a Verbatim here and they say it's very clean - I bought it because I can't find Verbatim DVDs. ...snip...
Short of buying a new burner drive, maybe order some Verbatim 2.4 DVD +R discs from amazon. I ordered a 20 pack with free shipping since I couldn't find any locally and my first DL burn came out perfect.
Raptor
-
Most modern ones supports it. My cheap "non brands" also works and they are some years old. You'll never find in any manual that is shipped with a player if it supports the option or not.
Burn a DL disc with the option enabled and the layer break in the middle of a video titelset and take the disc to the shop and watch what's happens when it plays at the layer break.
I see that the seamless option in ImgBurn is checked by default. So the DL disc I just burned should have that option. I'll test the disc on my current DVD player (that always pauses at layer breaks) and then use that disc to test players in the store (if they will let me do it.) The problem of course is that stores normally have one player feeding all of their displays so they may not allow testing except to use the "buy, bring home, test, return" procedure.
BTW, question for anyone.
Is there a way to determine where the layer break is on commercial DVDs by examining the Video_TS file on the disc? I mean the original DVDs in my collection that I did not rip yet. Just nice to know info so no big deal.
Thanks for your help,
Raptor
-
Hi mmalves & Cynthia,
Thank you both for always helping us ImgBurn challanged folks.
Cynthia, I never knew about the seamless option. Is it hard to find out if that option exists for a stand alone player? Since I'm thinking about buying a new upconverting DVD player (not bluray), any recommendations for a brand/model?
Thanks,
Raptor
-
I successfully burned my first DL DVD on my first attempt using ImgBurn. Used Verbatim 2.4 DL disc per mmalves suggestion.
One question. During ImgBurn's setup process, it displayed four layer breaks all of which were "average". When I previewed all four, they were all in the same scene quite close together. So I just selected the first layer break on the list and crossed my fingers.
Is there a preferred way to choose which layer break to use? Like is the first or last break preferable to middle ones? Just want to learn the best way from the pros.
Thanks,
Raptor
-
I know what kind of drives I have on my systems but I'm writing a control program for ImgBurn that others can use. In the setup portion of my program I ask the user for their optical drive letters and to identify the types of optical drives they have but some novice users may not know that info. So far I came up with this procedure to use ImgBurn to help them out:
----------
1. Load ImgBurn.
2. Click "Write image file to disc".
3. In the Destination section, click the down arrow to the right of the text box.
4. All of your burner drives will be displayed. Write down the drive letters for each burner drive.
... The drive letters are in parenthesis at the end of the line. Example: D: or E: etc.
5. Now in the menu bar, click "Mode" and then "Read".
6. In the Source section, click the down arrow to the right of the text box.
7. All of the optical drives on your system will be displayed.
8. Write down all of the drive letters.
9. Any drive letters in step-8 that were not shown in step-4 are Read-Only drives.
(Note that ALL burner drives can read & burn discs, but Read-Only drives cannot burn discs.)
----------
This procedure gives the user the drive letters and whether the drive is a Read-Only or Burner Drive.
I'm not sure if the drive name will "ALWAYS" identify a drive as a CD-Only or a CD-DVD drive.
Is there an easier way to use ImgBurn to help the users identify their drives and drive letters?
Thanks,
Raptor
-
QUESTION:
If ImgBurn creates a .BIN file, will it "always" create a .CUE file too?
Yes, always.
Helpful info as usual. Thanks mmalves.
Raptor
-
1. The program makes a CUE (and therefore a BIN file rather than an ISO) if the CD disc is multitrack/session or contains Mode 2 sectors (rather than Mode 1).
The program makes a MDS file if the DVD/HD DVD/BD disc is double layer or < 1GB in size.
2. Yes.
3. Yes, there's a chance you won't get the LB in the right place.
Thanks for all that "good" info. The types of files ImgBurn creates during a read operation is more complicated than I originally thought.
BTW, for the clueless folks like me, I googled what "LB" means and I think it's an abbreviation for Layer Break.
By testing I know ImgBurn can create a .ISO file without creating a .MDS file.
QUESTION:
If ImgBurn creates a .BIN file, will it "always" create a .CUE file too?
Thanks,
Raptor
-
1. I'm trying to determine which file types ImgBurn will create when reading a CD or DVD disc to the HDD.
Just trying to cover the four most common types of discs that people want to copy. Is the list below correct?
DATA CD (has folders and files)--- .ISO only
AUDIO CD (playable in CD players)--- .BIN and .CUE
DATA DVD (has folders and files)--- .ISO and .MDS
MOVIE DVD (has Audio & Video_TS folders) --- .ISO and .MDS
2. Then to burn the files to a disc, should ImgBurn always be told to burn the .CUE and .MDS files if they exist rather than the associated .BIN or .ISO files?
3. Will there be any negative effects if I always select the .ISO file to burn even if an associated .MDS file exists?
.... (I believe I should always select the .CUE file to burn the .BIN file.)
Thanks,
Raptor
-
Now, is there a setting in ImgBurn to make it burn the last disc it read regardless of the name of the disc?
Nope.
I guess the only way around this issue is for me to add a new cli switch to just accept that it can't be named *.iso and then for you to check if the *.iso exists after a read operation, if it doesn't then use *.bin.
Of course if you load the iso/bin when an mds/cue should have been loaded it'll moan again
(Need a cli switch for that too I guess)
In that case I guess the only way around it for now is for my batch file to ask the user what kind of disc he/she is trying to copy.
I have a question on the kind of files generated for different types of discs which would be more helpful to others by starting another thread with the proper subject header. I'll start that thread now after I transmit this post.
Thanks a lot for your time!
Raptor
-
Read mode has its own setting for the destination path.
When set to 'automatic' it'll use the drive with the most free space - assuming the user has permission to write to it. If they don't then it'll go in their documents folder.
Hi Ligntning, thanks for your reply.
I went to TOOLS > SETTINGS > READ, clicked CUSTOM and set the path to C:\IBurnTmp. Now my batch file read command saves the files to that folder. Great!
Now, is there a setting in ImgBurn to make it burn the last disc it read regardless of the name of the disc?
IOW, remember the path to the last file(s) (.bin, .cue) it wrote on the HDD during the last read operation?
Thanks,
Raptor
-
Working on my copy disc batch file control program. My problem is how to determine which file to burn. Let me explain.
If I use a specific destination path in my read command to ImgBurn like this:
"C:\Program Files\ImgBurn\ImgBurn" /mode read /src %InputDrive%: /dest "C:\IBurnTmp\ImgBurnTemp.iso" /overwrite yes /eject %EjectDisc% /close /start
It works fine if I'm trying to copy a DVD. But if I try to copy an audio CD, ImgBurn pops up a message saying that I made a booboo and it will write to a .bin file. It does that OK but the user has to answer the pop up message before the read process can continue. I don't want that.
So I delete the destination in my read command as follows:
"C:\Program Files\ImgBurn\ImgBurn" /mode read /src %InputDrive%: /overwrite yes /eject %EjectDisc% /close /start
Now ImgBurn writes the proper files to the HDD. But it writes it to E:\DiscLabel.bin. Why it writes the file to the root directory of E: I have no clue since in TOOLS > SETTINGS > FILE LOCATIONS, every entry is using the C: drive. Why is it writing the file to the E: root directory?
I'm afraid that other users on different computers will have the file written to different hard drives so how can I find the proper file to burn it automatically?
WHAT I'VE TRIED:
After searching this forum, I found a post where Lightning suggested to check the "Add to write queue when done". So I checked that in ImgBurn but when I try to do the read and write operation manually (not from a batch file), ImgBurn still doesn't know where the file for the last read operation is stored. How do other users using ImgBurn manually (not from a batch file) know where the file was written to the HDD so they can select it during the burn operation?
Any suggestions on how I can write my batch file so it will write the file from a data cd, audio cd, data dvd or movie dvd on the HDD and then let my batch file find the files and burn them on the disc all automatically without any user intervention?
Thanks,
Raptor
-
Indeed, copying an Audio CD is no different to copying any other type of disc.
It's just Read mode and then Write mode.
If your burnt disc came out blank then you probably had 'Test Mode' (which tells the drive not to turn the laser on) enabled - and that's your fault I'm afraid!
Hi Lightning,
I don't know why but I did the exact same burn procedure today and this time the same CD that I used before did burn & verify OK. I had not set 'Test Mode' in my previous try yesterday but the CD did not burn. It was as if the test mode flag in the software was somehow set by a ghost.
I had not used ImgBurn since my last failed burn attempt yesterday. When I opened ImgBurn today, 'Test Mode' was unchecked. Wouldn't that confirm that 'Test Mode' was not set yesterday when the burn completed successfully but the CD ended up being blank? (The burn attempt yesterday was without verify checked since I was in a rush to leave the house and wanted to play the CD in the car while driving).
Although all of the functions are in ImgBurn to make a backup copy of an audio CD, I still think it would be a good thing to post as a sticky guide to save other newbies hours of Google searching for a step-by-step procedure like I did and was still unsuccessful in finding one. For instance I thought that the file on the HDD would be an .ISO and had to learn that the files created were actually a .BIN and a .CUE. But of course it's your program and your call. I'll respect your decision either way since you're making ImgBurn free for us to use so in no way should anyone complain!!!
Raptor
-
Thought I'd share a first impression of using ImgBurn to make a backup copy of an audio CD.
Bear in mind that I've not fully researched this yet and this is just a first impression as a FYI.
I wanted to make a backup copy of an audio CD (not mp3) to use in our car. I only made one attempt and found it's not so easy using ImgBurn.
First it said I was trying to create an ISO file but shouldn't and ImgBurn would create the proper files for me "this time".
I have not found how to create it properly yet so ImgBurn doesn't have to do it for me "this time".
Then I found that the ImgBurnTemp.bin file was 634,691 KB in size so it does contain data. I selected the CUE file and burned a CD. Got a successfully completed but the CD wouldn't play and it looks to be still blank.
I just spent about 3 hours googling and have not found a step-by-step procedure on how to use ImgBurn to copy an audio CD.
I searched Cynthia's how to use ImgBurn but did not find what I needed.
I just found this thread and it appears that making a backup copy of an audio CD is not that easy.
Believe me, I'm not complaining. My main reason for using ImgBurn is to burn DVDs (with verify!) and it's done that superbly so far.
Just thought a new user's experience might be helpful. If might be a good thing to post a step-by-step procedure to make backup copies of audio CDs to make it easier for newbies.
Raptor
-
I must not be coding the ImgBurn command line properly.
Nope, you are, it just doesn't work.
I do no testing at all on CLI stuff, I leave that to the people that want to use it - i.e. people like you.
I'll fix it for 2.5.1.0
Hi Lightning,
Thanks a lot! I'm really glad that you even made the CLI available for our use! Thanks for that too.
Best regards,
Raptor
Invalid address for write
in ImgBurn Support
Posted · Edited by Raptor88
The problem appears to be solved.
Actually prior to posting here, I noticed a high amount of TCP Connections so was wondering if an infection was causing secret internet connections. Or if it wasn't the TCP Connections, maybe a different infection was causing the problem. I was thinking about using the Windows "Startup" to disable all of the startup programs or to use Safe mode to do the same + the minimal driver loads. If it was an infection, then using "Startup" to disable start up programs might not have stopped the problem from happening. Using Safemode seemed like a more sure way but I was wondering if even that would stop any infection from doing its thing.
Luckily Safe mode did appear to stop the problem from happening. (Intermittent problem so couldn't say for sure.) A restore of an earlier backup did not resolve the problem so I restored a backup that was done when I first setup the PC for my friend. Since doing that restore, the problem has not happened. Will see how it goes in actual use but the problem appears to have been resolved.
Thanks for the help,
Raptor88