Memory Corrupts on Re-start of 5500

I have a Nokia 5500 that came with firmware v3.14 and I upgraded last week to v3.55 using the Nokia Software Updater successfully. But since then I have been having a problem with my memory card. Everytime I switch off and on the phone and try to access the memory card, it says that the memory card is corrupted. After a format it works till the next re-start.
I tried formatting the phone and also doing a full format using windows but even now whenever I restart the phone the memory card gets corrupted. I wonder if this is a problem with the new firmware.
Has anyone faced such a problem and can anyone guide me on how to rectify this problem. Would it help if I somehow revert back to the older firmware? If yes, then how do I reinstall the older firmware version?
Thanks in Advance,
Prashanth

Sad to say, I have a similar and recurrent problem with my E61. Out of nowhere, it will report "Memory Card Corrupted," and the only "solution" it offers is to Format the card. Brilliant. I've accepted that option twice now, and have also done reformats in my PC Card reader in both FAT and FAT32. No difference. The E61, when so inclined, reports the "Memory Card Corrupted" and I'm back to square one. A REAL annoyance as I have serious applications (e.g., TomTom Navigator on my card). Nokia has been quite unhelpful with my previous queries about SD cards. The essence of what they told me was that if it's not a NOKIA brand card, then they won't do anything. But, the bigger question is: what CAN they do? There's NO reason to think this is a card-specific issues. It's much more likely that it's a NOKIA phone defect. Having a Nokia-branded SD card would mean only that I had the dubious satisfaction of getting the same message with a "supported" card. Not exactly a motivation to buy an over-priced Nokia brand card.

