BSOD Minidump Crashes

Toggle sidebar Toggle sidebar
H

hazel1393

Reputable
Aug 1, 2014
6
0
4,510
Hey all,

Ever since since downgrading to Windows 7 from Windows 8, I've been getting a BSOD/System Crash. I've tried re-installing Windows 7 and it still happens. I believe I have all of my drivers up to date (I know for sure that my video card is). I will be copying and pasting the Problem Details and the "Who Crashed" report. Thanks for the help in advance!

Windows' Problem Details:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 109
BCP1: A3A039D89B70753D
BCP2: 0000000000000000
BCP3: 916F819E17AE76A4
BCP4: 0000000000000101
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\080114-10140-01.dmp
C:\Users\Andrew_H\AppData\Local\Temp\WER-1244529-0.sysdata.xml


The "WhoCrashed" Report indicates that the two files (right above) have the BugCheck name of "CRITICAL_STRUCTURE_CORRUPTION"


********************************UPDATE*********************************

Now I'm getting an IRQL_NOT_LESS_OR_EQUAL BSOD...

********************************UPDATE********************************* 8/4/2014

Now a NFTS_FILE_SYSTEM BSOD

I did ran a memtest and it all came up clear. I'm trying my hardest to update all of my drivers because I feel that that must be the problem. But to be honest, I'm not even sure at what to update at this point. Do I need upadate/flash the motherboard maybe???

 
Solution
J
you can not tell what the problem without looking at the actual memory .dmp file.
basically the bugcheck indicates that a critical portion of the windows operating system detected that it has been corrupted in memory.
These data structures are key targets for malware attacks so you will need to run malwarebytes scan to make sure your machine does not have malware.
there can be other causes for this same error:
The files may be corrupted as stored on the hard drive, they may be corrupted by a virus or other device driver that over writes another device drivers memory. Or it can be a physical problem with the BIOS setting for the RAM or a actual failure in a memory location in RAM.

I would start with running memtest86.exe on its own...
Sort by date Sort by votes
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
you can not tell what the problem without looking at the actual memory .dmp file.
basically the bugcheck indicates that a critical portion of the windows operating system detected that it has been corrupted in memory.
These data structures are key targets for malware attacks so you will need to run malwarebytes scan to make sure your machine does not have malware.
there can be other causes for this same error:
The files may be corrupted as stored on the hard drive, they may be corrupted by a virus or other device driver that over writes another device drivers memory. Or it can be a physical problem with the BIOS setting for the RAM or a actual failure in a memory location in RAM.

I would start with running memtest86.exe on its own boot disk to confirm that your machine's hardware is working as expected.
if that testing passes, you will want to update as many device drivers for your system as you can get, make sure you have the windows updates then make sure you get the chipset updates for your CPU (google intel chipset drivers if you have a intel CPU to get the drivers)

if you still get the problem after you have done the update and memory testing you should copy your memory .dmp file up to a cloud server with public access and someone can take a quick look and see if they get a hint as to the cause of the problem.
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom