Ubuntu reports bad RAM?

Similar Questions

• Kernel Panic #2 and another batch of bad RAM?

  OKAY this is getting annoying. A few days ago, I posted about a previous kernel panic and if it linked to the bad RAM.

  My question has been answered by Illaass and Grant Bennet-Alder, the culprit in my kernel panic was bad RAM as Illaass noted

  The expression '6 banks to report errors' panic report almost always means bad RAM.

  The key is to several banks of error reports.

  Also the phrase "Machine Check" usually means a hardware problem

  I got the replacement RAM this morning and installed, the system showed as having 12 GB for about two hours. I got a Kernel Panic OTHER then when I rebooted my machine showed as having 8 GB of RAM once again, the two new modules have been installed would not be saved. -I opened the side of my machine to instept memory, I was surpised to find the error LED on one of the DIMMs I had installed just a few hours before.

  I have therefore three options in front of me.

  1. I received a second faulty module in the modules that I replaced, but what is the probability that I would get two modules of the 'bad' like this.

  2. the second is of course the DIMM location on riser from the Mac Pro RAM "kills" any module installed in it. (I don't know what is the probability of this)

  So I contacted the dealer that I bought the memory with a few basic troubleshooting I've been able to identify the faulty module and remove (and the other 'good' module of my system), with the deleted modules my system boots and behaves correctly, with replacement modules in my system boots (slower than normal) and new modules do not even register System Profiler , they show that slots "empty."

  I took my machine to my local provider of Apple and asked their opinion, they said that it is very unlikely that the slot is the question and I just received two faulty memory sticks.

  I contacted the retailer and they will send me another one module replacement, but I don't know what the probability of exactly the same thing repeats again and again.

  I also have the details of my second kernel panic which I attach to this message in a minute, I'm open to suggestions as to what can happen.

  Fri Jun 17 14:13:28 2016

  panic (cpu 0 0x8a1d1e8b appellant): "error memory Fbd incorrigible detected. FERR_NF = 0 x 00002000, NERR_NF is 0x02002021\n"@/SourceCache/AppleMCEDriver/AppleMCEDriver-119.4.0/AppleMCEDriver .cpp:947

  Backtrace (CPU 0), Frame: return address (4 potential args on stack)

  0x10bc58: 0x21b837 (0x5dd7fc 0x10bc8c 0x223ce1 0x0)

  0x10bca8: 0x8a1d1e8b (0x8a1d290c 0 x 2000 x 0 2002021 0x8100a4)

  0x10bd18: 0x8a1d215d (0 x 12654500 0 x 12654500 0 x 2 0 x 820044)

  0x10bd98: 0x7fda0a50 (0 x 12654500 0 0 0x117f1880 x 0 x 0)

  0x10bdc8: 0x7fd9fd09 (0x1141f200 0 x 0 0 x 0 0x1c)

  0x10bde8: 0x7fdaeebc (0x1c 0x10be5c 0 x 8 0x7fdac5f0)

  0x10be18: 0x7fdaf0be (0x117d391c 17 0x1141f53e 0 x 0 x 0)

  0x10be78: 0x7fdb662e (0x112ecd28 0x10bec8 0x10bef8 0x0)

  0x10be98: 0x56ac20 (0x112ecd28 0 0 0x112cad80 x 0 x 0)

  0x10bee8: 0x7ffad5bb (0x1141f280 0 0 0x1141f280 x 0 x 0)

  0x10bf18: 0x7fd93213 (0x117c8600 0 x 0 0 x 0 0 x 49)

  0x10bf38: 0x7fd9e911 (0 x 49 0 0 0x10bf78 x 0 x 0)

  0x10bf58: 0x580d96 (0x11329b80 0 x 0 0x11329f80 0 x 49)

  0x10bf78: 0x2ab432 (0 x 49 0x8941ba50 0x1c8db 0 x 1)

  0x10bfd8: 0x2a1c2e (0x8941ba50 0x2a2a00 0 x 0 0x2a2a5b)

  0x8941bae8: 0x225bba (0x84bf3c 0x2d6586f7 0x85c 0x84bf28)

  0x8941bb48: 0x22698c (0 x 1 0x141873d4 0x112c4c58 0x85c)

  0x8941bbb8: 0x2275b0 (0x141873f0 0x141873f0 0x8941bc18 0 x 233203)

  0x8941bc28: 0 x 227654 (0 x 0 0 x 0 0 x 0 0 x 0)

  0x8941bc48: 0x2a1422 (0 x 0 0 x 0 0xdd 0 x 80000002)

  0x8941bcd8: 0x260c62 (0x2199ede8 0 0 0x2a45e3 x 0 x 0)

  0x8941bde8: 0x25847e (0x8941bf40 0x63e14000 0xd2a 0 x 3)

  0x8941bf38: 0x2ab83c (0x121d5d74 0x63e14000 0xd2a 0 x 3)

  0x8941bfc8: 0x2a18da (14184204 x 0 0 x 0 0 x 10 0 x 0)

  Extensions of kernel in trace (with dependencies):

  com.apple.driver.AppleMCEDriver (1.1.9) @0x8a1ce000-> 0x8a1d3fff

  dependency: com.apple.iokit.IOACPIFamily (1.3.0) @0x7fad4000

  com.apple.driver.AppleAPIC (1.4) @0x7ffac000-> 0x7ffaefff

  com.apple.driver.AppleACPIPlatform (1.3.6) @0x7fd91000-> 0x7fdd3fff

  dependency: com.apple.iokit.IOACPIFamily (1.3.0) @0x7fad4000

  dependency: com.apple.iokit.IOPCIFamily (2.6.5) @0x7fcda000

• Blue screen and bad RAM memory?

  My MBP 2011 early all just stopped working yesterday, it worked very well without any problem of performance for the last 5 years, and then suddenly a blue screen (of death) and it has problems starting.

  He will ring the Bell to start, display the bar loading and Apple, and then there will be a glitch on the big screen (horizontally) 1 inch above the Apple, after that, the fans speed up and all that I see a gray screen, not user interface.

  I zapped the PRAM/MSC and tried the unique memory sticks, I have no spare RAM on hand, but who will order soon.

  Tips to solve this problem?

  AHT says this - 65/4MEM/4000000000: 0x84f6f918

  Google says it is bad memory

  Here is the BSoD:

  

  I think you have a problem of memory, although if your MacBook Pro 15 or 17 inch, you should consider video issue as well now.

  http://www.Apple.com/support/MacBookPro-videoissues/

• iMac running slow. Etrecheck reports bad performance: joint report

  EtreCheck version: 2.9.12 (265)

  Report generated 2016-05-24 15:39:21

  Download EtreCheck from https://etrecheck.com

  Time 12:25

  Performance: Poor

  Click the [Support] links to help with non-Apple products.

  Click [details] for more information on this line.

  Problem: Computer is too slow

  Hardware Information: ⓘ

  iMac (21.5 inch, at the end of 2013)

  [Data sheet] - [User Guide] - [warranty & Service]

  iMac - model: iMac14, 1

  1 2.7 GHz Intel Core i5 CPU: 4 strands

  16 GB expandable RAM - [Instructions]

  BANK 0/DIMM0

  OK 8 GB DDR3 1600 MHz

  BANK 1/DIMM0

  OK 8 GB DDR3 1600 MHz

  Bluetooth: Good - transfer/Airdrop2 taken in charge

  Wireless: en1: 802.11 a/b/g/n/ac

  Video information: ⓘ

  Iris Pro Intel

  W2242 1680 x 1050 at 60 Hz

  iMac, 1920 x 1080

  Software: ⓘ

  OS X El Capitan 10.11.5 (15F34) - since startup time: less than an hour

  Disc information: ⓘ

  HTS541010A9E662 disk HARD APPLE disk0: (1 TB) (rotation)

  EFI (disk0s1) < not mounted >: 210 MB

  Macintosh HD (disk0s2) /: 999,35 go-go (846,23 free)

  Recovery HD (disk0s3) < not mounted > [recovery]: 650 MB

  USB information: ⓘ

  Apple Inc. BRCM20702 hub.

  Apple Inc. Bluetooth USB host controller.

  Apple Inc. FaceTime HD camera (built-in)

  Hub keyboard Apple, Inc.

  Apple Inc. Apple Keyboard

  Reader SuperDrive for MacBook Air Apple Inc..

  Lightning information: ⓘ

  Apple Inc. Thunderbolt_bus.

  Guardian: ⓘ

  Any where

  Launch system officers: ⓘ

  [loaded] 7 tasks Apple

  [loading] 151 tasks Apple

  [operation] 80 tasks Apple

  Launch system demons: ⓘ

  [loaded] 46 tasks Apple

  [loading] 159 tasks Apple

  [operation] 86 tasks Apple

  Launch officers: ⓘ

  [no charge] com.adobe.AAM.Updater - 1.0.plist (2016-02-08) [Support]

  [failure] com.adobe.ARMDCHelper.cc24aef4a1b90ed56a... plist (2016-05-14) [Support]

  [operation] com.bjango.istatmenusagent.plist (2015-09-29) [Support]

  [operation] com.bjango.istatmenusnotifications.plist (2015-09-29) [Support]

  [operation] com.bjango.istatmenusstatus.plist (2015-09-29) [Support]

  [loading] com.oracle.java.Java - Updater.plist (2014-12-09) [Support]

  Launch demons: ⓘ

  [loading] com.adobe.ARMDC.Communicator.plist (2016-05-14) [Support]

  [loading] com.adobe.ARMDC.SMJobBlessHelper.plist (2016-05-14) [Support]

  [loading] com.adobe.agsservice.plist (2016-02-08) [Support]

  [loading] com.adobe.fpsaud.plist (2016-05-10) [Support]

  [operation] com.bjango.istatmenusdaemon.plist (2015-09-29) [Support]

  [loading] com.microsoft.autoupdate.helpertool.plist (2016-05-17) [Support]

  [loading] com.microsoft.office.licensingV2.helper.plist (2015-12-06) [Support]

  [loading] com.oracle.java.Helper - Tool.plist (2014-12-09) [Support]

  [operation] com.syniumsoftware.CleanAppDaemon.plist (2014-12-20) [Support]

  User launch officers: ⓘ

  [failure] com.adobe.ARM. [...]. plist (2015-01-27) [Support]

  [loading] com.google.keystone.agent.plist (2016-03-03) [Support]

  Items in user login: ⓘ

  iTunesHelper Application (/ Applications/iTunes.app/Contents/MacOS/iTunesHelper.app)

  PopClip application (/ Applications/PopClip.app)

  Clipboard history application hidden (/ Applications/Clipboard History.app)

  Dropbox application (/ Applications/Dropbox.app)

  A fantastic Application (/ Applications/Fantastical.app)

  BetterTouchTool Application (/ Applications/BetterTouchTool.app)

  Antnotes application (/ Applications/Antnotes.app)

  Australian weather application (/ Applications / Australian Weather.app)

  Hidden AdobeResourceSynchronizer Application (/ Applications / Adobe Acrobat 2015/Adobe Acrobat.app/Contents/Helpers/AdobeResourceSynchronizer.app)

  Alfred 3 Application (/ Applications/Alfred 3.app)

  Other applications: ⓘ

  [ongoing] 2BUA8C4S2C.com.agilebits.onepassword4 - helper

  [performance]    EKT6323JY3.com.guidedways.TodoMac.helper

  [load] to. EternalStorms.yoinkLoginStarterHelper

  [loading] au.com.shiftyjelly.australianweather.mac - helper

  [ongoing] au.com.shiftyjelly.australianweather.Mac.49312

  [ongoing] com.agileroute.clipboardhistory.52512

  [ongoing] com.etresoft.EtreCheck.56032

  [ongoing] com.flexibits.fantastical.57312

  [ongoing] com.getdropbox.dropbox.54752

  [ongoing] com.hegenberg.BTTRelaunch.95712

  [ongoing] com.hegenberg.BetterTouchTool.52192

  [ongoing] com.pilotmoon.popclip.72032

  [operation] com.runningwithcrayons.Alfred - 3.145632

  [ongoing] ua.com.AntLogic.Antnotes.48352

  ua.com.AntLogic.AntnotesLauncher [loading]

  [loading] 397 tasks Apple

  [operation] 212 tasks Apple

  Plug-ins Internet: ⓘ

  AdobeAAMDetect: AdobeAAMDetect 1.0.0.0 - SDK 10.6 (2016-02-08) [Support]

  FlashPlayer - 10.6: 21.0.0.242 - SDK 10.6 (2016-05-24), [Support]

  QuickTime Plugin: 7.7.3 (2016-05-17)

  AdobePDFViewerNPAPI: 15.010.20056 - SDK 10.8 (2015-12-19) [Support]

  AdobePDFViewer: 15.010.20056 - SDK 10.8 (2015-12-19) [Support]

  Flash Player: 21.0.0.242 - SDK 10.6 (2016-05-24), [Support]

  Default browser: 601 - SDK 10.11 (2016-05-17)

  npDDRia: 0.0.14.3 - 10.9 SDK (2014-10-02) [Support]

  SharePointBrowserPlugin: 14.6.4 - SDK 10.6 (2016-05-17) [Support]

  MeetingJoinPlugin: Unknown - SDK 10.6 (2014-08-05) [Support]

  JavaAppletPlugin: Java 8 update 65 build 17 (2015-11-03) check the version of

  Safari extensions: ⓘ

  1Password - AgileBits - https://agilebits.com/onepassword (2016-05-24)

  Cleaner Facebook - Sonny Fazio - http://sonstermedia.com (07-08-2014)

  Adblock more - Eyeo GmbH - https://adblockplus.org/ (2016-03-29)

  QR Code Generator - D.G. Midwinter - http://www.midwinter-dg.com/downloads.html (2016-02-15)

  Save on Pocket - Read It Later, Inc. - http://getpocket.com/ (2015-11-10)

  Sho.RT - Nowy - http://nowy.co.nr (07-08-2014)

  3rd party preference panes: ⓘ

  Flash Player (2016-05-10) [Support]

  Java (2015-11-03) [Support]

  Time Machine: ⓘ

  Time Machine not configured!

  Top of page process CPU: ⓘ

  4% WindowServer

  2% Dropbox

  kernel_task 2%

  1% iStatMenusDaemon

  0% AdobeCRDaemon

  Top of page process of memory: ⓘ

  955 MB kernel_task

  Mdworker (15) 246 MB

  Safari of 246 MB

  Dropbox 197 MB

  180 MB mds_stores

  Virtual memory information: ⓘ

  9.75 GB of free RAM

  6.25 GB used RAM (3.71 GB being cached)

  Used Swap 0 B

  Diagnostic information: ⓘ

  24 may 2016, 15:12:46 Self test - passed

  24 may 2016, 01:55:15 PM/Library/Logs/DiagnosticReports/Adobe Flash Player install Manager_2016-05-24-135515_ [redacted] .crash

  / Applications/utilities/Adobe Flash Player install Manager to Install Flash Player Manager.app/Contents/MacOS/Adobe

  Ways to help make a slow Mac faster

  17 reasons why your Mac runs slower than expected

  Slow performance of Mac? This Article addresses!

  Difficulty of slow start in OS X | MacFixIt - CNET Reviews

  How to fix the slow down time and start. | MacTip.net

  6 easy tips to speed up OS X Yosemite on your Mac.

  Avoid using third-party software that claims to clean your computer. This software does more harm than good. In addition, you don't need it. Note that all computers become slower over time even in the normal conditions of use. Generally, the experienced users erasing the hard drive and do a clean install from scratch at least once a year or every time that the installation of a major upgrade of the OS. Well sure doing so also means that you need to maintain regular and several backups.

  Add more RAM or reduce the number of simultaneously executed from applications and utilities. Remove unnecessary software such as anti-malware and that promises to clean your Mac. Look for the runaway process: Runaway applications can shorten the battery life, affect performance and increase the heat and fan activity. Also, visit The FAQ XLab and read the FAQ on the treatment with The Spinning Beach Ball of Death.

  The ultimate solution

  Back up everything, wipe the drive, reinstall OS X and restore your data from backup. Reinstall the third-party software of original/zero media.

  [Permission to use any part of the foregoing has been granted by khati, exclusively, to theratter.]

  
  

  Nothing really stood out in the report of EtreCheck as a cause of poor results.
  

• How will I know if I have a bad RAM or bad treatment or a bad hard drive?

  Hi guys I recently opened my laptop for cleaning fan and so I disassembled it and I just noticed that the thermal paste is pretty bad, so I replace and apply a new thermal compound can clean the vents, then I put the laptop back together, then what happens is that when I copy the files it takes me a lot of time I reinstalled windows , then what is happening is that it's always the same thing how do you know and what are the factors which makes it slow during the copying thanks for help

  Here is my card

  Intel pentium dual-core [email protected]

  toshibamk3255gsx ata hdd

  2 x 1 GB ddr2 800 mhz ram

  test of Windows 7 ultimate 32 bit

  Yep

  We need a willing participant :/

  Not that she'll show us everything that isn't in the original post, but can at least help the op get a new version :)

  http://www.CPUID.com/softwares/CPU-z.html

  He may have followed the instructions of shots image download and screen well :)

