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: Strange BSODs, Unable to Determine Cause Alone

15 Jun 2015   #1

7 Ultimate x64
Strange BSODs, Ntoskrnl.exe, Have Not Receive Help Yet

Occasionally, my entire system will just hang and either be forced to restart, or, very rarely, it will be able to regain control and continue working. I've ran memtest and memtestx86 to determine if the cause is my ram, but both tests showed the ram is working fine. The cause could be my GPU, an ASUS R9 290, but I have already done two RMA's to have the card repaired.

To get a bit of insight on these BSOD's, my system is very unstable for most games. When running Rust, my system seems to be extremely stable and can run the game for eternity. Whilst watching videos on youtube, the system is somewhat stable, the potential of a crash is still there, but I am free to do as I please for hours. Now, when playing other games, such as: League of Legends, Garry's Mod, Fallout: New Vegas, Bordelands 2, the system is extremely unstable. The most I can get is a few hours and crashing is extremely frequent.

I have been told that doing a bios update fixes most problems of an unstable system, but my motherboard rejected the latest bios that I tried to use in the update. I am afraid I have nothing left up my sleeve, and thus, must turn to these forums.

I have used the DM Log Collector program, so the ZIP is attached below. I am hoping to have this problem resolved soon as I must escape this elo hell in League of Legends and reach my true potential: Challenjour.

My System SpecsSystem Spec
22 Jun 2015   #2

7 Ultimate x64

So let's go through all that I do know and what I think I know.

System is somewhat unstable. BSODs are occurring a few times a day and seem to be reducing their occurrence as the days go on.

When the system crashes, there is not Blue Screen displayed, the system automatically restarts.

It would appear that Google Chrome could be possibly causing these crashes as I am able to play games for a longer period of time with Google Chrome closed. When it is open, the system will crash more frequently and even crash whilst I am watching videos or looking on various forums.

Some games retain stability for longer, Rust, World of Warcraft. Other games have some stability to them, League of Legends, Fallout: New Vegas. And other games will almost always crash within the first hour, Garry's Mod, Borderlands 2. So these crashes really depend on a factor. A factor that I do not know because I cannot read these .dmp files and someone has yet to view this thread and read them to me.

It's really a game of guessing and I am losing.
My System SpecsSystem Spec
22 Jun 2015   #3

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

You will do yourself a world of favours by installing a genuine copy of Windows 7, you have an HP PID on a retail Gigabyte motherboard which means your install is counterfeit.
Host Name:                 TURTLE-PC
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:          Levande
Registered Organization:   
Product ID:                00426-OEM-8992662-00010 ---> HP PID
Original Install Date:     6/1/2015, 5:31:39 PM
System Boot Time:          6/15/2015, 9:31:10 PM
System Manufacturer:       Gigabyte Technology Co., Ltd.
System Model:              GA-78LMT-USB3
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
Counterfeit installations such as yours can contain heavily modified code that can cause the installation to behave it unexpected ways. Analysing BSODs and determining their causes on these sorts of installations is completely unreliable, and for this reason most analysts won't attempt it.

My recommendation is to install a genuine copy of Windows 7. This will minimise the problems you are experiencing and make subsequent diagnosis of BSODs far more reliable. Once you are running a genuine Windows 7 installation and are still experiencing BSODs, upload your new logs we will be happy to help you solve them.
My System SpecsSystem Spec

23 Jun 2015   #4

7 Ultimate x64

I'll just be purchasing a new copy of Windows 7 later on today, like I should have months ago. Thanks for the help. I'll be sure to post again if my computer still has a major problem intertwined within the major components that allow it to run on the most basic level.
My System SpecsSystem Spec
23 Jun 2015   #5

7 Ultimate x64

So I installed Windows 7 Home Premium with a fresh key that was just purchased today. After installing the AMD video drivers, my computer, sadly, crashed. The new DM Logs will be attached.
My System SpecsSystem Spec
23 Jun 2015   #6

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

Good move on going genuine. The single dump is a 0x124 which denotes a hardware error but doesn't show which piece of hardware is faulty.
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8007faa038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

3: kd> !errrec fffffa8007faa038
Common Platform Error Record @ fffffa8007faa038
Record Id     : 01d0ade7f1c5a188
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 6/23/2015 19:08:18 (UTC)
Flags         : 0x00000002 PreviousError