Similar Messages

  • MacBook won't start after latest OS update ("Possible memory corruption")

    I am running a late 2009 MacBook, 250GB, 4GB ram. I have just updated the OS (standard, regular update), iTunes and an older iMovie update. I made the necessary restart, and begun using iTunes. After 5 minutes, it crashed, and when turned back on, the startup apple logo screen was filled with command prompt code. The only thing I can do, is to force it to shutdown. At the top of the command prompt text, it now says "possible memory corruption".
    Latest update: I am now met with a black screen every time I turn on - the "sleep" light is on, but that appears to be all that's happening.
    Help!

    Do you have any 3rd party memory modules installed?  What system did you upgrade from? What MacBook module do you have, i.e.
    Check the memory modulds to make sure they are securly seated and try again. If you have 3rd party modules installed remove them and leave just the original Apple modules and try a restart.
    OT

  • Eterm crashes - malloc(): memory corruption (fast): 0x08080318

    Lately Eterm started to just "disappear" from the screen. I checked the ~/.xsessionerrors and the last messages are:
    *** glibc detected *** Eterm: malloc(): memory corruption (fast): 0x08080318 ***
    ======= Backtrace: =========
    /lib/libc.so.6[0xb7ac9c06]
    /lib/libc.so.6[0xb7acc35d]
    /lib/libc.so.6(__libc_malloc+0x97)[0xb7acd467]
    /usr/lib/libX11.so.6(_XReply+0x8f)[0xb7c00a2f]
    /usr/lib/libX11.so.6(XSync+0x6a)[0xb7bf4d3a]
    /usr/lib/libEterm-0.9.4.so(scr_refresh+0x1aa7)[0xb7eda4d7]
    /usr/lib/libEterm-0.9.4.so(scr_rvideo_mode+0xcc)[0xb7edbb4c]
    /usr/lib/libEterm-0.9.4.so(scr_bell+0x6d)[0xb7edbcdd]
    /usr/lib/libEterm-0.9.4.so(main_loop+0x417)[0xb7ea8307]
    /usr/lib/libEterm-0.9.4.so(eterm_bootstrap+0x8ee)[0xb7ee85be]
    Eterm[0x8048522]
    /lib/libc.so.6(__libc_start_main+0xe0)[0xb7a79f90]
    Eterm[0x8048471]
    ======= Memory map: ========
    08048000-08049000 r-xp 00000000 08:01 1081392 /usr/bin/Eterm
    08049000-0804a000 rw-p 00000000 08:01 1081392 /usr/bin/Eterm
    0804a000-080c7000 rw-p 0804a000 00:00 0 [heap]
    b7600000-b7621000 rw-p b7600000 00:00 0
    b7621000-b7700000 ---p b7621000 00:00 0
    b77cd000-b77d5000 r-xp 00000000 08:01 34197 /lib/libnss_files-2.6.1.so
    b77d5000-b77d7000 rw-p 00007000 08:01 34197 /lib/libnss_files-2.6.1.so
    b77ec000-b77f6000 r-xp 00000000 08:01 1077345 /usr/lib/libgcc_s.so.1
    b77f6000-b77f7000 rw-p 00009000 08:01 1077345 /usr/lib/libgcc_s.so.1
    b77f7000-b78b8000 r--s 00000000 00:08 54165514 /SYSV00000000 (deleted)
    b78b8000-b78c7000 r-xp 00000000 08:01 364494 /lib/libbz2.so.1.0.4
    b78c7000-b78c8000 rw-p 0000f000 08:01 364494 /lib/libbz2.so.1.0.4
    b78c8000-b78ca000 r-xp 00000000 08:01 1094853 /usr/lib/gconv/ISO8859-2.so
    b78ca000-b78cc000 rw-p 00001000 08:01 1094853 /usr/lib/gconv/ISO8859-2.so
    b78cc000-b78d0000 r-xp 00000000 08:01 1082780 /usr/lib/libXfixes.so.3.1.0
    b78d0000-b78d1000 rw-p 00003000 08:01 1082780 /usr/lib/libXfixes.so.3.1.0
    b78d1000-b78d8000 r-xp 00000000 08:01 1075970 /usr/lib/libXrender.so.1.3.0
    b78d8000-b78d9000 rw-p 00007000 08:01 1075970 /usr/lib/libXrender.so.1.3.0
    b78d9000-b78e1000 r-xp 00000000 08:01 1089143 /usr/lib/libXcursor.so.1.0.2
    b78e1000-b78e2000 rw-p 00007000 08:01 1089143 /usr/lib/libXcursor.so.1.0.2
    b78e2000-b78e3000 r-xp 00000000 08:01 1147850 /usr/lib/imlib2/loaders/argb.so
    b78e3000-b78e4000 rw-p 00000000 08:01 1147850 /usr/lib/imlib2/loaders/argb.so
    b78e4000-b78e7000 r-xp 00000000 08:01 1147838 /usr/lib/imlib2/loaders/bmp.so
    b78e7000-b78e8000 rw-p 00002000 08:01 1147838 /usr/lib/imlib2/loaders/bmp.so
    b78e8000-b78e9000 r-xp 00000000 08:01 1147839 /usr/lib/imlib2/loaders/bz2.so
    b78e9000-b78ea000 rw-p 00000000 08:01 1147839 /usr/lib/imlib2/loaders/bz2.so
    b78ea000-b78f1000 r-xp 00000000 08:01 1085895 /usr/lib/libungif.so.4.1.4
    b78f1000-b78f2000 rw-p 00007000 08:01 1085895 /usr/lib/libungif.so.4.1.4
    b78f2000-b7902000 r-xp 00000000 08:01 1086532 /usr/lib/libid3tag.so.0.3.0
    b7902000-b7904000 rw-p 0000f000 08:01 1086532 /usr/lib/libid3tag.so.0.3.0
    b7904000-b7926000 r-xp 00000000 08:01 1082925 /usr/lib/libpng12.so.0.22.0
    b7926000-b7927000 rw-p 00021000 08:01 1082925 /usr/lib/libpng12.so.0.22.0
    b7927000-b7946000 r-xp 00000000 08:01 1082939 /usr/lib/libjpeg.so.62.0.0
    b7946000-b7947000 rw-p 0001e000 08:01 1082939 /usr/lib/libjpeg.so.62.0.0
    b7947000-b7999000 r-xp 00000000 08:01 1084025 /usr/lib/libtiff.so.3.8.2
    b7999000-b799b000 rw-p 00052000 08:01 1084025 /usr/lib/libtiff.so.3.8.2
    b799b000-b79f1000 r--p 00000000 08:01 1089076 /usr/lib/locale/locale-archive
    b79f1000-b79f3000 rw-p b79f1000 00:00 0
    b79f3000-b79f7000 r-xp 00000000 08:01 1081182 /usr/lib/libXdmcp.so.6.0.0
    b79f7000-b79f8000 rw-p 00003000 08:01 1081182 /usr/lib/libXdmcp.so.6.0.0
    b79f8000-b7a0e000 r-xp 00000000 08:01 603521 /usr/lib/libxcb.so.1.0.0
    b7a0e000-b7a0f000 rw-p 00016000 08:01 603521 /usr/lib/libxcb.so.1.0.0
    b7a0f000-b7a10000 r-xp 00000000 08:01 603525 /usr/lib/libxcb-xlib.so.0.0.0
    b7a10000-b7a11000 rw-p 00000000 08:01 603525 /usr/lib/libxcb-xlib.so.0.0.0
    b7a11000-b7a13000 r-xp 00000000 08:01 1075750 /usr/lib/libXau.so.6.0.0
    b7a13000-b7a14000 rw-p 00001000 08:01 1075750 /usr/lib/libXau.so.6.0.0
    b7a14000-b7a15000 rw-p b7a14000 00:00 0
    b7a15000-b7a60000 r-xp 00000000 08:01 1082177 /usr/lib/libXt.so.6.0.0
    b7a60000-b7a64000 rw-p 0004a000 08:01 1082177 /usr/lib/libXt.so.6.0.0
    b7a64000-b7b8f000 r-xp 00000000 08:01 34177 /lib/libc-2.6.1.so
    b7b8f000-b7b90000 r--p 0012b000 08:01 34177 /lib/libc-2.6.1.so
    b7b90000-b7b92000 rw-p 0012c000 08:01 34177 /lib/libc-2.6.1.so
    b7b92000-b7b95000 rw-p b7b92000 00:00 0
    b7b95000-b7bb8000 r-xp 00000000 08:01 34172 /lib/libm-2.6.1.so
    b7bb8000-b7bba000 rw-p 00022000 08:01 34172 /lib/libm-2.6.1.so
    b7bba000-b7bbc000 r-xp 00000000 08:01 34173 /lib/libutil-2.6.1.so
    b7bbc000-b7bbe000 rw-p 00001000 08:01 34173 /lib/libutil-2.6.1.so
    b7bbe000-b7ca3000 r-xp 00000000 08:01 1073106 /usr/lib/libX11.so.6.2.0
    b7ca3000-b7ca7000 rw-p 000e4000 08:01 1073106 /usr/lib/libX11.so.6.2.0
    b7ca7000-b7ca8000 rw-p b7ca7000 00:00 0
    b7ca8000-b7cb5000 r-xp 00000000 08:01 1082251 /usr/lib/libXext.so.6.4.0
    b7cb5000-b7cb6000 rw-p 0000c000 08:01 1082251 /usr/lib/libXext.so.6.4.0
    b7cb6000-b7cf7000 r-xp 00000000 08:01 1086554 /usr/lib/libast.so.2.0.1
    b7cf7000-b7cf8000 rw-p 00041000 08:01 1086554 /usr/lib/libast.so.2.0.1
    b7cf8000-b7cfa000 rw-p b7cf8000 00:00 0
    b7cfa000-b7d0e000 r-xp 00000000 08:01 1082346 /usr/lib/libXmu.so.6.2.0
    b7d0e000-b7d0f000 rw-p 00014000 08:01 1082346 /usr/lib/libXmu.so.6.2.0
    b7d0f000-b7d23000 r-xp 00000000 08:01 1087401 /usr/lib/libICE.so.6.3.0
    b7d23000-b7d24000 rw-p 00014000 08:01 1087401 /usr/lib/libICE.so.6.3.0
    b7d24000-b7d26000 rw-p b7d24000 00:00 0
    b7d26000-b7d2d000 r-xp 00000000 08:01 605740 /usr/lib/libSM.so.6.0.0
    b7d2d000-b7d2e000 rw-p 00006000 08:01 605740 /usr/lib/libSM.so.6.0.0
    b7d2e000-b7d54000 r-xp 00000000 08:01 32974 /lib/libpcre.so.0.0.1
    b7d54000-b7d55000 rw-p 00025000 08:01 32974 /lib/libpcre.so.0.0.1
    b7d55000-b7d56000 rw-p b7d55000 00:00 0
    b7d56000-b7d58000 r-xp 00000000 08:01 32545 /lib/libdl-2.6.1.so
    b7d58000-b7d5a000 rw-p 00001000 08:01 32545 /lib/libdl-2.6.1.so
    b7d5a000-b7d6b000 r-xp 00000000 08:01 32798 /lib/libz.so.1.2.3
    b7d6b000-b7d6c000 rw-p 00010000 08:01 32798 /lib/libz.so.1.2.3
    b7d6c000-b7d6d000 r-xp 00000000 08:01 1147840 /usr/lib/imlib2/loaders/gif.so
    b7d6d000-b7d6e000 rw-p 00001000 08:01 1147840 /usr/lib/imlib2/loaders/gif.so
    b7d6e000-b7d71000 r-xp 00000000 08:01 1147841 /usr/lib/imlib2/loaders/id3.so
    b7d71000-b7d72000 rw-p 00002000 08:01 1147841 /usr/lib/imlib2/loaders/id3.so
    b7d72000-b7d74000 r-xp 00000000 08:01 1140742 /usr/lib/imlib2/loaders/jpeg.so
    b7d74000-b7d75000 rw-p 00001000 08:01 1140742 /usr/lib/imlib2/loaders/jpeg.so
    b7d75000-b7d77000 r-xp 00000000 08:01 1147843 /usr/lib/imlib2/loaders/lbm.so
    b7d77000-b7d78000 rw-p 00001000 08:01 1147843 /usr/lib/imlib2/loaders/lbm.so
    b7d78000-b7d7a000 r-xp 00000000 08:01 1147844 /usr/lib/imlib2/loaders/png.so
    b7d7a000-b7d7b000 rw-p 00002000 08:01 1147844 /usr/lib/imlib2/loaders/png.so
    b7d7b000-b7d7e000 r-xp 00000000 08:01 1147845 /usr/lib/imlib2/loaders/pnm.so
    b7d7e000-b7d7f000 rw-p 00002000 08:01 1147845 /usr/lib/imlib2/loaders/pnm.so
    b7d7f000-b7d81000 r-xp 00000000 08:01 1147846 /usr/lib/imlib2/loaders/tga.so
    b7d81000-b7d82000 rw-p 00001000 08:01 1147846 /usr/lib/imlib2/loaders/tga.so
    b7d82000-b7d84000 r-xp 00000000 08:01 1147836 /usr/lib/imlib2/loaders/tiff.so
    b7d84000-b7d85000 rw-p 00001000 08:01 1147836 /usr/lib/imlib2/loaders/tiff.so
    b7d85000-b7d88000 r-xp 00000000 08:01 1147848 /usr/lib/imlib2/loaders/xpm.so
    b7d88000-b7d89000 rw-p 00002000 08:01 1147848 /usr/lib/imlib2/loaders/xpm.so
    b7d89000-b7d8a000 r-xp 00000000 08:01 1147835 /usr/lib/imlib2/loaders/zlib.so
    b7d8a000-b7d8b000 rw-p 00000000 08:01 1147835 /usr/lib/imlib2/loaders/zlib.so
    b7d8c000-b7e03000 r-xp 00000000 08:01 1075218 /usr/lib/libfreetype.so.6.3.16
    b7e03000-b7e07000 rw-p 00077000 08:01 1075218 /usr/lib/libfreetype.so.6.3.16
    b7e07000-b7e53000 r-xp 00000000 08:01 1084197 /usr/lib/libImlib2.so.1.4.0
    b7e53000-b7e54000 rw-p 0004b000 08:01 1084197 /usr/lib/libImlib2.so.1.4.0
    b7e54000-b7e68000 rw-p b7e54000 00:00 0
    b7e68000-b7e8e000 r-xp 00000000 08:01 1086529 /usr/lib/libttf.so.2.2.0
    b7e8e000-b7e8f000 rw-p 00026000 08:01 1086529 /usr/lib/libttf.so.2.2.0
    b7e8f000-b7f12000 r-xp 00000000 08:01 1084286 /usr/lib/libEterm-0.9.4.so
    b7f12000-b7f17000 rw-p 00083000 08:01 1084286 /usr/lib/libEterm-0.9.4.so
    b7f17000-b7f22000 rw-p b7f17000 00:00 0
    b7f22000-b7f23000 r-xp b7f22000 00:00 0 [vdso]
    b7f23000-b7f3d000 r-xp 00000000 08:01 34182 /lib/ld-2.6.1.so
    b7f3d000-b7f3e000 r--p 00019000 08:01 34182 /lib/ld-2.6.1.so
    b7f3e000-b7f3f000 rw-p 0001a000 08:01 34182 /lib/ld-2.6.1.so
    bfd99000-bfdac000 rwxp bfd99000 00:00 0 [stack]
    bfdac000-bfdaf000 rw-p bfdac000 00:00 0
    Eterm: Error: Received terminal signal SIGABRT (6)
    Eterm: Error: Attempting to dump a stack trace....
    Eterm: Error: Your system does not support any of the methods Eterm uses. Exiting.
    X Error: BadWindow (invalid Window parameter) 3
    Major opcode: 19
    Minor opcode: 0
    Resource id: 0x6200003
    (emerald:26202): Wnck-WARNING **: Property _NET_STARTUP_ID contained invalid UTF-8
    (emerald:26202): Wnck-WARNING **: Property _NET_STARTUP_ID contained invalid UTF-8
    Last edited by MAC!EK (2007-10-15 15:01:03)

    I'm getting a similar crash message when I run su.  It errs this way only the first time I run it, however.  The second su works:
    % su -
    Password or swipe finger:
    *** glibc detected *** su: malloc(): memory corruption: 0x09d63050 ***
    ======= Backtrace: =========
    /lib/libc.so.6[0xb7ef7ee4]
    /lib/libc.so.6[0xb7efa510]
    /lib/libc.so.6(__libc_malloc+0x9c)[0xb7efc18c]
    /lib/libc.so.6[0xb7f20d6b]
    /lib/libc.so.6(opendir+0x63)[0xb7f20f03]
    /usr/lib/libusb-0.1.so.4(usb_os_find_busses+0x22)[0xb7ff34d2]
    /usr/lib/libusb-0.1.so.4(usb_find_busses+0x1f)[0xb7ff09ff]
    /usr/lib/libthinkfinger.so.0[0xb7ff8740]
    /usr/lib/libthinkfinger.so.0(libthinkfinger_verify+0x26)[0xb7ff8cf6]
    /lib/security/pam_thinkfinger.so[0xb7ffc591]
    /lib/libpthread.so.0[0xb7ccd155]
    /lib/libc.so.6(clone+0x5e)[0xb7f5ca5e]
    ======= Memory map: ========
    08048000-08050000 r-xp 00000000 08:07 212591 /bin/su
    08050000-08051000 rw-p 00007000 08:07 212591 /bin/su
    09d5d000-09d7e000 rw-p 09d5d000 00:00 0 [heap]
    b6c5d000-b6c5e000 ---p b6c5d000 00:00 0
    b6c5e000-b745e000 rw-p b6c5e000 00:00 0
    b745e000-b745f000 ---p b745e000 00:00 0
    b745f000-b7c5f000 rw-p b745f000 00:00 0
    b7c5f000-b7c68000 r-xp 00000000 08:07 2289484 /lib/libcrypt-2.9.so
    b7c68000-b7c69000 r--p 00008000 08:07 2289484 /lib/libcrypt-2.9.so
    b7c69000-b7c6a000 rw-p 00009000 08:07 2289484 /lib/libcrypt-2.9.so
    b7c6a000-b7c91000 rw-p b7c6a000 00:00 0
    b7c91000-b7ca4000 r-xp 00000000 08:07 2289485 /lib/libnsl-2.9.so
    b7c68000-b7c69000 r--p 00008000 08:07 2289484 /lib/libcrypt-2.9.so
    b7c69000-b7c6a000 rw-p 00009000 08:07 2289484 /lib/libcrypt-2.9.so
    b7c6a000-b7c91000 rw-p b7c6a000 00:00 0
    b7c91000-b7ca4000 r-xp 00000000 08:07 2289485 /lib/libnsl-2.9.so
    b7ca4000-b7ca5000 r--p 00012000 08:07 2289485 /lib/libnsl-2.9.so
    b7ca5000-b7ca6000 rw-p 00013000 08:07 2289485 /lib/libnsl-2.9.so
    b7ca6000-b7ca8000 rw-p b7ca6000 00:00 0
    b7cc7000-b7cdb000 r-xp 00000000 08:07 2551021 /lib/libpthread-2.9.so
    b7cdb000-b7cdc000 r--p 00014000 08:07 2551021 /lib/libpthread-2.9.so
    b7cdc000-b7cdd000 rw-p 00015000 08:07 2551021 /lib/libpthread-2.9.so
    b7cdd000-b7cdf000 rw-p b7cdd000 00:00 0
    b7ce7000-b7cf1000 r-xp 00000000 08:07 3074372 /lib/security/pam_unix.so
    b7cf1000-b7cf2000 rw-p 00009000 08:07 3074372 /lib/security/pam_unix.so
    b7cf2000-b7cfe000 rw-p b7cf2000 00:00 0
    b7cfe000-b7d07000 r-xp 00000000 08:07 2485525 /lib/libnss_files-2.9.so
    b7d07000-b7d08000 r--p 00008000 08:07 2485525 /lib/libnss_files-2.9.so
    b7d08000-b7d09000 rw-p 00009000 08:07 2485525 /lib/libnss_files-2.9.so
    b7d09000-b7e87000 r--p 00000000 08:07 1815223 /usr/lib/locale/locale-archive
    b7e87000-b7e88000 rw-p b7e87000 00:00 0
    b7e88000-b7e8a000 r-xp 00000000 08:07 2551022 /lib/libdl-2.9.so
    b7e8a000-b7e8b000 r--p 00001000 08:07 2551022 /lib/libdl-2.9.so
    b7e8b000-b7e8c000 rw-p 00002000 08:07 2551022 /lib/libdl-2.9.so
    b7e8c000-b7fcc000 r-xp 00000000 08:07 2289562 /lib/libc-2.9.so
    b7fcc000-b7fcd000 ---p 00140000 08:07 2289562 /lib/libc-2.9.so
    b7fcd000-b7fcf000 r--p 00140000 08:07 2289562 /lib/libc-2.9.so
    b7fcf000-b7fd0000 rw-p 00142000 08:07 2289562 /lib/libc-2.9.so
    b7fd0000-b7fd3000 rw-p b7fd0000 00:00 0
    b7fd3000-b7fd5000 r-xp 00000000 08:07 3074336 /lib/libpam_misc.so.0.81.3
    b7fd5000-b7fd6000 rw-p 00001000 08:07 3074336 /lib/libpam_misc.so.0.81.3
    b7fd6000-b7fe0000 r-xp 00000000 08:07 3074340 /lib/libpam.so.0.81.12
    b7fe0000-b7fe1000 rw-p 00009000 08:07 3074340 /lib/libpam.so.0.81.12
    b7fe1000-b7fe2000 rw-p b7fe1000 00:00 0
    b7fe2000-b7fee000 r-xp 00000000 08:07 638583 /usr/lib/libgcc_s.so.1
    b7fee000-b7fef000 rw-p 0000c000 08:07 638583 /usr/lib/libgcc_s.so.1
    b7fef000-b7ff5000 r-xp 00000000 08:07 509123 /usr/lib/libusb-0.1.so.4.4.4
    b7ff5000-b7ff7000 rw-p 00005000 08:07 509123 /usr/lib/libusb-0.1.so.4.4.4
    b7ff7000-b7ffa000 r-xp 00000000 08:07 540079 /usr/lib/libthinkfinger.so.0.0.0
    b7ffa000-b7ffb000 rw-p 00002000 08:07 540079 /usr/lib/libthinkfinger.so.0.0.0
    b7ffb000-b7ffd000 r-xp 00000000 08:07 2485513 /lib/security/pam_thinkfinger.so
    b7ffd000-b7ffe000 rw-p 00001000 08:07 2485513 /lib/security/pam_thinkfinger.so
    b7ffe000-b7fff000 r-xp 00000000 08:07 3074371 /lib/security/pam_rootok.so
    b7fff000-b8000000 rw-p 00000000 08:07 3074371 /lib/security/pam_rootok.so
    b8001000-b8002000 r-xp b8001000 00:00 0 [vdso]
    b8002000-b801e000 r-xp 00000000 08:07 2485519 /lib/ld-2.9.so
    b801e000-b801f000 r--p 0001b000 08:07 2485519 /lib/ld-2.9.so
    b801f000-b8020000 rw-p 0001c000 08:07 2485519 /lib/ld-2.9.so
    bfb0a000-bfb1f000 rw-p bffeb000 00:00 0 [stack]
    zsh: abort su -
    TIA

  • IPhone SDK 2.2 memory corruption

    Hello. I'm working on an application for iPhone SDK 2.2 and seem to be having weird memory corruption problems. Not necessarily leaks because using Instruments shows my memory stamp never going above about 1.8 megs. The nature of the app is a database of animals so I'm constantly loading and unloading sounds and images. None of the objects are very large (at most I'll have 4 800k pngs loaded at once) and I've checked and rechecked my alloc/retain/release and everything is in order (hence no memory usage increase). However...after using the application for a while I'll notice strange behavior. For example:
    1) we have a UILabel as the title for each page. After a while the font size of this will change.
    2) I have several screens with a subclassed UIScrollView where images are loaded and then added to. The problem shows itself here by the images not showing up. there's no crash, stepping through the debugger shows that the image loads up fine, it's just that the image is not there.
    3) I have a UILabel at the top of an animal description screen, which in the nib file is called "Animal Name" by default. This will change to show "Animal Name" at the top.
    I've removed all audio in our latest build so that isn't the problem. What I'm starting to suspect is that altering anything defined in a nib file will cause corruption. For example, the UIScrollView is defined in the nib file, and I constantly am reassigning the contents of that with a UIImageView. This UIImageView is handled within the subview class like :
    UIImageView *imgView = [[UIImageView alloc] initWithImage: [ UIImage imageWithContentsOfFile:[[NSBundle mainBundle ] pathForResource:imageToLoad ofType:@"png" ]] ];
    imgView.tag = 50;
    [self addSubview:imgView ];
    [ imgView release ];
    Then later when moving away from the screen I'll find that view's tag and remove it from the superview (since addSubView increases the retain count, the alloc+addSubView is cancelled by release+removeFromSuperView)
    I can't explain why titles that are never changed would be affected, but it must somehow be related. What I'm wondering is: are there any known issues involving modification of the contents of objects defined in Nib files? Perhaps the memory allocated when initWithNibName is restrained, then any modification of objects allocated within it can cause corruption. I'm starting to think I should just alloc and free anything modified in code and skip using nib files altogether (I reset the text on buttons for example). If this is a known issue please let me know. I'll give you more information if I can.
    Thank you

    Just download the huge SDK package and install. No need to uninstall the old SDK.

  • Help finding location of Memory corruption using libumem and mdb

    Hi there,
    I am debugging an application, an rpc based server that runs on a solaris 10 box. This is a server that has a footprint of about 2.3 gigs (while using libumem debug options, its close to 3.5 gigs). Most of the size is because of caching. When certain modifications are done to objects in the cache, a copy of the cache is made by the modifying thread, and then the older copy is freed when no other thread is using it.
    One of our customers is using libumem as the memory manager. They started seeing crashes every now and then when the copy of cache is being freed. Obviously, it doesnt crash everytime, and each time the crash is with a different object all together. libumem raises a signal 6 abort, and complains that a piece of memory that is being freed is invalid or corrupt memory. Needless to say, countless hours of code walkthrough, and trying to reproduce the problem in house has failed. So we turned on libumem debugging and logging. Using watchmalloc at this site is not an option because of performance considerations. This is the setup we are using.
    LD_PRELOAD=${LD_PRELOAD}:libumem.so.1
    export LD_PRELOAD
    UMEM_DEBUG=default;export UMEM_DEBUG
    UMEM_LOGGING=transaction;export UMEM_LOGGING
    We have a core from this crash. I am using mdb to analyze the core.
    ::umem_status tells me that the address being freed is invalid or corrupt memory. It even shows me where it was initially allocated. I want to find out where this piece of memory got corrupted.
    ::umalog shows the log of all memory allocation and freeing transactions. But because this is a huge app, it has a ton of information. I tried using address::umalog and that doesnt seem to narrow down the log.
    So my question is, given the core generated using these settings, what mdb commands do I use to find out what operation/code corrupted the memory. I would expect to see three pieces of information for the address whose free failed.
    1. Where it was initially allocated
    2. Where the error/crash occured
    3. What operation corrupted the memory, whether its a overwrite or freeing (leading to double free)
    I ll be glad to provide more information if needed.
    Any help is deeply appreciated.

    If you have the address that is corrupt, try finding addresses that are just before the corrupt address. If your corrupt address is 0xF028, for example, look for addresses like 0xF020 or 0XF018. Most likely what's happening is some code is writing too far into a block, corrupting what's in the next block.

  • Memory corruption due to bad RAM in late 2012 iMac

    I just unpacked a brand new late-2012 iMac a few days ago. Its specs are basically maxed out, only choice being the 3TB fusion drive. To summarize:
    3.4 GHz Core i7
    32GB RAM
    3TB Fusion Drive
    2GB NVidia
    Latest patches for Mountain Lion
    Since I got it, I have been experiencing intermittent abnormalities with it. Programs randomly crash with error messages along the lines of "such and such file appears corrupt, please run --repair".
    I do a lot of programming in my job and just today I started getting bizarre 'segmentation fault' messages in Terminal. What worked just a few minutes ago started crashing with a segfault. The exact same programs have no negative effect on my Macbook Pro and work just fine. In a matter of minutes, the entire iMac became unresponsive and I got the "we shut down your computer to prevent damage" panic screen.
    After a reboot, I started thinking it could be some sort of memory corruption. I downloaded the 'memtest' utility and started the basic test with:
    memtest all 2
    In just a few minutes, below are the results I receive (I re-ran multiple times to the same effect).
    Any opinions on whether this is indeed bad RAM? How do I handle this with Apple support? Any suggestions/comments are most welcome.
    Thank you,
    Ozgun
    Excerpt from the crash report in Console:
    Process:         ghc [96618]
    Path:            /usr/local/lib/ghc-7.6.2/ghc
    Identifier:      ghc
    Version:         ???
    Code Type:       X86-64 (Native)
    Parent Process:  Emacs-10.7 [37299]
    User ID:         501
    Date/Time:       2013-03-20 21:06:30.389 -0400
    OS Version:      Mac OS X 10.8.3 (12D78)
    Report Version:  10
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: EXC_I386_GPFLT
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   ghc                                     0x000000010bb44b10 evacuate1 + 5296
    1   ghc                                     0x000000010bb4927f scavenge_block1 + 703
    2   ghc                                     0x000000010bb4a78c scavenge_loop1 + 1548
    3   ghc                                     0x000000010bb4639e scavenge_until_all_done + 798
    4   ghc                                     0x000000010bb46c57 GarbageCollect + 1639
    5   ghc                                     0x000000010bb378ff scheduleDoGC + 991
    6   ghc                                     0x000000010bb3982b schedule + 1579
    7   ghc                                     0x000000010bb39df4 scheduleWaitThread + 164
    8   ghc                                     0x000000010bb3478e real_main + 68
    Memtest Results:
    Memtest version 4.22 (64-bit)
    Copyright (C) 2004 Charles Cazabon
    Copyright (C) 2004-2008 Tony Scaminaci (Macintosh port)
    Licensed under the GNU General Public License version 2 only
    Mac OS X 10.8.3 (12D78) running in multiuser mode
    Memory Page Size: 4096
    System has 8 Intel core(s) with SSE
    Requested memory: 24009MB (25176211456 bytes)
    Available memory: 24009MB (25176211456 bytes)
    Allocated memory: 24009MB (25176211456 bytes) at local address 0x0000000101000000
    Attempting memory lock... locked successfully
    Partitioning memory into 2 comparison buffers...
    Buffer A: 12004MB (12588105728 bytes) starts at local address 0x0000000101000000
    Buffer B: 12004MB (12588105728 bytes) starts at local address 0x00000003ef4f4000
    Running 2 test sequences... (CTRL-C to quit)
    Test sequence 1 of 2:
    Running tests on full 24009MB region...
      Stuck Address       : testing  1 of 16
    FAILURE! Data mismatch at local address 0x0000000262d778c0
    Actual Data: 0x0200000262d778c0
      Linear PRN          : testing  1 of 16
    FAILURE! Data mismatch at local address 0x0000000262d77900
    Expected Data: 0xa378ecfaa3ecf6b9, Actual Data: 0x0178ecfaa3ecf6b9
    Running comparison tests using 12004MB buffers...
      Random Value        :
    FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
    BUFA Data: 0x3ddd57d041eb5a06, BUFB Data: 0x3fdd57d041eb5a06
      Compare XOR         :
    FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
    BUFA Data: 0x826aabfcebf44332, BUFB Data: 0x806aabfcebf44332
      Compare SUB         :
    FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
    BUFA Data: 0x8e6cbb4010b8a88d, BUFB Data: 0x8a6cbb4010b8a88d
      Compare MUL         :
    FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
    BUFA Data: 0x54fd2f0176d1ab9e, BUFB Data: 0xfefd2f0176d1ab9e
      Compare DIV         :
    FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
    BUFA Data: 0x0200000000000000, BUFB Data: 0x0000000000000002
      Compare OR          :
    FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
    BUFA Data: 0x6eaf35c4f7fc13fb, BUFB Data: 0x6caf35c4f7fc13fb
      Compare AND         :
    FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
    BUFA Data: 0x6ea704c077fc1399, BUFB Data: 0x6ca704c077fc1399
      Sequential Increment:
    FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
    BUFA Data: 0x7caad7e9fb32b8ca, BUFB Data: 0x7eaad7e9fb32b8ca
      Solid Bits          : testing  1 of 64
    FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
    BUFA Data: 0xfdffffffffffffff, BUFB Data: 0xffffffffffffffff
      Block Sequential    : testing   1 of 256
    FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
    BUFA Data: 0x0200000000000000, BUFB Data: 0x0000000000000000
      Checkerboard        : testing  1 of 64
    FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
    BUFA Data: 0x0155555555555555, BUFB Data: 0x5555555555555555
      Bit Spread          : testing   1 of 128
    FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
    BUFA Data: 0x0200000000000005, BUFB Data: 0x0000000000000005
      Bit Flip            : testing   1 of 512
    FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
    BUFA Data: 0xfdfffffffffffffe, BUFB Data: 0xfffffffffffffffe
      Walking Ones        : testing   1 of 128
    FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
    BUFA Data: 0x11fffffffffffffe, BUFB Data: 0xfffffffffffffffe
      Walking Zeroes      : testing   1 of 128
    FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
    BUFA Data: 0x0200000000000001, BUFB Data: 0x0000000000000001
    Test sequence 2 of 2:
    Running tests on full 24009MB region...
      Stuck Address       : testing  1 of 16
    FAILURE! Data mismatch at local address 0x0000000262d778c0
    Actual Data: 0x0200000262d778c0
      Linear PRN          : testing  1 of 16
    FAILURE! Data mismatch at local address 0x0000000262d77900
    Expected Data: 0xa378ecfaa3ecf6b9, Actual Data: 0x0178ecfaa3ecf6b9
    Running comparison tests using 12004MB buffers...
      Random Value        :
    FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
    BUFA Data: 0xf54d78773a1d75d1, BUFB Data: 0xf74d78773a1d75d1
      Compare XOR         :
    FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
    BUFA Data: 0x01e08f19e0bd343d, BUFB Data: 0xbbe08f19e0bd343d
      Compare SUB         :
    FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
    BUFA Data: 0x01e38c4ae6cbd9e0, BUFB Data: 0x5be38c4ae6cbd9e0
      Compare MUL         :
    FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
    BUFA Data: 0x01d2ccf452aabcc0, BUFB Data: 0x5ed2ccf452aabcc0
      Compare DIV         :
    FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
    BUFA Data: 0x0200000000000003, BUFB Data: 0x0000000000000003
      Compare OR          :
    FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
    BUFA Data: 0x01f97d3f343b8641, BUFB Data: 0xe7f97d3f343b8641
      Compare AND         :
    FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
    BUFA Data: 0x0181413c143a0641, BUFB Data: 0xe381413c143a0641
      Sequential Increment:
    FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
    BUFA Data: 0x11df0c80ebf82821, BUFB Data: 0xf2df0c80ebf82821
      Solid Bits          : testing  1 of 64
    FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
    BUFA Data: 0x11ffffffffffffff, BUFB Data: 0xffffffffffffffff
      Block Sequential    : testing   1 of 256
    FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
    BUFA Data: 0x0200000000000000, BUFB Data: 0x0000000000000000
      Checkerboard        : testing  1 of 64
    FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
    BUFA Data: 0x0155555555555555, BUFB Data: 0x5555555555555555
      Bit Spread          : testing   1 of 128
    FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
    BUFA Data: 0x0200000000000005, BUFB Data: 0x0000000000000005
      Bit Flip            : testing   1 of 512
    FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
    BUFA Data: 0xfdfffffffffffffe, BUFB Data: 0xfffffffffffffffe
      Walking Ones        : testing   1 of 128
    FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
    BUFA Data: 0x11fffffffffffffe, BUFB Data: 0xfffffffffffffffe
      Walking Zeroes      : testing   1 of 128
    FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
    BUFA Data: 0x0200000000000001, BUFB Data: 0x0000000000000001
    *** Address Test Failed ***  One or more DIMM address lines are non-functional.
    Execution time: 230 seconds.
    ➜  ~  memtest all 2

    This must be my last last thing.  AHT was on an iMac I bought in 2009.  It was included on my "disk 2" along with several other applications.  When I wiped and installed the full Lion, AHT was gone.  Same is true for the full Mountain Lion installation media.  It does not have AHT.  I'm not at all sure how to get it back from Apple.
    I was able to find it on my SL disc 2 and extract it again from that.  Disc 2 won't install on Mountain Lion (the packages are too out of date) but the AHT pkg does.
    Since you have it, consider packing it up and keeping it safe.  Maybe someone who knows AHT better than I can elaborate on AHT.  From what I've seen, you get it when your mac ships but if you ever wipe and reinstall the OS, you lose it.

  • Satellite 5200 - Video memory corruption

    One month ago I encountered a problem with a slightly garbled screen
    on the internal and external displays. More or less visible vertical
    strips appear on the screen. They are mainly blue on dark background
    (best visible) or yellow on white background (less visible) and have
    approximately the same thickness of order 1-2 mm and length of order
    1 cm. The locations of the strips depend on the positions of details
    of the actual picture currently displayed on the screen.
    The boot screen is also garbled but now by red vertical strips located on the left and on the right of the red logo "In Touch with Tomorrow Toshiba"
    In the full screen text mode, odd characters appear in positions which correlate with positions of true characters.
    The BurnIn Test V4.0 Pro indicated a video memory corruption (the adapter is NVIDIA GeForce4 460 Go, 64 MB, integrated RAMDAC). That is very interesting, yesterday
    there was a short period of about 5 minutes when all the described above symptoms suddenly disappeared.
    Even the BurnIn Test showed that everything is OK. But after this period, the symptoms recovered again. For this
    reason I would like to ask how to solve the problem.
    Is this indeed a bad video memory which can recover and then become bad again or other reasons, such as a bad connectivity, etc.?
    Thanks.

    hi, i had the same problem on a Satellite m70-159. With one diference- mine would start only in safe mode. But the same vertical strips, even in the ''in touch with tomorow'' screen. this was the good news. the bad news is that they had to replace both the motherboard and the video module.
    sorry.. and it's not like anything had happened to my notebook..

  • E63 - Memory Corrupted - Due to Device Lock / Remo...

    I have a brand new Nokia E63 (same as E71). My memory card is suddenly corrupted, but I managed to fix it. I believe the source of the problem is the Remote Lock and the Device Lock of the unit.
    The problem started after I enabled the Device Lock and Remote Lock of my E63 unit. After a couple of hours, I tried opening my apps in the memory card. To my surprise, it's corrupted! I didn't panic because I'm confident I could retrieve the contents of the card with a memory reader device. But when I inserted my memory card to my PC, the card is unreadable. I had a feeling that the card must had been badly corrupted. But how? I just got this unit almost a day ago. I didn't do anything odd. I'm an OOP-Design Patterns oriented programmer so I'm not newbie when it comes to best practices.
    As I searched the web, I found that there are people who encountered the same exact problem. And their guess is also the Device Lock.
    So what I did is I disabled the Remote Lock and the Device Lock feature. I checked my memory card and it's still corrupted!
    I turn off my unit and turn it on again, but sadly it's still corrupted!
    I removed the memory card while the unit is on and then reinserted the card, and it worked.
    In summary, to solve this memory corrupted problem, try disabling the Remote Lock and Device Lock feature. To disable the Device Lock, revert the password to "12345" (Do not type the quotes). Remove the memory card (Use the remove memory card feature of your unit!). Re-insert the card to your unit and problem should be fixed.

    i wonder if its a problem with this phone...i have faced a lot of problems with accessing data on the memory card...time & again the songs added to the music player list disappear...the applications that i installed on the memory card are also sometimes "invisible"...when i try installing them again, it says these already exist...
    have formatted the memory card quite a few times now...
    luckily for me i took the backup of the memory card (that came in the box) & phone on the very 1st day...
    hence, every time i format the memory card, i copy the initial contents...
    but its quite irritating & frustrating...1 nite i go to sleep after listening to songs, the next morning it shows no songs found...have to restart the phone 2-3 times to find them again...
    is phone lock & device lock the same thing that you talking about? i have tried the phone lock but my memory card did not get corrupted...remote lock i have never tried...
    as for your queries sidy_porche,
    1) as per the specs mentioned on the site "Video recording file formats: .mp4, .3gp; codecs: H.263, MPEG-4 VSP" & "Video playback file formats: .Flash Lite 3, mp4, .3gp; codecs: H.263, MPEG-4 VSP" also "Video streaming: .3gp, mp4, .rm"
    i think the specs that you mentioned for playback will be compatible...d  "640x480, 15fps, 3GP"
    2) 3GP videos are played...but its quite interesting...the phone plays some videos while says "file corrupt" for others of the same format...i had 2-3 video songs of mp4 format,they work absolutely fine...i then transferred some new mp4 videos & they simply wont play...
    3) it takes exactly 2 hours ( you can see it on the clock  ) to charge from 0 to 100%...which is quite good coz a 1500mah battery gets charged in 2 hours...i had a 6265 earlier which took around 2.5 hrs to 3 hrs to get charged with the charger that came in the box...using the adapter, ca44 or something, it got charged in 1.5 hours dot.
    4) ya the hearset has a mic...the best thing about this phone or rather one of the best thing is that it has a 3.5mm audio jack...you can insert any damn headphones (your fav ones) into it & enjoyyyyy...even speakers that you attach to your laptop/computer can be used...its awesome 
    i hope it helps
    regards,
    anupam149
    Message Edited by anupam149 on 19-May-2009 07:31 AM
    regards,
    anupam149

  • Could not retrieve the in-memory service URL after starting the in-memory.

    A local jvm process is discovered but mission control will not connect.
    Both jvm process and mission control are on the same host.
    Any suggestion?
    Thanks.
    This is the mission control help version:
    Oracle® JRockit Mission Control 3.1.0 (R27.6.3-40_o, 112101)
    I'm running mission control and a jboss web server on jrockit:
    $ java -version
    java version "1.6.0_11"
    Java(TM) SE Runtime Environment (build 1.6.0_11-b03)
    BEA JRockit(R) (build R27.6.3-40_o-112056-1.6.0_11-20090318-2103-linux-x86_64, compiled mode)
    On linux:
    $ uname -a
    Linux isidore 2.6.27-11-generic #1 SMP Wed Apr 1 20:53:41 UTC 2009 x86_64 GNU/Linux
    This is the message that appears in the controlling tty window:
    Apr 24, 2009 9:55:43 PM com.jrockit.mc.browser.attach.LocalConnectionDescriptor tryJRCMDStyleStartingOfTheAgent
    SEVERE: Could not retrieve the in-memory service URL after starting the in-memory agent!
    Apr 24, 2009 9:55:43 PM com.jrockit.mc.browser.attach.LocalConnectionDescriptor tryJRCMDStyleStartingOfTheAgent
    Here is the exception in the dialog details:
    Could not open Management Console for [1.6] JBoss (5,474).
    java.lang.NullPointerException: null
    java.lang.NullPointerException
         at com.jrockit.mc.rjmx.ConnectionDescriptorToolkit.getHostName(ConnectionDescriptorToolkit.java:152)
         at com.jrockit.mc.rjmx.internal.RJMXConnection.setupServer(RJMXConnection.java:521)
         at com.jrockit.mc.rjmx.internal.RJMXConnection.connect(RJMXConnection.java:144)
         at com.jrockit.mc.rjmx.internal.RJMXConnectorModel.establishConnection(RJMXConnectorModel.java:111)
         at com.jrockit.mc.rjmx.internal.RJMXConnectorModel.connect(RJMXConnectorModel.java:154)
         at com.jrockit.mc.rjmx.ConnectionManager.innerConnect(ConnectionManager.java:95)
         at com.jrockit.mc.rjmx.ConnectionManager.connect(ConnectionManager.java:61)
         at com.jrockit.mc.console.ui.actions.StartConsole$1.preConnect(StartConsole.java:38)
         at com.jrockit.mc.browser.utils.PreConnectJob.run(PreConnectJob.java:74)
         at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

    After I posed the above, I saw that the url on the exception is munged.
    I didn't stumble over how to manually override that url.
    Instead, I added remote jmx capability to the process and added a connector. That is my work around.
    Thanks,
    John

  • Memory corruption detected with linux 3.9.2-1

    I have this message with dmesg and kernel 3.9.2-1, it disappears with kernel downgrade (3.8.11), what can i do ??
    p.s.
    the system seems to be stable.
    [   61.584649] Corrupted low memory at ffff880000006598 (6598 phys) = ff0000000000
    [   61.584695] ------------[ cut here ]------------
    [   61.584709] WARNING: at arch/x86/kernel/check.c:140 check_for_bios_corruption+0x10f/0x120()
    [   61.584712] Hardware name: HP Pavilion dv6 Notebook PC
    [   61.584714] Memory corruption detected in low memory
    [   61.584719] Modules linked in: fuse uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core joydev videodev media hp_wmi sparse_keymap iTCO_wdt iTCO_vendor_support arc4 snd_hda_codec_hdmi intel_powerclamp coretemp microcode psmouse serio_raw pcspkr i2c_i801 intel_ips acpi_cpufreq mperf ath9k ath9k_common ath9k_hw ath mac80211 cfg80211 r8168(O) rfkill thermal wmi snd_hda_codec_idt battery snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc hp_accel snd_timer lis3lv02d input_polldev snd ac evdev mei soundcore lpc_ich processor radeon ttm nfs lockd sunrpc fscache ext4 crc16 mbcache jbd2 sr_mod cdrom sd_mod ahci libahci ehci_pci ehci_hcd libata scsi_mod usbcore usb_common i915 video button i2c_algo_bit intel_agp intel_gtt drm_kms_helper drm i2c_core
    [   61.584832] Pid: 23, comm: kworker/0:1 Tainted: G           O 3.9.2-1-ARCH #1
    [   61.584835] Call Trace:
    [   61.584845]  [<ffffffff81058090>] warn_slowpath_common+0x70/0xa0
    [   61.584851]  [<ffffffff8105810c>] warn_slowpath_fmt+0x4c/0x50
    [   61.584858]  [<ffffffff8104543f>] check_for_bios_corruption+0x10f/0x120
    [   61.584865]  [<ffffffff8104545e>] check_corruption+0xe/0x40
    [   61.584873]  [<ffffffff81075e30>] process_one_work+0x170/0x440
    [   61.584880]  [<ffffffff81076905>] worker_thread+0x115/0x3d0
    [   61.584886]  [<ffffffff810767f0>] ? manage_workers+0x340/0x340
    [   61.584892]  [<ffffffff8107b5d0>] kthread+0xc0/0xd0
    [   61.584898]  [<ffffffff8107b510>] ? kthread_create_on_node+0x120/0x120
    [   61.584905]  [<ffffffff814d96ac>] ret_from_fork+0x7c/0xb0
    [   61.584910]  [<ffffffff8107b510>] ? kthread_create_on_node+0x120/0x120
    [   61.584914] ---[ end trace 1563130596fe98e7 ]---

    Nekos wrote:
    I have this message with dmesg and kernel 3.9.2-1, it disappears with kernel downgrade (3.8.11), what can i do ??
    p.s.
    the system seems to be stable.
    Well, the pithy answer would be to buy a computer from a vendor who supports free operating systems.
    Of course, I own and love my DV4.
    What does it mean?  Some BIOS implementations use areas of low memory without properly allocating it (letting the operating system know it is in use).  Windows just does not use that area of memory, and some vendors do a sloppy job in their software quality; it only has to work with Redmond code, so why fix it?
    Linux is forced to implement a bunch of ridiculous hacks to work around low quality hardware and firmware.  You found one.  The kernel was watching that memory to see if it could be trusted.  Something changed that memory when nothing (in the kernel's view) should have touched it.  Since it changed, the kernel has taken note that that memory should not be trusted.  Kind of analogous to finding a bad block on a disk drive and subsequently ignoring it by adding it to a list of bad blocks.
    So, aside from sucking it up because you lost some usable memory, you need do nothing.
    EDIT: BTW, it probably means the new kernel is more stable.
    Last edited by ewaller (2013-05-16 15:03:00)

  • On a macbook I purchased secondhand hard drive got corrupted and I started to get the flashing folder with the question mark, I purchased a new hard drive and snow lion install DVD I installed the hard drive and tried disc but kept getting blinking folder

    On a macbook I purchased secondhand hard drive got corrupted and I started to get the flashing folder with the question mark, I purchased a new hard drive and snow lion install DVD I installed the hard drive and tried disc but kept getting blinking folder

    Welcome to Apple Support Communities. We're users here and do not speak for "Apple Inc."
    Power on the computer and insert the DVD immediately.
    Hold down the 'C' key to boot from the Snow Leopard DVD.
    http://support.apple.com/kb/ht1533
    After selecting the appropriate language, if necessary, select Utilities, and Disk Utility.
    You'll likely need to partition and format the new drive before it's recognized.
    http://manuals.info.apple.com/MANUALS/0/MA161/en_US/MacBook_13inch_HardDrive_DIY .pdf
    (Yes, these instructions ARE 7 years old, but the procedure is the same for installing from DVD media.)

  • Windows 7 crashing from memory corruption

    For a while now my computer has been crashing at random times. I know it is from memory corruption but I don't know how to fix this I have logs for a little while ago but the newer ones can not be opened because of this.
    https://onedrive.live.com/redir?resid=92544E03407D477B%21161
    This is the file for the dmp files sadly these are the only accessible ones.
    One more thing is I am pretty sure it is from a malware because I changed computer yet it was still happening, I would just like to know how to fix this thanks.

    Unable to load image nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+152e64 )
    VIDEO_TDR_TIMEOUT_DETECTED (117)
    The display driver failed to respond in timely fashion.
    (This code can never be used for real bugcheck).
    Arguments:
    Arg1: fffffa800c74c4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800f171e64, The pointer into responsible device driver module (e.g owner tag).
    Arg3: 0000000000000000, The secondary driver specific bucketing key.
    Arg4: 0000000000000000, Optional internal context dependent data.
     NVidia Display driver caused this malfunction. Please check your pc, device or motherboard manufacturer's support page for an update for
    NVidia display driver and update it.
    More helpful information about the crash.
    VIDEO_TDR_TIMEOUT_DETECTED.
    http://msdn.microsoft.com/en-us/library/windows/hardware/ff557271(v=vs.85).aspx
    Resolving stop (blue screen) errors in Windows 7.
    http://windows.microsoft.com/en-us/windows7/resolving-stop-blue-screen-errors-in-windows-7
    Also, MarvinBus64.sys should not be loading on this system, simply because of it's age. Update the software or remove it!
    MarvinBus64.sys Fri Sep 23 17:17:03 2005 (433470CF) :
    http://sysnative.com/drivers/driver.php?id=MarvinBus64.sys

  • HP Envy 17 Bios Memory Corruption

    Dear all,
    Booting with linux kernel 2.6.34, with X86_RESERVE_LOW_64K and X86_CHECK_BIOS_CORRUPTION enabled, on my HP Envy 17 1010el with BIOS F13A, I'm getting "Memory corruption in low memory" from dmesg output at 60s:
    WARNING: at arch/x86/kernel/check.c:134 check_for_bios_corruption+0xc0/0xd6()
    Hardware name: HP ENVY 17 Notebook PC
    Memory corruption detected in low memory
    Modules linked in:
    Pid: 22, comm: events/3 Not tainted 2.6.34-gentoo-r6 #3
    Call Trace:
    [<ffffffff8103bd4a>] warn_slowpath_common+0x77/0x8f
    [<ffffffff8103bdaf>] warn_slowpath_fmt+0x3c/0x3e
    [<ffffffff8102027b>] check_for_bios_corruption+0xc0/0xd6
    [<ffffffff8102029a>] check_corruption+0x9/0x2b
    [<ffffffff810506cd>] worker_thread+0x19d/0x224
    [<ffffffff81020291>] ? check_corruption+0x0/0x2b
    [<ffffffff8105435f>] ? autoremove_wake_function+0x0/0x34
    [<ffffffff81050530>] ? worker_thread+0x0/0x224
    [<ffffffff81053f23>] kthread+0x7a/0x82
    [<ffffffff81003754>] kernel_thread_helper+0x4/0x10
    [<ffffffff81053ea9>] ? kthread+0x0/0x82
    [<ffffffff81003750>] ? kernel_thread_helper+0x0/0x10
    Could someone verify it and maybe provide an official fix.
    Thank you very much.

    Hi:
    Actually with the Intel Core i7-720QM processor, you can install 2 x 8 GB of PC3-10600 memory, even though the specs from HP, and even Intel state the max is 8 GB.
    There are several folks on this forum that have installed 16 GB of memory in notebooks with first generation core series quad processors.
    Here is one such post...
    http://h30434.www3.hp.com/t5/Hardware-Upgrades-Replacements/Will-Upgrading-Pavilion-dv8t-Memory-to-1...
    16 GB will not work in notebook with a first generation core series dual processor.
    Windows 7 Home Premium allows up to 16 GB of memory so that wouldn't be the problem.

  • Is there a solution to Multiple Memory Corruption Vulnerabilities in Illustrator CS4? (APSB12-10)

    My system is beeing flagged for having the Multiple Memory Corruption Vulnerabilities referenced in APSB12-10. The solution included in that bulletin does not apply to CS4, so I'm wondering if there is another patch or fix or something for earlier versions of the product.
    Thanks!

    Just because there is a potential issue does not mean anyone is actively exploiting it. If I wanted to hurt someone and infect their computer I certainly would find a million times more efficient ways than creating a malicious TIFF file that in the end only 3 people may download at all on the odd chance that they may actually run a version of AI or PS that is succeptible to these attacks. See the point? You are worrying about something that is effectively a non-issue and I'm sure you have web browsers, chat clients, media players etc. and their extensions/ plug-ins on your system that pose a significantly higher risk such as leaky/ malicious Flash games. Again, unless you are the type who "finds" his content and software on illegal sites, there is nothing going on here. the biggest security threat still is human carelessness, anyway.
    Mylenium

  • Panic: Memory corruption detected

    The server reboots from time to time with message:
    savecore: [ID 570001 auth.error] reboot after panic: Memory corruption detected for connection [::ffff:some_IP , ::ffff:some_other_IP] TCP_ESTABLISHED"
    The vmcore:
    =========
    panic[cpu1]/thread=2a10034bd40:
    0x30002237620:  Memory corruption detected for connection [::ffff:212.182.39.5.8
    000, ::ffff:212.182.39.219.3410] TCP_ESTABLISHED.
    0x300022379e0:
    0x3000374d123:  000002a10034b120 tcp:tcp_rput_data+2fe0 (5b4, 0, 0, 3000375e624,
    3000375e610, 30007e682e0)
    0x3000374cfe3:    %l0-3: 000003000328efc0 0000000000000010 000003000305ebc0 0000
    000000000000
      %l4-7: 00000000ee16f8a2 000000004d354cd9 0000030002434520 0000000000000097
    0x3000374dc63:  000002a10034b360 unix:putnext+21c (0, 3000305ebc0, 20, 0, 8, 8)
    0x3000374cea3:    %l0-3: 00000000012e43b4 0000030002434700 0000030002434520 0000
    000000000000
      %l4-7: 0000000000000000 00000000780321d0 00000300032aaa78 000003000305ebc0
    0x3000374cae3:  000002a10034b410 ip:ip_rput_local+c94 (3000305ebc0, 0, 3000375e6
    10, 0, 0, 3000305ebc0)
    0x30003018ee3:    %l0-3: 0000030003530638 000000007801e400 0000000000000000 0000
    0300035306a0
      %l4-7: 00000300032aaa78 0000030002a95cc8 000003000228ddb8 0000030000061130
    0x30003018c63:  000002a10034b570 ip:ip_rput+3bc (30002434298, 30000061130, 0, 30
    00375e610, 8, 8)
    0x30002236363:    %l0-3: 0000000000000000 0000030002a95cc8 0000030002a95cc8 0000
    03000305ebc0
      %l4-7: 000003000375e610 0000030000061130 0000030002434298 0000000000000000
    0x30002e71223:  000002a10034b640 unix:putnext+21c (0, 30002269f80, 1, 30002a93ed
    8, 16, 14)
    0x30003091ae3:    %l0-3: 0000000001274658 000003000226dee0 0000030002434298 0000
    000000000000
      %l4-7: 0000030002269f88 000000007801e830 00000300025a67b0 000003000305ebc0
    0x300030189e3:  000002a10034b6f0 pfil:pfilmodrput+5ac (300025a67b0, 3000305ebc0,
    20, 30002a93ed8, 0, d03f0000)
    0x30002e52c23:    %l0-3: 000000000005fb58 00000001ff1a50c0 0000030000399e10 0000
    0300002a5de8
      %l4-7: 00000300002a5d68 0000000078000000 0000000001496000 000003000305ebc0
    0x30003091d63:  000002a10034b820 unix:putnext+21c (0, 3000305ebc0, 300025b1cf0,
    3990, 10, 0)
    0x300030910e3:    %l0-3: 00000000013d9ce8 00000300025a6990 00000300025a67b0 0000
    000000000000
      %l4-7: 0000000000000000 0000000078052580 00000300025a7458 000003000305ebc0
    0x30002e71723:  000002a10034b8d0 eri:eri_read_dma+35c (3000305ebc0, ffff, 780501
    f4, 3e, fc00, 1)
    0x3000374db23:    %l0-3: 00000300025a7458 0000000000010000 0000000000001cc8 0000
    030002a2e640
      %l4-7: 000000000000003c 000003000266a000 00000300022f7990 0000000000020800
    0x3000374d763:  000002a10034b9c0 eri:eri_intr+414 (3000267a278, 1c000, 10220, 10
    278, 10290, 10270)
    0x300030900a3:    %l0-3: 000000000000001f 00000300022f7990 000003000266a000 0000
    0000000003ff
      %l4-7: 000003000267a2b8 00000300022f7990 0000000078050098 00000300022f4000
    0x30003091863:  000002a10034baa0 pcisch:pci_intr_wrapper+74 (30002254310, 21d, 3
    0002252000, 2a10034bd40, 43a0, 1218d90)
    0x30003090323:    %l0-3: 00000000013ce458 000003000257ba58 0000000000000000 0000
    000000000000
      %l4-7: 00000300002a5d68 00000300022f7870 0000000078000000 0000000078000000
    0x3000374d8a0:
    0x30003018123:  syncing file systems...
    =========There was installed pfil and ipf ver 4.1.5 (http://coombs.anu.edu.au/~avalon/ip-filter.html)
    Can Anyone help with avoid the problem in the future?
    Has anyone any idea?
    Greetings
    Daniel

    What does "$C" show for stack?
    Typically, this is a little different from console output.
    max

Maybe you are looking for

  • Skillbuilder modal page 2.0 causes a javascript error in APEX 4.2

    After installing the Skillbuilder's modal page 2.0 plugin in APEX 4.2, the following javascript error is shown. Line: 194 Error: Object doesn't support this property or method Using IE8 debugger the following code seems to be at fault. function(){ape

  • Can't import Serial Numbers with DTW

    Hi, I'm trying all day long to import data with the oInventoryGenEntry Template. I always got the error message : [IGN1.WhsCode][line: 1],'LS46BPPNB connot be released from stock without a full selection of serial/batch no.'Application-defined or obj

  • How do i update flash player plug-in?

    how do i update flash player plug-in and is it necessary?

  • Keyword problem - assigned kw from earlier versions won't work in 1.3

    All of my images are organized by keywords and I've just noticed that most of the keywords assigned in earlier versions of LR are not working. The keyword palette is there, it says there's x amount of photos with each keyword, a thumbnail displays in

  • 4G 5Spot Device

    When using an IPad2 with a third party wireless connection, will there be any charges on the verizon account.  The 4G/5Spot device is not being used.  It is off.