• Satellite A100-250: A value of bad RAM

  Hello

  I have a Toshiba a100-250.
  In addition to the 512 MB ram module, I bought a 1 024 MB module to boost it up a little bit. They are running and DDR2 at 533 mhz. Now the problem is that my computer laptop doesn´t recognizes the two modules.

  I was just curious and exchanging modules and put them separately or together in different locations, but it doesn´t find 1 024 MB module if both are put in place or module 512 if I do not put one inside.
  I updated my bios 2.10 BU he doesn´t solve the problem. Can please help me because now I have a 512 MB module which is useless.

  Thanks in advance!

  Hello

  Are you sure you bought a 1 024 MB module at 100%?
  Because it sounds like the new module of memory has only 512 MB.

• R [52] Description of bad ram online?

  Hello

  I needed a ram upgrade on my ibm thinkpad r52, then I looked towards the top of the form to:

  http://www-307.IBM.com/PC/support/site.WSS/document.do?lndocid=MIGR-58833#mem

  Here, it is clearly mentioned that I need DDR ram - so I bought it - was very expensive, because it is more so common, does not fit - so I understood, my laptop DDR2 ram needs.

  Had to drive back to the shop, so I had a lot of hassle, cost for 2 times the path, and of course I'm old DDR ram which I can't use.

  I look forward to the correct information on the Web site of the company that wants to be in a League of '' business. ''

  @balabushka:

  You're wrong.

  (a) there is NO such thing as 4200 DDR RAM, not for laptops anyway.

  (b) the number '2', 'PC' letters in the RAM specification means DDR2.

  Therefore, if you knew what you were looking in a first time, you have not made a mistake.

  Second, even if you didn't know about the card, any competent retailer would have provided you with correct RAM what is indicated on the support page...

