Windows XP hard crash reboot after login

I've seen a few topics about this, but none of them with solid regression info yet so i'm starting this thread. I hope some of you out there can help out, but I fear the answer is that were all screwed.
SUMMARY:
Windows XP will hard crash (reboot) just after login after loading the UI and during the loading of network components. This then results in the system rebooting into a black screen with no standard windows debug. (which can be forced by F8) Hard shut down is required to restart boot process. This problem can also occur from a waking from sleep, and very rarely occurs at random. When its caused during normal operation its usually spawned on by pressing a button on the keyboard. It will occur randomly at startup, and will occur with Starup Disc set or Option Select. Rarely it will boot into windows XP on the first try, more often (over time) it will require 3-5 reboots to get into XP successfully. This problem isn't caused by the install of any software, instead it progressively gets worse over time. I have experienced this problem with BootCamp 1.3, 1.4 and 2.0 on my MacBook Pro 2.16, but I have never experienced it with my Mac Pro ever which has the same OS and bootcamp installed.
I'm convinced it has something to do with the network drivers and how they are loading. I've noticed that the times it fails to boot that the WiFi and Local Area network icons aren't loaded in the system tray, and the times I have success getting into XP that they are already present when the UI is loading. This same behavior occurs on my Mac Pro and other PC clones, but they dont hard crash when this occurs. On them, you just have to wait for the network to be available.
STEPS:
0) MacBook Pro 2.16 17", Mac OS X 10.5.1, Bootcamp 2.0, Windows XP Pro SP2
1) Power up
2) Hold down Option (can set bootdrive as well)
3) Select Windows
4) Select a User (with password set)
5) Enter password
RESULTS:
Hard crash reboot just after UI loads while network compoents begin to load into the system tray.
WORKAROUND:
Shoot dog
REGRESSION:
Never occures on Mac Pro
Occures with Bootcamp 1.3, 1.4 and 2.0
P.S. I'm writing this in Bootcamp

UPDATE
I've gone into msconfig and turned off everything and have been starting up just fine, so it seams one of these items is cuasing the problem. I see that some people say its the keyboard manager, and I wouldn't doubt it now. So i'm going to leave everything off for now, make sure its always booting and then slowing rool items back on. I'll keep this up to date.
If you want to do this yourself, you can do it two ways.
Built in:
1) Click on the Start Button
2) Select Run...
3) type "msconfig" and hit OK
4) Select the "Startup" tab
5) Unselect everything you see there
6) Close and reboot!
3rd party (the way i prefer)
1) Get Spybot (the new one is awesome)
2) install Spybot
3) Run Spybot
4) Update, immulize and scan (optional, but you will be surprised)
5) Select the "Mode" menu option
6) Select "Advanced mode"
7) Select 'tools" on the lower left hand side
8) Select "System Startup"
9) uncheck all options.
10) close and reboot!
Note: this appiaction is really great, and it will also install a device to watch for reg changes which is good for this sort of regression. Again, its not nessiary to install spybot, but i love it and have it on every PC i ever use and have never regretted it. IT WONT SLOW YOUR COMPUTER LIKE OTHER CRAPPY APPS. This is a very light and clean app.

