BSOD - Fallout 3

[TredeDk]

Greetings

I was running Fallout 3 like many times before, and only had my browser, Mod Organizer, NMM (Nexus Mod Manager), uTorrent and a few folders open. I was trying to discover why my Fallout 3 crashed at times, so I spawned in 100 Radroaches, and that wasn't a problem in of itself, but I thought it a good idea to let my character idle for a while, in order to provoke the Fallout 3 crash but after a few minutes I got the BSOD.

I recently reinstalled my entire computer, and therefor only have a few programs installed. I haven't had many BSOD in the past, so I don't believe it to be the computer itself.
I'm pretty sure, that it was Fallout 3 that caused it, but I'm not entirely sure, so I'd like to have it checked out, just in case it's something else.

Thank you in advance.

Peter

 

[Boozad]

Your single dump file is showing a STOP 0x109 which denotes a Critical Structure Corruption. This can be down to a device driver but none are showing in your dump. It can also be defective hardware, in many cases RAM.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d8a5f6a672, b3b7465ef87375c8, fffff80002fb4036, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+59a )

Followup: Pool_corruption
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d8a5f6a672, Reserved
Arg2: b3b7465ef87375c8, Reserved
Arg3: fffff80002fb4036, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification

Please follow the steps outlined below, test and report back.

:ar: Download and run MemTest86+ to test your RAM.

   Note

View attachment 335305
Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.

:ar: Uninstall Daemon Tools, a proven cause of BSODs.

1. Uninstall Daemon Tools.
2. Download the SPTD standalone installer and follow these steps:
3. Double click the executable to open it
4. Click the button shown below

If the button it is grayed out, as shown in the image, there is no more SPTD installation on your system, and you can just close the window.

 

[TredeDk]

I tried doing as you said, but I still get BSOD.
The Memtest said, that no errors were found, and I uninstalled Daemon Tools.

It's strange that I've gotten quite a few BSOD in the last few days, because my computer is a few years old, and it has never been a problem before. As I mentioned earlier, I reinstalled my entire computer not too long ago, and I think that has something to do with it, or a component in my computer is beginning to malfunction.

I've uploaded a new zip file, which I created just moments ago. Hopefully it'll be able to tell us more, than last time.

Thank you.

 

[Boozad]

Right, let's start off with getting some information in your System Specs.

   Information

At 7F we rely heavily on knowing what hardware you have in your system, by filling out your system specs in the manner outlined below your specs will follow you round in every single post so we can see your hardware configuration at the click of a button without having to trawl through threads to find them.

​

Follow http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html to fill in your System Specs with as much info as possible. We're looking for something like the example below.

​

 

[TredeDk]

I'm unable to see your attachment, but I have done as you asked.

 

[Boozad]

Do you know which make and model of RAM sticks you have? Are the all from the same kit and do they have the same timings?

 

[TredeDk]

I must admit, that I do not. I have attached a picture of one of my RAM sticks. The 2 I have are identical, and I haven't done anything fancy to them, so they should have the same settings as when I bought them.

 

[Boozad]

That's Kingston HyperX, Genesis by the look of it. I just wanted to rule out mismatched RAM. Just to amuse me, could you download Speccy and run it. Click on the RAM tab on the left hand pane and post a screenshot of the RAM details.

We'll look at other possibilities after that.

 

[TredeDk]

Sure thing.

 

[Boozad]

Well it looks like we've all but ruled out RAM.

As a test, can you remove ASRock eXtreme Tuner from your Startup. Test after clearing that from startup and post up any subsequent BSODs for further steps.

 

[TredeDk]

And I'm back.

I just got BSOD once again. I've attached a photo of my recent dumps, it appears to happen every few days. My computer is used every day.
I've also attached the newest zip.

Edit: I didn't remove the ASRock eXtreme Tuner from my startup, but I close it as soon as it has run. I've used it since I first got my computer, and it has never been a problem. If I don't run it, my fans will spin at full speed and make quite a lot of noise, so it'd be quite inconvenient to not run it.

 

[Boozad]

OK, what I would like to try now is running Driver Verifier to see if it will weed out any driver that is trying to modify the kernel code. That's the most likely scenario given that the RAM is not the problem. Driver Verifier will stress your drivers and cause BSODs if any fail. Follow this tutorial to enable/disable it. http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

If a BSOD occurs after enabling DV please upload as soon as possible and take note of the information below.

   Information

Enable Driver Verifier but only enable these options:
Standard settings and IRP logging step 3.
Don't enable Force Pending I/O Requests

   Warning

Make a System Restore point before enabling Driver Verifier.

   Note

Your system will act very sluggishly while DV is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.