nero is eating my ram?

[joe113]

Hi, bit of a problem. I posted it on another thread about something else. I've waited a week or so but no reply's. As of late, almost every burn I do, my available ram out of 703mb goes right down to like 4mb. This happens within the first minute of burning. It seems to happen no matter what size the amount of data is being written, wheter (not sure of spelling) it's 350 mb avi file or 4.35 gb dvd backup. I use nero burning rom to burn backups and nero make a data disc for avi files. When the ram drops down to the 4mb mark or so, the led light on the front of my burner goes orange, the buffer completly empties out, the hard disc light on my pc stays constantly on, reading or writing what I don't know. The buffer slowly climbs back up, after a minute or so it is full, then the burner(lite-on LDW851S), goes back to full burning mode. Now, I'm not sure how long it takes again, it seems to vary, but it's not long that the whole process starts again. My burns are coming out ok but it is making the burning time take twice as long. Maybe if somebody had some similar experiences they could possibly help me out? By the way, before I start a burn available ram on my pc if left idle is normally between 350 - 450 mb. After I close off nero it goes up to almost 600mb, I don't know if this is relevant.


Thanks in advance for any possible solutions, its not that important as my burns are turning out ok, but I'd still like to know what the craic is with it.

Joe.

[LT. Columbo]

first, see if your DMA is on

http://forum.digital-digest.com/showthread.php?s=&threadid=44808

right click any open apps next to the clock that may be running and exit them to free up more ram. could you also post a burn log from nero?

c/programfiles/ahead/nero/nerohistory.log

[Chewy]

I just started a 16x burn with nero,
my 512 megs are constant(300 free) buffer stays full
nero using 94megs(constant)
like lt says post nero log

[joe113]

ok, here is the log when I burned 2.1 gb of data to a dvdrw disc at 4x.

Windows XP 5.1
IA32
WinAspi: File 'Wnaspi32.dll': Ver=4.71 (0002), size=45056 bytes, created 16/07/2004 09:24:34
ahead WinASPI: File 'C:\Program Files\Ahead\nero\Wnaspi32.dll': Ver=2.0.1.74, size=164112 bytes, created 26/10/2004 18:35:34
Nero Version: 6.6.0.16
Internal Version: 6, 6, 0, 16b
(Nero Express)
Recorder: <LITE-ON DVDRW LDW-851S> Version: GS0P - HA 2 TA 0 - 6.6.0.16
Adapter driver: <> HA 2
Drive buffer : 2048kB
Bus Type : default (0) -> ATAPI, detected: ?
CD-ROM: <TOSHIBA DVD-ROM SD-M1612>Version: 1806 - HA 1 TA 0 - 6.6.0.16
Adapter driver: <atapi> HA 1

=== Scsi-Device-Map ===
DiskPeripheral : Maxtor 4D040H2 atapi Port 0 ID 0 DMA: On
CdRomPeripheral : TOSHIBA DVD-ROM SD-M1612 atapi Port 1 ID 0 DMA: On
CdRomPeripheral : SAMSUNG CD-R/RW SW-224B atapi Port 1 ID 1 DMA: On

=== CDRom-Device-Map ===
TOSHIBA DVD-ROM SD-M1612 D: CDRom0
SAMSUNG CD-R/RW SW-224B E: CDRom1
LITE-ON DVDRW LDW-851S F: CDRom2
=======================

AutoRun : 1
Excluded drive IDs:
WriteBufferSize: 83886080 (0) Byte
ShowDrvBufStat : 0
BUFE : 0
Physical memory : 703MB (720368kB)
Free physical memory: 449MB (460136kB)
Memory in use : 36
Uncached PFiles: 0x0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Disabled (0)

14.10.2005
ISO compilation
19:20:36 #1 Text 0 File Isodoc.cpp, Line 6356
Iso document burn settings
------------------------------------------
Determine maximum speed : FALSE
Simulate : FALSE
Write : TRUE
Finalize CD : FALSE
Multisession : TRUE
Multisession type: : Continue multisession
Burning mode : DAO
Mode : 1
ISO Level : 1 (Max. of 11 = 8 + 3 char)
Character set : ISO 9660
Joliet : TRUE
Allow pathdepth more than 8 directories : TRUE
Allow more than 255 characters in path : TRUE
Write ISO9660 ;1 file extensions : TRUE

19:20:36 #2 Text 0 File Reader.cpp, Line 127
Reader running

19:20:36 #3 Text 0 File Writer.cpp, Line 122
Writer LITE-ON DVDRW LDW-851S running

19:20:36 #4 ISO9660GEN -11 File geniso.cpp, Line 3309
First writeable address = 0 (0x00000000)

19:20:36 #5 Text 0 File Burncd.cpp, Line 3233
Turn on Disc-At-Once, using DVD media

