not enough memory

Can anyone help,
I've had this problem come up before as regards burning, there was not enough phsical memory then so i bought another memory stick, so i've now got 256mb,that was only last week,and when i put the new memory stick in it was burning ok.

But now i think i've got the same problem as it shows below, can anyone sugest what is best and is there a way to get rid of some of the memory that i'm using, but i can't uderstand why it is ok one minute than in a matter of day's it's back to normal. Thanks

Windows XP 5.1
IA32
WinAspi: -
ahead WinASPI: File 'C:\Program Files\Ahead\Nero\Wnaspi32.dll': Ver=2.0.1.74, size=164112 bytes, created 26/10/2004 17:35:34
Nero API version: 6.6.0.18
Using interface version: 6.3.1.4
Installed in: C:\Program Files\Ahead\Nero\
Application: ahead\Nero - Burning Rom
Internal Version: 6, 6, 0, 18e

Recorder: <LITE-ON DVDRW SHM-165P6S>Version: MS0M - HA 1 TA 1 - 6.6.0.18
Adapter driver: <atapi> HA 1
Drive buffer : 2048kB
Bus Type : default (0) -> ATAPI, detected: ATAPI

=== Scsi-Device-Map ===
DiskPeripheral : ST320413A atapi Port 0 ID 0 DMA: On
CdRomPeripheral : LITE-ON DVDRW SHM-165P6S atapi Port 1 ID 1 DMA: On

=== CDRom-Device-Map ===
LITE-ON DVDRW SHM-165P6S D: CDRom0
=======================

AutoRun : 1
Excluded drive IDs:
WriteBufferSize: 40894464 (0) Byte
ShowDrvBufStat : 0
BUFE : 0
Physical memory : 255MB (261620kB)
Free physical memory: 24MB (25512kB)
Memory in use : 90 %
Uncached PFiles: 0x0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Disabled (0)

16.1.2007
NeroAPI
22:47:11 #1 Phase 112 File APIProgress.cpp, Line 276
DVD-Video files reallocation started

22:47:11 #2 Phase 114 File APIProgress.cpp, Line 276
DVD-Video files reallocation completed (no file modified)

22:47:11 #3 Phase 111 File APIProgress.cpp, Line 276
DVD-Video files sorted

22:47:12 #4 Text 0 File Reader.cpp, Line 127
Reader running

22:47:12 #5 Text 0 File AudioCompilationImpl.cpp, Line 842
DRM: StartDrmRecording(RealRec:1, ImageRec:0, Copies:1)
DRM: Beginning burn process.

22:47:12 #6 Text 0 File Writer.cpp, Line 122
Writer LITE-ON DVDRW SHM-165P6S running

22:47:12 #7 ISO9660GEN -11 File geniso.cpp, Line 3309
First writeable address = 0 (0x00000000)

22:47:12 #8 ISO9660GEN -11 File geniso.cpp, Line 3309
First writeable address = 0 (0x00000000)

22:47:12 #9 Text 0 File Burncd.cpp, Line 3233
Turn on Disc-At-Once, using DVD media

22:47:12 #10 Text 0 File DlgWaitCD.cpp, Line 270
Last possible write address on media: 2297887 (510:38.37, 4488MB)
Last address to be written: 579759 (128:50.09, 1132MB)

22:47:12 #11 Text 0 File DlgWaitCD.cpp, Line 282
Write in overburning mode: NO

22:47:12 #12 Text 0 File DlgWaitCD.cpp, Line 2483
Recorder: LITE-ON DVDRW SHM-165P6S, Media type: DVD-RW
Disc Manufacturer: RITEKW - 01
Disc Application Code: 64, Disc Physical Code: 214

22:47:12 #13 Text 0 File DlgWaitCD.cpp, Line 448
>>> Protocol of DlgWaitCD activities: <<<
=========================================

22:47:12 #14 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 + 579760 (579760) = #579760/128:50.10
relocatable, disc pos for caching/writing not required/ required, no patch infos
-> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 579760 blocks [LITE-ON DVDRW SHM-165P6S]
--------------------------------------------------------------