• Photoshop cs 5 bad RAM memory

  No happy feeling on my new PC and how to behave (LeRiz) plugins I decided to add another memory to 8 Gig RAM to my totaaling 4 12G. I thought it would make things got super speed but to my surprise it actually slower fel.

  I went to-> Preferences-> performance and checked my meory usage and my problem seems obvious. That Photoshop does not show that I added memeory and think that I only have 4 Gigs. How can this be? How can I let Photoshop know that I have more memory than what he thinks I have?

  Thanks in advance

  Mich

  OS: Windows 7 Home Premium 64-bit

  Photoshop CS5 32/64-bit

  32-bit applications are unable to use more then 4 gigabytes of ram, so if you use the 32-bit version you can only see the possible 4 gigs max ram, like the poster above, use the 64-bit version of Photoshop and you get more ram available for use.

• Interactive report - bad graphic value data axis

  Hello
  
  We have created an interactive report based on the demo_orders table.
  The interactive chart displays incorrect data on the y-axis (4,00000 instead of 4 000,00)!
  Values in the table are ok, even the value displayed when the user clicks about data specific is correct.
  
  Anyone had similar problems?
  
  Request Express 3.2.0.00.27
  AnyChart #5.1.3
  
  
  Thank you.
  
  Kind regards
  Kristjan

  Hi Kristjan,

  I am able to reproduce the issue you report, using a report interactive optional APEX 3.2.1 and 4.0, where the language of the application is a non-English. So for example, if my English is * 10 000,00 graphic label * and when I pass the main language of the Application in German, so the values displayed should be * 10,000.00 * however it is incorrectly appearing as * 10 000 *. When you run in some non-English languages, used NLS decimal separator is a comma ",", but it is not properly applied to interactive report table. The problem is that the decimal separator parameter in the XML table is not correctly be escaped and is ignored. I have connected the bug 10154666 to follow this issue and a fix for this will be available in our next release. Thanks for that bring to our attention. At the same time, while ensuring that the values in your chart are displayed accurately, it might be better to create a region of separate table on the page in question, rather than using interactive report table.

  Kind regards
  Hilary