19:20:37 #6 Text 0 File DlgWaitCD.cpp, Line 270
Last possible write address on media: 2295103 (510:01.28, 4482MB)
Last address to be written: 1530643 (340:08.43, 2989MB)

19:20:37 #7 Text 0 File DlgWaitCD.cpp, Line 282
Write in overburning mode: NO (enabled: CD)

19:20:37 #8 Text 0 File DlgWaitCD.cpp, Line 2483
Recorder: LITE-ON DVDRW LDW-851S, Media type: DVD+RW
Disc Manufacturer ID: INFODISC, Media Type ID: A10, Product revision number: 1
Disc Application Code: 0, Extended Information Indicators: 1

19:20:37 #9 Text 0 File DlgWaitCD.cpp, Line 448
>>> Protocol of DlgWaitCD activities: <<<
=========================================

19:20:37 #10 Text 0 File ThreadedTransferInterface.cpp, Line 838
Setup items (after recorder preparation)
0: TRM_DATA_MODE1 ()
2 indices, index0 (150) not provided
original disc pos #0 + 1162336 (1162336) = #1162336/258:17.61
relocatable, disc pos for caching/writing not required/ required, no patch infos
-> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 1162336 blocks [LITE-ON DVDRW LDW-851S]
1: TRM_DATA_MODE1 ()
2 indices, index0 (0) not provided
original disc pos #15 + 4 (4) = #19/0:0.19
relocatable, disc pos for caching/writing not required/not required, no patch infos
-> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 4 blocks [LITE-ON DVDRW LDW-851S]
--------------------------------------------------------------

19:20:37 #11 Text 0 File ThreadedTransferInterface.cpp, Line 1051
Prepare recorder [LITE-ON DVDRW LDW-851S] for write in CUE-sheet-DAO
DAO infos:
==========
MCN: ""
TOCType: 0x00; Session Closed, disc not fixated
Tracks 1 to 2:
1: TRM_DATA_MODE1, 2048/0x00, FilePos 0 0 2380464128, ISRC ""
2: TRM_DATA_MODE1, 2048/0x00, FilePos 2380464128 2380464128 2380472320, ISRC ""
DAO layout:
===========
__Start_|____Track_|_Idx_|_CtrlAdr_|_RecDep_______ ___
368304 | lead-in | 0 | 0x41 | 0x00
368304 | 1 | 0 | 0x41 | 0x00
368304 | 1 | 1 | 0x41 | 0x00
1530640 | 2 | 0 | 0x41 | 0x00
1530640 | 2 | 1 | 0x41 | 0x00
1530644 | lead-out | 1 | 0x41 | 0x00

19:20:39 #12 Phase 24 File dlgbrnst.cpp, Line 1832
Caching of files started

19:20:40 #13 Text 0 File Burncd.cpp, Line 4120
Cache writing successful.

19:20:40 #14 Phase 25 File dlgbrnst.cpp, Line 1832
Caching of files completed

19:20:40 #15 Phase 36 File dlgbrnst.cpp, Line 1832
Burn process started at 4x (5,540 KB/s)