22:47:12 #15 Text 0 File ThreadedTransferInterface.cpp, Line 1051
Prepare recorder [LITE-ON DVDRW SHM-165P6S] for write in CUE-sheet-DAO
DAO infos:
==========
MCN: ""
TOCType: 0x00; Session Closed, disc fixated
Tracks 1 to 1:
1: TRM_DATA_MODE1, 2048/0x00, FilePos 0 0 1187348480, ISRC ""
DAO layout:
===========
__Start_|____Track_|_Idx_|_CtrlAdr_|_RecDep__________
0 | lead-in | 0 | 0x41 | 0x00
0 | 1 | 0 | 0x41 | 0x00
0 | 1 | 1 | 0x41 | 0x00
579760 | lead-out | 1 | 0x41 | 0x00

22:47:12 #16 Phase 24 File APIProgress.cpp, Line 276
Caching of files started

22:47:12 #17 Text 0 File Burncd.cpp, Line 4122
Cache writing successful.

22:47:12 #18 Phase 25 File APIProgress.cpp, Line 276
Caching of files completed

22:47:13 #19 Phase 36 File APIProgress.cpp, Line 276
Burn process started at 2x (2,770 KB/s)

22:47:13 #20 Text 0 File ThreadedTransferInterface.cpp, Line 2661
Verifying disc position of item 0 (relocatable, disc pos, no patch infos, orig at #0): write at #0

22:47:13 #21 Text 0 File DVDR.cpp, Line 2571
Recording mode: Sequential Recording Mode

22:47:13 #22 Text 0 File Mmc.cpp, Line 21774
Set BUFE: Buffer underrun protection -> ON , SMART-BURN : ON

22:47:13 #23 Text 0 File DVDR.cpp, Line 2726
Start write address at LBA 0
DVD high compatibility mode: Yes

22:47:13 #24 Text 0 File Cdrdrv.cpp, Line 8892
---- DVD Structure: Physical Format Information (00h) ----
Layer: 0, Address: 0 (0 h), AGID: 0; Length: 2050
Book Type: DVD-RW (3), 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: recordable
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: BD8AF h
End Sector Number in Layer 0: 0 h (LBN: FFFD0000 h, 4193920 MB)
Data in Burst Cutting Area (BCA) exist
Start sector number of the current Border-Out: 0 h
Start sector number of the next Border-In: 0 h
Media Specific [16..63]:
80 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................

22:47:58 #25 Text 0 File Cdrdrv.cpp, Line 1288
22:47:58.327 - LITE-ON DVDRW SHM-165P6S\H1 T1 : Queue again later

23:00:04 #26 SCSI -1135 File Cdrdrv.cpp, Line 1436
SCSI Exec, HA 1, TA 1, LUN 0, buffer 0x00BE0000
Status: 0x04 (0x01, SCSI_ERR)
HA-Status 0x00 (0x00, OK)
TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
Sense Key: 0x03 (KEY_MEDIUM_ERROR)
Sense Code: 0x0C
Sense Qual: 0x00
CDB Data: 0x2A 0x00 0x00 0x04 0xE5 0x00 0x00 0x00 0x20 0x00 0x00 0x00
Sense Data: 0x71 0x00 0x03 0x00 0x00 0x00 0x00 0x0A
0x00 0x00 0x00 0x00 0x0C 0x00

23:00:04 #27 CDR -1135 File Writer.cpp, Line 311
Write error

23:00:04 #28 Text 0 File ThreadedTransfer.cpp, Line 228
all writers idle, stopping conversion

23:00:04 #29 Text 0 File ThreadedTransfer.cpp, Line 222
conversion idle, stopping reader

23:00:04 #30 Text 0 File DVDR.cpp, Line 2969
EndDAO: Last written address was 320767

23:00:16 #31 Phase 181 File APIProgress.cpp, Line 276
Writing lead-out...

23:00:16 #32 Text 0 File DVDR.cpp, Line 3002
Estimated time for 30mm Borders: 2min 53sec

23:00:16 #33 Phase 38 File APIProgress.cpp, Line 276
Burn process failed at 2x (2,770 KB/s)

23:00:16 #34 Text 0 File AudioCompilationImpl.cpp, Line 867
DRM: DRM burn session terminated.

23:00:16 #35 Text 0 File AudioCompilationImpl.cpp, Line 896
DRM: Closing entire DRM handling. Bye.


Existing drivers:
File 'Drivers\PXHELP20.SYS': Ver=2.03.32a, size=20640 bytes, created 27/07/2006 17:28:33 (Prassi/Veritas driver for win 2K)

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

This should be in the Hardware section really.

Your problem is you're running XP on 256mb of RAM, you need at least 512mb if you want to run other progs, especially burning software.
If you can't put more memory in then open Task Manager and close all the progs you can, like a/v and firewall, then try burning.

ps, your system specs would help us as well. ;)

