Bios acting stange

HI
For the last few days I've been noticing some really strange things with my
Neo FSR2 board. I've had lots of craches lately and notice the system temp
is around 50c at load and 45c idle(never went over 41c before) and CPUz
reports my CPU core as ClawHammer but it's a NewCastle (allways did report
it as NewCastle). And no, I did not switch CPU  
!Untill now it has been working perfeclty and 100% stable!
Could I have some virus in my Bios or something? or could a clean bios flash help?
*I did read the temps in Bios mode*
*Edit: Forgot to ad CPU temp, ranging from 36-44c (lower then systemp )

Hi!
It was awile since I made this post and I have replaced my PSU since that for a TurboCool510 (see sig) and it worked just fine for awile untill now
when suddenly my comp just died and the power led was flashing, even a few secs after unplugging the power cable.
I managed to start it up again with no problems and ran it for a few mins then it died again.    ..... I unplugged the ATX cable and AGAIN, that brown
on pin 1, 2 and 11 on my new PSU just like with my old one.. I read in the manual that those pins are all for 3.3V and I'm pretty sure now that something
on my mobo is Frelled, but what? 
I will upgrade to a 939 PCI-Xpress board (not likely one from MSI I'm afraid) later on but then I need not only a mobo but allso a new CPU and a graphics card and I can't afford that atm.
*Edit*
One thing I noticed today when I got home from work and started it up was the onboard LAN would not work and that it kept frezing for a seckond over
and over just as if it was under heavy load. I plugged in my old Realtek 10/100 card and dissabled onboard LAN and Audio and got it to work. I'm not sure
how stable it is at this point.

Similar Messages

  • Our Mac is Acting Stange

    Computer: PowerMac G5
    OS: 10.4.11
    Our Mac has been acting really strange since yesterday afternoon.
    Sometimes the Dock Stays up when I take the cursor off of it, and other times it won't come up. I had to kill Dock and restart it today just to get it to come up.
    The Finder is acting weird too. Yesterday, the windows would open with the top above the menu bar. That seems to be fixed for now that I trashed the Finder preference file (/Users/**/Library/Preferences/com.apple.finder.plist).
    Then, this morning, my mom gets on the computer for a few minutes to visit her favorite forum (which she's been going to for years). No big deal. So she puts the computer to sleep and walks away. A few minutes later, the fan inside the computer tower revs up and starts blowing full blast. At this point, my mom tries to turn the computer back on, but it was frozen and unresponsive. So she held the main power button on the tower until it turned completely off, then turned it back on. Everything appeared normal during the boot up, but when the desktop came up, the System Preferences app was open.
    Any ideas of what this is?

    Great news Scotty, thanks!
    You might consider getting Applejack...
    http://www.versiontracker.com/dyn/moreinfo/macosx/19596
    After installing, reboot holding down CMD+s, (+s), then when the DOS like prompt shows, type in...
    applejack AUTO
    Then let it do all 5 of it's things.
    At least it'll eliminate some questions if it doesn't fix it.
    The 6 things it does are...
    Correct any Disk problems.
    Repair Permissions.
    Clear out Cache Files.
    Repair/check several plist files.
    Dump the VM files for a fresh start.
    Trash old Log files.
    It'll be availble if you ever need it, or maybe use it every month or two to help prevent future problems... once you really need it, you can't install it!

  • Indesign Acting Stange

    Having reinstalled twice my InDesign Suite 5.  My InDesign no longer allows me to "cut" text or move text or elements with my mouse.  They will move with the arrow keys. Copy command stopped working also.  Everything else seems fine.  No viruses found either.  All other software runs fine. Any ideas or settings that could cause this effect?

    Try the steps detailed in this link here.

  • HP MS218 Not Booting - Does not POST - Cannot reach BIOS

    Hello,
    I have an MS218 (product number: BR372AA #ABA) that I have been having issues with. It used to work fine (ran on WinXP), but currently will not even boot properly at all. No software or hardware changes were made to cause this problem to begin occurring, it simply just started happening one day when I went to turn the computer back on. The issue that I am currently experiencing is as follows:
    - Power stays on, but nothing is ever displayed on the screen
    - Does not post, cannot reach BIOS
    - Acts almost as if it is resetting itself constantly, the fan in the back will start to spin for a second or two, then stop, then start again, and repeat indefinitely until I unplug the power adapter.
    I initially figured it was a hardware issue, likely the motherboard, and began to troubleshoot the problem. As I removed non-vital components, the problem would persist. For instance, it happens regardless of external things (keyboard, mouse, etc.) being plugged in, or regardless of the hard drive or optical drive being plugged in. It still appears to happen in the absense of memory, however, I will instead hear beep codes (likely telling me that I don't have any RAM in). Ultimately, I decided to order a replacement motherboard, which recently arrived. Upon replacing the motherboard, the exact same problems happen, which leads me to believe that the motherboard was somehow not the culprit. I have also tried multiple power adapters to no avail, as well as resetting the CMOS battery without any luck. I'm really at a loss for what to do from here, and am currently sitting on hold with HP tech support.
    Any advice is welcome. Thanks in advance for your time and assistance.

    Hello Jaycera,
    There are two more components that we haven't replaced or look at and I would approach them in the order listed.
    1. Power supply
    2. Processor
    It sounds like it's a power issue the computer is getting enough power to start booting up and then losing it. Thus anytime I hear a power issue the first thing I think of is a power supply issue.
    The other thing is it could be the processor. The computer starts booting, makes a call to the processor, fails, boots down, starts booting up, makes a call to the processor and here we are in a vicious cycle.
    It could just be the processor needing reseated. Take it out, put it back in and make sure it's in properly and no pins are bent, or the processor could be bad.
    If I have helped you in any way click the Kudos button to say Thanks.
    The community works together, click Accept as Solution on the post that solves your issue for other members of the community to benefit from the solution.
    - Friendship is magical.

  • Satellite P100-324: 4 GB RAM Solution

    Hello,
    I have been happily using my P100-324 for a couple of months now. Last week it turned out that I need 4 GB of RAM to work, so I bought the extra modules. Since the official specification states the support for that amount of RAM, I didn't expect any problems.
    So, right now my situation looks like this:
    - P100-324 with 4 GB RAM installed,
    - 3072M System Memory Passed - in BIOS,
    - BIOS updated to 4.00 (1),
    - KB929777 installed,
    - ~3 GB RAM usable in different OSes (2),
    - ~2500 EUR spent on notebook, warranty extension and extra memory.
    My question: is there any way to use 4 GB RAM with this notebook - as stated in the official specification?
    If not: which Toshiba company is responsible for disributing this machine in Poland? I understand that Toshiba has many different branches dedicated to different product lines. I talked to my lawyer and she said I should sue the distributor for the money spent. So basically, I need the confirmation that it is definiately impossible to use 4 GB RAM on P100-324.
    Should somebody have any useful information for me, I'd be very happy to hear them.
    Regards,
    (1) - It was supposed to help, as stated [here|http://support.toshiba-tro.de/kb0/TSB7601WE0007R01.htm]. However, it seems like blaming 32-bit OSes for the lack of memory remapping support in BIOS (required by 945PM) is not the way to go.
    (2) - I tested the configuration on the following OSes, without any success:
    a: Vista Ultimate 32-bit (with PAE explicitly enabled),
    b: Vista Ultimate 64-bit,
    C: Debian 64-bit,
    d: Sabayon Linux 64-bit,
    e: FreeBSD 6.2 (64-bit custom built kernel).
    Message was edited by: Admin

    ENABLING 4GB RAM / STAGE 2
    Changes since the stage 1 (first post):
    1) BIOS updated to 4.20-WIN.
    Actually, this was done twice. First time, when the BIOS patch was not linked on the official drivers download site yet (I found it manually browsing Toshiba's drivers repo). Later on, I patched the BIOS once again, to make sure there were no changes in officially-enabled files. To make sure I didn't break anything with the first update, I compared the checkums of the two bios upgrade files and they were exactly the same.<br />
    <br />
    In fact, I didn't notice any visible changes between versions 4.00 and 4.20. It turns out that blaming 4.20 for the hot-GPU issue was a mistake (explained in the next point). Both versions of the BIOS act exactly the same, reporting 4096 MB RAM in the BIOS setup, and later on "3072 M System Memory Passed" during the BIOS phase of the bootup.
    2) GPU Temperature issue in Vista x64.<br />
    After several days of workin with 64-bit Vista installation I noticed that the bottom of the notebook is becoming incredibly hot. I installed Nvidia's MonitorView and I was shocked to discover that the idle temperature of my GPU is over 90 C! The heavy-load temperature oscillated around 105 C. The strange thing is that when the computer is booting, or when in BIOS, or when working with non-Windows OS, one of the fans works loudly and cools down the GPU. However, at the moment I launch Vista, that fan stops running and the temperature starts increasing.<br />
    <br />
    My small investigation the way my computer acts (described above) shows that it's the GPU driver that may be responsible. As one of this forum gurus stated, +this is the reason why we should only use the official drivers released by Toshiba+. It seems that those drivers are able to fully access the graphical chipset and control the fan (generic nvidia drivers cannot read/control fan's state with my notebook). That brings us to the next point:<br />
    3) 4 GB Ram issue
    Many people (even on this forum) state, that in order to use 4 GB RAM one has to use 64-bit Operating System. Even one of the Toshiba's official support pages confirms this point of view. So please help me find an error in this way of thinking (cause maybe all of this mess is because of me):<br />
    <br />
    working with P100-324, I will be able to use 4 GB RAM, as stated in the official specs
    it's not possible to use more than 3 GB RAM with 32-bit OS (even though I disagree with that), so I buy 64-bit Vista Ultimate Box) and install it on my notebook,<br />
    The notebook has Designed for Windows XP Windows Vista Capable sticker, so I don't expect any problems (the sticker doesn't say "Vista 32-bit capable),<br />
    Later on I find out that 64-bit systems are not supported by Toshiba, because of the fact that they're not
    What do you guys suggest?
    A couple of screenshots:
    <a href="http://tesserakt.eu/p100_324_4gb_vista64_bios420.png" target="_newWindow" class="jive-link-external">Control Panel -&gt; System</a><br />
    <br />
    <a href="http://tesserakt.eu/p100_324_mini_2.png" target="_newWindow" class="jive-link-external">Nvidia MonitorView (Polish)</a><br />
    <br />
    <a href="http://tesserakt.eu/p100_324_mini_3.png" target="_newWindow" class="jive-link-external">Toshiba's Official P100-324 Specs</a><br />
    <br />
    <em>Regards!</em>
    </p>
    Message was edited by: admin

  • NVRM: RmInitAdapter failed! (hardware problem?) [SOLVED]

    Fairly recently, an older i686 box I have cannot load X but displays the bootup info, and non-graphical login prompt just fine.  The video card is an nVidia 8400GS.  After googling around for several of the dmesg errors, and not finding much of relevance, I am starting to wonder if the card itself is bad.  Anyone with experience is welcomed to chime in with suggestions.
    I have tried:
    * Moving the card to another PCI slot.
    * Both the linux/nvidia and linux-lts/nvidia-lts packages.
    * Chapter 8 of the nvidia README recommends several kernel bootline mods, none of which work.
    Links
    Complete dmesg: http://pastebin.com/J0y8yKT6
    Complete /var/log/Xorg.log: http://pastebin.com/iCkq9kM5
    Relevant drivers:
    % pacman -Qs nvidia
    local/libvdpau 0.7-1
    Nvidia VDPAU library
    local/nvidia 325.15-8
    NVIDIA drivers for linux
    local/nvidia-libgl 325.15-1
    NVIDIA drivers libraries symlinks
    local/nvidia-utils 325.15-1
    NVIDIA drivers utilities
    Interestingly, I cannot read any info from the card itself which is in stark contrast to any of the other nvidia machines to which I have access:
    % cat /proc/driver/nvidia/gpus/0/information
    Model: GeForce 8400 GS
    IRQ: 16
    GPU UUID: GPU-????????-????-????-????-????????????
    Video BIOS: ??.??.??.??.??
    Bus Type: PCIe
    DMA Size: 40 bits
    DMA Mask: 0xffffffffff
    Bus Location: 0000:02.00.0
    Specific errors in dmesg:
    [ 7.318404] nvidia: module license 'NVIDIA' taints kernel.
    [ 7.318413] Disabling lock debugging due to kernel taint
    [ 7.361296] vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
    [ 7.363264] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:02:00.0 on minor 0
    [ 7.363285] NVRM: loading NVIDIA UNIX x86 Kernel Module 325.15 Wed Jul 31 18:18:15 PDT 2013
    [ 7.654888] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input4
    [ 8.503106] Adding 1023996k swap on /dev/sda3. Priority:-1 extents:1 across:1023996k FS
    [ 9.440825] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
    [ 9.779428] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
    [ 10.444258] systemd-journald[93]: Received request to flush runtime journal from PID 1
    [ 65.003814] nvidia 0000:02:00.0: irq 40 for MSI/MSI-X
    [ 69.922053] NVRM: RmInitAdapter failed! (0x12:0x2b:1830)
    [ 69.922070] NVRM: rm_init_adapter(0) failed
    [ 76.328374] nvidia 0000:02:00.0: irq 40 for MSI/MSI-X
    [ 80.706326] NVRM: RmInitAdapter failed! (0x12:0x2b:1830)
    [ 80.706343] NVRM: rm_init_adapter(0) failed
    [ 87.113316] nvidia 0000:02:00.0: irq 40 for MSI/MSI-X
    [ 91.491315] NVRM: RmInitAdapter failed! (0x12:0x2b:1830)
    [ 91.491332] NVRM: rm_init_adapter(0) failed
    % grep EE Xorg.0.log
    [ 346.147] Initializing built-in extension MIT-SCREEN-SAVER
    [ 346.220] (EE) Failed to load module "nouveau" (module does not exist, 0)
    [ 346.222] (EE) Failed to load module "nv" (module does not exist, 0)
    [ 346.222] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 346.223] (EE) Failed to load module "modesetting" (module does not exist, 0)
    [ 346.223] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 350.605] (EE) NVIDIA(0): The NVIDIA kernel module does not appear to be receiving
    [ 350.605] (EE) NVIDIA(0): interrupts generated by the NVIDIA GPU at PCI:2:0:0.
    [ 350.605] (EE) NVIDIA(0): Please see Chapter 8: Common Problems in the README for
    [ 350.605] (EE) NVIDIA(0): additional information.
    [ 350.605] (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
    [ 350.605] (EE) NVIDIA(0): Failing initialization of X screen 0
    [ 350.606] (EE) Screen(s) found, but none have a usable configuration.
    [ 350.606] (EE)
    [ 350.606] (EE) no screens found(EE)
    [ 350.606] (EE)
    [ 350.606] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 350.606] (EE)
    [ 351.125] (EE) Server terminated with error (1). Closing log file.
    Last edited by graysky (2013-10-06 15:54:40)

    After exhausting various options in the BIOS (acting under the belief that something was interfering with the IRQ of the card), I thought I would try installing the nvidia-304-xx driver which ended up solving the problem.  As of 06-Oct-2013, the Nvidia web site advises to use the 325.xx or 319.xx driver which is flat out wrong. 
    In short, using the legacy 304xx driver seems to be required for the 8400GS.
    % cat /proc/driver/nvidia/gpus/0/information
    Model: GeForce 8400 GS
    IRQ: 16
    GPU UUID: GPU-7f6a5800-9dce-8f7b-a3a8-9bc018f522ef
    Video BIOS: 62.98.12.00.00
    Bus Type: PCIe
    DMA Size: 40 bits
    DMA Mask: 0xffffffffff
    Bus Location: 0000:02.00.0
    % pacman -Qs nvidia
    local/libvdpau 0.7-1
    Nvidia VDPAU library
    local/nvidia-304xx 304.108-7
    NVIDIA drivers for linux, 304xx legacy branch
    local/nvidia-304xx-utils 304.108-1
    NVIDIA drivers utilities and libraries, 304xx legacy branch
    Last edited by graysky (2013-10-20 09:57:18)

  • IPad in reboot loop

      After installing latest OS upgrade, system have been acting stange - latest problem was Messages would not send - so I have had to reboot multiple times.  Each time it took a very long time (have not had this problem with my iPhone 4S), and now it appears to be stuck in a loop and will not complete.  Working with iPad 2.

    Took my iPad to an Apple Store and they wiped it and started a restore from an iCloud backup, which is still running almost 24 hours later - not the best solution, but I at least had the backup.  They said the fact that I had ran the upgrade over WiiFii may have caused a corruption, which makes sense, but is not a good response - the install should account for such things.

  • 2.6 processes swapped out

    I have a 2.6 on an i386 platform.
    He is up and running at the moment but it's acting stange.
    Uptime doesn't give the time it's up.
    who -r doesn't give the runlevel he is in.
    When i give vmstat i see that 16 processes are swapped out.
    When i tried to install top he gives me "pkgadd: ERROR: unable to determine current run-state"
    what is wrong here ?

    Gullible Jones wrote:
    brain0 wrote:
    neodreams wrote:
    Fatal error: Your kernel does not support iptables.
    Firewall not started
    Go back to 2.6.15
    As I can't view the WebCVS right now, I am not sure. But many iptables modules moved to Xtables, which has to be enabled for iptables, ip6tables and arptables. If you forget to enable Xtables (or just copy the old .config file from the old kernel) you will end up without iptables support.
    In that case, Xtables should be enabled in the stock kernel (which is what Neodreams is using).
    I have same problem with Shorewall Firewall:
    ERROR: Trafic Shaping requires mangle support in your kernel and iptables
    I don't have other problems except boot is slower but it doesn't bother me

  • SteelSeries Engine Lighting on my GT60 2OD

    Hey guys, I am wondering if anyone else is having issues with Dual Color and Breathing keyboard zone lighting options.  All other options work fine, and the rest of the SSE program has zero issues.  I think I remember Keyboard Light Manager also having some issues sometimes with Windows 8.1 after some updates.  So this is probably just a driver issue that maybe they will update?  It doesn't bother me as I don't use those, I was just wondering. 
    My laptop is a GT60 2OD 780m version but I've upgraded it quite a bit from stock. 

    Quote from: Talon on 25-December-14, 02:10:45
    Based on your responses, I have concluded you have no idea what you're talking about.
    The BIOS is working perfectly as programmed.  It is correctly recognizing my laptop SKU as a 2QD, because it I have a 16F4 motherboard, and a 970m graphics card.  It is determining based on that (because its programmed this way) my laptop is 2QD.  Obviously I purchased a 2OD, but based on its components it is now recognized as a 2QD because it shares the same components.   
    The EC and BIOS version for the GT60 2OD and 2QD are the exact same!  THE SAME!  Let that sink in for a minute.  They also rock the same motherboard, same and same chassis.  Let that sink in for a minute as well.  Now tell me again how one of them supports a GPU and one doesn't?  That is a lemming response.  Because MSI tells you they aren't compatible, it must be true?  But MSI isn't even telling you that, the newest EC version from the GT60 2OD support website reads
    "1. Update new CPU FAN control table R07, S/W shutdown Temp 94 For Nvidia GTX 970M 980 M.
    2. Modify N16E detect."
    The EC release notes alone show it is compatible with a 970/980m.  In case you also need more proof, here is my thread at NBR, and also a video showing my 970m card in action on BF4. 
    http://forum.notebookreview.com/msi/765058-official-msi-gt60-70-970m-980m-upgrade-thread.html  -- 51 pages of users who have upgraded various machines with 970m and 980m mxm cards. 
    Also I am aware of my warranty status, in all of my years of owning MSI laptops, I've never had to use a warranty.  MSI makes awesome sturdy computers, and I will continue to buy their laptops as long as they offer this type of easy maintenance, and upradeability.  Doing upgrades the user always assumes all risks and liability for any and all damages.  Anyone that upgrades their should be aware of that and willing to accept the risks.  Usually people that upgrade are out of factory warranty anyways, and are upgrading to extend the life of their systems.  Like desktops, the graphics card is always the component holding people back in gaming.
    Good day sir!  And thank you for the great laugh.
    First of all didnt you state earlier you upgraded your gpu so then bios acted as another model and SSE wouldnt work? if thats correct then i know what i'm talking about and you dont, since even another forum mod here is saying same that most of msi laptops with GTX 780M series do not support GTX 900 series gpu due to it's not compatible, so please get your facts correct next time before you laugh at me like that since you dont have any skills yourself.
    Since i remembering others with GTX 700 series in their model asked about upgrade to 900 series and this mod and another user said no it isnt compatbile reason why is heatsink needs to be changed which msi dont provide any for gtx 900 series for some model while ones with gtx 800 series by default has it's support for GTX 900 series.

  • P67a-gd65 (m-flash) now boot loops

    Since I bought my board from day 1 I have updated the bios using m-flash all was fine and dandy... upgrading worked like a charm every single time. Well I noticed a new bios was released but this time as soon as it rebooted it started to boot loop.
    I cleared CMOS and still it boot loops.
    no hardware has been changed or moved, and it happened immediately after I m-flashed 1f or 1.15 as it's listed.
    what can I do??? Don't tell me I have to RMA?!?!?

    How do I flash back to a previous bios when it bootloops?
    I was updating the bios assuming that there would be improved reliability and settings, as it seemed in the early revisions that the menus kept changing and it made the bios "act" in a more reliable fashion... I know, I know that not the reason to flash a bios especially seeing as its always a bit risky but I cant seem to help but 'update' to the latest.
    I tried so far everything I have done on older computers. removed the power cable, removed the battery, switched the psu off, and waited 10+ minutes... I also repeated the process while holding the cmos for a while and no luck. I did notice that when it tries to boot the keyboard lights up (num lock and caps lock) but quickly the lights turn off and the keyboard doesnt function... a few seconds later it reboots. Total time to 'boot loop' is maybe 5-7 seconds.
    I guess I learned a lesson -----> IF aint broke DONT FIX IT!

  • What is your K7N420 Mobo revision...

    ...number and do you have a heatsink on your MCP-D chip? do other manufacturers use a heatsink on this chip?
    My MCP-D gets scorching hot, i wonder if that might be the cause of the black screens of death.
    Ive been at this black screen of death almost 24/7 for little more than a week, tried anything i could come up with. It seems it is just not possible to solve it.
    Im beginning to wonder if other brands of nForce mobos suffer from the same problem?
    And i wonder if there is a batch of bad MCP-D chips on MSI's mobos, or even a design flaw on the MSI mobo itself?

    It would also be interesting for people to list the info on the southbridge chip.
    I have a suspicion this may be why some people have trouble others can't duplicate.  Remember nVidia had to change the southbridges that go into the xbox due to hacks and I'm fairly certain the nforce southbridge would only be a relabelled version of that chip.
    I have a situation, where I have an early nforce and a client has a somewhat later model.  both boards have seagate hard drives attached.  My board operates the drive in UDMA mode no problem.  The clients board will not operate the drive in UDMA mode no matter what.
    I tried updating their BIOS to 2.6 and that allows you to force UDMA, but, under that BIOS the drive isn't even seen when booting regardless of the UDMA setting, and the board has to have the BIOS cleared with the jumper every single time you restart the machine or you get nothing but a black screen when starting the machine up.
    Before anyone asks, yes they are using an ATA100 undamaged IDE cable and yes the drive is setup correctly with the jumper config.
    I gave up in the end and put my machines BIOS on (v2.2) and they are having to live without UDMA on the HDD at present.
    I wish MSI would get their BIOS act together with the nforce and fix the problems properly.  I will be getting an nforce2 motherboard soon, but thanks to fiasco's like BIOS quality and PCI writes issues with K7N420 Pro I can guarantee it won't be a MSI nforce2 I'll be getting.  This is a shame because overall I quite like MSI boards, but, motherboards REQUIRE solid BIOSes and regular, timely updates to BIOS problems.  Your competition can manage it - why not you?
    Greg

  • T510 acting weird after unclean shutdowns (BIOS bug?)

    From time to time I have to do unclean system shutdowns (press and hold the power button). When this happens, my T510 often (not always) won't boot on the first try afterwards. Sometimes it just sits at the Lenovo screen, other times I get a "disk error" (or similar). However, subsequent boots always succeed.
    Is this caused by some kind of memory corruption? A hardware or BIOS issue?
    Using a T510 with the latest BIOS, a OCZ Vertex 2 SSD, 6GB RAM, and Ubuntu Linux 11.04.

  • MSI K7N2 Delta ILSR - RAID BIOS Option ???

    hi ho,
    i have my 2 storage devices pluged into the promise 376 onboard controller. they are not connected as a real raid (not mirror nor real stripe). my OS is win2k on the first sata device and everything was fine for a long time.
    but now when my system boots, it detects the ide drives and then i see the irq board.
    right after that the system stops and tells me 'disk boot failure'. so i don`t get the chance to configure my raidcontroller or my sata devices.
    it is as the controller is deactivated. i remember a bios version where you could activate and deactivate the sata controller. but in my bios (right now it is v7.8) there is no such option.
    i have tested so far:
    - reset cmos
    - flash bios v7.5 to 7.8
    - disconnected sata drives
    anyone with similar problems or any suggestion?
    > MoBo : K7N2 Delta-ILSR Bios v7.8
    > CPU   : AMD Barton 2500+ (not overclocked)
    > Ram  : TwinMos 1GB 3200 400Mhz
    > Sata  : 2 x Maxtor 120GB Sata (as single Devices on Raid-Controller)
    > Ide   : 60GB IBM DeckStar
    > Gra  :  ATI 9600 pro 128MB
    > Aud  :  SB Audigy 2 ZS
    > Pow  : SilverPower 350W, +3,3V/+5V@25A and 12V@18A
    > OS    : win 2000 SP4 + Security Updates 31.07.04 + DirectX 9.0c

    watch the bottom of the screen after pressing Enter on the "Welcome to Setup" screen. There will be some moments of files being loaded, and then you should see a message appear which says "Press F6 if you need to install a 3rd party SCSI or RAID driver". This message will only stay on the screen for a couple of seconds, so press F6 as soon as you see it appear. After this is done, you will see other messages appear, and it will act as though nothing is happening, but eventually a screen will appear which will allow you to install the drivers for the sata controller.
    specify a device press S, select "win 2000 promise fasttrak 376 controller" it will read floppy and load, dot not remove floppy yet, continue win2000 install it may nead to access floppy to finish installing raid driver, did you do it like this.
    try making some floppy boot disks and boot to floppy instead of cd.
    http://freepctech.com/pc/002/files010.shtml
    when you say there not listed, where did you see this? they wont be listed, windows will search for fasttrak controller so it will see sata's conected to it with out you knowing, so long as you load the controller from floppy that came with mobo as above.

  • Dell Venue 11 Pro (5130 64Bit) BIOS update in WinPE 5.1 x64

    I have encountered an issue while trying to upgrade BIOS on Dell Venue 11 Pro (5130 64Bit) in WinPE 5.1 (64-bit). To pre-empt any questions why not use BIOS update option available from boot menu: while it may be quite elegant solution for home use, it doesn't fit well in production environment where the action needs to be repeated hundreds of times, custom audit trail required and some other (automated) post-upgrade tasks need to happen.
    After running the executable I receive the following error message:
    The subsystem needed to support the image type is not present.
    This would point to 32/64 bit application incompatibility and/or limitations of WinPE itself. I have following packages present in my image, as well as CCTK HAPI installed:
    Feature Name
    SMB1Protocol
    WinPE-HTA
    WinPE-WMI
    WinPE-NetFx
    Microsoft-Windows-NetFx-Shared-Package-WinPE
    WinPE-PowerShell
    WinPE-DismCmdlets
    WinPE-SecureBootCmdlets
    WinPE-SecureStartup
    WinPE-TPM
    WinPE-Scripting
    WinPE-WDS-Tools
    WinPE-EnhancedStorage
    Unfortunately I cannot run the update from a "proper" copy of Windows as we need to upgrade BIOS for one of our customers without installing OS (we are shipping devices with default Dell preloaded version of Windows). The way I see it, before I am forced to go down the route of upgrading BIOS from boot menu, I have two options:
    - Get a grip of what the exact issue is in x64 PE. Would anyone be able to help out here? Is this something I can fix by adding any components to my PE image?
    - Try running update in x86 PE (I believe the executable is 32-bit despite "64bit" string in the name). Currently I can only boot using x64 image as BIOS is set to UEFI mode. I am reluctant to change boot mode to Legacy just to give it a go. Will I be able to safely go back to UEFI without any additional recovery work? I am not intending to change the contents of the HDD. Also will cctk be able to change boot mode back to UEFI automatically, or will I have to implement it as a manual step at the end of the process?
    Due to other restrictions and time scales involved Windows To Go is not an option as well. Any help with this will be much appreciated.

    The issue is that the subsystem required to support 32bit apps does not exist in the WinPE 64bit, and there is no way to add it.  You'll either have to use WinPE 32bit, or update your BIOS after the OS has been installed.  Other manufacturers provide x64 BIOS update executables, so I don't know why Dell can't get their act together and do the same.

  • Cant access to BIOS aftre HDD/SSD password!

    Hello,
    Today I set a HDD/SSD password to my Tecra A-11 (updated BIOS) and I am verry happy with that pas,but I cant enter to the BIOS after I enter my HDD/SSD passwor - I press F2,but the screen just go dark for a second or two and the system acts like just being restarted - starting Windows 7 Ultimate.
    Please advice what have to be done so I can enter my BIOS again.
    Thanks in advance

    If it thinks it has a BIOS or HDD password, there's no way to remove that without servicing. It sounds like it likely got damaged in the drop.
    - Peter

Maybe you are looking for