Random BSODS (mostly "memory management"), often on startup


  1. Posts : 4
    Windows 7 ultimate x64
       #1

    Random BSODS (mostly "memory management"), often on startup


    I'm having ALOT of problems right now...
    Most annoying and disrupting problem are the random BSOD's. I downloaded Whocrashed and alot of crashes seem to be "memory management" . Sometimes it's 3rd party programs..

    The BSOD lasts for 1/2 a second and computer immediately reboots so it's hard for me to say what it was about. I checked in event viewer the different errors but i'm at 1000+ error/warnings.

    At one point, as i was downloading Leagues of Legends ( game ) and Crysis 2 from Origins, while my uTorrent was actively downloading and Firefox was opened, i got an error from uTorrent saying "windows ran out of memory".

    What do I do. My computer keeps randomly crashing and i've been looking online for solutions, it's just too complicated for me to find anything related to my problems.

    The BSODS often occur on a reboot of the computer after installing/uninstalling a program. Right after entering my user password , 2 seconds into loading desktop, it immediately crashes. Not always but i've noticed it happens often.

    now i'm getting problems with applications. Its crashes after crashes after crashes.

    I have origin installed for Crysis 2 and BF3.

    Crysis 2 and BF3 though are a very big problem. Both applications crash non-stop. i can't even play for one second. BF3 has a browser launcher, when i try to launch a game, before even opening it says " Battlefield 3 has stopped working ". In the Event Viewer, it seems to give me something like this pretty often

    " Faulting application name: bf3.exe, version: 1.5.0.0, time stamp: 0x50c39964
    Faulting module name: atidxx32.dll, version: 8.17.10.451, time stamp: 0x5013494f
    Exception code: 0xc0000005
    Fault offset: 0x00154f65
    Faulting process id: 0x49c
    Faulting application start time: 0x01cdf464afbe0bdd
    Faulting application path: C:\Program Files (x86)\Origin Games\Battlefield 3\bf3.exe
    Faulting module path: C:\Windows\system32\atidxx32.dll
    Report Id: f02e3d92-6057-11e2-98fc-c86000be7d46"

    It's always the atidxx32. Sometimes it's "unknown" but i'm pretty sure it's the same file.

    This problem was fixed I THINK by turning off the two EPU / TPU switches on my MOBO and completely disabling overclocking/performance features. Is it NORMAL that "stock" features on my mobo actually makes it unusable ??!!

    I was also getting ALOT of warnings which was fixed the same way I THINK
    "A corrected hardware error has occurred.

    Reported by component: Processor Core
    Error Source: Corrected Machine Check
    Error Type: Internal parity error
    Processor ID: 2

    The details view of this entry contains further information."
    always the same one.

    Also, my firefox keeps crashing non-stop. It's very random. Sometimes i can't even reopen it right away, i have to restart the computer to open it up again.

    Lastly, ALOT of my errors seem to be "memory management" when i run Whocrashed .
    How do i know if all of this comes from faulty hardware or just corrupted files ?
    I have a limit for RMA'ing my components and i'm running out of time.

    heres the ZIP
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.

       Tip



    Let us know the results, with the subsequent crash dumps, if any.
      My Computer


  3. Posts : 4
    Windows 7 ultimate x64
    Thread Starter
       #3

    i posted on Techsupport a while ago, i never got an answer about my problems
    i did run Driver Verifier at the time, heres the post i put there when i did

    "Tried running Driver verifier.
    Computer rebooted, upon loading of windows 7, the computer kept freezing.
    No BSOD, just freeze. Had to hit the reset button everytime.

    Ran system restore in safe mode. Now it's back to where i was before. "
      My Computer


  4. Posts : 4
    Windows 7 ultimate x64
    Thread Starter
       #4

    I will run it right away while i sleep.

    if i find out it crashed when i wake up, how do i get the information you need to know ?
    Last edited by Lukamo; 21 Jan 2013 at 16:43.
      My Computer


  5. Posts : 4
    Windows 7 ultimate x64
    Thread Starter
       #5

    Yup... Just tried running it.
    When system rebooted, it froze 2 seconds after desktop showed ( not even finished loading the taskbar icons )
    Hit the reset button, tried again to load the desktop. This time it fully loaded everything ( i think ) and when i clicked on firefox to come post the failure of the first attempt, computer froze.

    No bsods, just froze both of the times.

    Restored to last saved point ( pre driver verifier )

    whats next ?

    if it helps, i ran whocrashed just now, i'm not quite sure if its the correct events because i used system restore and right now it's 5h04PM but it says the computer crashed at 7h05PM ...

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Mon 21/01/2013 7:05:20 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012113-7269-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0x19 (0x3, 0xFFFFF8A00576E100, 0xFFFF78A00576E100, 0xFFFFF8A00576E100)
    Error: BAD_POOL_HEADER
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a pool header is corrupt.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 21/01/2013 7:05:20 PM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x19 (0x3, 0xFFFFF8A00576E100, 0xFFFF78A00576E100, 0xFFFFF8A00576E100)
    Error: BAD_POOL_HEADER
    Bug check description: This indicates that a pool header is corrupt.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:57.
Find Us