Similar Messages

  • 7.0.0.102 Crashes immediately after login

    After updating to Skype 7 it crashes immediately after login.
    I don't have facerig or FFsplit or any webcams. Windows is updated firewall is turned off.
    The eventlogs show this:
    Faulting application name: Skype.exe, version: 7.0.0.102, time stamp: 0x54897add
    Faulting module name: Skype.exe, version: 7.0.0.102, time stamp: 0x54897add
    Exception code: 0xc0000005
    Fault offset: 0x00d527d7
    Faulting process id: 0x1e7c
    Faulting application start time: 0x01d029890c579caf
    Faulting application path: C:\Program Files (x86)\Skype\Phone\Skype.exe
    Faulting module path: C:\Program Files (x86)\Skype\Phone\Skype.exe
    Report Id: 58eb96c6-957c-11e4-aae2-00224d806fdf
    Any ideas what I can do to get it working again?
    Solved!
    Go to Solution.
    Attachments:
    DxDiag.zip ‏6 KB

    I appear to have the same problem. See below. Do we know when there might be a fix?
    Elmsteader
    Log Name:     Application
    Source:       Application Error
    Date:         27/01/2015 15:40:27
    Event ID:     1000
    Task Category: (100)
    Level:         Error
    Keywords:     Classic
    User:         N/A
    Computer:     Antec
    Description:
    Faulting application name: Skype.exe, version: 7.0.60.102, time stamp: 0x5489935b
    Faulting module name: Skype.exe, version: 7.0.60.102, time stamp: 0x5489935b
    Exception code: 0xc0000005
    Fault offset: 0x00d527d7
    Faulting process id: 0x1670
    Faulting application start time: 0x01d03a4783381172
    Faulting application path: C:\Program Files (x86)\Skype\Phone\Skype.exe
    Faulting module path: C:\Program Files (x86)\Skype\Phone\Skype.exe
    Report Id: d04f9672-a63a-11e4-84d9-00241dd94d4c
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
       <Provider Name="Application Error" />
       <EventID Qualifiers="0">1000</EventID>
       <Level>2</Level>
       <Task>100</Task>
       <Keywords>0x80000000000000</Keywords>
       <TimeCreated SystemTime="2015-01-27T15:40:27.000000000Z" />
       <EventRecordID>129636</EventRecordID>
       <Channel>Application</Channel>
       <Computer>Antec</Computer>
       <Security />
    </System>
    <EventData>
       <Data>Skype.exe</Data>
       <Data>7.0.60.102</Data>
       <Data>5489935b</Data>
       <Data>Skype.exe</Data>
       <Data>7.0.60.102</Data>
       <Data>5489935b</Data>
       <Data>c0000005</Data>
       <Data>00d527d7</Data>
       <Data>1670</Data>
       <Data>01d03a4783381172</Data>
       <Data>C:\Program Files (x86)\Skype\Phone\Skype.exe</Data>
       <Data>C:\Program Files (x86)\Skype\Phone\Skype.exe</Data>
       <Data>d04f9672-a63a-11e4-84d9-00241dd94d4c</Data>
    </EventData>
    </Event>

  • Windows 8 apps crash immediately after opening

    Windows 8 apps crash immediately after opening
    when ever i open any app downloaded from windows store some of them crashes immediately.......
    after re-installing it only works for 1-2 days then again same problem  

    Hi,
    Please also check these two blogs to see if any suggestion work for you when the issue happens again:
    Fix Store App in Windows 8.1
    http://blogs.msdn.com/b/notime/archive/2013/10/18/fix-store-app-in-windows-8-1.aspx
    What to do if your Windows 8 Modern App fails to start
    http://blogs.technet.com/b/askperf/archive/2013/10/11/what-to-do-if-your-windows-8-modern-app-fails-to-start.aspx
    If the issue still persists, please post back the %TEMP%\winstore.log
    and saved AppModel-Runtime and Apps event logs under Event Viewer>Applications and Services Logs>Microsoft>Windows here for our research.
    Please upload them to a file sharing service like Onedrive or "Rapidshare" and put a link to them in your reply.
    Kate Li
    TechNet Community Support

  • Crash right after login on windows 8 and android w...

    Skype crashes on android and also on windows 8. But when i login with a different username, it all works fine. So there is something wrong with my account, but what?

    exactly the same problem for me too... and the other accounts are working perfectly.

  • Windows 8.1 crashing/rebooting

    My windows 8.1 is rebooting multiple times per day. I've uploaded all the dmp files to my skydrive.
    Here's the output/report for WhoCrashed.  I'm not sure how to troubleshoot from here.
    computer name:
    P6X58D-FLL
    windows version: Windows 8 , 6.2, build: 9200
    windows dir:
    C:\Windows
    Hardware: ASUSTeK Computer INC., P6X58D PREMIUM
    CPU:
    GenuineIntel Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz Intel586, level: 6
    8
    logical processors, active mask: 255
    RAM: 12875546624 total
    VM:
    2147352576, free: 1922887680
    Crash Dump Analysis
    Crash dump
    directory: C:\Windows\Minidump
    Crash dumps are enabled on your
    computer.
    On
    Tue 2/11/2014 7:05:24 AM GMT your computer crashed
    crash dump file:
    C:\Windows\Minidump\021114-6703-01.dmp
    This was probably caused by the
    following module: ntoskrnl.exe (nt+0x14DCA0)
    Bugcheck code: 0x1A
    (0x41287, 0x76C55701, 0x0, 0x0)
    Error: MEMORY_MANAGEMENT
    file path:
    C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that a severe memory management
    error occurred.
    This might be a case of memory corruption. More often memory
    corruption happens because of software errors in buggy drivers, not because of
    faulty RAM modules.
    The crash took place in the Windows kernel. Possibly
    this problem is caused by another driver that cannot be identified at this time.
    On
    Tue 2/11/2014 7:05:24 AM GMT your computer crashed
    crash dump file:
    C:\Windows\memory.dmp
    This was probably caused by the following module:
    ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code:
    0x1A (0x41287, 0x76C55701, 0x0, 0x0)
    Error: MEMORY_MANAGEMENT
    Bug check description: This
    indicates that a severe memory management error occurred.
    This might be a
    case of memory corruption. More often memory corruption happens because of
    software errors in buggy drivers, not because of faulty RAM modules.
    The
    crash took place in the Windows kernel. Possibly this problem is caused by
    another driver that cannot be identified at this time.
    On
    Mon 2/10/2014 10:56:58 PM GMT your computer crashed
    crash dump file:
    C:\Windows\Minidump\021014-5953-01.dmp
    This was probably caused by the
    following module: ntoskrnl.exe (nt+0x14DCA0)
    Bugcheck code: 0x3B
    (0xC0000005, 0xFFFFF80164C5A430, 0xFFFFD00023127FC0, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path:
    C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that an exception happened while
    executing a routine that transitions from non-privileged code to privileged
    code.
    This appears to be a typical software driver bug and is not likely to
    be caused by a hardware problem.
    The crash took place in the Windows kernel.
    Possibly this problem is caused by another driver that cannot be identified at
    this time.
    On Mon 2/10/2014 10:27:14 PM GMT your computer
    crashed
    crash dump file: C:\Windows\Minidump\021014-6234-01.dmp
    This
    was probably caused by the following module:
    ntoskrnl.exe (nt+0x14DCA0)
    Bugcheck code: 0x20001
    (0x11, 0x220FBC, 0x1005, 0xFFFFE80005268B20)
    Error: HYPERVISOR_ERROR
    file path:
    C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: The hypervisor has encountered a fatal
    error.
    The crash took place in the Windows kernel. Possibly this problem is
    caused by another driver that cannot be identified at this time.
    On
    Sat 2/8/2014 6:49:56 PM GMT your computer crashed
    crash dump file:
    C:\Windows\Minidump\020814-6140-01.dmp
    This was probably caused by the
    following module: ntoskrnl.exe (nt+0x14DCA0)
    Bugcheck code: 0xA
    (0xFFFFFA7FFFFFFFD0, 0x2, 0x0, 0xFFFFF800CDBA353D)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path:
    C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that Microsoft Windows or a
    kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This
    appears to be a typical software driver bug and is not likely to be caused by a
    hardware problem.
    The crash took place in the Windows kernel. Possibly this
    problem is caused by another driver that cannot be identified at this time.
    On
    Fri 2/7/2014 3:23:35 PM GMT your computer crashed
    crash dump file:
    C:\Windows\Minidump\020714-6171-01.dmp
    This was probably caused by the
    following module: usbport.sys (USBPORT+0x14B5)
    Bugcheck code: 0x1E
    (0xFFFFFFFFC0000005, 0xFFFFF80002AAB4B5, 0x0, 0xFFFFFFFFFFFFFFFF)
    Error:
    KMODE_EXCEPTION_NOT_HANDLED
    file path:
    C:\Windows\system32\drivers\usbport.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: USB 1.1 & 2.0
    Port Driver
    Bug check description: This indicates that a kernel-mode program
    generated an exception which the error handler did not catch.
    This appears to
    be a typical software driver bug and is not likely to be caused by a hardware
    problem.
    The crash took place in a standard Microsoft module. Your system
    configuration may be incorrect. Possibly this problem is caused by another
    driver on your system that cannot be identified at this time.
    On
    Thu 2/6/2014 4:51:43 PM GMT your computer crashed
    crash dump file:
    C:\Windows\Minidump\020614-6984-01.dmp
    This was probably caused by the
    following module: ntoskrnl.exe (nt+0x14DCA0)
    Bugcheck code: 0x3B
    (0xC0000005, 0xFFFFF803AE557929, 0xFFFFD00028C58AA0, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path:
    C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that an exception happened while
    executing a routine that transitions from non-privileged code to privileged
    code.
    This appears to be a typical software driver bug and is not likely to
    be caused by a hardware problem.
    The crash took place in the Windows kernel.
    Possibly this problem is caused by another driver that cannot be identified at
    this time.
    On Sat 1/25/2014 12:43:17 PM GMT your computer
    crashed
    crash dump file: C:\Windows\Minidump\012514-6031-01.dmp
    This
    was probably caused by the following module:
    ntoskrnl.exe (nt+0x14DCA0)
    Bugcheck code: 0x1A
    (0x8886, 0xFFFFFA80073DCC70, 0xFFFFFA8006D1E3E0, 0x201)
    Error: MEMORY_MANAGEMENT
    file path:
    C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that a severe memory management
    error occurred.
    This might be a case of memory corruption. More often memory
    corruption happens because of software errors in buggy drivers, not because of
    faulty RAM modules.
    The crash took place in the Windows kernel. Possibly
    this problem is caused by another driver that cannot be identified at this time.
    On
    Fri 1/24/2014 4:38:48 PM GMT your computer crashed
    crash dump file:
    C:\Windows\Minidump\012414-8156-01.dmp
    This was probably caused by the
    following module: ntoskrnl.exe (nt+0x14DCA0)
    Bugcheck code: 0x1E
    (0xFFFFFFFFC000001D, 0xFFFFF800F5E676A7, 0xFFFFE0000A0A2880, 0x0)
    Error:
    KMODE_EXCEPTION_NOT_HANDLED
    file path:
    C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that a kernel-mode program
    generated an exception which the error handler did not catch.
    This appears to
    be a typical software driver bug and is not likely to be caused by a hardware
    problem.
    The crash took place in the Windows kernel. Possibly this problem
    is caused by another driver that cannot be identified at this time.
    On
    Sun 1/12/2014 9:50:53 AM GMT your computer crashed
    crash dump file:
    C:\Windows\Minidump\011214-6531-01.dmp
    This was probably caused by the
    following module: ntoskrnl.exe (nt+0x14DCA0)
    Bugcheck code: 0x1A
    (0x3300, 0xFFFFC00003CD9000, 0xC080000015C17963, 0x0)
    Error: MEMORY_MANAGEMENT
    file path:
    C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that a severe memory management
    error occurred.
    This might be a case of memory corruption. More often memory
    corruption happens because of software errors in buggy drivers, not because of
    faulty RAM modules.
    The crash took place in the Windows kernel. Possibly
    this problem is caused by another driver that cannot be identified at this time.
    Conclusion
    11 crash dumps
    have been found and analyzed. Only 10 are included in this report. No offending
    third party drivers have been found. Consider using WhoCrashed Professional
    which offers more detailed analysis using symbol resolution. Also configuring
    your system to produce a full memory dump may help you.
    Read the
    topic
    general suggestions for troubleshooting system crashes for
    more information.
    Note that it's not always possible to state with
    certainty whether a reported driver is actually responsible for crashing your
    system or that the root cause is in another module. Nonetheless it's suggested
    you look for updates for the products that these drivers belong to and regularly
    visit Windows update or enable automatic updates for Windows. In case a piece of
    malfunctioning hardware is causing trouble, a search with Google on the bug
    check errors together with the model name and brand of your computer may help
    you investigate this further.

    We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  
    We prefer at least 2 DMP files to spot trends and confirm the cause.
    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask
    Wanikiya and Dyami--Team Zigzag

  • Windows 8 .1 black screen after login with cursor

    after login in pc i get a black screen and a cursor i can do nothing please help me i updated windows 8 to windows 8.1.

    HI , Welcome to the HP Forums! It is a grand  place to find answers and information! For you to have the best experience in the HP forum I would like to direct your attention to the HP Forums Guide. Learn How to Post and More How Do I Find My Model Number or Product Number? I grasp that you have a HP 15 notebook and you recently upgraded from Windows 8. to 8.1.  Now after you enter your Windows password you get a black screen with a cursor. Here is a link to HP PCs - Black or blank screen with blinking cursor after entering Windows password.   To say thanks for responding please click the thumbs up icon below. If this solved your difficulty please tell people by selecting solution provided.   Best of Luck!

  • [SOLVED] Skype crashing soon after login

    Hi Everyone,
    I'm using OSS.
    I installed skype-oss and successfully managed to use it yesterday.
    I tried to revert back to ALSA this morning, but as I wasn't able to get it working, I decided to stick to OSS.
    Skype just crashes soon after I login. I've tried what was suggested here: https://wiki.archlinux.org/index.php/Sk … mmediately , but it hasn't helped.
    Contents of:
    1. /etc/modprobe.d/alsa_blacklist.conf
    blacklist soundcore
    2. rc.conf
    DAEMONS=(hwclock syslog-ng !network netfs crond oss dbus wicd)
    gdb output:
    (gdb) r
    Starting program: /usr/bin/skype
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/lib/libthread_db.so.1".
    [New Thread 0xb76a4b40 (LWP 943)]
    [New Thread 0xb74c1b40 (LWP 944)]
    [New Thread 0xb72ffb40 (LWP 945)]
    [New Thread 0xb6afeb40 (LWP 946)]
    [New Thread 0xb68ffb40 (LWP 947)]
    [New Thread 0xb687eb40 (LWP 948)]
    [New Thread 0xb67fdb40 (LWP 949)]
    [New Thread 0xb677cb40 (LWP 950)]
    [Thread 0xb67fdb40 (LWP 949) exited]
    [New Thread 0xb5f7bb40 (LWP 951)]
    Program received signal SIGSEGV, Segmentation fault.
    0x08355977 in ?? ()
    Is there anything I can do to get Skype working again?
    Thanks,
    Samuel
    Last edited by samebchase (2012-03-13 17:23:18)

    Ehm... Does your sound work with oss? As in can you hear sound?
    Try fresh Skype configuration directory:
    mv ~/.Skype ~/.Skype_bcc
    To revert back to ALSA you need to uninstall OSS and remove the blacklisted modules, and then restart or
    modprobe soundcore

  • ColorFX hard crashing Color after 1.0.1 update

    I'm not sure if this is a Decklink issue, or if it's a Color issue, but in any case, since upgrading to 1.0.1, Every time I add a ColorFX node to one of my projects, Color will hard crash instantly.
    Desktop Video Out has been disabled in my Decklink Preferences. I've repaired permissions several times, as well.
    This is on a 10.4.9 PPC system running Decklink 6.3, Radeon x850 card and Color 1.0.1 (in addition to all the other recent ProApps updates)
    Any help would be really appreciated, because I just purchased Graeme Nattress' great Advanced Plugins for Color, and was excited to start playing with them, but alas, I am stuck in the mud right now.

    I am having the same problem. Have you resolved it yet?
    G5 Dual 2.5GHz 2GB RAM, ATI X800, Decklink Extreme, FCP 6.0/Color 1.0.1, Mac OS 10.4.10, QT 7.2.0
    Thanks,
    ANdrew

  • OS X Mountain Lion crashes immediately after login and reboots.

    Help please.

    HI,
    Yesterday there was an outage with both FaceTime and iMessages at the server end.
    Has it been working up until then ?
    9:15 PM      Monday; November 19, 2012
    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
      iMac 2.5Ghz 5i 2011 (Mountain Lion 10.8.2)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),
     Couple of iPhones and an iPad
    "Limit the Logs to the Bits above Binary Images."  No, Seriously

  • After Installing Leopard Finder Crashes directly after Login

    Hi,
    i Installed Leopard on my MacBook Core 2 Dual. After install the Macbook worked fine for a while (ca. 30 Minutes) then it crashed and asked me to reboot by pressing the power on key a while. But after restart and login it crashes again, and again, and again.
    So i tried booting in save mode ... (pressing shift while boot) ... now i can login, but what now?
    I started to look around in the system and step by step deinstall every app that may interfere with leopard. But no success up to now. Each time i boot normally it crashes again.
    Does anybody else had the same problem ?
    And maybe found what's causing this problem.
    Thanks in advance.

    OK, its coming up now ...
    deinstalled:
    VMWare Fusion
    NDAS Driver
    Little Snitch 2.0 beta 10
    3D Desktop Aquarium ScreenSaver
    collection of plasq Screensavers
    ToasterClone Screensaver
    Parallels Extensions from StartupItems Folder
    not an idea at the moment which of them was the bad guy,
    but i will find out
    @Sebastian try disabling those above if you have installed ones of them an come back posting if that helped

  • Reboots after login

    After logging into the network and the machine boots up into Windows it automatically restarts the computer at the point when normally software shared on our building network begins to load. The one way I can get around this is to shut down and power off the machine followed by disconnecting the power from the MAC and and then restarting.
    I'm running an I mac with OS X (10.5.8) boot camped with Windows XP Pro. This unit is my work computer and is used in Windows mode 98% of the time. The last thing I did before I noticed my problem was run updates for the OS X side.
    Any suggestions?

    Is it random, or every login?
    If the problem seems to be random, talk to your IT folks about pushed software.
    for example, if you are bound to active directory, and your IT folks are pushing security updates and such, there are a number of updates (for windows and some AV software) that require the system be rebooted.
    (If the CPU is turned off when the updates are pushed, then the push may start as soon as you begin your login process.)
    When the push completes and the update installs (often silently, so you see no dialog or progress bar), if a reboot is required) the system reboots. Sometimes with warning, sometimes without. (Depends on how the IT people wrote the push script)

  • [A64] RS480 random lockups, hard crashes, rebooting, freezing

    Now that I've got your attention, specs:
    AMD A64 3200+ rev. e (Venice)
    MSI RS480, bios ver. 3.4
    2x512 Corsair Value Select Dual Channel kit PC3200 CAS2.5
    Leadtek PX6600GT Extreme (550/1100 stock)
    SB Live! Value
    WD 80GB 7200rpm 8mb cache IDE ATA100
    Seasonic SS-380 (25a on 12v rails, 380w total)
    Pioneer DVR-109
    Inwin S500T mATX case
    Nexus 92mm CPU fan on Thermalright XP-90 heatsink
    I've been experiencing random lockups and restarts in 3d apps & games (Battlefield 2, Warcraft 3, Warhammer 40k: Dawn of War, GTA:SA) since I built this system back in May.  I'm so sick of this computer right now that I could happily take a sledge to it and reduce it to rubble.
    Symptoms:
    1) Random reboots and lockups, *not* due to heat.  Heat prior to lockups using Speedfan has the CPU consistently around 50 C and the video card consistently at 40-45 C.  Needless to say, these are very cool temps, but an extra case fan was added to make sure that air flow in case was good.
    2) Motherboard RMA'd after purchase - simply refused to post.
    3) RAM RMA'd after about a month after several dozen memtest86 errors found.  New RAM has been tested - each stick individually & together - and no errors after testing each configuration for 12 hours.
    4) Video card RMA'd after massive heat spikes (upwards 120 C) detected.  New video card arrived yesterday & have had one lockup since, which wasn't unusual with old setup.  Problem still remains.
    5) Sound card was removed for testing when lockup in #4 above occurred, which leads me to believe that my POS SB Live isn't the problem.  Too bad, as it would have been a terrific excuse to upgrade to an Audigy 2 ZS.
    6) When video card was removed, system was rock solid, not a single crash.  With video card in, crashed all the time prior to RMA, and once in two days after new one received.  While the old video card certainly appeared to have problems, I'm hesitant at this point to put all my problems on the video card.  Is this an erroneous assumption?
    7) At least eight or nine different Forceware versions were used for testing; different driver versions did not prevent crashes.
    Now, it hasn't crashed again (which means nothing; it's been a couple of hours) since disabling SATA in bios and downloading & installing AMD driver for processor.  Will be moving RAM from slots 1 & 2 to 3 & 4 shortly.  Before my sanity is finally and truly lost, is there anything else that anybody can think of to stop these hard locks?  I'm off to move the RAM around and do some further testing, but any advice whatsoever would be absolutely terrific.  Thanks!
    (topic title changed.  apparently some people thought I was kidding.)

    Quote from: Tiresmoke on 28-July-05, 02:39:59
    Well yes it could be the RAM. For what it is worth everyone I have seen with Kingmax RAM seems to be happy and so far as I know it works with all the cores. It is also not very expensive stuff. Hope that helps.
    Kingmax, eh?  I'll see if I can find any (I'm in Canada).  Do you know how good their customer service is?
    I think that before I try to pick up some new ram I'll send Corsair an email; according to their site, the VS is supposed to be compatible with the RS480, which is one of the reasons I bought it.  Who knows; maybe they'll upgrade the RAM that I've got for cheap.  But thanks for the advice!
    Quote from: dannol48
    FYI...you're not the first to report problems trying an nVidia gForce video card on this motherboard (ATI surroundview enabled Xpress 200 chipset).
    If you didn't notice, the Compatibility Report posted for the board ONLY has ATI Radeon cards.
    Bloody hell!  Why didn't I check that?  Well, I gotta think about this some more.  Good grief.  Thanks for bringing this to my attention!

  • Dock crashes continuously after login

    Hello,
    I've been trying to fix this Mac (MacBook Pro, OS 10.7.5) and it has me completely flummoxed.
    A few seconds after logging into the user account, the screen begins periodically flashing gray, then jumps back to the desktop, where the Dock is gone but then reloads. There are multiple crash reports in the system for the Dock crashing, so I'm assuming it is the problem.
    I've found some similar problems that people have had, but they've been able to fix it by creating a new user account. I tried that, but the new user had the same problem. I'm thinking it probably needs the OS to be reloaded, but I don't have any disks to accomplish that.
    Any ideas? Thanks!

    This could be a sign of hardware problems.
    Restart in Safe Boot mode and see if the problem goes away.
    *  shutdown
    *  start the Mac and *wait* for the startup chime to sound
    *  after the sound, press and hold down the shift key
    *  keep holding and *wait* until the grey  Apple logo appears
    *  now release the shift key and just wait (it could take a few minutes)
    *  eventually the login screen appears with the words SAFE BOOT
    *  continue to login to see if the problem goes away.
    If the problem exists in Safe Boot mode, the boot into the Recovery Drive and select to Reinstall OS X. This should download the 10.7.5 installer and refresh your install.
    Boot into the Recovery Drive by holding down Command R when restarting.
    If you still have problems, you need to take your computer in for a diagnosis.

  • Windows 7 HDMI stops working after login in normal boot. Safe modes work

    Hi guys, I have a problem and I am a complete dummie at this. (Sorry in advance for bad english and hardware/software knowlegde.)
    Here's what happened: Yesterday evning I turned off my PC after playing my games. Today when I got home from work my PC looses HDMI connection after "STARTING WINDOWS" screen. That's when my monitor says "No Synch" which means it cant detect a HDMI. I have to hold in off button and restart and then i get to this black classic screen where I can choose Safemode etc. and Normaly. Turns out I can enter safe mode and HDMI works, but i've tried normaly many times and it wont work!
    So I've been reading all day and haven't found any working solution(lowering my resolution etc.) So it was suggested that I needed to u-innstall my video drivers and get them again. Or even get older versions first and then installing new ones along with the latest windows update. My problem is that I have no idea what video card I have and in safe mode I can't see it in CONTOL PANEL display settings either.
    I'm playing on a little **bleep** tv monitor JWC something btw.
    So I'm stuck not knowing what video drivers I need and where to get them, if that's even the problem to beginn with?
    I hope someone out there are smarter than me, haha! Thanks Guys!

    I'm sorry I thought you were using a notebook and the monitor was your 2nd display device... So it's your primary display, right? And safe mode works...I don't know then. Is there any auto adjustment button on monitor or similar function in monitor's menu?
    I work for HP

  • Windows Media Player Crashes straight after starting program.

    Hi Guys, 
    Can Anybpody help me resolve the followiung  ....
    I am running Windows 8.1 x64 on my unit (M6 Envy 1205sa).
    I am facing the following problem: 

    Hello again @J-Singh,
    I have a couple other suggestions for you to try to fix your Windows Media Player. First to lets try removing Windows Media Player and putting it back to see if it helps. As Windows Media Player is part of your Windows operating system it is not removed and added in the traditional sense, but a feature of the operating system you can remove and put back. Please follow the steps I have set out below to remove and put Windows Media Player back:
    Step 1. At your Tiles Menu type "control panel"
    Step 2. Click on Control Panel
    Step 3. Click on Programs and Features
    Step 4. Click on Turn Windows features on or off
    Step 5. Click on the + beside Media Features
    Step 6. Uncheck the check mark in the check box beside Windows Media Player
    Step 7. You will receive a warning message simply click 'Yes'
    ***It will take a bit of time, but once it is finished removing Windows Media Player restart your computer.
    To turn the Windows Media Player feature back on simply follow the steps above only put the check mark back in the check box.
    Now if  the above steps do not work we are going to try to fix any corrupted files on your computer. To do this follow the steps I have set out below:
    Step 1. At your Tiles Menu type "command prompt"
    Step 2. Right-click on Command Prompt
    Step 3. Click on Run as administrator
    Step 4. Type "sfc /scannow" and hit Enter
    ***This will take a bit let it run it's course
    Now the above steps will look for any corrupt files in your operating system and fix them. If they do not resolve your issue it could be with a file that is not part of the operating system in which case I would like you to follow the next set of steps below:
    Step 1. Open My Computer
    Step 2. Right-click on C: and choose Properties
    Step 3. Click on the Tools Tab
    ***Windows may tell you that you don’t need to scan the drive, as Windows hasn’t found any errors on the drive. Ignore it and continue
    Step 4. Click Scan Drive
    ***Windows may tell you about any problems it encounters and asks for your permission to fix them. Go right ahead and have it fix them.
    After you have checked your disc for errors ensure that you restart your computer.
    Now it none of the above work the only thing left it to backup and recover your operating system back to factory settings. To backup your personal information and ensure that it is not lost I would like you to review and follow the steps set out in the HP Support document: Backing Up Your Files (Windows 8), which will ensure your personal files are up to date.
    ***WARNING!! If you want to keep any emails or bookmarks/favorites you will want to back those up as well as I do not believe they are backed up in the HP Backup process.
    Next, I would like you to review and follow the steps set out in the HP Support document: Performing an HP System Recovery (Windows 8), which will you through recovering your computer back to factory settings.
    *** IMPORTANT - Your personal files such as libraries, personalization settings, user accounts, and desktop themes are permanently removed. As well the computer settings are returned to the defaults (the way it was when it came from the factory). All apps and software that were installed on the computer when it came from the factory are reinstalled, and their settings are reset to the defaults. Additionally, software, apps, programs, and everything that you have installed or saved on the computer are permanently removed.
    I would like to thank you for posting on the HP Forums. Have a great day!
    Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
    Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
    Dunidar
    I work on behalf of HP
    Find out a bit more about me by checking out my profile!
    "Customers don’t expect you to be perfect. They do expect you to fix things when they go wrong." ~ Donald Porter

