Overclocking blues

Hey, I am having some "difficulties" and wondering if anyone here can offer some insight. First, I'll go over the hardware.
AMD Athalon XP 2400+ (Tbred)
Coolermaster HHC-001 HSF
MSI K7N2-L motherboard
2x 256MB Corsair XMS PC3200 LL DDR (the good stuff ;-)
Leadtek GeForce 4 Ti4400
WD JB100 7200rpm drive ("special" edtion)
Vantec Stealth 420W PSU
Lian Li PC52 aluminum case w/ 2 92mm blowholes
Okay, now the questions-
What's up with dual channel?  The instruction manual really doesn't say much of anything about dual channel DDR in it at all.  I thought this motherboard supported it, but running Sandra says that my memory bandwidth is just slightly ahead of PC2100 (stock FSB).  I have my DIMMs in the 0 and 2 slots
Overclocking.  Unforunately, every time I try to change the multiplier the bios won't post, and I have to change 2 jumpers to reset the bios and go again.  I have tried upping the core voltage and this doesn't help.  Stock you are running 133x15=2000.  But even 166x12=2000 it won't post with or without an increased vcore. Do I need to use the wire trick?
As far as overclocking, my CPU seems to be running pretty hot.  Should I be concerned with temps 50/56 idle/load?  The Coolermaster is a pretty good one and I used Artic Silver 2.  Thanks.

Thanks for the info.
What I meant by the 2400+ producing more heat is actually a fact.  The higher the rating, the more heat it produces (in watts).  Therefore an 1800 tBred will be much cooler than a 2400 tBred (all other factors being equal).  I wasn't trying to tell you that my system was better or anything. (even if it might be   )
I'm getting a Vantec Aeroflow, should work well and be quieter.  As soon as it comes, I'll lap it, wire trick, Arctic Silver III, and I should be good to go, thanks!  I'm looking forward to getting it all running well.  I'm looking to get 200x10.5 (2100 MHz) to run stable and smooth.  I could OC more but for everyday use we'll see what temps I'm getting First.
***sidenote***
My case is pretty cool. I have an aluminum Lian Li PC52b modded with two 92mm (blowholes) clear/red LED fans pumping out roughly 96 cfm (total).  These fans are situated two inches above the HSF and RAM.  Also an 80 mm intake blowing across my HD. So with 2 on the vid card and 3 on the Vantec Stealth, I have 9 total fans.  :D Yeah, its pretty loud but will get better when I nix the HHC-001.

