Random BSOD errors happening at random times


  1. Posts : 5
    windows 7 64bit
       #1

    Random BSOD errors happening at random times


    Hello , im having random BSOD issues and after a BSOD i can use my PC again but the problem is it keeps happening randomly and i will be able to use again
    Here are some of the errors i have got:
    PAGE FAULT IN NON PAGED AREA
    BAD or CORRUPTED POOL
    MEMORY MANAGMENT
    I have the files Windows_NT6_BSOD_jcgriff2 and perfmon files included in this post
    System specs
    Os: Windows 7 home premium 64 bit
    I have bought this about a week ago , i had it built.
    Proccesor : AMD FX 6100 Proccesor
    gpu :nvidia gtx 560
    ram: 8gb
    hard drive : 1tb
      My Computer


  2. Posts : 306
    Windows 7 Ultimate x64
       #2

    Hello, welcome to SevenForums!

    I have taken a look at your provided dump files. There are tons of memory management and memory corruption errors. Before we continue, if any of your hardware is overclocked, PLEASE reset your clocks to stock for diagnostic purposes.

    First off, before we continue onto memory.... in your drivers list I noticed you have sptd.sys listed, which is the driver for Daemon Tools. Please uninstall Daemon Tools from your system as it's known to cause many issues in the Windows 7 environment. Once you've done so, restart and then run DuplexSecure's sptd uninstaller to fully remove sptd.sys from your system. After you've done so, restart again.

    Next, tons and tons of memory management and memory corruption errors as I've said earlier. Please read the following thread to download and install Memtest to test your memory for any bad sticks.
      My Computer


  3. Posts : 5
    windows 7 64bit
    Thread Starter
       #3

    if i run memtest will it fix my system as well?
      My Computer


  4. Posts : 306
    Windows 7 Ultimate x64
       #4

    Haha, if only the world worked so easy!

    Memtest is a test to see if your memory is at fault, if it is, it will show errors. At that point if your memory was under warranty you'd call the manufacturer / contact them and open up an RMA ticket to send in your memory and have it replaced. If it's not though, you'll need to purchase new memory.
      My Computer


  5. Posts : 5
    windows 7 64bit
    Thread Starter
       #5

    thanks for the help man
    but one more thing , i only got the computer on monday and i think i remember walking in to it that day and seeing "windows has recovered from an unexpected shutdown"
    I didnt think much of it because i hadnt seen the blue screen so how could it be broke
    everythings new , i helped them make the start of it and saw everything in new packages.So it must be in wrong or something
      My Computer


  6. Posts : 28,845
    Win 8 Release candidate 8400
       #6

    byybyy36 said:
    thanks for the help man
    but one more thing , i only got the computer on monday and i think i remember walking in to it that day and seeing "windows has recovered from an unexpected shutdown"
    I didnt think much of it because i hadnt seen the blue screen so how could it be broke
    everythings new , i helped them make the start of it and saw everything in new packages.So it must be in wrong or something



    We do need the 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.

    If you are overclocking STOP

    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

    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 the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

    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.
      My Computer


  7. Posts : 5
    windows 7 64bit
    Thread Starter
       #7

    zigzag3143 said:
    byybyy36 said:
    thanks for the help man
    but one more thing , i only got the computer on monday and i think i remember walking in to it that day and seeing "windows has recovered from an unexpected shutdown"
    I didnt think much of it because i hadnt seen the blue screen so how could it be broke
    everythings new , i helped them make the start of it and saw everything in new packages.So it must be in wrong or something



    We do need the 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.

    If you are overclocking STOP

    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

    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 the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

    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.
    i am not overclocking at all
    here are the dump folders
      My Computer


  8. Posts : 28,845
    Win 8 Release candidate 8400
       #8

    Memory Corruption and Daemon tools/alcohol


    Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.


    They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.


    Use this SPTD uninstaller DuplexSecure - Downloads
    DuplexSecure - FAQ

    when you're done you can use this Freeware:


    MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place


    Using MagicISO to create ISO image files






    These crashes were caused by memory corruption/exception (probably a driver).
    Please run these two tests to verify your memory and find which driver is causing the problem.


    * If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!

    * If you have raid update its Driver.




    Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

    *Boot from the CD, and leave it running for at least 5 or 6 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

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

    Any errors are indicative of a memory problem.

    If a known good stick fails in a motherboard slot it is probably the slot.

    RAM - Test with Memtest86+



    Driver verifier

    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen.
    Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
    The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
    If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
      My Computer


  9. Posts : 5
    windows 7 64bit
    Thread Starter
       #9

    thanks for the help everybody , i will try memtest tommorow and driver verifier .
    who knows maybe deleting that spdt will get rid of it because i had this from the very start of when i got my computer
    (my computer came with daemon tools) thank you so much for all the help everyone
      My Computer


  10. Posts : 28,845
    Win 8 Release candidate 8400
       #10

    byybyy36 said:
    thanks for the help everybody , i will try memtest tommorow and driver verifier .
    who knows maybe deleting that spdt will get rid of it because i had this from the very start of when i got my computer
    (my computer came with daemon tools) thank you so much for all the help everyone
    Good luck
      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 00:17.
Find Us