More RAM for sure. 256mb.. is mince.

I agree that the shortage of ram may be the cause, if you've just increased it to 256MB, what was it before? I can probably answer my own question, I suspect that it had 256MB physically but some was used for the graphics chip.

It is actually impossible to install XP without 256MB of available memory, but the mass manufacturers get round it by installing on a machine with more memory, then cloning the installation. Once this was been pointed out, most then offered double memory upgrades to avoid being sued, and marketed it as a "free" special deal.

Having said all that, look at log entry #26, 23:00:04. You will see
Sense Key: 0x03 (KEY_MEDIUM_ERROR)
which actually indicates faulty media. You haven't actually said what brand of disks you are using, the only thing we can get from the log is that the media code is RITEKW-01. Brands using that media code have pretty mixed reviews.

Look here to find your brand. If it is one of the brands with mixed reliability that could also be your problem.

Would it be a good idea to do a memory optimizer to see if i'm leaking any memory somewhere.

I think you would be wasting your time.

Face the simple facts -

your drive is faulty
- or -
you've got a bad batch of media
- or -
you haven't got enough memory.

Memory optimizers aren't going to help, you simply haven't got enough of the stuff, but that may not be the cause in this particular instance.

Thanks everyone,i've just incresed my memory to 640mb, and was able to burn a film without any problem.

So thanks again.:D

I've seen XP Pro fully installed and running in 128MB on a Celeron 433 and although I wouldn't try running any games on it, the stock control program, Word, Excel and various EPCs (parts catalogues) ran together without issue... just not very fast LOL
Minimum specs for XP were originally 64MB!
Mind you, that was then and this is now.

I gave a guy back his 256MB (less 64MB shared GFX) P4 2.5 Packard Bell(ocks) back yesterday after taking off all the shit (Limewire/MWS/MSB/N2S/WinMX/Kazaa3/McAfee/lotsa malware) and leaving him with p2p filesharing, antivirus, firewall, antispy, CDwriting etc etc.
It got to the desktop in 30 seconds and would have been much quicker if he didn't have AOL.
:)

Anyway, I think this particular problem is likely to be media related.

chewie,tahnks for all the help buti've seem to come back to the same problem,as to my las reply things was going ok, but than i had a trojan horse so i think i manage to get rid of that as my avg scan has not picked it up in reason scans nor has my anti-spyware.But is there a chance that a trojan can get into you're memory?i'm getting error message again,can you tell me if i'm low on memory again from my log below.The only thing i'm getting now is popups when i'm on the net.Thanks.
Attachment 2641

Looks to me as though your PC is just plain infected, which would certainly account for the low memory condition.

Wipe and reload, FTW.

Clocker, thanks for replying to my post,can you recomend the best way to get rid ofthe virus that is infected my pc?
And why is my antivirus or anti-spyware not picking this trojan up.
I've turned off my system restore and scan after that and restarted my pc, so i'm not sure what else i can do.

Quote:

---

Originally Posted by clocker

Looks to me as though your PC is just plain infected, which would certainly account for the low memory condition.

Wipe and reload, FTW.

---

Wipe & reload might be best.

But you might try these 2 1st.

http://www.kaspersky.com/kos/english/kavwebscan.html

&

Install & run the free version of this.
http://www.emsisoft.com/en/software/free/

It is most probably not due to not enough memory. My laptop can run on 256 MB,albeit slowly. Most probably it is a virus. Is your CPU usage high,even though you are doing nothing on it ?

yeh not enought memory