Section 0     : Processor Generic
Descriptor    @ fffffa8007faa0b8
Section       @ fffffa8007faa190
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000600f20
Processor ID  : 0x0000000000000000

Section 1     : x86/x64 Processor Specific
Descriptor    @ fffffa8007faa100
Section       @ fffffa8007faa250
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : 20 0f 60 00 00 08 06 00 - 0b 32 98 3e ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa8007faa250

Section 2     : x86/x64 MCA
Descriptor    @ fffffa8007faa148
Section       @ fffffa8007faa2d0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xfe00000000070f0f
  Address     : 0x00000000fdefc024
  Misc.       : 0xc00a0fff01000000
Run all rounds of Windows Updates prior to carrying out the stress and diagnostic tests outlined below.

Strange BSODs, Unable to Determine Cause Alone STOP 0x124 Troubleshooting Strange BSODs, Unable to Determine Cause Alone
Read carefully before proceeding.

warning   Warning
If you're overclocking your system, revert back to stock clocks now.

Note   Note
Test the system once the overclock is removed before continuing with the steps outlined below.

Part One: CPU Stress Test
Part Two: MemTest86+ RAM Diagnostic
Part Three: Hard Drive Diagnostics
Part Four: GPU Stress Test

Strange BSODs, Unable to Determine Cause Alone ONE Strange BSODs, Unable to Determine Cause Alone

Run Prime95 to stress test your CPU. Hardware - Stress Test With Prime95

warning   Warning
Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

Strange BSODs, Unable to Determine Cause Alone TWO Strange BSODs, Unable to Determine Cause Alone

Run MemTest86+ to analyse your RAM. RAM - Test with Memtest86+

Note   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Strange BSODs, Unable to Determine Cause Alone THREE Strange BSODs, Unable to Determine Cause Alone

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use

Note   Note
Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk Disk Check

Strange BSODs, Unable to Determine Cause Alone FOUR Strange BSODs, Unable to Determine Cause Alone

Run Furmark to stress test your GPU. Video Card - Stress Test with Furmark

Note   Note
Run Furmark for around 30 minutes.
warning   Warning
Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.
My System SpecsSystem Spec
23 Jun 2015   #7

7 Ultimate x64

Ran both Furmark and the Hard drive test.

All hard drive tests showed the spinning disk of storage was running as intended to.

Furmark showed nothing except for how hot a GPU can truly become. Snapped an image of the program before closing it out.

I'm currently running the CPU test, however, my system did crash after sometime when I tried to do this earlier. This happened whilst I was away, which means no information gathered. We'll see if we can last through the test.
My System SpecsSystem Spec

 Strange BSODs, Unable to Determine Cause Alone

Thread Tools

Similar help and support threads
Thread Forum
WEI Unable to determine memory performance Error
W7X64 Pro ASUS X99-DELUXE CPU5960X DDR4 Crossair 2800Mhz GTX750Ti/K5000/K20 M.2 Plextor 256GB Extended Drive System C: + Xp941 System C: 512 GB WD Black2TB X3 XT750GB X2 When I run Windows performance Index
Performance & Maintenance
BSOD, unable to determine exact cause
Been receiving numerous BSOD for months. I never was able to determine the exact cause the first time. Most of the time the error occurs during a game such as Skyrim, Diablo 3. However, sometimes the error happened when watching videos on YouTube or even while idle. Every time I thought I fixed...
BSOD Help and Support
BSOD Unable to determine origin
Heya! I seem to be getting the BSOD when playing games, most recently during a game of Dota2. When the BSOD does occur my computer hangs and a weird, electronic - it's hard to describe - whining sound comes through the speakers. I've run the SF_Diagnostic_Tool.exe as per the...
BSOD Help and Support
Unable to Determine BSOD Cause. Occurs Randomly
I built this computer about a year ago. Things were running smooth up until recently. I m usually pretty good at figuring out what is causing Errors on my computers but I cannot figure out what is causing this one. I do see kernel Errors in the event log but that is only about a bug check after it...
BSOD Help and Support
"Setup was unable to determine...BitLocker"
While attempting to do an upgrade from Vista Home Premium 64 bit to Windows 7 Home Premium 64 bit I get the following message; "Setup was unable to determine if BitLocker Drive Encryption is in use." The only option then is to cancel the upgrade. I've tried installing 3 times now with the same...
Installation & Setup

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 09:32.
Twitter Facebook Google+