X120e - Aftermarket memory causing BSOD, unstable boot

Purchased a 4gb stick of GSkill memory (F3-10600CL9S-4GBSQ, CL9-9-9-24) hoping to get a little extra memory in my system. However, it seems to make my computer extremely unstable - restarting several times before getting to the login screen, flashing BSODS about sytem hangs and a memory error - both with and without the 2gb stick, and in both slots, often after waking from hibernation. I ran Memtest86+ and the windows memory test, and both seemed to pass alright. Since the 2gb stick by itself seems to work, I was planning on returning the new stick, but was wondering if you all knew of a more likely-to-work thing of memory for the computer.
Thanks for your help!

Buy the memory that has a Lenovo FRU number on it. You can buy direct from Lenovo or search for the memory FRU numbers and buy them from online retailers.
An additional advantage to buying a Lenovo FRU is that it's covered under the notebook's warranty, so if the memory goes bad during the warranty period, you can get a replacement from Lenovo without having to ship the bad part back first.

Similar Messages

  • Found: Intel Turbo Memory causing T61 wake-up from sleep / standby problems

    This is related to my earlier post, but I've found a new cause and thought to post a new message to make it easier for others to find it if they are running into similar problems.
    My system
    T61 model 7662-CTO (built July 2007)
    Vista Business w/ SP1 
    Nvidia Quadro NVS 140M (driver version:  7.15.11.7597)
    Intel Turbo Memory (driver version: 1.7.0.1029)
    Intel Wireless card 4965AGN (driver version: 11.5.0.36)
    Thinkpad BIOS (version 7LETC4WW,  2.24)
    no card reader or integrated webcam
    I was having problems with Vista failing to wake-up after being put into sleep (or standby) mode. Instead of returning to the desktop, the system immediately crashes and reboots. After many hours, I reformatted the drive and re-installed Vista (business edition). Before running the Lenovo system update, I installed Vista Service Pack 1, then I ran Windows Update and installed any remaining update hotfixes. (I never delayed restarting the machine when prompted)
    I incrementally began installing Lenovo drivers, and after the Power Management driver determined that hibernate was working.
    The 'sleep' option was unavailable until I installed the Nvidia Quadro NVS 140M drivers. Then sleep worked!
    Note: Intel Turbo Memory driver was uninstalled at this time.
    After all other lenovo programs were installed, I installed the driver for the Intel Turbo Memory. I put the computer to sleep, and it crashed/rebooted upon being woken up.
    I uninstalled the Turbo Memory driver from the Device Manager, and normal sleep -> wakeup function resumed.
    Because the sleep / standby feature requires the Nvidia Quadro drivers, and the Vista OS and the Intel Turbo Memory must properly work together for the turbo memory to work, I imagine the failure involves some driver mismatch between these three. I cannot recall now whether this issue was present when I first received the machine over a year ago (pre-installed Vista Ultimate, service pack 1 not even out yet). Perhaps Vista SP1 made some change that the Turbo Memory driver doesn't like, particularly with the Nvidia Quadro drivers in the mix too.
    Just FYI for anyone interested or curious.

    Remove the two aftermarket memory modules and observe the results.

  • Sat Pro 4300: BSOD on boot, avoided if delay

    Hi
    I have a Sat Pro 4300, running W2K SP4. Had it since 2001 with no problems.
    Recently I've been getting "unexpected kernel mode trap" and sometimes "ACPI BIOS not fully ACPI compliant" BSODs during boot (before it gets to any kind of graphics). Happens in safe and normal mode.
    By experimentation I've found that I get no BSOD and boot normally if I F2 during bootup and just hang arond for a while (five minutes or so), then boot.
    If I run a memory test after booting into the Ultimate Boot CD, sometimes I see a lot of bad memory, sometimes not. I think it depends how long I've waited before booting into the CD.
    Anyone like to hazard a guess whether this is hardware or software? I rather assume the former. I suppose it could be memory gone bad, or worse power regulation on the mainboard has begun to go.
    In either case probably not worth repairing, but I'd appreciate anyone's opinions.

    Hello
    I do not know for sure what the problem can be but replacement part for this oldie are not so expensive and you can try to make some experiments. Check eBay. There you can find everything possible. I can imagine the whole mainboard for this oldie should not be expensive.
    Check the prices and make decision.

  • BSOD on boot

    I have a p15 s420 that BSODs on boot. I can't boot to a CD to run memtest as it seems to ignore boot order. I have disabled booting to the HDD as well as network boot to force it to see the optical drive. It still however attepts a network boot. The optical drive doesn't seem to be working.
    My concern is at the BIOS page it reports: System Memory 640KB Extended Memory 510 MB.
    Is 640K the correct amount of system memory? Doesn't seem right.

    Where did you get it? Did you try restoring from recovery? Did it include any form of recovery?
    And I h8te hard disk backups and paid for OEM Disks they take away what little flexibility you get with installing stuff to different boxes when upgrading! And HDD can fail screwing yourself and OEM isint true install if OEM manufactuer does a crappy job.
    laptops- ex satillite l755-s5353 inspiron e1505 desktop dimension 400/300

  • Reader 9 causes BSOD on Windows XP Pro

    We have a few systems here that are having real problems with Adobe Reader 9. When the users attempt to open a .pdf file, they get a BSOD, and the system reboots. Once the system comes back up, they are able to open the offending file with no problems.
    Here are details of our systems:
    Dell Optiplex 755
    Windows XP Pro SP3
    2GB Ram
    32 Bit OS
    I have found this occurs most often when opening pdf's that were created with earlier versions.
    I'm sure I have left out some vital piece of information, so if you need clarification on something, please ask. Any suggestions would be greatly appreciated!

    [While the original post was for Reader 9, I found this same problem with Acrobat 9 Pro, and found a solution.]
    Problem: Opening one PDF file is fine, but once you open the second file -- BSOD.
    Cause: There is still a problem with Adobe's 2D GPU Acceleration feature.
    Per http://kb.adobe.com/selfservice/viewContent.do?externalId=kb405218&sliceId=1, "If acceleration hardware is detected, then optimization is enabled for all files except the first one opened when Acrobat launches." That is why the first file opens OK, but the second causes BSOD.  Adobe is either not detecting acceleration hardware correctly, or is not calling it correctly.
    Temporary Solution:
      1.  In Acrobat or Adobe Reader, choose to Edit > Preferences.
      2.  Go to the Page Display panel.
      3.  Uncheck Use 2D GPU acceleration.
    I tested my machine [Dell Optiplex 755, ATI Radion HD 2400 XT 8.420.0.0, Win XP Pro, Adobe 9 Pro] with "2D GPU acceleration" checked, attempted open of 4 PDFs from File Explorer -->first one opened, then BSOD, rebooted, unchecked "2D GPU", attempted the exact same operation --> all four opened in their windows and now I am happily typing on this page.
    This is per http://kb.adobe.com/selfservice/viewContent.do?externalId=324073, which is a post from two years ago and relates to Adobe 8.  So, Dell has been fielding calls on this for at least two years.  Way to stick in there, Dell.  Two years ago, Adobe knew the problem ("You are using an desktop ATI video card with driver version 8.291 or 8.301 and have the Acrobat Page Display Preference 'Use 2D GPU acceleration' enabled." was what they said back then, and recommended updating the video drivers.  So, Dell stays with it, Adobe says to update your drivers.  Well, I bought an entirely new Dell to get the latest drivers and it didn't help.
    Permanent solution:
    Adobe needs to get 2D GPU acceleration to really work (how about a line of code where you check whether it is going to work before you execute it?) or ship their product with that feature off by default.

  • Windows 2008 R2 DC Recovery Test BSOD on boot

    Hello everyone.
    first off i have a perfectly healthy production domain with 2 domain controllers and replication occurring between them, the only issue is there on the same site.
    i am in a test environment testing a scenario where both DC's are broken and i need to build a new one on new hardware, and all i have is a system state backup.
    following the instructions,
    Build a new machine closely matching the original machine hardware, (RAM and HDD size)
    install 2008r2. allocate static IP address and reboot in DRM
    add windows feature, windows server backup
    select restore in WSB and select the system state.
    DC then restores the data and askes to be rebooted.
    after the reboot i get a BSOD on boot and its seems to occur when to loading CLASSPNP.SYS file any suggestions on how to resolve this?
    also is there a way of building a DC, using DCPRMO then restoring the data to another location and then importing it into active directory.
    basically i need a plan that can be used in a total disaster scenario with a off site backup of the system state / backup as my only options.
    cheers
    Gordon

    Have you seen? Also make sure to install the exactly same operating system and service pack level
    http://support.microsoft.com/kb/249694/
    Enfo Zipper
    Christoffer Andersson – Principal Advisor
    http://blogs.chrisse.se - Directory Services Blog

  • Drivers cause BSOD {URGENT}

    Good day
    About 2 years ago I bought this laptop for a really good deal and i was impressed with the performance i got with it. Its quite a powerful and quality piece of tech.
    There are some drawbacks...
    In the two years ive had it ive formatted the laptop twice. Once to upgrade to windows 8.1,  and now because windows got corrupted and it didnt want to use a restore point. Which is normal for windows, it doesnt last forever.
    Drivers are a mess. Most i can gather is i'm suppose to download my laptop's drivers from here.
    http://support.hp.com/us-en/drivers/selfservice/HP​-Pavilion-dv6-Entertainment-Notebook-PC-series/522​...
    There are 3 different wireless lan drivers, the chipset drivers cause BSOD's, i can install every single driver on the list and i still have about 4 unknown devices in my device manager.
    Point is Im better off googling for the hardware ID's and scrubbing forums for my drivers.
    Please could Someone supply me a link where i can download a complete Driver DVD image for my laptop model that works.  I am more than willing to download a 1.4 gig torrent if it has proper work everytime drivers.
    Infact i would even drive to hp head office if they could supply me with a hardcopy.
    Help Please!
    Before i break something.
    Back on windows 7 btw

    Hi @Pixelite ,
    Thank you for visiting the HP Support Forums and Welcome. I have looked into your issue about your HP Pavilion dv6-7030ei Notebook and needing a recovery disk. Here is a link to show you how to and or order the Recovery Media you need.
    FWI: The driver page shows all drivers that were installed on all HP Pavilion  Notebooks.
    I would uninstall all the drivers with a yellow mark or caution on it. Restart the Notebook and if they are still there right click on the device and install or update the drivers.
    I hope this helps you out.
    Thanks.
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

  • Bios Update = BSOD on Boot

    Had a new one and I'm in the middle of repairing my windows install right now so I can at least backup.
    Updated to the new Bios due to a few minor issues I was experiencing and suddenly I load windows to a BSOD (before boot even completes) to a reboot (before I can even see the BSOD error) and loop.
    Tried dropping back to 1.1, no success.  Did everything I can think of, but I can't drop to one drive as I'm running RAID 0 and have stuff to back up...
    Just one big headache at the moment.  I've done thousands of bios updates and never had a situation like this.......
    EDIT: Adding System Config since my sig is dead temporarily....
    MSI K9A Platinum
    AMD X2 4600+ AM2
    2 x 1GB Crucial PC-4300 DDR2
    2 x 160GB Samsung SATA II in Raid 0 Configuration
    PowerColor ATI Radeon X1900XTX 512MB
    HP DVD-RW Drive
    Dual Samsung 940B LCD Monitors
    Logitech DiNovo Media Desktop Laser - Bluetooth

    Life is fun.  I dumped the system today and went to do a reinstall and believe I now know where the problem started.
    During the reinstall I attempted to use my original ATI Raid disk I made when I first recieved the board (based on catalyst 6.8 I believe).  BSOD during install with a driver error....
    So I tried the ones currently on MSI's site (6.9) and BSOD again during install. 
    All driver related....
    So, I downloaded 6.10 cats from ATI and extracted them to pull the drivers......
    Installing fine now.

  • Ntkrnlmp.exe causing BSOD randomly

    Recently we have been having random reboots and BSODs on our TS box
    Background:
    Windows Server 2012 R2 - RDS/Print/File - VM on Hyper-V Host (Windows server 2012 r2)
    https://onedrive.live.com/redir?resid=AF339BCAC63CB706!228&authkey=!AG-5gWy6tUwoAiE&ithint=folder%2c
    Attached are the dump files^^^
    Ran ran memtest86 on the host with no errors
    Ran Windows memory diags on host and VM with no errors
    Updated all firmware and drivers for our HP Proliant ML350 gen8 server
    Ran Driver Verifier and pointed it towards the problem child (ntoskrnl.exe) and the server bsod twice in a matter of ten minutes with, of course "Driver Verifier detected a Violation"
    Checked the version number Ntoskrnl.exe version 6.3.9600.16452 - Removed
    Windows Update Rollup - KB2903939
    Double checked and verified removed.
    Rebooted and ran Driver verifier after update removal - BSOD twice with same scenario as above. Disabled Driver verifier for now. 
    I'm hoping to find a fix for this as this is the main RDS server. 
    I appreciate your time. If you need anything else, please let me know. 
    Thanks!
    *Going to add another DUMP that happened today Below*
    Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Bitmap Dump File: Only kernel address space is available
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       .sympath SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: .sympath SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
    Windows 8 Kernel Version 9600 MP (6 procs) Free x64
    Product: Server, suite: TerminalServer
    Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
    Machine Name:
    Kernel base = 0xfffff802`1f286000 PsLoadedModuleList = 0xfffff802`1f54a990
    Debug session time: Fri Apr  4 16:32:20.197 2014 (UTC - 4:00)
    System Uptime: 0 days 6:36:23.236
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
    Loading Kernel Symbols
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 00007ff6`35f58018).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    ************* Symbol Loading Error Summary **************
    Module name            Error
    ntkrnlmp               The system cannot find the file specified
    You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
    You should also verify that your symbol search path (.sympath) is correct.
    *                        Bugcheck Analysis                                    *
    Use !analyze -v to get detailed debugging information.
    BugCheck 3B, {c0000005, fffff8021f2cc740, ffffd000276e0eb0, 0}
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***    Type referenced: nt!_KPRCB                                     ***
    Probably caused by : ntkrnlmp.exe ( nt!RtlAvlRemoveNode+478 )
    Followup: MachineOwner

    Thanks for the information.
    In case you do need to enable Driver Verifier, refer to the following:
    Driver Verifier:
    What is Driver Verifier?
    Driver Verifier is included in Windows 8/8.1, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows
    kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.
    Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.
    Before enabling Driver Verifier, it is recommended to create a System Restore Point:
    Vista - START | type rstrui - create a restore point
    Windows 7 - START | type create | select "Create a Restore Point"
    Windows 8/8.1 -
    http://www.eightforums.com/tutorials/4690-restore-point-create-windows-8-a.html
    How to enable Driver Verifier:
    Start > type "verifier" without the quotes > Select the following options -
    1. Select - "Create custom settings (for code developers)"
    2. Select - "Select individual settings from a full list"
    3. Check the following boxes -
    - Special Pool
    - Pool Tracking
    - Force IRQL Checking
    - Deadlock Detection
    - Security Checks (Windows 7 & 8)
    - DDI compliance checking (Windows 8)
    - Miscellaneous Checks
    4. Select  - "Select driver names from a list"
    5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
    6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
    7. Click on Finish.
    8. Restart.
    Important information regarding Driver Verifier:
    - If Driver Verifier finds a violation, the system will BSOD. To expand on this a bit more for the interested, specifically what Driver Verifier actually does is it looks for any driver making illegal function calls, causing memory leaks, etc. When and/if this
    happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled, it is monitoring
    all 3rd party drivers (as we have it set that way) and when it catches a driver attempting to do this, it will quickly flag that driver as being a troublemaker, and bring down the system safely before any corruption can occur.
    - After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will detect it in violation almost straight away, and
    as stated above, that will cause / force a BSOD.
    If this happens, do not panic, do the following:
    - Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
    - Once in Safe Mode - Start > Search > type "cmd" without the quotes.
    - To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
    ・    Restart and boot into normal Windows.
    If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:
    - Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
    - Once in Safe Mode - Start > type "system restore" without the quotes.
    - Choose the restore point you created earlier.
    -- Note that Safe Mode for Windows 8/8.1 is a bit different, and you may need to try different methods:
    5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1
    How long should I keep Driver Verifier enabled for?
    I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier. I will usually say whether or not I'd like for you to keep it enabled any longer.
    My system BSOD'd with Driver Verifier enabled, where can I find the crash dumps?
    They will be located in %systemroot%\Minidump
    Any other questions can most likely be answered by this article:
    http://support.microsoft.com/kb/244617
    Regards,
    Patrick

  • U305-S7448 memory upgrade / BSOD / PFN_LIST_corrupt

    My laptop came with 2x1GB Samsung DDR2-667 / PC2 5300 memory , Vista Home OS, from Toshiba.
    It originally had BIOS v2.5.  A search on Toshiba site showed me this has been revised many times, and is now at v5.10.  I downloaded and installed this version successfully before attempting memory upgrage.  Also, all drivers and OS updates are current, according to Win Vista auto update application.
    I've purchased 2x2GB Transcend DDR2-667 memory from Newegg.
    I've successfully installed 3GB of memory only - 1GB Samsung memory in Slot A, and either one of the 2 GB Transcend memory in Slot B (they'll both work in Slot B).
    I can verify the 3GB memory from the My Computer desktop icon, it's definitely there.
    If I attempt to install both 2GB memory for total of 4GB (2GB Transcend memory in Slots A and B), I get BSOD and PRN_LIST_Corrupt message, repeatedly.  If I boot into BIOS with F2 key, I can see that 4096mb of RAM is installed and read, at least at the BIOS level.
    Questions:
    1. Will my laptop (U305-S7448) actually accept 4GB RAM?  I get mixed messages on this from diligent googling.  Toshiba specs say 2048 max, but I have already proven that it WILL go to 3GB by actually trying the memory.   In fact, I've run the laptop for months with 3GB fine.  A big improvement over 2GB BTW.
    2. Do I need a specific proven brand of 2GB memory in both slots to get successful upgrade to 4GB total, or just in Slot A, and use my Transcend 2GB in Slot B.   Can someone recommend a proven memory brand for my laptop, that will definitely work?
    3. OT, but what does the teensy hidden partition on my laptop actually do?  I've thought of wiping the whole drive with Acronis Disk Director, consolidating into a single partition, and reinstalling either bare Vista without all the standard install bloatware, or perhaps Win XP or even the beta Win 7.  I'm not sure which drivers I'll have problems with in either of these OS.  Do I really need that hidden partition?
    Thanks in advance for any useful advice.
    Message Edited by seeker333 on 03-28-2009 02:20 PM

    You are having a Memory Configuration error.  Your specs are:Configured with 2048MB PC2-5300 DDR2 SDRAM (both memory slots
    may be occupied). Maximum capacity 2048MB
     t23
    Memory is tricky and Kingston has a compatabiity diagnostic which advises what will work on a Toshiba spcific model.  You have a T2310 unit and you are trying to force it to exceed board specs. Although the specs maybe the same ny tiny flaw in modeule output causes an error.  Try not to destroy the unit.
    Return the memory to Newegg unsure what their policy RMA is.  Agree you may see it but when you ty to run a program, the safety mechanisms kick in to shtdown the unit to prevent internal damage.  BE SAFE here.   
    Your query:      what does the teensy hidden partition on my laptop actually do?                                                                                                     
                                                                                                                                                                                                                                     response--it is there for the Recovery Disc and house reinstall avenues to setup.  The Recovery Disc works only for OS Vista.  If you decide to install XP your will need to hae a floppy acquired for reinstall of SATA HDD driver, plus drivers for hardware. There are some XP drivers for your unit listed at www.toshiba.com, download and input your model#, follw menu and search.  Good idea would be to copy down manuf's hardware name so that a reload and missing driver can be acquired.  Review other posts where we are continually putting advise to follow furnished by Jerry and others.

  • Usb 6501 unresponsive causing BSOD(Blue Screen Error)

    There are a lot posts about the same issue but mine is a little peculiar so i decided to post it.
    I am using two usb DAQ in the same pc(usb-6501, usb-6001), connected to the usb port on the back. The usb-6501 is used to obtain digital inputs from read switches, Sensors through an ssr. The usb-6001 is used to control 2 double valve solenoid, 1 dc motor, 2 indicator lamps. usb-6001 is also used to read analog values of current(using hall effect sensor) and voltage(using potentiometer).
    At first i was facing problems with the usb-6001(the usb-6501 was working fine at this point) resetting during operation accompanied by BSOD. Then i learned it was due to my relay, which requires 30 mA of current to switch so i used the ULN2003a to interface the usb-6001 with the relays and after that the application was running perfectly for 4 days.
    Now the usb-6501 is having the same problem and when i perform "Self Test" from NI MAX it shows "Error Code:50405" and i am able to reset the device from NI MAX only sometimes, other times i would have to unplug the USB device then plug it back in. As the application is used for an automated test rig the customer is frustrated by this problem. Once the card becomes unresponsive(or after the card is reset) BSOD occours.
    I have checked all the device drivers and OS for any errors but they are fine. i have even tried changing the ram to solve the BSOD with no use.
    System Details:
    Windows 7 SP1
    NI MAX 14.0
    power saving is disabled 
    I have attached the latest mini dump files as they might help in finding out the reason behind this problem(File extensions changed for the purpouse of uploading).
    I need to know: Is there any permanent solution for this problem? and what is the reason for this problem.
    Attachments:
    060115-12480-01.txt ‏315 KB
    053015-12324-01.txt ‏315 KB
    052615-17440-01.txt ‏315 KB

    Additional info : i did an analysis of the dump files and this is the result
    0: kd> !analyze -v
    * Bugcheck Analysis *
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: fffff88009fe10b1, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff8800657922e, address which referenced memory
    Debugging Details:
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c30e8
    fffff88009fe10b1
    CURRENT_IRQL: 2
    FAULTING_IP:
    nifslk+822e
    fffff880`0657922e 0fb650ff movzx edx,byte ptr [rax-1]
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    BUGCHECK_STR: 0xD1
    PROCESS_NAME: System
    TRAP_FRAME: fffff80000b9c6b0 -- (.trap 0xfffff80000b9c6b0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff88009fe10b2 rbx=0000000000000000 rcx=0000000000000000
    rdx=fffff80000b9c8e0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800657922e rsp=fffff80000b9c840 rbp=fffff88009fe10b1
    r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na po nc
    nifslk+0x822e:
    fffff880`0657922e 0fb650ff movzx edx,byte ptr [rax-1] ds:c8e0:fffff880`09fe10b1=??
    Resetting default scope
    LAST_CONTROL_TRANSFER: from fffff80003091be9 to fffff80003092640
    STACK_TEXT:
    fffff800`00b9c568 fffff800`03091be9 : 00000000`0000000a fffff880`09fe10b1 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff800`00b9c570 fffff800`03090860 : fffffa80`06adc250 fffffa80`05c3a060 fffffa80`06adc250 00000000`0000ffff : nt!KiBugCheckDispatch+0x69
    fffff800`00b9c6b0 fffff880`0657922e : fffff880`05d47468 fffff880`01d91f90 00000000`00000000 fffff880`09fe0770 : nt!KiPageFault+0x260
    fffff800`00b9c840 fffff880`05d47468 : fffff880`01d91f90 00000000`00000000 fffff880`09fe0770 fffff880`09fe17a0 : nifslk+0x822e
    fffff800`00b9c848 fffff880`01d91f90 : 00000000`00000000 fffff880`09fe0770 fffff880`09fe17a0 fffff880`09fe10b1 : 0xfffff880`05d47468
    fffff800`00b9c850 00000000`00000000 : fffff880`09fe0770 fffff880`09fe17a0 fffff880`09fe10b1 fffff800`00b9c8e0 : nipalk+0x75f90
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    nifslk+822e
    fffff880`0657922e 0fb650ff movzx edx,byte ptr [rax-1]
    SYMBOL_STACK_INDEX: 3
    SYMBOL_NAME: nifslk+822e
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nifslk
    IMAGE_NAME: nifslk.dll
    DEBUG_FLR_IMAGE_TIMESTAMP: 51f2daeb
    FAILURE_BUCKET_ID: X64_0xD1_nifslk+822e
    BUCKET_ID: X64_0xD1_nifslk+822e
    Can anyone help me with what this means?

  • [Solved] Unable to use all memory or unable to boot

    I solved this issue by uninstalling the Nouveau drivers. So if you have both the NVIDIA binary drivers and nouveau installed and the computer doesn't boot past the UDev uevents line, try uninstalling the nouveau drivers.
    Hello!
    I've been having some problems with my desktop PC, and was wondering if anybody knows how to fix these problems.
    First, my computer refuses to boot if I have my NVIDIA GeForce 8400 GS in the PCIe slot. It boots fine into Windows XP and 7.
    What happens is that the computer boots all the way to "Waiting for UDev uevents to be processed", where it locks up, ignoring keyboard input.
    I found that if I booted the computer with the option mem=6GB added to the kernel boot options, the computer boots properly. (Yes, I know, 6GB should be 6G)
    however, this reduces my usable memory to 4GB.
    This is what dmesg says:
    Memory: 4565500k/6291456k available (3312k kernel code, 1573636k absent, 151368k reserved, 1752k data, 472k init)
    If I remove the graphics card, the computer boots as normal, and shows all of my 6GB of ram.
    Here is my entire dmesg output:
    Linux version 2.6.32-ARCH (tobias@T-POWA-LX) (gcc version 4.4.2 20091208 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Jan 7 22:28:29 CET 2010
    Command line: root=/dev/sda1 mem=6GB ro
    KERNEL supported cpus:
    Intel GenuineIntel
    AMD AuthenticAMD
    Centaur CentaurHauls
    BIOS-provided physical RAM map:
    BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
    BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
    BIOS-e820: 00000000000e8000 - 0000000000100000 (reserved)
    BIOS-e820: 0000000000100000 - 000000009ffb0000 (usable)
    BIOS-e820: 000000009ffb0000 - 000000009ffc0000 (ACPI data)
    BIOS-e820: 000000009ffc0000 - 000000009fff0000 (ACPI NVS)
    BIOS-e820: 000000009fff0000 - 00000000a0000000 (reserved)
    BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
    BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved)
    BIOS-e820: 00000000ff380000 - 0000000100000000 (reserved)
    BIOS-e820: 0000000100000000 - 00000001d0000000 (usable)
    user-defined physical RAM map:
    user: 0000000000000000 - 000000000009fc00 (usable)
    user: 000000000009fc00 - 00000000000a0000 (reserved)
    user: 00000000000e8000 - 0000000000100000 (reserved)
    user: 0000000000100000 - 000000009ffb0000 (usable)
    user: 000000009ffb0000 - 000000009ffc0000 (ACPI data)
    user: 000000009ffc0000 - 000000009fff0000 (ACPI NVS)
    user: 000000009fff0000 - 00000000a0000000 (reserved)
    user: 00000000fec00000 - 00000000fec01000 (reserved)
    user: 00000000fee00000 - 00000000fef00000 (reserved)
    user: 00000000ff380000 - 0000000100000000 (reserved)
    user: 0000000100000000 - 0000000180000000 (usable)
    DMI present.
    AMI BIOS detected: BIOS may corrupt low RAM, working around it.
    e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
    last_pfn = 0x180000 max_arch_pfn = 0x400000000
    MTRR default type: uncachable
    MTRR fixed ranges enabled:
    00000-9FFFF write-back
    A0000-EFFFF uncachable
    F0000-FFFFF write-protect
    MTRR variable ranges enabled:
    0 base 0000000000 mask FF80000000 write-back
    1 base 0080000000 mask FFE0000000 write-back
    2 base 00A0000000 mask FFF0000000 write-back
    3 disabled
    4 disabled
    5 disabled
    6 disabled
    7 disabled
    TOM2: 00000001d0000000 aka 7424M
    x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    e820 update range: 00000000b0000000 - 0000000100000000 (usable) ==> (reserved)
    last_pfn = 0x9ffb0 max_arch_pfn = 0x400000000
    Scanning 0 areas for low memory corruption
    modified physical RAM map:
    modified: 0000000000000000 - 0000000000010000 (reserved)
    modified: 0000000000010000 - 000000000009fc00 (usable)
    modified: 000000000009fc00 - 00000000000a0000 (reserved)
    modified: 00000000000e8000 - 0000000000100000 (reserved)
    modified: 0000000000100000 - 000000009ffb0000 (usable)
    modified: 000000009ffb0000 - 000000009ffc0000 (ACPI data)
    modified: 000000009ffc0000 - 000000009fff0000 (ACPI NVS)
    modified: 000000009fff0000 - 00000000a0000000 (reserved)
    modified: 00000000fec00000 - 00000000fec01000 (reserved)
    modified: 00000000fee00000 - 00000000fef00000 (reserved)
    modified: 00000000ff380000 - 0000000100000000 (reserved)
    modified: 0000000100000000 - 0000000180000000 (usable)
    initial memory mapped : 0 - 20000000
    init_memory_mapping: 0000000000000000-000000009ffb0000
    0000000000 - 009fe00000 page 2M
    009fe00000 - 009ffb0000 page 4k
    kernel direct mapping tables up to 9ffb0000 @ 10000-15000
    init_memory_mapping: 0000000100000000-0000000180000000
    0100000000 - 0180000000 page 2M
    kernel direct mapping tables up to 180000000 @ 13000-1a000
    RAMDISK: 37f59000 - 37fef385
    ACPI: RSDP 00000000000fa870 00014 (v00 ACPIAM)
    ACPI: RSDT 000000009ffb0000 00038 (v01 A_M_I OEMRSDT 08000708 MSFT 00000097)
    ACPI: FACP 000000009ffb0200 00084 (v02 A M I OEMFACP 12000601 MSFT 00000097)
    ACPI: DSDT 000000009ffb0440 04C5F (v01 ALV6V ALV6V172 00000172 INTL 20051117)
    ACPI: FACS 000000009ffc0000 00040
    ACPI: APIC 000000009ffb0390 00070 (v01 A_M_I OEMAPIC 08000708 MSFT 00000097)
    ACPI: MCFG 000000009ffb0400 0003C (v01 A_M_I OEMMCFG 08000708 MSFT 00000097)
    ACPI: OEMB 000000009ffc0040 00060 (v01 A_M_I AMI_OEM 08000708 MSFT 00000097)
    ACPI: SSDT 000000009ffb50a0 00206 (v01 A M I POWERNOW 00000001 AMD 00000001)
    ACPI: Local APIC address 0xfee00000
    (8 early reservations) ==> bootmem [0000000000 - 0180000000]
    #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
    #1 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000]
    #2 [0001000000 - 000169c898] TEXT DATA BSS ==> [0001000000 - 000169c898]
    #3 [0037f59000 - 0037fef385] RAMDISK ==> [0037f59000 - 0037fef385]
    #4 [000009fc00 - 0000100000] BIOS reserved ==> [000009fc00 - 0000100000]
    #5 [000169d000 - 000169d12b] BRK ==> [000169d000 - 000169d12b]
    #6 [0000010000 - 0000013000] PGTABLE ==> [0000010000 - 0000013000]
    #7 [0000013000 - 0000015000] PGTABLE ==> [0000013000 - 0000015000]
    found SMP MP-table at [ffff8800000ff780] ff780
    [ffffea0000000000-ffffea00053fffff] PMD -> [ffff880001800000-ffff8800057fffff] on node 0
    Zone PFN ranges:
    DMA 0x00000010 -> 0x00001000
    DMA32 0x00001000 -> 0x00100000
    Normal 0x00100000 -> 0x00180000
    Movable zone start PFN for each node
    early_node_map[3] active PFN ranges
    0: 0x00000010 -> 0x0000009f
    0: 0x00000100 -> 0x0009ffb0
    0: 0x00100000 -> 0x00180000
    On node 0 totalpages: 1179455
    DMA zone: 56 pages used for memmap
    DMA zone: 104 pages reserved
    DMA zone: 3823 pages, LIFO batch:0
    DMA32 zone: 14280 pages used for memmap
    DMA32 zone: 636904 pages, LIFO batch:31
    Normal zone: 7168 pages used for memmap
    Normal zone: 517120 pages, LIFO batch:31
    Nvidia board detected. Ignoring ACPI timer override.
    If you got timer trouble try acpi_use_timer_override
    Detected use of extended apic ids on hypertransport bus
    ACPI: PM-Timer IO Port: 0x4008
    ACPI: Local APIC address 0xfee00000
    ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
    ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
    IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
    ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    ACPI: BIOS IRQ0 pin2 override ignored.
    ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
    ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
    ACPI: IRQ9 used by override.
    ACPI: IRQ14 used by override.
    ACPI: IRQ15 used by override.
    Using ACPI (MADT) for SMP configuration information
    SMP: Allowing 2 CPUs, 0 hotplug CPUs
    nr_irqs_gsi: 24
    PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    PM: Registered nosave memory: 00000000000a0000 - 00000000000e8000
    PM: Registered nosave memory: 00000000000e8000 - 0000000000100000
    PM: Registered nosave memory: 000000009ffb0000 - 000000009ffc0000
    PM: Registered nosave memory: 000000009ffc0000 - 000000009fff0000
    PM: Registered nosave memory: 000000009fff0000 - 00000000a0000000
    PM: Registered nosave memory: 00000000a0000000 - 00000000fec00000
    PM: Registered nosave memory: 00000000fec00000 - 00000000fec01000
    PM: Registered nosave memory: 00000000fec01000 - 00000000fee00000
    PM: Registered nosave memory: 00000000fee00000 - 00000000fef00000
    PM: Registered nosave memory: 00000000fef00000 - 00000000ff380000
    PM: Registered nosave memory: 00000000ff380000 - 0000000100000000
    Allocating PCI resources starting at a0000000 (gap: a0000000:5ec00000)
    Booting paravirtualized kernel on bare hardware
    NR_CPUS:16 nr_cpumask_bits:16 nr_cpu_ids:2 nr_node_ids:1
    PERCPU: Embedded 29 pages/cpu @ffff880005a00000 s89048 r8192 d21544 u1048576
    pcpu-alloc: s89048 r8192 d21544 u1048576 alloc=1*2097152
    pcpu-alloc: [0] 0 1
    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1157847
    Kernel command line: root=/dev/sda1 mem=6GB ro
    PID hash table entries: 4096 (order: 3, 32768 bytes)
    Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
    Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
    Initializing CPU#0
    Checking aperture...
    No AGP bridge found
    Node 0: aperture @ 20000000 size 32 MB
    Aperture pointing to e820 RAM. Ignoring.
    Your BIOS doesn't leave a aperture memory hole
    Please enable the IOMMU option in the BIOS setup
    This costs you 64 MB of RAM
    Mapping aperture over 65536 KB of RAM @ 20000000
    PM: Registered nosave memory: 0000000020000000 - 0000000024000000
    Memory: 4565500k/6291456k available (3312k kernel code, 1573636k absent, 151368k reserved, 1752k data, 472k init)
    SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
    Hierarchical RCU implementation.
    NR_IRQS:768
    spurious 8259A interrupt: IRQ7.
    Console: colour VGA+ 80x25
    console [tty0] enabled
    Fast TSC calibration using PIT
    Detected 2209.953 MHz processor.
    Calibrating delay loop (skipped), value calculated using timer frequency.. 4421.06 BogoMIPS (lpj=7366510)
    Security Framework initialized
    Mount-cache hash table entries: 256
    CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    CPU: L2 Cache: 512K (64 bytes/line)
    tseg: 0000000000
    CPU: Physical Processor ID: 0
    CPU: Processor Core ID: 0
    mce: CPU supports 5 MCE banks
    using C1E aware idle routine
    Performance Events: AMD PMU driver.
    ... version: 0
    ... bit width: 48
    ... generic registers: 4
    ... value mask: 0000ffffffffffff
    ... max period: 00007fffffffffff
    ... fixed-purpose events: 0
    ... event mask: 000000000000000f
    ACPI: Core revision 20090903
    Setting APIC routing to flat
    ..TIMER: vector=0x30 apic1=0 pin1=0 apic2=-1 pin2=-1
    CPU0: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ stepping 02
    Booting processor 1 APIC 0x1 ip 0x6000
    Initializing CPU#1
    Calibrating delay using timer specific routine.. 4421.68 BogoMIPS (lpj=7365900)
    CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    CPU: L2 Cache: 512K (64 bytes/line)
    CPU: Physical Processor ID: 0
    CPU: Processor Core ID: 1
    CPU1: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ stepping 02
    Brought up 2 CPUs
    Total of 2 processors activated (8842.75 BogoMIPS).
    CPU0 attaching sched-domain:
    domain 0: span 0-1 level MC
    groups: 0 1
    CPU1 attaching sched-domain:
    domain 0: span 0-1 level MC
    groups: 1 0
    NET: Registered protocol family 16
    node 0 link 0: io port [1000, ffffff]
    TOM: 00000000b0000000 aka 2816M
    node 0 link 0: mmio [e0000000, efffffff]
    node 0 link 0: mmio [a0000, bffff]
    node 0 link 0: mmio [b0000000, fe0bffff]
    TOM2: 00000001d0000000 aka 7424M
    bus: [00,ff] on node 0 link 0
    bus: 00 index 0 io port: [0, ffff]
    bus: 00 index 1 mmio: [b0000000, ffffffff]
    bus: 00 index 2 mmio: [a0000, bffff]
    bus: 00 index 3 mmio: [1d0000000, fcffffffff]
    ACPI: bus type pci registered
    PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
    PCI: Not using MMCONFIG.
    PCI: Using configuration type 1 for base access
    bio: create slab <bio-0> at 0
    ACPI: EC: Look up EC in DSDT
    ACPI: Executed 1 blocks of module-level executable AML code
    ACPI: Interpreter enabled
    ACPI: (supports S0 S1 S4 S5)
    ACPI: Using IOAPIC for interrupt routing
    PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
    PCI: MCFG area at e0000000 reserved in ACPI motherboard resources
    PCI: Using MMCONFIG at e0000000 - efffffff
    ACPI Warning: Incorrect checksum in table [OEMB] - C5, should be 96 (20090903/tbutils-314)
    ACPI: No dock devices found.
    ACPI: PCI Root Bridge [PCI0] (0000:00)
    pci 0000:00:01.1: reg 10 io port: [0xdc00-0xdc3f]
    pci 0000:00:01.1: reg 20 io port: [0x5000-0x503f]
    pci 0000:00:01.1: reg 24 io port: [0x6000-0x603f]
    pci 0000:00:01.1: PME# supported from D3hot D3cold
    pci 0000:00:01.1: PME# disabled
    pci 0000:00:02.0: reg 10 32bit mmio: [0xdbfff000-0xdbffffff]
    pci 0000:00:02.0: supports D1 D2
    pci 0000:00:02.0: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:00:02.0: PME# disabled
    pci 0000:00:02.1: reg 10 32bit mmio: [0xdbffec00-0xdbffecff]
    pci 0000:00:02.1: supports D1 D2
    pci 0000:00:02.1: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:00:02.1: PME# disabled
    pci 0000:00:05.0: reg 10 32bit mmio: [0xdbff8000-0xdbffbfff]
    pci 0000:00:05.0: PME# supported from D3hot D3cold
    pci 0000:00:05.0: PME# disabled
    pci 0000:00:07.0: reg 10 32bit mmio: [0xdbffd000-0xdbffdfff]
    pci 0000:00:07.0: reg 14 io port: [0xd480-0xd487]
    pci 0000:00:07.0: supports D1 D2
    pci 0000:00:07.0: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:00:07.0: PME# disabled
    pci 0000:00:08.0: reg 10 io port: [0xe00-0xe07]
    pci 0000:00:08.0: reg 14 io port: [0xe20-0xe23]
    pci 0000:00:08.0: reg 18 io port: [0xe40-0xe47]
    pci 0000:00:08.0: reg 1c io port: [0xe60-0xe63]
    pci 0000:00:08.0: reg 20 io port: [0xc880-0xc88f]
    pci 0000:00:08.0: reg 24 32bit mmio: [0xdbffc000-0xdbffcfff]
    pci 0000:00:08.1: reg 10 io port: [0xe80-0xe87]
    pci 0000:00:08.1: reg 14 io port: [0xea0-0xea3]
    pci 0000:00:08.1: reg 18 io port: [0xec0-0xec7]
    pci 0000:00:08.1: reg 1c io port: [0xee0-0xee3]
    pci 0000:00:08.1: reg 20 io port: [0xc000-0xc00f]
    pci 0000:00:08.1: reg 24 32bit mmio: [0xdbff7000-0xdbff7fff]
    pci 0000:00:09.0: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:00:09.0: PME# disabled
    pci 0000:00:0b.0: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:00:0b.0: PME# disabled
    pci 0000:00:0c.0: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:00:0c.0: PME# disabled
    pci 0000:00:0d.0: reg 10 32bit mmio: [0xda000000-0xdaffffff]
    pci 0000:00:0d.0: reg 14 64bit mmio pref: [0xb0000000-0xbfffffff]
    pci 0000:00:0d.0: reg 1c 64bit mmio: [0xd9000000-0xd9ffffff]
    pci 0000:00:0d.0: reg 30 32bit mmio pref: [0xdbfc0000-0xdbfdffff]
    pci 0000:00:04.0: transparent bridge
    pci 0000:02:00.0: reg 10 32bit mmio: [0xdf000000-0xdfffffff]
    pci 0000:02:00.0: reg 14 64bit mmio pref: [0xc0000000-0xcfffffff]
    pci 0000:02:00.0: reg 1c 64bit mmio: [0xdc000000-0xddffffff]
    pci 0000:02:00.0: reg 24 io port: [0xec00-0xec7f]
    pci 0000:02:00.0: reg 30 32bit mmio pref: [0xdefe0000-0xdeffffff]
    pci 0000:00:09.0: bridge io port: [0xe000-0xefff]
    pci 0000:00:09.0: bridge 32bit mmio: [0xdc000000-0xdfffffff]
    pci 0000:00:09.0: bridge 64bit mmio pref: [0xc0000000-0xcfffffff]
    pci_bus 0000:00: on NUMA node 0
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.BR10._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.BR11._PRT]
    ACPI: PCI Interrupt Link [LNKA] (IRQs 16 17 18 19) *0, disabled.
    ACPI: PCI Interrupt Link [LNKB] (IRQs 16 17 18 19) *0, disabled.
    ACPI: PCI Interrupt Link [LNKC] (IRQs 16 17 18 19) *0, disabled.
    ACPI: PCI Interrupt Link [LNKD] (IRQs 16 17 18 19) *0, disabled.
    ACPI: PCI Interrupt Link [LNEA] (IRQs 16 17 18 19) *0, disabled.
    ACPI: PCI Interrupt Link [LNEB] (IRQs 16 17 18 19) *0, disabled.
    ACPI: PCI Interrupt Link [LNEC] (IRQs 16 17 18 19) *0, disabled.
    ACPI: PCI Interrupt Link [LNED] (IRQs 16 17 18 19) *10
    ACPI: PCI Interrupt Link [LUB0] (IRQs 20 21 22 23) *14
    ACPI: PCI Interrupt Link [LUB2] (IRQs 20 21 22 23) *10
    ACPI: PCI Interrupt Link [LMAC] (IRQs 20 21 22 23) *14
    ACPI: PCI Interrupt Link [LAZA] (IRQs 20 21 22 23) *11
    ACPI: PCI Interrupt Link [LACI] (IRQs 20 21 22 23) *0, disabled.
    ACPI: PCI Interrupt Link [LMC9] (IRQs 20 21 22 23) *11
    ACPI: PCI Interrupt Link [LSMB] (IRQs 20 21 22 23) *11
    ACPI: PCI Interrupt Link [LPMU] (IRQs 20 21 22 23) *0, disabled.
    ACPI: PCI Interrupt Link [LSA0] (IRQs 20 21 22 23) *14
    ACPI: PCI Interrupt Link [LSA1] (IRQs 20 21 22 23) *10
    ACPI: PCI Interrupt Link [LATA] (IRQs 20 21 22 23) *0, disabled.
    vgaarb: device added: PCI:0000:00:0d.0,decodes=io+mem,owns=none,locks=none
    vgaarb: device added: PCI:0000:02:00.0,decodes=io+mem,owns=io+mem,locks=none
    vgaarb: loaded
    PCI: Using ACPI for IRQ routing
    NetLabel: Initializing
    NetLabel: domain hash size = 128
    NetLabel: protocols = UNLABELED CIPSOv4
    NetLabel: unlabeled traffic allowed by default
    Switching to clocksource jiffies
    pnp: PnP ACPI init
    ACPI: bus type pnp registered
    pnp: PnP ACPI: found 16 devices
    ACPI: ACPI bus type pnp unregistered
    system 00:09: ioport range 0x4d0-0x4d1 has been reserved
    system 00:09: ioport range 0x800-0x80f has been reserved
    system 00:09: ioport range 0x4000-0x407f has been reserved
    system 00:09: ioport range 0x4080-0x40ff has been reserved
    system 00:09: ioport range 0x4400-0x447f has been reserved
    system 00:09: ioport range 0x4480-0x44ff has been reserved
    system 00:09: ioport range 0x4800-0x487f has been reserved
    system 00:09: ioport range 0x4880-0x48ff has been reserved
    system 00:09: ioport range 0x2000-0x207f has been reserved
    system 00:09: ioport range 0x2080-0x20ff has been reserved
    system 00:09: iomem range 0xfefe0000-0xfefe01ff has been reserved
    system 00:09: iomem range 0xfefe1000-0xfefe1fff has been reserved
    system 00:09: iomem range 0xfee01000-0xfeefffff has been reserved
    system 00:0a: iomem range 0xfec00000-0xfec00fff could not be reserved
    system 00:0a: iomem range 0xfee00000-0xfee00fff has been reserved
    system 00:0d: ioport range 0x290-0x29f has been reserved
    system 00:0e: iomem range 0xe0000000-0xefffffff has been reserved
    system 00:0f: iomem range 0x0-0x9ffff could not be reserved
    system 00:0f: iomem range 0xc0000-0xcffff has been reserved
    system 00:0f: iomem range 0xe0000-0xfffff could not be reserved
    system 00:0f: iomem range 0x100000-0xafffffff could not be reserved
    system 00:0f: iomem range 0xff380000-0xffffffff has been reserved
    Switching to clocksource acpi_pm
    pci 0000:00:04.0: PCI bridge, secondary bus 0000:01
    pci 0000:00:04.0: IO window: disabled
    pci 0000:00:04.0: MEM window: disabled
    pci 0000:00:04.0: PREFETCH window: disabled
    pci 0000:00:09.0: PCI bridge, secondary bus 0000:02
    pci 0000:00:09.0: IO window: 0xe000-0xefff
    pci 0000:00:09.0: MEM window: 0xdc000000-0xdfffffff
    pci 0000:00:09.0: PREFETCH window: 0x000000c0000000-0x000000cfffffff
    pci 0000:00:0b.0: PCI bridge, secondary bus 0000:03
    pci 0000:00:0b.0: IO window: disabled
    pci 0000:00:0b.0: MEM window: disabled
    pci 0000:00:0b.0: PREFETCH window: disabled
    pci 0000:00:0c.0: PCI bridge, secondary bus 0000:04
    pci 0000:00:0c.0: IO window: disabled
    pci 0000:00:0c.0: MEM window: disabled
    pci 0000:00:0c.0: PREFETCH window: disabled
    pci 0000:00:04.0: setting latency timer to 64
    pci 0000:00:09.0: setting latency timer to 64
    pci 0000:00:0b.0: setting latency timer to 64
    pci 0000:00:0c.0: setting latency timer to 64
    pci_bus 0000:00: resource 0 io: [0x00-0xffff]
    pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffffffffffff]
    pci_bus 0000:01: resource 3 io: [0x00-0xffff]
    pci_bus 0000:01: resource 4 mem: [0x000000-0xffffffffffffffff]
    pci_bus 0000:02: resource 0 io: [0xe000-0xefff]
    pci_bus 0000:02: resource 1 mem: [0xdc000000-0xdfffffff]
    pci_bus 0000:02: resource 2 pref mem [0xc0000000-0xcfffffff]
    NET: Registered protocol family 2
    IP route cache hash table entries: 262144 (order: 9, 2097152 bytes)
    TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
    TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    TCP: Hash tables configured (established 262144 bind 65536)
    TCP reno registered
    NET: Registered protocol family 1
    pci 0000:00:00.0: Found enabled HT MSI Mapping
    pci 0000:00:00.0: Found enabled HT MSI Mapping
    pci 0000:00:00.0: Found enabled HT MSI Mapping
    pci 0000:00:00.0: Found enabled HT MSI Mapping
    pci 0000:00:00.0: Found enabled HT MSI Mapping
    pci 0000:00:00.0: Found enabled HT MSI Mapping
    pci 0000:00:00.0: Found enabled HT MSI Mapping
    pci 0000:00:00.0: Found enabled HT MSI Mapping
    pci 0000:02:00.0: Boot video device
    Unpacking initramfs...
    Freeing initrd memory: 600k freed
    PCI-DMA: Disabling AGP.
    PCI-DMA: aperture base @ 20000000 size 65536 KB
    PCI-DMA: using GART IOMMU.
    PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
    Scanning for low memory corruption every 60 seconds
    audit: initializing netlink socket (disabled)
    type=2000 audit(1263386771.770:1): initialized
    VFS: Disk quotas dquot_6.5.2
    Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    msgmni has been set to 8920
    alg: No test for stdrng (krng)
    Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    pcieport 0000:00:09.0: irq 24 for MSI/MSI-X
    pcieport 0000:00:09.0: setting latency timer to 64
    pcieport 0000:00:0b.0: irq 25 for MSI/MSI-X
    pcieport 0000:00:0b.0: setting latency timer to 64
    pcieport 0000:00:0c.0: irq 26 for MSI/MSI-X
    pcieport 0000:00:0c.0: setting latency timer to 64
    Linux agpgart interface v0.103
    Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
    00:0c: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    input: Macintosh mouse button emulation as /devices/virtual/input/input0
    PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
    PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
    serio: i8042 KBD port at 0x60,0x64 irq 1
    mice: PS/2 mouse device common for all mice
    cpuidle: using governor ladder
    cpuidle: using governor menu
    TCP cubic registered
    NET: Registered protocol family 17
    PM: Resume from disk failed.
    registered taskstats version 1
    Initalizing network drop monitor service
    Freeing unused kernel memory: 472k freed
    input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
    SCSI subsystem initialized
    libata version 3.00 loaded.
    sata_nv 0000:00:08.0: version 3.5
    ACPI: PCI Interrupt Link [LSA0] enabled at IRQ 23
    sata_nv 0000:00:08.0: PCI INT A -> Link[LSA0] -> GSI 23 (level, low) -> IRQ 23
    sata_nv 0000:00:08.0: setting latency timer to 64
    scsi0 : sata_nv
    scsi1 : sata_nv
    ata1: SATA max UDMA/133 cmd 0xe00 ctl 0xe20 bmdma 0xc880 irq 23
    ata2: SATA max UDMA/133 cmd 0xe40 ctl 0xe60 bmdma 0xc888 irq 23
    ACPI: PCI Interrupt Link [LSA1] enabled at IRQ 22
    sata_nv 0000:00:08.1: PCI INT B -> Link[LSA1] -> GSI 22 (level, low) -> IRQ 22
    sata_nv 0000:00:08.1: setting latency timer to 64
    scsi2 : sata_nv
    scsi3 : sata_nv
    ata3: SATA max UDMA/133 cmd 0xe80 ctl 0xea0 bmdma 0xc000 irq 22
    ata4: SATA max UDMA/133 cmd 0xec0 ctl 0xee0 bmdma 0xc008 irq 22
    Floppy drive(s): fd0 is 1.44M
    FDC 0 is a post-1991 82077
    ata3: SATA link down (SStatus 0 SControl 300)
    ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ata1.00: ATA-7: WDC WD3200AAKS-00SBA0, 12.01B01, max UDMA/133
    ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 0/32)
    ata1.00: configured for UDMA/133
    scsi 0:0:0:0: Direct-Access ATA WDC WD3200AAKS-0 12.0 PQ: 0 ANSI: 5
    ata2: SATA link down (SStatus 0 SControl 300)
    ata4: SATA link down (SStatus 0 SControl 300)
    sd 0:0:0:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sda: sda1 sda2 sda3 sda4 < sda5 >
    sd 0:0:0:0: [sda] Attached SCSI disk
    EXT3-fs: mounted filesystem with writeback data mode.
    kjournald starting. Commit interval 5 seconds
    Driver 'rtc_cmos' needs updating - please use bus_type methods
    rtc_cmos 00:02: RTC can wake from S4
    rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
    rtc0: alarms up to one year, y3k, 114 bytes nvram
    udev: starting version 146
    input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
    ACPI: Power Button [PWRB]
    input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
    ACPI: Power Button [PWRF]
    NET: Registered protocol family 23
    sd 0:0:0:0: Attached scsi generic sg0 type 0
    processor LNXCPU:00: registered as cooling_device0
    input: PC Speaker as /devices/platform/pcspkr/input/input4
    processor LNXCPU:01: registered as cooling_device1
    lp: driver loaded but no devices found
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    nvidia: module license 'NVIDIA' taints kernel.
    Disabling lock debugging due to kernel taint
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    ACPI: PCI Interrupt Link [LUB2] enabled at IRQ 21
    ehci_hcd 0000:00:02.1: PCI INT B -> Link[LUB2] -> GSI 21 (level, low) -> IRQ 21
    ehci_hcd 0000:00:02.1: setting latency timer to 64
    ehci_hcd 0000:00:02.1: EHCI Host Controller
    ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1
    ehci_hcd 0000:00:02.1: debug port 1
    ehci_hcd 0000:00:02.1: cache line size of 64 is not supported
    ehci_hcd 0000:00:02.1: irq 21, io mem 0xdbffec00
    parport_pc 00:07: reported by Plug and Play ACPI
    parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
    ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 10 ports detected
    i2c i2c-0: nForce2 SMBus adapter at 0x5000
    i2c i2c-1: nForce2 SMBus adapter at 0x6000
    k8temp 0000:00:18.3: Temperature readouts might be wrong - check erratum #141
    forcedeth: Reverse Engineered nForce ethernet driver. Version 0.64.
    ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 20
    forcedeth 0000:00:07.0: PCI INT A -> Link[LMAC] -> GSI 20 (level, low) -> IRQ 20
    forcedeth 0000:00:07.0: setting latency timer to 64
    EDAC MC: Ver: 2.1.0 Jan 7 2010
    ppdev: user-space parallel port driver
    lp0: using parport0 (interrupt-driven).
    ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    EDAC amd64_edac: Ver: 3.2.0 Jan 7 2010
    device-mapper: uevent: version 1.0.3
    device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: [email protected]
    [drm] Initialized drm 1.1.0 20060810
    w83627ehf: Found W83627EHG chip at 0x290
    forcedeth 0000:00:07.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:19:66:46:79:3b
    forcedeth 0000:00:07.0: highdma pwrctl mgmt lnktim msi desc-v3
    ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 23
    HDA Intel 0000:00:05.0: PCI INT B -> Link[LAZA] -> GSI 23 (level, low) -> IRQ 23
    HDA Intel 0000:00:05.0: setting latency timer to 64
    hda_codec: ALC888: BIOS auto-probing.
    input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:05.0/input/input5
    ACPI: PCI Interrupt Link [LUB0] enabled at IRQ 22
    ohci_hcd 0000:00:02.0: PCI INT A -> Link[LUB0] -> GSI 22 (level, low) -> IRQ 22
    ohci_hcd 0000:00:02.0: setting latency timer to 64
    ohci_hcd 0000:00:02.0: OHCI Host Controller
    ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
    ohci_hcd 0000:00:02.0: irq 22, io mem 0xdbfff000
    usb usb2: configuration #1 chosen from 1 choice
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 10 ports detected
    EDAC amd64: This node reports that Memory ECC is currently disabled, set F3x44[22] (0000:00:18.3).
    EDAC amd64: WARNING: ECC is disabled by BIOS. Module will NOT be loaded.
    Either Enable ECC in the BIOS, or set 'ecc_enable_override'.
    Also, use of the override can cause unknown side effects.
    amd64_edac: probe of 0000:00:18.2 failed with error -22
    nvidia 0000:00:0d.0: enabling device (0000 -> 0002)
    ACPI: PCI Interrupt Link [LMC9] enabled at IRQ 21
    nvidia 0000:00:0d.0: PCI INT A -> Link[LMC9] -> GSI 21 (level, low) -> IRQ 21
    nvidia 0000:00:0d.0: setting latency timer to 64
    ACPI: PCI Interrupt Link [LNED] enabled at IRQ 19
    nvidia 0000:02:00.0: PCI INT A -> Link[LNED] -> GSI 19 (level, low) -> IRQ 19
    nvidia 0000:02:00.0: setting latency timer to 64
    NVRM: loading NVIDIA UNIX x86_64 Kernel Module 190.53 Wed Dec 9 15:29:46 PST 2009
    usb 2-4: new low speed USB device using ohci_hcd and address 2
    usb 2-4: configuration #1 chosen from 1 choice
    usbcore: registered new interface driver hiddev
    input: USB Mouse as /devices/pci0000:00/0000:00:02.0/usb2/2-4/2-4:1.0/input/input6
    generic-usb 0003:15D9:0A37.0001: input,hidraw0: USB HID v1.10 Mouse [USB Mouse] on usb-0000:00:02.0-4/input0
    usbcore: registered new interface driver usbhid
    usbhid: v2.6:USB HID core driver
    EXT3 FS on sda1, internal journal
    Adding 2650684k swap on /dev/sda5. Priority:-1 extents:1 across:2650684k
    forcedeth 0000:00:07.0: irq 27 for MSI/MSI-X
    NET: Registered protocol family 10
    lo: Disabled Privacy Extensions
    eth0: no IPv6 routers present
    Any thoughts or suggestions would be much appreciated.
    Last edited by xentalion (2010-01-14 14:38:15)

    Also, (don't know if this is relevant) but I've got three sticks of ram: 2 2GB modules and 2 1GB modules. They are grouped together properly.

  • MB Pro 13 (2010) BSOD in Boot Camp followed by question mark folder

    Hello, good folks of the Apple support communities. Let me describe my problem to you guys and maybe you'll help me figure out what's wrong because I'm at my wit's end.
    A couple of months ago, my MBP13 randomly gave me a BSOD after which it refused to load - just gave me a blinking cursor. I was able to narrow that down to a somehow-messed up boot sequence. I was able to fix it from the Windows 7 repair console. I thought that this time around my situation would be similar, but I haven't been that lucky. So, let me paint the picture of what happened this time.
    Sitting in my kitchen, laptop on the counter, plugged in, having a conversation on Trillian and Skype. I pick it up and move to another room, sit down and try to continue and for a couple of minutes everything is fine, but then the cursor freezes and I get a BSOD, followed by an illuminated dark screen. All my attempts to resuscitate prove futile - any time I press the power button, all I get is that gray screen. I reset the PRAM and then got the white screen that usually appears when I just power on. Unfortunately, no choices of boot (Mac of Windows 7 Ultimate 64-bit which I'm running in Boot Camp) - and then the flashing folder with question mark followed. I was 15 minutes away from driving off to the airport, needing to get on a plane, so I grabbed the MBP, the OSX DVD and the Windows DVD and an external hard drive (2.5 inch SATA) and went to the airport. Started reading support forums and narrowed the issue down to potential HD issues. So I tried first to re-seat the drive - no dice. Then I tried booting from the OSX DVD and going to disk utility - the HD was not being recognized. Same story with the Windows 7 DVD. Mid-flight I disassembled the external drive and swapped the two - the external was being picked up, no problem, so I figured it was a hard drive issue, not a motherboard one, say.
    So, I'm thinking, great, my HD is fried. I've got a whole bunch of data on it that I wanted to salvage (primarily on the Boot Camp partition), so I swapped the MBP drive into the enclosure and hooked it up to a buddy's laptop. To my surprise, Windows 7 on his Dell picked it up without a problem (only Boot Camp, not the Mac part, but since Mac isn't formatted for Windows that probably shouldn't have been surprising) and after futzing with the permissions, I was able to start backing stuff up - never finished, though, figuring that if it's being picked up, I'd just do it later. But I needed a functioning laptop, so I went to Best Buy and picked up a Momentus XT 500GB, installed it and thought I'd be able to install an OS on it. Nope. Windows never even saw the drive and OSX tried to format it but couldn't allocate memory, according to the report. So back to BB the Seagate went. I am coming back to school tomorrow and should be able to have our IT people look at it, but what do you guys think are my best and worst case scenarios and options here? If the Mac HD is completely toast, why would it get picked up just like that via USB? And if it's not toast, can I somehow still boot it? Or should I just salvage what files I have and bite the bullet with a new HD? And which one, if that's the case, since the Momentus crapped out on me big time (in fairness, I later read about all its problems and realized I was better off without it). Or should I just cut my losses, sell the MBP and find myself another computer, perhaps an ultrabook?
    Any thoughts greatly appreciated! Ideally I would like to spend as little as possible while restoring my pre-BSOD situation as much as possible, as you might surmise, so I really don't want to buy a new laptop quite yet...

    Thanks for the detailed explanation! If MacBook supports AHCI/SATA only in native “UEFI mode”, while reverting back to PATA/IDE in legacy “BIOS mode”, then it could make perfect sense to use UEFI to make sure that technology like Native Command Queuing (NCQ) is employed, as it may give noticeable performance improvements for certain operations: www.happysysadm.com/2012/12/intel-g530-nas-performance-part-3.html. I wonder how do you get Windows 8 x64 with EFI bootloader installed on MacBook?
    Simply choosing EFI Boot (“Some EFI platforms support both UEFI and BIOS firmware. On some of those systems, it is not always clear if the default DVD boot option is an EFI or BIOS boot option. On these systems, using the EFI shell command may be required. If you do not specifically start Windows Setup by using the EFI boot entry, the default firmware boot entry for BIOS may be used. If Windows Setup starts in BIOS mode on a combined EFI/BIOS system, the ESP and MSR partitions are not created.”) from Win8 x64 DVD when installing on blank HDD would yield “The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed" message. Also, if the hard drive was not in SATA mode during Windows installation, registry tweaking may be required before switching from PATA to SATA. Do you do registry tweaking and EFI bootloader configuration manually after a copy of Windows was installed in its dedicated partition in a regular way?

  • Memory Allocation Error during Boot

    Hi,
    I am posting this on a different computer than the one on which I istalled Java because I can no longer get it to boot.
    Here's the history:
    I am working in Windows 98
    I added a line to the autoexec.bat so that the PATH lines looked like this:
    SET PATH=C:PROGRA~1\UTILIT~1\SYMATEC\PCANYW~1
    PATH=%PATH%;"C:Program Files\Mts";"C:j2sdk1.4.0_02\bin
    I then rebooted and tried the javac and java commands in different folders and everything worked fine. I shut down the computer and tried to reboot a day later. The following are pieces of the message I received (I don't usually go near the autoexec.bat or system settings so I have no idea how to get past these errors, nor fix them):
    SET PATH=C:PROGRA~1\UTILIT~1\SYMATEC\PCANYW~1
    PATH=C:WINDOWS;C:WINDOWS\COMMAND;C:PROGRA~1\UTILIT~1\SYMATEC\PCANYW~1;"C:Program Files\Mts";"C:j2sdk1.4.0_02\bin
    General Protection Fault in C:WINDOWS\SCANDISK.ALT at 0090:1921
    Memory Allocation Error
    Cannot load COMMAND, system halted
    Please help!
    Thanks,
    Julie

    SET PATH=C:PROGRA~1\UTILIT~1\SYMATEC\PCANYW~1
    PATH=C:WINDOWS;C:WINDOWS\COMMAND;C:PROGRA~1\UTILIT~1\SY
    ATEC\PCANYW~1;"C:Program
    Files\Mts";"C:j2sdk1.4.0_02\bin
    General Protection Fault in C:WINDOWS\SCANDISK.ALT at
    0090:1921This shouldn't have been caused by the Java installation. As I understand the situation, at load time scandisk has been called. This is usually due to the computer not having been shut down properly, or a sign of real problems. However, scandisk is unable to run.
    You should try a forum/newsgroup for Windows for more help. My own suggestion would be to load to the command prompt (or try safe mode). (Press F8 during boot to get a menu.) And then run scandisk manually. If it works, try renaming the C:\WINDOWS\SCANDISK.ALT file and rebooting.
    Regards,
    Bhaveet

  • Ntkrnlpa.exe 22fa3 causing bsod at point of final shutdown

    My minidump file says: "ntkrnlpa.exe+22fa3" has caused the BSOD.
    This BSOD appears at the final point of shut down / restart.
    Other syptoms:
    This DC7700p using SP3 is running slowly - memory seems to over used.
    I have run Malwarebytes, CCleaner, SuperSpyware and NIS is loaded on this machine.
    All report "no problems"
    Also my USB mouse is affecting the audio when moved.
    The later may just be just lack of memory.
    System:
    O/s build 2600 lang: 0809
    RAM 3.6GB
    Bios 786e1 vo3.07
    Tried replacing SP3 and every other thing I have found to sort this problem.
    Fed up reading and searching for the answer.
    Any thoughts

    Hi Silverfox1947,
    I was wondering when was the last time your system was defragmented? Here is a document on how to defragment your disk drive volumes in Windows XP.
    http://support.microsoft.com/kb/314848
    If that does not work the next step would be to do a system restore. Here is a link on how to do that.
    http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/app_system_restore_hs...
    Hope it helps.
    Thanks
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

Maybe you are looking for

  • How get all rows of a table with a BAPI

    Hi, how is it possible to get more then one row by calling a BAPI from the WD. In my Application I need the rows of a Table coming from the r/3 System. How is it possible to get all the rows after the first call? What is the logic behind it? My purpo

  • Audigy platinum pinouts for dri

    I have an original Audigy platinum with the connections for a dri've bay - which I did not purchase. My new case allows for a front panel microphone and headphone (as well as other connections) in addition to the back panel ones. After installing the

  • Why do JPEG files with LR Develop settings open in Photoshop Camera Raw?

    Why does an image that has been altered by Lightroom cause the RAW Converter to open when trying to view it in Photoshop. Perhaps this might help; if I import, enhance and convert a RAW image in Lightroom to a jepg image it will open in Photoshop wit

  • How to use autodj with wxMusik?

    I see this feature mentioned in my preferences, and online, but I don't know how to start using it! It sounds like it plays my whole library on random, filtered by settings I can choose. I like the sounds of it, but I don't know how to use it once I

  • Error: Account Can be Posted Internally Only

    Hi All, I am trying to make a JE Posting to a P&L account and getting the error message that the account has the indicator ' Automatic Posting only". I checked the GL master and the indicator is not set. Any ideas why this error would be showing up??