• VM reports bad disk VMDK

  I run RVTools against our VMware environment every morning and today one of the virtual machines is back with a message "possibly a VMDK of Zombie file.» Please check ". When I change the settings of the virtual machine and look at the hard drive, it shows provisionsed size = 0 and the vmdk file appears as vmname - 000002.vmdk. Is not the actual name of the file (see screenshot) vmdk. The virtual machine is in place and works very well. Anyone know what could be the cause?

  Thank you

  Scott

  Hello.

  You have known snapshots on this virtual machine?  That's what "vmname - 000002.vmdk" is pointing.

  Good luck!

• AHT inconsequential error Ram 4MEM (Mac Pro 4.1)

  Hi all.

  Something weird going on here. Evil Finder behave sometimes (especially with the readers of WebDAV connected cloud/external) and Photoshop don't... Well well... strange things. So I thought I would check my material with AHT.

  I have a Mac Pro 4.1 / 2.93 GHz Quad with 24 GB of RAM: 2 x 4 and 2 x 8 GB. AHT reports a RAM error (4MEM). So I removed all the DIMMS and test began with the two 4 GB ones and AHT returned an error (4MEM) RAM. When I test both 4 GB modules in AHT 1 and 2 housing reports and a mistake. When I test a single module of 4 GB in slot 1 or 2, I get no error 4MEM. So the two modules installed together DIMMS = error. Installed individually don't = "no found prolems.

  In addition, 4MEM errors seem incompatible:

  65/4MEM/40000006: 0X799D7C18

  9/4MEM/40000006: 0X799D2998

  Then, I tested all of the 24 GB of RAM with MemTest86 CD but he could not find any problems.

  Someone has an idea, what happens?

  It would be really good if, when an error has been detected, memory modules would all just dropping dead, problems would be easy to isolate. But this isn't the case. Memory problems are difficult to find, they come and go, it is very difficult to 'catch them in the Act. Synthetic patterns of tests memory do not always generate the same failure that made a running system.

  But your money Mac Pro tower with processor Xeon processor uses memory RAM of code of error correction. Modules of memory have eight extra in addition to the 64 data bits control bits, as well as your Xeon processor use on all references to memory.

  On writing, permutations of parity on the subsets manufactured with care the data bits are stored in the extra bits '' syndrome. '' On reading, a lot of correction and error detection can occur. Mistakes single-bit are detected and hardware corrects these errors in tense cycle of memory, without any software intervention. Error indicators are read from time to time in the background, and the results are recorded by the memory module.

  Generally, a benarde error cannot be corrected, so to design this cause your Mac to stop during a panic machine control, core, often detected by multiple processors to prevent the poisoning of your data.

  Errors counters can be read by the memory of the about this Mac report:

  

  chart de.com

  your report will be slightly different, but the information it presents is STATIC - for updated information, you must refresh the report or call it again.

  Many tests memory of third parties are not designed to run on a Mac with memory error correction. As simple mistakes are corrected in Hardware on-the-fly, they aren't.

  In addition, the error correction is used very aggressively at the start. The reasoning is that the nay errors that occur in these seconds must be so severe that the modules must not be used by the system, and their locations will be marked "void".

  Any module that is seen as BAD in any situation is really BAD, even if they suffer later. If your Mac was overheating for a different reason, which may explain why the modules tested bad is perhaps the only excuse. If you eliminate overheating, these modules may be ok later.