Similar Messages

  • BLUE SCREEN OF DEATH 1800+ XP T-Bred Overclock 1.92 GHz

    I get the BSOD in any game while overclocked 166 FSB to 1.92 GHZ. I've uninstalled and reinstalled ATI display drivers and NVIDIA board drivers with the same results. It wasn't this unstable for a week at a 166 FSB setting!
    At the normal 1800+ speed of 1.53 GHz I have no display problems and no blue screen of death speed.
    Why the instability at a 166 FSB?
    Pie~3.14
    K7N2-L
    320 W PSU
    Win XP Pro SP1
    Athlon XP 1800+ T-Bred
    ATI Radeon 7000 64 DDR~Catalyst 3.1 Drivers
    ~Direct X 9.0
    Sound Blaster Audigy PCI
    Pioneer DVD-ROM 16x
    LG 52x24x52
    Maxtor 40Gb 7200 RPM Quiet Drive
    Elixir PC-2700 256Mb x 2
    :::::RAS# to CAS# Delay: 3
    :::::RAS#Precharge: 3
    :::::Cycle Time: 7

    I didn't touch the multiplier, and I won't now and here's why. Last time I did, my board fried when lowered the multiplier and upped the FSB up around 200. I'm not feeling that adventurous.
    I have never adjusted the CPU Vcore. What is a typical adjustment?
    Pie~3.14

  • MSI 770-C45 locking up/blue screening/other errors on boot

    I recently built a new HTPC and have been having allot of problems getting it to boot.  It may take 10-15min of trying to boot up over and over with random blue screens, lockups, or errors that the C drive needs to be checked for consistency before Windows will finally load up and work.  At first I thought it was a bad drive, but according to Western Digital’s HDD Diag util, both the controller and the drives surface checks out OK.  I just wiped the drive out and reinstalled Windows 7 again, and this time went with IDE instead of AHCI, hoping it was a driver issue.  It only worked well for a day before the same problems started rearing their ugly head again.
    At this point I don’t know if I have a memory issue, a CMOS setting wrong (which are All Auto), or what.  I hoping someone here might have an idea of what this problem could be.   
    My system specs: 
    MSI 770-C45 Motherboard -  BIOS v1.9 05182010
    AMD Phenom II X4 945 Deneb 3.0GHz 4 x 512KB L2 Cache 6MB L3 Cache Socket AM3 95W Quad-Core Processor HDX945WFGIBOX
    4GB RAM – Memory Master-2-Pack 2GB PC3-10666 DDR3 DIMM Memory Kit-MMD4096KD3-1333 SKU: 9360032
    MSI R4550-MD1GH Radeon HD 4550 1GB 64-bit GDDR3 PCI Express 2.0 x16
    Drive C: - Western Digital 320GB WD3200AAKS
    Drive D: - Western Digital 1.5TB WD15EARS
    Linksys WUSB54GC v3 Wireless USB Adapter
    Windows 7 64bit Enterprise
    All recent MSI 770 and Radeon Drivers

    Quote from: Mavrick007 on 23-July-10, 02:39:51
    According to MSI, my motherboard supports the following modules:
    DDR3 800/1066/1333/1600*(OC)
    http://www.msi.com/index.php?func=prodmbspec&maincat_no=1&cat2_no=171&cat3_no=656&prod_no=1812
    This are the speeds of the DDR 3 RAM supported ,1600Mhz beeing done with overclocking ,because the CPU memory controller is no able to do 1600 by default.
    Quote from: Mavrick007 on 23-July-10, 02:39:51
    When I look at the test results for my Motherboard:
    http://www.msi.com/uploads/test_report/TR10_1812.pdf
     I see 1333 RAM list like PC11000 DDR III RAM (DDR-1333).  However, If I go to a site like Bestbuy or NewEgg and search for DDR3 1333, it shows results like Corsair - 2-Pack 2GB PC3-10666 DDR3 DIMM Memory Kit.  I see PC3-10666 and PC3-10600, but nothing for PC11000.
    The only mention of 1333 modules on the test report is for 1333 OC
    When you see the PC 11000 DDR3 or PC3 10666 specifications they are refering to the theoretical bandwidth ,it s related to the frequency of course ,but it s something else it s a data rate.Its wikipedia but it s good enough -> http://en.wikipedia.org/wiki/DDR_3 Some specs are atipical like 10666 ,marketing thngyes
    Search the internet for memory that works ok with your CPU ,look for "real" DDR 3 1066Mhz or DDR 3 1333Mhz."real" means that that memory should be able to run at those frequencies without voltage increase over the default one.Usually when a memory vendor says you need to increase voltage for a specific frequency it means that you overclock and that there is no warranty they will work in your configuration.
    So you need DDR 3 1066Mhz or DDR 3 1333Mhz ,it needs to be AMD tested memory and it needs to be a known to work RAM on MSI motherboards timings wise.Look up on newegg and see what works.
    The performance gaps between 1066 and 1333 are small in real practice and you can overcome some loss by using a "real" DDR 3 1066Mhz , tweaking different timings ,using Command Rate of 1T for example ( you may "feel" it smoother in desktop than a 1333Mhz at 2T).

  • I'm getting "MACHINE_CHECK_EXCEPTION" blue screens

    But this is not the same as the other guys :/  
    this computer is about 3 months old and just started to get this error 2 days ago..."MACHINE_CHECK_EXCEPTION"  What the hell does that mean???
    I was started a game, went to the track to start racing and I was sitting at 2 frames per second.  For 3 months with this computer I've been getting avg of 100-140fps.  So i turn the game off, as soon as i turn it off i get a Blue screen then it rebooted!!!  It rebooted fine at that point.  I try another game UT2004, play for about 30 mins, shut off the game, BAM!!!! Blue screen again!!! I figure, "ok i need to reinstall xp".
    So i reinstall xp, I load the K8N Neo mobo drivers, reboot, works fine.  Install Audio Drivers, I get a blue screen "MACHINE_CHECK_EXCEPTION" on boot, I uninstall it, works fine.  I install SP1, blue screen"MACHINE_CHECK_EXCEPTION" on reboot, I uninstall and install SP2, works fine. Odd?  Yes, I think so.... Now I've tried all kinds of combos here between the BIOS and whats installed.  Most commonly ON board sound enabled, and the sound drivers NOT installed, i will not get a Blue screen...Most commonly.  Out of about 50 reboots to test this theory, when every i install the sound device's drivers i get the error.  So i'm thinking it has something to do with the drivers are conflicting with the hardware.  But, this same computer has been working fine for 3 months prior to 2 days ago.  I dont get it!!! Did my mobo go bad?  Is there anything out there that can fix this, something i need to look at.  I shouldn't have to use a sound card because the mobo's onboard sound is suppose to be fine.  Any help please!  
    Thanks
    My DxDiag Report
    Time of this report: 12/3/2004, 23:52:51
    Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2)
    System Manufacturer: NVIDIA
    System Model: AWRDACPI
    BIOS: Phoenix - AwardBIOS v6.00PG
    Processor: AMD Athlon(tm) 64 Processor 3200+,  MMX,  3DNow, ~2.2GHz
    Memory: 1024MB RAM
    DirectX Version: DirectX 9.0c (4.09.0000.0904)
    MotherBoard:  K8N Neo Platinum
    PS I think its hardware failure but I could be wrong.

    Thanks I'll give it a try... also I got this answer for other forums maybe some one can help with this
    interesting... machine_check_exception is a hardware related issue. typically caused with hardware and pentium processors, buti guess in your case its a little different. straighe from microsoft: "A machine check exception occurs when Windows XP and your hardware platform cannot recover from a hardware error so that the system can continue to run successfully and reliably. More specific diagnosis of machine check exceptions is difficult, and there is no general solution." You've got a beast of a computer there, so i really don't see why you'd be having much problem... i've heard overclocking is a common cause of this error, so if you are... change that. If that doesn't do it it could be your power supply, over heating, or bad memory. "
    I'm not overclocking, and he did menition "bad Memory"  So in moving that around I guess I'll have to try one stick at a time or both?

  • Blue screen with the following error SYSTEM SERVICE EXCEPTION (ACPL.sys)

    Hi,
    I had a blue screen with SYSTEM SERVICE EXCEPTION (ACPL.sys) error message yesterday.
    It happened right after the graphic card update was completed. I have an HP Spectre XT laptop with Windows 8 and Intel(R) HD Graphics 4000.
    After restart, I noticed that the available free space on my hard disk dropped by 4 GB!
    Can you please assist?
    Thank you.

    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 NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.
    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
    If you are overclocking stop.  (chances are if you dont know if you are, you are not)a
    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.  We need at least 2 DMP FILES to diagnose and confirm
    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button. (if available on  your site, MS doesnt have this)
     *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.
    Link for how to  upload below.
    http://www.wikihow.com/Use-SkyDrive
    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
    Please also run MSinfo32 and upload the output as well.
    To run MSinfo32 please go to start>run>MSinfo32
    Go to "file" "save" and upload the saved file with the DMPS
    System specs are extremely useful so please include whatever you know.
    Blue Screen View & Who Crashed are often wrong and should only be used in an emergency
    Team Zigzag3143.com
    Wanikiya & Dyami--Team Zigzag

  • Blue screen after fresh install 8.1

    I keep getting errors, of blue screen right after install...And after all that typing i get this message... that I can't post links/images... so Here I post a log.Log Name:      SystemSource:        Microsoft-Windows-Kernel-PowerDate:          20-2-2014 21:34:14Event ID:      41Task Category: (63)Level:         CriticalKeywords:      (2)User:          SYSTEMComputer:      AWMDescription:The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.Event Xml:<Event xmlns="://schemas.microsoft.com/win/2004/08/events/event">  <System>    <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />    <EventID>41</EventID>    <Version>3</Version>    <Level>1</Level>    <Task>63</Task>    <Opcode>0</Opcode>    <Keywords>0x8000000000000002</Keywords>    <TimeCreated SystemTime="2014-02-20T20:34:14.758130700Z" />    <EventRecordID>347</EventRecordID>    <Correlation />    <Execution ProcessID="4" ThreadID="8" />    <Channel>System</Channel>    <Computer>AWM</Computer>    <Security UserID="S-1-5-18" />  </System>  <EventData>    <Data Name="BugcheckCode">239</Data>    <Data Name="BugcheckParameter1">0xffffe001fe921580</Data>    <Data Name="BugcheckParameter2">0x0</Data>    <Data Name="BugcheckParameter3">0x0</Data>    <Data Name="BugcheckParameter4">0x0</Data>    <Data Name="SleepInProgress">0</Data>    <Data Name="PowerButtonTimestamp">0</Data>    <Data Name="BootAppStatus">0</Data>  </EventData></Event>
    Above you can see the log name, not sure if you can read it, I've put it in a code block.
    I thought it was my RAM that was default/bad /corrupt. So I bought new ones, but the problem keeps ocuring. I re-installed my windows 8.1 using new RAM, but it keeps giving me "windows/freeze lag" and then blue screen.
    See logs.
    Log Name:      System
    Source:        Microsoft-Windows-Kernel-Power
    Date:          20-2-2014 21:24:04
    Event ID:      41
    Task Category: (63)
    Level:         Critical
    Keywords:      (2)
    User:          SYSTEM
    Computer:      AWM
    Description:
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Event Xml:
    <Event xmlns="://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
        <EventID>41</EventID>
        <Version>3</Version>
        <Level>1</Level>
        <Task>63</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000002</Keywords>
        <TimeCreated SystemTime="2014-02-20T20:24:04.336182100Z" />
        <EventRecordID>253</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>AWM</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="BugcheckCode">239</Data>
        <Data Name="BugcheckParameter1">0xffffe0007c3e1080</Data>
        <Data Name="BugcheckParameter2">0x0</Data>
        <Data Name="BugcheckParameter3">0x0</Data>
        <Data Name="BugcheckParameter4">0x0</Data>
        <Data Name="SleepInProgress">0</Data>
        <Data Name="PowerButtonTimestamp">0</Data>
        <Data Name="BootAppStatus">0</Data>
      </EventData>
    </Event>
    Log Name:      System
    Source:        Microsoft-Windows-Kernel-Power
    Date:          20-2-2014 19:45:24
    Event ID:      41
    Task Category: (63)
    Level:         Critical
    Keywords:      (2)
    User:          SYSTEM
    Computer:      AWM
    Description:
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Event Xml:
    <Event xmlns="://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
        <EventID>41</EventID>
        <Version>3</Version>
        <Level>1</Level>
        <Task>63</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000002</Keywords>
        <TimeCreated SystemTime="2014-02-20T18:45:24.960461300Z" />
        <EventRecordID>218</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>AWM</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="BugcheckCode">0</Data>
        <Data Name="BugcheckParameter1">0x0</Data>
        <Data Name="BugcheckParameter2">0x0</Data>
        <Data Name="BugcheckParameter3">0x0</Data>
        <Data Name="BugcheckParameter4">0x0</Data>
        <Data Name="SleepInProgress">0</Data>
        <Data Name="PowerButtonTimestamp">0</Data>
        <Data Name="BootAppStatus">0</Data>
      </EventData>
    </Event>
    My set up:
    Processors AMD FX-6300 Black Edition
    motherboard/Moederborden ASRock 970 Extreme3 R2.0
    Memory intenral/ Geheugen intern Crucial Ballistix Tactical BLT2C4G3D1608ET3LX0CEU
    GPU/ Videokaarten MSI R9 270X GAMING 2G
    Internal Driive/ Interne harde schijven Seagate ST1000DX001, 1TB
    PC case/ Behuizingen Corsair Carbide 200R Closed
    PSU / Voedingen Seasonic S12II-Bronze 430W

    I keep getting errors, of blue screen right after install...And after all that typing i get this message... that I can't post links/images... so Here I post a log.Log Name:      SystemSource:        Microsoft-Windows-Kernel-PowerDate:          20-2-2014 21:34:14Event ID:      41Task Category: (63)Level:         CriticalKeywords:      (2)User:          SYSTEMComputer:      AWMDescription:The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.Event Xml:<Event xmlns="://schemas.microsoft.com/win/2004/08/events/event">  <System>    <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />    <EventID>41</EventID>    <Version>3</Version>    <Level>1</Level>    <Task>63</Task>    <Opcode>0</Opcode>    <Keywords>0x8000000000000002</Keywords>    <TimeCreated SystemTime="2014-02-20T20:34:14.758130700Z" />    <EventRecordID>347</EventRecordID>    <Correlation />    <Execution ProcessID="4" ThreadID="8" />    <Channel>System</Channel>    <Computer>AWM</Computer>    <Security UserID="S-1-5-18" />  </System>  <EventData>    <Data Name="BugcheckCode">239</Data>    <Data Name="BugcheckParameter1">0xffffe001fe921580</Data>    <Data Name="BugcheckParameter2">0x0</Data>    <Data Name="BugcheckParameter3">0x0</Data>    <Data Name="BugcheckParameter4">0x0</Data>    <Data Name="SleepInProgress">0</Data>    <Data Name="PowerButtonTimestamp">0</Data>    <Data Name="BootAppStatus">0</Data>  </EventData></Event>
    Above you can see the log name, not sure if you can read it, I've put it in a code block.
    I thought it was my RAM that was default/bad /corrupt. So I bought new ones, but the problem keeps ocuring. I re-installed my windows 8.1 using new RAM, but it keeps giving me "windows/freeze lag" and then blue screen.
    See logs.
    Log Name:      System
    Source:        Microsoft-Windows-Kernel-Power
    Date:          20-2-2014 21:24:04
    Event ID:      41
    Task Category: (63)
    Level:         Critical
    Keywords:      (2)
    User:          SYSTEM
    Computer:      AWM
    Description:
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Event Xml:
    <Event xmlns="://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
        <EventID>41</EventID>
        <Version>3</Version>
        <Level>1</Level>
        <Task>63</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000002</Keywords>
        <TimeCreated SystemTime="2014-02-20T20:24:04.336182100Z" />
        <EventRecordID>253</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>AWM</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="BugcheckCode">239</Data>
        <Data Name="BugcheckParameter1">0xffffe0007c3e1080</Data>
        <Data Name="BugcheckParameter2">0x0</Data>
        <Data Name="BugcheckParameter3">0x0</Data>
        <Data Name="BugcheckParameter4">0x0</Data>
        <Data Name="SleepInProgress">0</Data>
        <Data Name="PowerButtonTimestamp">0</Data>
        <Data Name="BootAppStatus">0</Data>
      </EventData>
    </Event>
    Log Name:      System
    Source:        Microsoft-Windows-Kernel-Power
    Date:          20-2-2014 19:45:24
    Event ID:      41
    Task Category: (63)
    Level:         Critical
    Keywords:      (2)
    User:          SYSTEM
    Computer:      AWM
    Description:
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Event Xml:
    <Event xmlns="://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
        <EventID>41</EventID>
        <Version>3</Version>
        <Level>1</Level>
        <Task>63</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000002</Keywords>
        <TimeCreated SystemTime="2014-02-20T18:45:24.960461300Z" />
        <EventRecordID>218</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>AWM</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="BugcheckCode">0</Data>
        <Data Name="BugcheckParameter1">0x0</Data>
        <Data Name="BugcheckParameter2">0x0</Data>
        <Data Name="BugcheckParameter3">0x0</Data>
        <Data Name="BugcheckParameter4">0x0</Data>
        <Data Name="SleepInProgress">0</Data>
        <Data Name="PowerButtonTimestamp">0</Data>
        <Data Name="BootAppStatus">0</Data>
      </EventData>
    </Event>
    My set up:
    Processors AMD FX-6300 Black Edition
    motherboard/Moederborden ASRock 970 Extreme3 R2.0
    Memory intenral/ Geheugen intern Crucial Ballistix Tactical BLT2C4G3D1608ET3LX0CEU
    GPU/ Videokaarten MSI R9 270X GAMING 2G
    Internal Driive/ Interne harde schijven Seagate ST1000DX001, 1TB
    PC case/ Behuizingen Corsair Carbide 200R Closed
    PSU / Voedingen Seasonic S12II-Bronze 430W
    Please update your powersupply to a 1000 watt and you good to go, don't be so cheap, a 400wtt for a monster like that. jeez man are you on something.
    Good psu is the most important part of a computer
    You do not need to buy a 1000 watt power supply. Best way to determine how much PSU power you need can be calculated here:
    http://www.thermaltake.outervision.com/
    My guess would be to get one around 650-750 watts. Having more is always nice because it leaves you room for growth but also remember that technology is improving everyday and hardware is utilizing less power than previous editions and it keeps getting better.
    I personally would only recommend getting a 1000 watt PSU if you are doing serious overclocking, and/or running more than one high end gpu such as SLI or CrossFire.
    I have a system right now that I'm using which is i7 4770k, 16gb ram, 560Ti, SSD, and one mechanical HD, and I'm using a 600 watt PSU on Windows 8.1. The system is stable and never has problems with power.
    gluck
    BS, a gamer needs all the power we need more so when I over clock.
    Edit: I had a high Q PSU 750watt lasted 5 months playing bf3. I had 100 thousand minutes playing in 5 months. The psu over heated. When I took it apart to lookscey, the transformers were finished. If you plan on overclocking like I did you will need the
    higher watt psu. Don't fall into I told ya so.
    I was then running subzero temps so my overclocking was extreme. 3.5 Ghz running 5GHZ, Memory to voltages all over clocked. Video OC to its max, hard ware flashed OC'ed.
    If your going to be a pencil pusher with your computer then do whatever but he said a gaming computer
    The COUGAR GX V3 High-End PSU

  • Blue screen of death Windows 7 (BUGCODE_USB_DRIVER)

    I have the Inspiron 1564 and I am encountering many blue screens.
    Here is the information I have collected from the BSOD dump
    Bug Check String : BUGCODE_USB_DRIVER
    Bug Check Code : 0x000000fe
    Parameter 1 : 00000000`00000008
    Parameter 2 : 00000000`00000006
    Parameter 3 : 00000000`00000005
    Parameter 4 : fffffa80`05c66160
    Caused By Driver : usbhub.sys
    Caused By Address : usbhub.sys+12a60
    Fire Descripiton : Default Hub Driver for USB
    Crash Address : ntoskrnl.exe+6f880
    Thank you and possibly if someone could help me it would be great.
    I checked out the Device Manager and I noticed that the USB Controllers has a sign next to it when I plug in a USB ( by the USB Mass Storage Device and it says Windows is uninstalling this device. (Code 21))
    (And if i only need to reinstall the driver, I would like to know where i can locate it.)

    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 NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.
    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
    If you are overclocking stop.  (chances are if you dont know if you are, you are not)a
    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.  
    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button. (if available on  your site, MS doesnt have this)
     *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.
    Link for how to  upload below.
    http://www.wikihow.com/Use-SkyDrive
    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
    Please also run MSinfo32 and upload the output as well.
    To run MSinfo32 please go to start>run>MSinfo32
    Go to "file" "save" and upload the saved file with the DMPS
    System specs are extremely useful so please include whatever you know.
    Blue Screen View & Who Crashed are often wrong and should only be used in an emergency
    Team Zigzag3143.com
    Wanikiya & Dyami--Team Zigzag

  • Blue Screen error !!! 0x00000101

    Hi
    sorry if my english is`t that good....
    I recetnly have a problem with my windows...
    this blue screen error often appeare when I playing games...
    Os: win 7 32B
    Ram : 4g
    Cpu : core i3 2100
    and this is my minidump error that windows saved : http://0up.ir/up7/9-010210-15958-01.rar
    for more information i can tell u that i reistall my windows and defrag hard and error cheack my HDD

    STOP 0x101: CLOCK_WATCHDOG_TIMEOUT Troubleshooting
    Here's a good thread on http://www.sysnative.com/forums/showthread.php/1248-0x101-quote-A-clock-interrupt-was-not-received-on-a-secondary-processor-quote
    What you're looking for will be in one of the following categories:
    a) BIOS bug
    b) a driver whose activity is causing the target processor to lock up
    c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...) ?I wonder about CPU defect also)
    So, check the drivers http://www.carrona.org/dvrref.php
    Then check the inside of the case (temperature, voltage, dust, etc).
    Then run hardware stress tests
    Try this free video stress test: http://www.ozone3d.net/benchmarks/fur/
        FurMark Setup:
        - If you have more than one GPU, select Multi-GPU during setup
        - In the Run mode box, select "Stability Test" and "Log GPU Temperature"
        Click "Go" to start the test
        - Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
        - Click "Quit" to exit
     Try this free stress test: Free Software - http://download.cnet.com/Prime95-32-bit/3000-2053_4-192895.html
        Prime95 Setup:
        - extract the contents of the zip file to a location of your choice
        - double click on the executable file
        - select "Just stress testing"
        - select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
        - "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
        The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
        Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
        The Test selection box and the stress.txt file describes what components that the program stresses.
    More Video Stress Tests:
        1. Thanks to Vir Gnarus (http://www.sysnative.com/forums/members/vir-gnarus.html) for finding this video memory test: https://simtk.org/home/memtest
            Alternate download link (w/o registration) located here: http://folding.stanford.edu/English/DownloadUtils
        2. Two other video stress tests (may be more stressful than FurMark):
            NOTE: I have had reports that some ISP's will block this website
            Video Memory stress Test - http://nvworld.ru/utilities/vmt/
            Artifact Locator - http://nvworld.ru/utilities/alocator/
            Sorry, but I don't read the language that this website is made in.
        3. Another interesting test that came to my attention: http://www.ocbase.com/perestroika_en/index.php?Download
        USE AT YOUR OWN RISK - the program doesn't have a whole bunch of safety features to protect you from yourself!
        Quote:
        CPU Stress Tests:
        Only need to run 1 or 2 of the tests under most circumstances. I haven't used any of the tests myself, so I listed all that I was able to find.
        - http://downloadcenter.intel.com/Deta...19182&lang=eng
        - http://7byte.com/index.php?page=hotcpu
        - http://www.7byte.com/index.php?page=burnin64
        - http://www.overclock.net/general-pro...ress-test.html
        - http://www.fossiltoys.com/cpuload.html
        - http://www.pcworld.com/downloads/fil...scription.html
        - http://www.overclock.net/general-pro...ress-test.html
        - http://majorgeeks.com/CPU_Stability_Test_d215.html
        - http://www.xtremesystems.org/forums/...d.php?t=201670
        - the test(s) suggested at this link are bootable: http://www.techsupportforum.com/foru...ml#post2232929
    Then try replacing parts.
    Then look up the versions of your BIOS to see what changes were done.
    Recently it was found (here: BSOD Stop 0x00000101 and Stop 0x0000009c ) that a wipe and reinstall of Windows fixed a STOP 0x101 problem. I'd have to recommend at least running SFC.EXE /SCANNOW on any PC that has this problem (simply because it's too easy easy
    to do and it may fix things). 
    Wanikiya and Dyami--Team Zigzag

  • Blue screen error Windows 7 after June 2014 Windows updates

    Hi,
    just wondering if someone could help determine the cause of a blue screen error from interpreting the following minidump file. My PC has been having blue screen problems after getting the automatic windows updates recently. Initially the only way I could
    get the computer working was to restore the system back to prior to the updates. The updates seem to have now successfully installed but are still causing occasional blue screen errors. I have Windows 7 Home Premium
    The minidump is 061614-32666-01 andthe  link is as follows:
    https://onedrive.live.com/redir?resid=1665B282DEF2D2DC%21111
    Any help would be appreciated

    Hi,
    just wondering if someone could help determine the cause of a blue screen error from interpreting the following minidump file. My PC has been having blue screen problems after getting the automatic windows updates recently. Initially the only way I could
    get the computer working was to restore the system back to prior to the updates. The updates seem to have now successfully installed but are still causing occasional blue screen errors. I have Windows 7 Home Premium
    The minidump is 061614-32666-01 andthe  link is as follows:
    https://onedrive.live.com/redir?resid=1665B282DEF2D2DC%21111
    Any help would be appreciated
    These crashes were related to memory corruption (probably caused by a driver). 
    Please run these tests to verify your memory and find which driver is causing the problem.  
    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't
    know what it is you probably are not overclocking.
    Since it is more likely to be a driver please run verifier first.
    1-Driver verifier (for complete directions see our wiki here)
    If verifier does not find the issue we can move on to this.
    2-Memtest. (You can read more about running memtest here)
    If you cannot boot after enabling verifier reboot into safe mode
    In Vista & win & (F8)
    In win 8 http://www.howtogeek.com/107511/how-to-boot-into-safe-mode-on-windows-8-the-easy-way/
    Co-Authored by  JMH3143
    Wanikiya and Dyami--Team Zigzag

  • Lightroom 4.1 (3, 4 or any version) causes computer to blue screen and crash

    Recently bought the new Lightroom 4.1 in an attempt to fix this issue, which had been occuring off and on for some time.  I have major difficulties with importing and/or rendering previews or editing Canon 5D Mark II and Canon 5D Mark III images using Lightroom.  The computer abruptly blue screens, then reboots.  The blue screen code is 124.  I'll attach a record of minidumps (all caused by editing or importing images using LR4.)
    Not sure if that can be viewed, but please ask so I can send you the dump file for inspection if necessary.  It essentially shows the Bug Check Code as 0x00000124, caused by address ntoskrnl.exe+4b09bc.
    System Information
    Time of this report: 6/14/2012, 02:40:11
    Machine name: THANATOS
    Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7600) (7600.win7_gdr.120401-1505)
    Language: English (Regional Setting: English)
    System Manufacturer: System manufacturer
    System Model: System Product Name
    BIOS: BIOS Date: 12/09/10 21:08:39 Ver: 08.00.15
    Motherboard type is a Asus Crosshair Forumla IV
    Processor: AMD Phenom(tm) II X6 1100T Processor (6 CPUs), ~3.3GHz
    Memory: 16384MB RAM
    Available OS Memory: 16382MB RAM
    Page File: 2892MB used, 29870MB available
    Windows Dir: C:\Windows
    DirectX Version: DirectX 11
    DX Setup Parameters: Not found
    User DPI Setting: Using System DPI
    System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
    DxDiag Version: 6.01.7600.16385 32bit Unicode
    Display Devices
    Card name: NVIDIA GeForce GTX 580
    Manufacturer: NVIDIA
    Chip type: GeForce GTX 580
    DAC type: Integrated RAMDAC
    Device Key: Enum\PCI\VEN_10DE&DEV_1080&SUBSYS_15803842&REV_A1
    Display Memory: 4063 MB
    Dedicated Memory: 1503 MB
    Shared Memory: 2559 MB
    Current Mode: 1920 x 1080 (32 bit) (60Hz)
    Monitor Name: Generic PnP Monitor
    Monitor Model: SMBX2450
    Monitor Id: SAM0722
    Native Mode: 1920 x 1080(p) (60.000Hz)
    Output Type: DVI
    Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
    Driver File Version: 8.17.0012.9610 (English)
    Driver Version: 8.17.12.9610
    DDI Version: 10.1
    Driver Model: WDDM 1.1
    Driver Attributes: Final Retail
    Driver Date/Size: 2/29/2012 20:02:00, 17642816 bytes
    WHQL Logo'd: Yes
    WHQL Date Stamp:
    Device Identifier: {D7B71E3E-53C0-11CF-787E-8C351FC2C535}
    Vendor ID: 0x10DE
    Device ID: 0x1080
    SubSys ID: 0x15803842
    Revision ID: 0x00A1
    I have an 850W PSU.  Running Windows 7 Ultimate on a 150GB SSD.
    I find this very frustrating because it's a PC that I built and that can do any complex task--anything from using PS CS4 with multiple layers, playing top-end games like Crysis 2 and Diablo 3 with graphics on full.  Other than this RAW development issue, the computer is flawless and VERY fast.  Anyone have any ideas, or see a hole in the system specs?
    Cheers,
    _E

    The video driver is up to date, and I would assume compliant with LR4.
    My BIOS version is default, and I tried installing new BIOS updates but ran into troubles.  The Asus motherboard uses ATI Catalyst to introduce new system updates, but it fries my PC (assuredly a conflict with my nVidia card) making the rig run even slower.  In fact, using the ATI Catalyst disc (the one that came with my mobo) crashed once I had tried to install any motherboard utilities!  I've gone through the BIOS configuration and turned off all of this mobo's overclocking features and set everything to default.
    No overclocking going on whatsoever--not once, and never will.
    Reseated the memory and tested the memory with no negative feedback.
    The PSU is relatively new and of high quality.  I replaced an old PSU because of exactly what you mentioned above.  It's a Corsair GS800 (not 850W, 800W).
    I'm at the point right now where I suspect the motherboard is failing me somehow.  I only bought it because I was in a rush and would have normally opted fro a "non-overclocking-enthusiast's" board.  Perhaps there's a way of updating BIOS without utilizing the disc (the ATI Catalyst, more to the point?)
    The PC is new in a sense.  I seem to recall a point where LR3 worked with fewer crashes.  I built the thing April 2011.  Just reinstalled Windows 7 and all the software again.

  • Machine Check blue screen (with error codes)

    I thought I had this fixed, but apparently I was wrong. Every now and then, for what seems to be no apparent reason, I get this blue screen error:
    Quote
    CRITICAL STOP: MACHINE CHECK EXCEPTION
    A problem has been detected and windows has been shut down to prevent damage to your computer.
    If this is the first time you have seen this stop error screen, restart your computer. If this screens appears again follow these steps:
    Check to make sure any new hardware and software is properly installed. If this is a new installation, ask your hardware or software manufactorer for any windows updates you may need.
    If problems continue, disable or remove any newly installed hardware or software. Disbable BIOS memory options such as caching or shadowing.
    TECH INFO: ***STOP: 0x0000009c (0x00000004, 0x80545ff0, 0xb2000000, 0x00070f0f)
    I had similar problems before, but the blue screen is new after replacing my video card. (Before the new video card, the computer was freezing up with a black screen. I'm assuming the blue screen is a step in the right direction?) Original thread is here.
    Right now, this is my current system:
    Motherboard: K8T Neo-FIS2R [Bios version 2.0 (I think; its the most current version as of 2-15-05)]
    CPU: Athlon 3000+
    PSU: Antec Truepower 550 (+5V=40A; -5V=0.5A; +12V=30A; -12V=1.0A; +3.3V=32A; +5V SB=2A)
    RAM: 1 1GB DDR400 (cas 3.0)
    HD: Seagate ST320082 200GB SATA Drive (VIA driver)
    DVD: LiteOn DVD Rom
    Floppy Drive
    Running Windows SP2, all current updates installed
    NVidia 6800GT video card (Asus; using TechConnect driver)
    Soundblaster Audigy 2
    DLink Wireless Network Adapter (DWL-G520)
    I have tried replacing the RAM, HD, video card, and Power supply with similar results.
    The error message clearly states that I should try disabling memory options such as BIOS memory options such as caching or shadowing, but I don't know what affect this would have if I did this. Any opinions on this and other suggestions would be greatly appreciated.
    Thanks...
    - doubleozero
    - EDIT -
    One more note: Nothing is overclocked in PC. All temperatures seem normal. CPU does not go over 38C.

    I ran memtest for about 5 hours with no errors. I'll give it a go for a while w/o the sound card for a week or two.
    I wish this thing wasn't so hard to troubleshoot. For example, it was happening about 2 times a day before I tried new ram. After going with the new stick of ram, it was fine for about 10 days, so I thought it was solved. Then last night, I got two of these again.

  • Blue screen 109 error, mini dump attached, please help

    Hi Experts,
    I am frequently getting blue screen error in my laptop. Please help. The link to minidump file is given below. I am using Windows 7 ultimate operating system.
    I have tried a lot of things to avoid this dump but it keep recurring.
    https://onedrive.live.com/redir?resid=49561AD592663106!107&authkey=!AFI9kcFyy6ncfJ8&ithint=file%2c.dmp
    regards,
    Ayaz

    AA
    This one DMP file was inconclusive please run driver verifier to find the underlying cause
    Please run these tests to verify your memory and find which driver is causing the problem.  
    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't
    know what it is you probably are not overclocking.
    Since it is more likely to be a driver please run verifier first.
    1-Driver verifier (for complete directions see our wiki here)
    2-Memtest. (You can read more about running memtest here)
    Co-Authored by  JMH3143
    Wanikiya and Dyami--Team Zigzag

  • Blue screen in windows 7

    I have been getting the blue screen after windows has been running for a while. Sometimes it happens when I am trying to install something. I have uploaded minidump files to the sky drive but I can't seem to read them, I tried copying and pasting them to
    the desktop and opening them as notepad files but all I get is gibberish, at least it is to me. I need to know how to make these accessible to the pros so I can repair this problem. I have the Technical information from the blue screen here:
    A clock interrupt was not received on  a secondary processor within the allocated time interval.
    *** stop 0x000000101 (0x0000000000000031, 0x0000000000000000, 0xFFFFF88002FD3180, 0x0000000000000003)
    Don't know if this helps but there it is.
    I am running Windows 7 P 64 bit desk top
    Gigabyte MB GA-MA78Gm-S2H Rev 1.0
    4GB Crucial Ballistix PC6400 800 Mhz 2Volt BL2CP25664A80A
    AMD PHENOM 9750 2.4Ghz QUAD CORE
    CPU temp was 32-34 degrees C last time I checked.
    Disk error check was inconclusive ( I walked away and when I returned windows had loaded ) I assume this means that no errors were found.
    RAM scanned and no errors were found.
    https://skydrive.live.com/?mkt=en-US#cid=74B3C1D7DE3540EC&id=74B3C1D7DE3540EC!130

    Alan
    These worked but were inconclusive 0oease run driver verifier to pin down the misbehaving driver.
    These crashes were related to memory management (probably caused by a driver). 
    Please run these tests to verify your memory and find which driver is causing the problem.  Since this appears to be a driver I would start with driver verifier.
    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't
    know what it is you probably are not overclocking.
    1-Memtest. (You can read more about running memtest here)
    2-Driver verifier (for complete directions see our wiki here)
    Co-Authored by  JMH3143
    Wanikiya and Dyami--Team Zigzag

  • Recurring Physical Memory Dump and Blue Screen on Windows 7

    I recently built a PC and have been getting pretty frequent blue screens whenever I use it. Today I got about 5 within an hour and have finally tried to fix it. I got Windows Debugger and have analyzed the .dmp files and the most common one that I have gotten
    is this one:
    *                        Bugcheck Analysis                                   
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa800d062028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.
    Debugging Details:
    BUGCHECK_STR:  0x124_GenuineIntel
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  f
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre
    STACK_TEXT:  
    fffff880`031dfb58 fffff800`0320ea3b : 00000000`00000124 00000000`00000000 fffffa80`0d062028 00000000`bf800000 : nt!KeBugCheckEx
    fffff880`031dfb60 fffff800`02da3463 : 00000000`00000001 fffffa80`0cc9f9a0 00000000`00000000 fffffa80`0cc9f9f0 : hal!HalBugCheckSystem+0x1e3
    fffff880`031dfba0 fffff800`0320e700 : 00000000`00000728 fffffa80`0cc9f9a0 fffff880`031dff30 fffff880`031dff00 : nt!WheaReportHwError+0x263
    fffff880`031dfc00 fffff800`0320e052 : fffffa80`0cc9f9a0 fffff880`031dff30 fffffa80`0cc9f9a0 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`031dfd50 fffff800`0320df0d : 00000000`00000008 00000000`00000001 fffff880`031dffb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`031dfd90 fffff800`03201e88 : 00000000`00000000 fffff880`031d7180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff880`031dfdc0 fffff800`02c8b4ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff880`031dfdf0 fffff800`02c8b313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`031dff30 fffff880`053889c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff880`031ffb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!C1Halt+0x2
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: GenuineIntel
    IMAGE_NAME:  GenuineIntel
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    IMAGE_VERSION:  
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_cache
    FAILURE_ID_HASH:  {270f58cb-a20a-a72d-6d81-eb8c82f01f7a}
    Followup: MachineOwner
    It looks like it's happening because of a system update I may have done? I'm not sure what to make of this or how to fix it.
    Any help would be greatly appreciated.
    Thanks

    Mike
    Virtual all of these are hardware related so I would start there.  This type of crash is called a BCC124 and 99 times out of 100 it is hardware related.
    Stop 0x124 is a hardware error
    If you are overclocking try resetting your processor to standard settings and see
    if that helps.
    If you continue to get BSODs here are some more things you may want to consider.
    This is usually heat related, defective hardware, memory or even processor though
    it is"possible" that it is driver related (rare).
    Stop 0x124 - what it means and what to try
    Synopsis:
    A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.
    Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.
     Generic "Stop 0x124" Troubleshooting Strategy:
    1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable
    ways.
    2) Ensure that the machine is adequately cooled.
     If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.
    3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
    It is good practice to run the latest drivers anyway.
    4) Update the motherboard BIOS according to the manufacturer's instructions and clear the CMOS.
    Their website should provide detailed instructions as to the brand and model-specific procedure.
    5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
    At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.
    6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
    The most obvious examples are the RAM and HDD(s).
    For the RAM, use the 3rd-party memtest86 utility to run many hours worth of testing. (6-8 passes to stress the ram out)
    For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
    Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is
    free from defects - only that none were encountered during the test passes.
    7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games,
    utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
    Should that fail to mitigate the 0x124 problem, jump to the next steps.
    If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine
    is still free from 0x124 crashes.
    Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
    If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
    Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:
    8) Clean and carefully remove any dust from the inside of the machine.
    Reseat all connectors and memory modules.
    Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.
    9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
    Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.
    Should you find yourself in the situation of having performed all of the steps
    above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.
    More advanced reading can be found here from a MS MVP IT PRO
    http://captaindbg.com/bug-check-0x124-whea_uncorrectable_error-how-to-troubleshoot/
    Wanikiya and Dyami--Team Zigzag

  • Blue Screen when connecting to internet

    I have this problem: blue screen appear in Win XP randomly when i try to connect to internet using a Genius modem. The error notification is this:
    "A problem has been detected and windows has been shut down to prevent damage to your computer.
    DRIVER_IRQL_NOT_LES_OR_EQUAL
    Tehnical information:
    ***STOP: 0x000000D1 (0X00000000, 0x00000002, 0x00000000, 0x00000000)
    Beginning dump of phisical memory....."
    First i suspected a memory issue, so i tested it with Memtest 86 but didn't find any errors. I run 3DMark 2001 several times with no errors, 3D games runs also without problems. I put the modem in 3rd PCI slot, the 4th is occupied by the network adapter and the 5th slot by the SB Audigy (with the newest drivers installed from Creative web site). There is an IRQ sharing between the network adapter and an USB host controller used for a Logitech Steering Wheel. CPU temp never exceed 50C, Dinamic Overclock is disabled and Performance is set to slow.BIOS is 1.3. Since i have this motherboard, (six days) i have this very annoyng problem 1 of 4 times i connect to the internet.
    Please, if you do have any suggestions i need some help.
    CPU P4 [email protected]
    MSI 865PE NEO2 LS
    MSI GFORCE4 TI 4200
    512 MB DDR400
    40GB WD
    CREATIVE SB AUDIGY
    GENIUS MODEM

    I researched this a bit, with my very similar error.
    I can tell you this much with certainty--that blue screen is a driver problem. Maybe in your case Norton FW is bringing it out, but it is probably a conexant chipset in your modem, and you are getting the same end result as me.
    They haven't released, at least that I can find, a driver for this modem chip set that correctly handles irq sharing. Conexant is what's inside of a suprising number of modems, and the software (base driver from them to the modem OEM) is old.
    Pretty sure Danny's on the right track with hyperthreading being the problem. The other possibility is the whole complicated HAL/APIC deal. Toss in some other HAL acronyms.
    But hyperthreading is a more recent development, so I will give it a shot, soon. Don't feel like crashing at the moment. But if that is the answer, I'm not going to turn off HT. Nope, the modem will be stuck with the generic 56k MS driver, which works ok, sorta, just doesn't report speeds right, or do compression and error handling right. Or 56K for that matter. OK, it's a bonejob, but I need HT more than a dial-up.
    Unless somebody has some ideas.
    One day I will take out my collection of really crappy modems and shoot them. Do a web page. I now have 5.
    Don't buy Bestdata. 2 year old driver and they want money to talk to tech support. Brand new. Says XP PRO on the box.

Maybe you are looking for