Solved BSOD - File system error or possible memory issue?

devroad

New member
Local time
2:50 PM
Messages
6
Good evening,
I've had recurring BSODs over the past few weeks. Last week, I was unable to start the system because it would BSOD while booting up or after the boot up was completed (within a few minutes).
Luckily, I had a full system image backup from December 24th, 2014. I recovered the system via the backed up image (Acronis) and so far the system had been working as expected.
This evening after I got back home, I realized my system had BSODed again (after maybe 2 days of continual use without any BSODs). Thankfully, a dump file was created and here I am hoping to resolve the issue.

I have a dual boot system with Linux Mint on an SSD (and a couple of other Linux distros running inside VMs). When Windows was not functional, I used Linux for almost a week or so without any issues. So I'm not sure if it's a memory issue or a hard drive issue.
I've had the system for a little over a year now.
i7 3770k
16.0 GB
3 Hard drives installed:
WD 3 TB - All media and current backups
C:\ - 1 TB Segate 7200 RPM HD (Windows 7)
128 GB SSD - Linux & other distros.

Thank you for all your help. :cool:
 
Last edited:

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom Build
OS
Windows 7 Ultimate x64
CPU
i7 3770k
Motherboard
ASUS P8Z77-V LX
Memory
Corsair 16 GB
Graphics Card(s)
Asus GTX 770
Antivirus
BitDefender Total Security
You only have one recent dump,

Code:
BugCheck 24, {1904fb, fffff8800c5e3f98, fffff8800c5e37f0, fffff88001281419}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

Here's a bigger problem though,

Code:
Host Name:                 DEVA
OS Name:                   Microsoft Windows 7 Ultimate 
OS Version:                6.1.7601 Service Pack 1 Build 7601
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          JEDI
Registered Organization:   
Product ID:                00426-OEM-8992662-00010
Original Install Date:     10/30/2013, 3:21:10 PM
System Boot Time:          2/24/2015, 9:54:12 PM
System Manufacturer:       System manufacturer
System Model:              System Product Name
System Type:               x64-based PC

Counterfeit installations such as yours contained heavily modified code that causes the installation to behave it unexpected ways. Analysing BSOD's and determining their causes on these sorts of installations is very unreliable. For this reason, many analysts won't attempt it.

My recommendation is to install a genuine Windows 7. This will minimise the problems you are experiencing, and make subsequent diagnosis of BSOD's far more reliable. Once you are running a genuine Windows 7 installation, and are still experiencing BSOD's, we will be happy to help you solve them :)
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Self Built
OS
Win 10 Pro x64
CPU
Intel I5-2500K @3.3GHz
Motherboard
Asrock P67 Extreme4
Memory
16GB G.Skill Ripjaws X (4x4GB)
Graphics Card(s)
EVGA GeForce 750 Ti SC 2GB
Sound Card
ASUS Xonar DG 5.1 Channels 24-bit 96KHz PCI Interface Sound
Monitor(s) Displays
auria eq2367
Screen Resolution
1920 x 1080
Hard Drives
250GB Samsung 850 EVO SSD
1TB WD Blue
1TB Hitachi
PSU
SeaSonic X 650W 80 Plus Gold
Case
Corsair Obsidian 750D
Cooling
Corsair H60, Three 140mm case fans
Keyboard
Logitech Wireless Keyboard K520
Mouse
Logitech Wireless Mouse M310
Internet Speed
Wave Broadband ~ 100 dn 5 up
Antivirus
Windows Defender, Malwarebytes Premium
Browser
Edge, IE11, Chrome
Other Info
Laptop specs: HP g7-1365dx /
CPU: AMD A6-3420M APU with Radeon(tm) HD Graphics /
RAM: Crucial 8Gb (2x4Gb) /
SSD: Crucial M4-CT128M4SSD2 ATA Device/ FW 000F /
GFX: AMD Radeon HD 6520G /
OS: Windows 10 Pro x64
Back
Top