• Guard judgment of Windows XP. Event Veiwer Watch: \Device\Harddisk0\D, has a bad block

  I have a Dell Dimension 2400 with Win XP PRO SP3. It keeps closing after half an hour to an hour. The event viewer shows the following error in the system log: \Device\Harddisk0\D, has a bad block

  Same thing happens in Safe Mode as well. I ran McAfee who reported no virus. I have auto-updated from Microsoft on and just installed the lates updates.

  Help, please. Thank you... Nam

  Speed stop?

  Unexpected/unpredictable and quick stops are generally caused by overheating or bad RAM modules.  This happens too fast to create an entry in the newspapers.  Try downloading / running the freeware 'CoreTemp'.  It will show you how hot your CPU is getting and how close to maximum temperature, it is.  If this is your problem, open your folder and check your fans to make sure they turn all.  Use a can of compressed air to remove dust, because it can act like a blanket and heat your components.

  To solve your problem of bad block, run "Chkdsk" with the 'repair' or ' / R ' option.  This should clean up your bad block problem.

  "How to perform the disk error checking in Windows XP"

  <>http://support.Microsoft.com/kb/315265 >

  HTH,

  JW

• Since installing new RAM, I now have a BSOD.

  I'm currently under Win 7 64 bit. I moved from 8 GB of ram, 16 GB, and after installing the new memory modules live, every now and then my system crashes with the BSOD. Here's the dmp file...
  http://www.wenatcheekennelclub.com/022713-33384-01.dmp
  Any ideas on what is the cause? Bad RAM? Conflict?

  These accidents were caused by the corruption of memory usually a driver, but since you updated your RAM at two different times, I ran two tests below.  First run Memtest and if that comes back clean run driver verifier.

  * Don't forget to download any other DMP files (especially those running auditor)

  * If you are overclocking reset all default before running these tests.
  In other words STOP!   If you don't know what it means that you're probably not

  1 - Memtest.
  * Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org
  * Boot from the CD and let it run at least 5 or 6 passes.
  * Don't forget, anytime Memtest reports errors, it can be bad RAM or a bad motherboard slot.
  * Test the sticks individually and if you find a good, test it in all slots.

  Any error is indicative of a memory problem.
  If a well-known stick fails in a slot of motherboard, it's probably the slot.
  
  2. Driver Verifier
  Using Driver Verifier is a dubious proposition. Most of the time it will crash and it will tell you what is the driver.

  * But sometimes it will crash and will not tell you the driver.
  * At other times it will crash until you can connect to Windows. If you can't mode without failure, then you will have to resort to editing the registry offline to disable driver verifier.
  * I would suggest that you first back up your data and make sure that you have access to another computer so you can contact us in case of problems.
  * Then do a system restore point (so you can restore the system using the functionality of Vista/Win7 Startup Repair).

  * Under Windows 7, you can do a startup repair disk by clicking Start... All programs... Maintenance... Create a system - with Windows Vista repair disc, you need to use your drive installation or from the "Repair your computer" option at the top of the Safe Mode menu.
  
  Here is the procedure:
  -Go to start and type "auditor" (without the quotes) and press enter
  -Select 'Create a custom settings (for code developers)' and click 'Next '.
  -Select "Select individual settings from the list complete" and click "Next".
  -Select the entire document except for "Low resource Simulation" and click "next".
  -Select "Select driver names from a list", then click "next".
  * Select all drivers that are NOT supplied by Microsoft and click on "Next".
  -On the next page, select "Finish".
  * Restart the system and wait as he crashed to blue screen.
  * Continue to use your system normally and if you know what are the causes of the crash, do it several times. The objective here is to get the system crash because Driver Verifier is stressing out the drivers. If it is not planted for you, then let it run for at least 36 hours of continuous operation.
  * If you are unable to Windows because it crashes too early, try safe mode.
  * If you can't mode without fail, try to use the system from the installation DVD restore to bring the system back to the previous point of restoration that you created.

  * Further reading
  http://support.Microsoft.com/kb/244617

