Random BSODs during random tasks, numerous BCCodes.


  1. Posts : 86
    Windows 7 Home Premium
       #1

    Random BSODs during random tasks, numerous BCCodes.


    For some reason, my last post here regarding this issue was deleted after ~2 days without warning or response from anyone, so here I am again now that I can view this section once more.

    For the past week or so now, my PC has been randomly BSODing at seemingly random times.. mostly when gaming. Before the BSODs started happening, I believe a day or so, Windows removed some orphaned files from the drive before starting. I don't know if this has anything to do with what's going on or not.

    When gaming, more often than not I'll suffer from crashes due to access violations; the errors stating that the memory couldn't be read. From this point, either I get a BSOD very shortly after, or immediately when doing something like checking the computer properties (to see perhaps if Windows had suddenly decided one of my sticks of RAM was bad and displayed as: "XGB of RAM (XGB usable).").

    At this point in this PC's life, I'm chalking it up to probably failing hardware. I recently had to disable Intel's SpeedStep on this processor, as I was having issues where it wouldn't initialize like it should and clock my CPU up to load-levels (thus leaving the system and anything I did with it a tad laggy). Until that point, it had been enabled since I built this PC and I had no problems with it whatsoever.

    As far as temperatures and voltages are concerned, all are well. I monitor temps as closely as I can, and I'm not overclocking. Power from my PSU is all normal.

    The only drivers I've messed with lately (today) are the video drivers, which I updated to the latest version. Nothing else involving drivers or other major software had been changed or messed with prior to the BSODs. I've taken out the RAM and tested each stick individually in each slot and it booted to Windows just fine in every configuration. I've ran both Memtest and the Windows memory diagnostic; both have found nothing. I've ran chkdsk /f, and it, too, found nothing.

    So I'm pretty much at a loss as to what's going on here, unless it's a failing CPU, motherboard, or some weird memory issue I can't isolate or replicate.

    Also worth noting: before I tested the RAM like I did, I'd just taken it out and reseated it. The PC ran just fine for about a day, then started BSODing again. Once I tested it all like that, it again ran fine until a little while ago (a span of about 2 days this time). This BSOD made no mention of any files (I'd noticed win32k.sys in one of the prior BSODs, and a different file before it; but they seem random), and had a BCCode of 132; which all google searches pointed towards a filesystem/hard drive problem.. but after that is when chkdsk found no errors/problems.

    At this point, I'm leaning more towards potential hardware failure than anything. This system is pushing 5 years old this coming March, and as much as it's been used, it just wouldn't surprise me if it was hardware.

    Anyway! Attached is the SFDT zip file with all the necessary files included.

    Thanks in advance, and sorry for the massive post. I'm trying to include as much information as possible.

    PS: If for some reason an admin/moderator here feels the need to delete my thread for whatever reason (my previous thread is still available in the Google cache; the zip file I'd included had 1 view before it was deleted without warning or word from anyone), at least have the decency to send me a message as to why this time. Thank you.
    Last edited by Requimatic; 05 Dec 2014 at 13:25. Reason: PS
      My Computer


  2. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #2

    Your .zip file doesn't contain any of the .dmp files required to analyse the BSOD/s.

    Please follow this:
    Dump Files - Configure Windows to Create on BSOD

    Now follow this:
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
    Driver Verifier - Enable and Disable

    Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

    I recommend creating a system restore point before turning on driver verifier:
    System Restore Point - Create

    If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
    Safe Mode

    Once you get a new BSOD when running Driver Verifier, follow this:

    1. Download the DM Log Collector application to your desktop by clicking the link below

    DM Log Collector.exe

    2. Run it by double-clicking the icon on your desktop, and follow the prompts.
    3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

      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 01:30.
Find Us