Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD - Fallout 3

01 Oct 2014   #1
TredeDk

Windows 7 Home Premium 64
 
 
BSOD - Fallout 3

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


My System SpecsSystem Spec
.
01 Oct 2014   #2
Boozad

W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
 
 

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.

Code:
*******************************************************************************
*                                                                             *
*                        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.

Download and run MemTest86+ to test your RAM.

Note   Note
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.


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.
My System SpecsSystem Spec
12 Oct 2014   #3
TredeDk

Windows 7 Home Premium 64
 
 

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.
My System SpecsSystem Spec
.

12 Oct 2014   #4
Boozad

W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
 
 

Right, let's start off with getting some information in your System Specs.
information   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 System Info - See Your System Specs to fill in your System Specs with as much info as possible. We're looking for something like the example below.

My System SpecsSystem Spec
12 Oct 2014   #5
TredeDk

Windows 7 Home Premium 64
 
 

I'm unable to see your attachment, but I have done as you asked.
My System SpecsSystem Spec
12 Oct 2014   #6
Boozad

W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
 
 

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?
My System SpecsSystem Spec
12 Oct 2014   #7
TredeDk

Windows 7 Home Premium 64
 
 

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.
My System SpecsSystem Spec
12 Oct 2014   #8
Boozad

W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
 
 

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.
My System SpecsSystem Spec
12 Oct 2014   #9
TredeDk

Windows 7 Home Premium 64
 
 

Sure thing.
My System SpecsSystem Spec
12 Oct 2014   #10
Boozad

W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
 
 

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.
My System SpecsSystem Spec
Reply

 BSOD - Fallout 3




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD playing Fallout New Vegas, Far Cry
Hi, I recently starting getting BSOD after playing about 30 mins of Fallout New Vegas. I've had over 50 hours of gameplay with no issue until a few days ago. Then I started playing Far Cry and the same thing happens about 30 minutes into the game. One thing I've noticed is that it usually...
BSOD Help and Support
BSOD playing Fallout New Vegas, stop code 0x0000003b
Hey guys, first post I have made here so cut me some slack if I make any mistakes. I have had this bsod twice and it was the same each time. I am walking around in game and then the game freezes and I hear a buzzing sound through my headset then I bsod. I have the 2 dumps and am hoping that I...
BSOD Help and Support
BSOD playing left 4 dead 2, and before Fallout NV. Code: 0x0000001E
2 occasions so far, once while playing FONV and once during Left 4 Dead 2. Any help would be appreciated. I should mention that i had a small OC on my gfx card during the first one, but turned it back to stock settings after. Thanks in Advance Callum
BSOD Help and Support
BSOD playing Fallout: New Vegas/Random BSODs during startup
Hello forum. I'm hoping somebody can assist me with these BSODs. My computer is about 2 years old and the only thing I've had replaced in it was a hard drive. Here is some information about the BSODs. Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.768.3...
BSOD Help and Support
BSOD errors playing Fallout 3, error 0x0000004e -3b - 7e
I just built a new computer from scratch, it's my first one and I've been trying to enjoy it but I've been catching random BSOD. I only get 1 of each code, it's never the same. I hope I can get some guidance in fixing these errors and I appreciate any help in doing so. I'm attaching the code for...
BSOD Help and Support
Fallout 1/ Fallout 2
I have a Windows 7 32bit OS. I can't seem to get Fallout 1 or 2 to work without the graphics being messed up. I've tried running it in compatibility mode with every previous OS to no avail. Is there another setting in compatibility I should be enabling? Is there a free program that lets me run...
Gaming


Our Sites

Site Links

About Us

Find 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 22:39.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App