• Replacement of my RAM will fix my problems?

  Ive had a laptop to play for about 5 years now. He was notorious for overheating and it happened a lot. After reviewing the problem for a few years with fans and coolers, I finally got a virus that put an end to him. I reinstalled Windows 7 (64 bit) on this subject, it worked for a little while, but had many problems. Finally, I had a boot error after it overheats once and I could not get past the blue screen with the error so I took it to a local computer maintenance shop to check how much it would cost me for repairs. The tech helped me to discover that one of my RAM slots has been damaged (either moisture or heat damage) he told me that I would be better to replace the whole motherboard and I couldn't afford it. But will start the computer and the work (with a lot of mistakes) as long as the damaged slot is not a stick of RAM in it. So Ive been running on 1 key 2 GB compared to the original 2 2 GB sticks since then with many more problems than before. As the programs getting errors and be forced to close, and I get an error fatal frequent blue screen. I finally have the money to buy a new key of 4 GB of RAM to upgrade instead of the 1 2 GB. Im hoping this will bring this back to the speed and fix problems. IM curious as to the time its worth buying or if my laptop is screwed for good? any comment is appreciated, thank you.

  Jclement

  These accidents were caused by the corruption of memory (probably a driver).  Run these two tests to check your memory and find which driver is causing the problem.
  
  * Don't forget to download any other DMP files (especially those running auditor)

  * If you are overclocking reset all default before running these tests.
  In other words STOP!   If you don't know what it means that you're probably not
  
  
  1 - Memtest.

  * Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org

  * Boot from the CD and let it run at least 5 or 6 passes.

  * Don't forget, anytime Memtest reports errors, it can be bad RAM or a bad motherboard slot.

  * Test the sticks individually and if you find a good, test it in all slots.

  Any error is indicative of a memory problem.

  If a well-known stick fails in a slot of motherboard, it's probably the slot.

  2. Driver Verifier

  Using Driver Verifier is a dubious proposition. Most of the time it will crash and it will tell you what is the driver.

  * But sometimes it will crash and will not tell you the driver.

  * At other times it will crash until you can connect to Windows. If you can't mode without failure, then you will have to resort to editing the registry offline to disable driver verifier.

  * I would suggest that you first back up your data and make sure that you have access to another computer so you can contact us in case of problems.

  * Then do a system restore point (so you can restore the system using the functionality of Vista/Win7 Startup Repair).

  * Under Windows 7, you can do a startup repair disk by clicking Start... All programs... Maintenance... Create a system - with Windows Vista repair disc, you need to use your drive installation or from the "Repair your computer" option at the top of the Safe Mode menu.

  So, here is the procedure:
  -Go to start and type "auditor" (without the quotes) and press enter
  -Select 'Create a custom settings (for code developers)' and click 'Next '.
  -Select "Select individual settings from the list complete" and click "Next".
  -Select the entire document except for "Low resource Simulation" and click "next".
  -Select "Select driver names from a list", then click "next".
  * Select all drivers that are NOT supplied by Microsoft and click on "Next".
  -On the next page, select "Finish".

  * Restart the system and wait as he crashed to blue screen.

  * Continue to use your system normally and if you know what are the causes of the crash, do it several times. The objective here is to get the system crash because Driver Verifier is stressing out the drivers. If it is not planted for you, then let it run for at least 36 hours of continuous operation.

  * If you are unable to Windows because it crashes too early, try safe mode.
  * If you can't mode without fail, try to use the system from the installation DVD restore to bring the system back to the previous point of restoration that you created.

  * Further reading
  'http://support.microsoft.com/kb/244617 '.

  Using Driver Verifier to identify issues with Windows drivers for users advanced