19:20:40 #16 Text 0 File ThreadedTransferInterface.cpp, Line 2654
Verifying disc position of item 0 (relocatable, disc pos, no patch infos, orig at #0): write at #368304

19:20:40 #17 Text 0 File ThreadedTransferInterface.cpp, Line 2654
Verifying disc position of item 1 (relocatable, no disc pos, no patch infos, orig at #15): write at #15

19:20:40 #18 Text 0 File Cdrdrv.cpp, Line 8862
---- DVD Structure: Physical Format Information (00h) ----
Layer: 0, Address: 0 (0 h), AGID: 0; Length: 2050
Book Type: DVD+RW (9), Part Version: 1.1x (2)
Disc Size: 120 mm, Maximum Rate: <not specified> (F h)
Number of Layers: 1, Track Path: Parallel Track Path (PTP), Layer Type: re-writable
Linear Density: 0,267 um/bit, Track Density: 0,74 um/track
Starting Physical Sector Number of Data Area: 30000 h (DVD-ROM, DVD-R/-RW, DVD+R/+RW)
End Physical Sector Number of Data Area: 1F850F h
End Sector Number in Layer 0: 0 h (LBN: FFFD0000 h, 4193920 MB)
Data in Burst Cutting Area (BCA) does not exist
Disc Application Code: 0 / 0 h
Extended Information indicators: 1 h
Disc Manufacturer ID: INFODISC
Media type ID: A10
Product revision number: 1
Number of Physical format information bytes in use in ADIP up to byte 63: 57
Media Specific [16..63]:
00 00 01 49 4E 46 4F 44 - 49 53 43 41 31 30 01 39 ...INFODISCA10.9
23 00 9C 7C 5C 02 28 00 - 96 7E 70 02 28 00 9C 7B #..|\.(..~p.(..{
68 02 28 04 04 20 E0 00 - F0 00 00 00 00 00 00 00 h.(.............

19:20:40 #19 Text 0 File DVDPlusRW.cpp, Line 665
Start write address at LBA 368304
DVD high compatibility mode: Yes

19:29:45 #20 Text 0 File ThreadedTransfer.cpp, Line 228
all writers idle, stopping conversion

19:29:49 #21 Text 0 File WriterStatus.cpp, Line 116
<LITE-ON DVDRW LDW-851S > start writing Lead-Out at LBA 368308 (59EB4h), lenght 0 blocks

19:29:51 #22 Text 0 File ThreadedTransfer.cpp, Line 228
all writers idle, stopping conversion

19:29:53 #23 Phase 37 File dlgbrnst.cpp, Line 1832
Burn process completed successfully at 4x (5,540 KB/s)

19:29:56 #24 Phase 78 File dlgbrnst.cpp, Line 1832
Data verification started

19:30:00 #25 Text 0 File ThreadedTransferInterface.cpp, Line 1119
Removed 16 run-out blocks from end of track 1. Length: 1162336 -> 1162320.

19:37:29 #26 Text 0 File ThreadedTransfer.cpp, Line 228
all writers idle, stopping conversion

19:37:29 #27 Text 0 File ThreadedTransfer.cpp, Line 228
all writers idle, stopping conversion

19:37:29 #28 Phase 80 File dlgbrnst.cpp, Line 1832
Data verification completed successfully


Existing drivers:
File 'Drivers\ASPI32.SYS': Ver=4.71 (0002) built by: WinDDK, size=16512 bytes, created 16/07/2004 09:24:34
File 'WNASPINT.DLL': Ver=5, 1, 0, 16, size=69632 bytes, created 30/01/2002 02:00:00
File 'Drivers\PXHELP20.SYS': Ver=2.03.28a, size=20640 bytes, created 11/03/2005 23:28:13 (Prassi/Veritas driver for win 2K)
File 'Drivers\atapi.sys': Ver=5.1.2600.2180 (xpsp_sp2_rtm.040803-2158), size=95360 bytes, created 04/08/2004 06:59:42 (Adapter driver for src)

Registry Keys:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)

====== *** Nero-Burning Rom, History File *** ======


Cheres

[joe113]

oops, judging by the date on that, irs the wrong file.

I'll try find the relevant one.

[joe113]

Or maybe its the right one, with just a bit of another one at the top?

Joe.

[joe113]

Just another reason to defrag your drive. After defragging, problem disappeared. Thanks for trying.

[anonymez]

odd solution, but glad it all worked out

[LT. Columbo]

some say defragmenting can correct this, even my owners manual for my writer says it's a possibility, others say it's a bunch of malarky. well proof is in the pudding i guess. the one time this sort of thing happened to me, it was that it reverted to PIO mode....(buffer underruns like a sunnuvagun). i tried defragmenting as per the book, which did nothing.

[nwg]

Defragging can be the solution to this sort of thing. If it isn't done then, there is too much fragmentation and the computer has to spend more time searching for the right data and use the RAM. A file if big enough can be split into different
positions around the hard disk. Defraggings sort this out to a minimum.

I try to defrag every couple of weeks. It depends on how full the disk is as it only works when at least 15% of space is left. I should really do it now but the hard disk is filled up.

[LT. Columbo]

that reminds me...5 months and counting, but i want to do it when i delete a bunch of projects, i've only got about 10% free space right now....

[joe113]

first, see if your DMA is on

http://forum.digital-digest.com/showthread.php?s=&threadid=44808

As mine is an external usb2 burner, I don't think dma is relevant, or is it?

Cheers.

[Taelon]

As mine is an external usb2 burner, I don't think dma is relevant, or is it?

Right, the DMA settings won't have any effect on the USB interface.

File 'WNASPINT.DLL': Ver=5, 1, 0, 16, size=69632 bytes, created 30/01/2002 02:00:00

This driver file is probably unnecessary, if it's in \WINDOWS\system32, I'd rename it to WNASPINT.BAK. Don't delete the file since there are a few burning programs that may need it including Acoustica MP3 Burner, CDRWin, Microstudio, and Musicmatch jukebox. But they should use the standard ASPI layer, or at least have their own copy in their folder. I think most programs will only install wnaspint.dll if a working ASPI layer wasn't found when the program is installed. There are instructions on how to locate the file and check it's version here.

[joe113]

Cheers bud. What effect, if any, will renaming this file have on my system?

[Taelon]

Renaming it eliminates a potential conflict when communicating to the optical drives. The full ASPI layer is more robust, and if you're burning with nero it installs it's own layer on top of that. You've also got PXHELP20.SYS installed which is part of Sonic's burning layer. The fewer things fighting for control of the SCSI bus the better IMO.