Maybe you are looking for

  • How to dynamically set connection string for report in C# code?

    Hi, I have installed CRVS2010. I have created new Crystal Report WPF Application and new report. I would like to set connection string for report in code dynamically. Is this possible? Thanks Ivana

  • Partition view on 10g and 11g

    Hi All, I am on 10.2 Standard edition and 11.1 Standard edition (2 databases in the application, one on 10g, another on 11g). Being on standard edition, cannot use many common features e.g. partitioning, bitmap indexes etc. I use to think that, parti

  • Cant open same excel file when it is already open by another user (cant open read only)

    We have been having an issue for a while now where if a user has an network saved excel document open, another user cannot open it at all. We get the error "Sorry we couldn't find your file. Is it possible it was moved, renamed or deleted?" and/or si

  • Multiple Outbound Deliveries

    Hi, How can I create multiple outbound deliveries for a Stock Transfer Order? The STO has more than a thousand items, which makes one outbound delivery with a thousand line items quite difficult to process with our current warehouse. I need to cut th

  • Using older keyboard and mouse

    Greetings: I have a new MacMini w/ Tiger 10.4 OS. I can't seem to get comfortable with / adjust to the smaller Apple keyboard. I wish to find an adapter so that I can use my older Apple extended keyboard and a Kensington track ball. I can't for the l