• Bad Pool Caller error (Windows 8) - including the link to my Minidump file

  Hello!

  I recently received 4 blue screens; the first three were probably related to Avast, so I uninstalled ( Memory_managementerror)

  Later, says error Bad_Pool_Caller

  I have already travelled through further discussion, so here is the link to my Minidump file

  https://www.dropbox.com/s/sinr1qwyjjj43qw/dump.zip

  Also, here are the results of WhoCrashed

  
  

  Thank you very much!

  
  

  (Local) information system
  computer name: KISS
  Windows version: Windows 8, 6.2, build: 9200
  Windows dir: C:\Windows
  CPU: GenuineIntel Intel (r) Core i7-3630QM CPU @ 2.40 GHz Intel586, level: 6
  8 logical processors, active mask: 255
  RAM: 21425922048 total
  VM: 2147352576, free: 1917325312

  Crash Dump Analysis
  Crash dump directory: C:\Windows\Minidump

  Dumps are enabled on your computer.

  Wednesday, October 29, 13 16:57:33 this computer crashed
  crash dump file: C:\Windows\Minidump\102913-8937-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7A040)
  Bugcheck code: 0xC2 (0x7, 0x11C1, 0x11AC6DA0, 0xFFFFFA8011AC6DB0)
  Error: BAD_POOL_CALLER
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that the current thread is doing a bad pool request.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, October 29, 13 16:57:33 this computer crashed
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: gdi32.sys (GDI32! D3DKMTPresent + 0xA)
  Bugcheck code: 0xC2 (0x7, 0x11C1, 0x11AC6DA0, 0xFFFFFA8011AC6DB0)
  Error: BAD_POOL_CALLER
  Bug control description: This indicates that the current thread is doing a bad pool request.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  A third-party driver has been identified as the likely cause of the system error. It is suggested that you search for an update the following driver: gdi32.sys.
  Google search: gdi32.sys BAD_POOL_CALLER

  Wednesday, October 29, 13 12:15:41 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\102913-13828-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7A040)
  Bugcheck code: 0x1A (0xFFFFF70001080000, 0x1C03, 0 x 5003, 0x1C0400003846)
  Error: MEMORY_MANAGEMENT
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an error occurred serious memory management.
  This could be a case of corruption of memory. The corruption of memory more often happens because of software errors in the defective drivers buggy, not because of RAM modules.

  
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, October 29, 13 11:42:59 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\102913-23578-01.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0x40C90)
  Verification of error code: 0 x 24 (0xFFFFF8800ACAE0C8, 0xFFFFF8800ACAD900, 0xB50019060B, 0xFFFFF8800197C552)
  Error: NTFS_FILE_SYSTEM
  file path: C:\Windows\system32\drivers\ntfs.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT file system driver
  Bug control description: This indicates there is a problem in the NTFS file system.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Tuesday, October 28, 13 18:22:31 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\102813-13562-01.dmp
  This was probably caused by the following module: dxgmms1.sys (dxgmms1 + 0x263E7)
  Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880049B53E7, 0xFFFFF8800975A4E8, 0xFFFFF88009759D20)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  file path: C:\Windows\system32\drivers\dxgmms1.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: DirectX Graphics MMS
  Bug control description: This indicates that a system thread threw an exception who did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Conclusion
  5 dumps were found and analysed. A third-party driver has been designated to be the cause of breakdowns of the system on your computer. It is strongly recommended that you check the updates for these drivers on their corporate Web sites. Click on the links below to search with Google for updates these drivers:

  Gdi32.sys

  These accidents were related to the corruption of memory (probably caused by a driver).

  Run these two tests to check your memory and find which driver is causing the problem.

  If you are overclocking anything reset by default before running these tests.
  In other words STOP!  
  If you don't know what it means that you're probably not

  1-Memtest. (You can learn more about running memtest here)
  Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Get it here
  Boot from the CD and let it run at least 5 or 6 passes.
  Remember, anytime Memtest reports errors, it can be bad RAM or a bad motherboard slot.
  Test the sticks individually and if you find a good, test it in all slots.

  If a well-known stick fails in a card mother slot but not an another is probably the slot.
  
  
  2-Driver Verifier (for full instructions, see our wiki here)
  Using Driver Verifier is a dubious proposition.
  Most of the time it will crash and it will tell you what is the driver, but sometimes, it will crash and will not tell you the driver.
  Sometimes it will crash until you can connect to Windows. If you can't mode without failure, then you will have to resort to editing the registry offline to disable driver verifier.

  I suggest that you first back up your data and make sure you have access to another computer so you can contact us in case of problems.
  Then do a system restore point (so you can restore the system using the functionality of Vista/Win7 Startup Repair).
  
  Here is the procedure:
  Go to Start and type "auditor" (without the quotes) and press enter
  Select "create of the custom settings (for code developers)" and click "Next".

  Select "Select individual settings from the list complete" and click "next".
  Select all elements EXCEPT FOR "Low Resource Simulation"
  Do not check to win 8 Concurrency stress test and the verification of the conformity of DDI, click "next".
  Select "Select the driver names from a list", then click on "next".
  Select all drivers NOT supplied by Microsoft, and then click "Next".
  Select 'Finish' on the next page.
  
  Restart the system and wait as he crashed to blue screen.
  Continue to use your system normally and if you know what are the causes of the crash, do it several times.
  The objective here is to get the system crash because Driver Verifier is stressing out the drivers.
  If it is not planted for you, then let it run for at least 36 hours of continuous operation.
  
  If you are unable to Windows because it crashes too early, try safe mode.
  If you can't mode without fail, try to use the system from the installation DVD restore to bring the system back to the previous point of restoration that you created.