Random Bluescreens - ntoskrnl.exe (Computer is really loud while BSOD)

[Blizzii]

Hey guys,

I randomly get BSOD while playing a game or just doing nothing but listening to music and watching youtube videos. My drivers are all up to date. I uploaded a file which i made with SF Diagnostic Tool. My computer specs are written on my profile too. It's getting annoying and I don't have a solution for this because I don't know if it's the software or hardware. I've been in several forums in order to find any solutions... found nothing.

Please help! :huh::huh:

 

[Saurabh A]

Hi Blizzii,

I've checked the 'Event Logs' and they look clean. 'Crash Dump' detects BugCheck Code '0x00000124' caused by 'ntoskrnl.exe' driver; please refer to this 'article' and follow the suggested steps: http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

I could also see the following errors in 'Windows Update logs':

2013-02-17	12:41:18:585	 896	edc	DnldMgr	FATAL: DM:CAgentDownloadManager::LoadUpdateMetadataFromDatastore: GetUpdates failed with 0x80248007.
2013-02-17	12:41:18:585	 896	edc	DnldMgr	  * WARNING: Exit code = 0x80248007
2013-02-17	12:41:18:585	 896	edc	DnldMgr	FATAL: DM:CAgentDownloadManager::RestoreDownloadJobs: RestoreDownloadJob failed with 0x80248007.
2013-02-17	12:41:18:585	 896	edc	DnldMgr	FATAL: DM:CAgentDownloadManager::LoadUpdateMetadataFromDatastore: GetUpdates failed with 0x80248007.


2013-02-27	21:04:22:919	1228	17d4	COMAPI	FATAL: Unable to initiate asynchronous installation successfully. (hr=80240016)
2013-02-27	21:04:27:914	 468	dac	Report	REPORT EVENT: {6D653856-E810-42BB-B46E-E6FA4841A352}	2013-02-27 21:04:22:915+0100	1	162	101

'Microsoft Security Essentials' seems to have been installed recently. If another 'anti virus / security software' is also installed, try uninstalling it and recheck results. The issue could also be due to a Maware. Try running a scan using this link and see if something is detected: Free Malware Removal Tool | Anti-Malware Scan Software

You may also try the following 'Microsoft Fixit'; and try updating 'Windows' to see if anything changes. Also observe the system for any crashes: Temporary connection-related errors may occur when you use Windows Update or Microsoft Update

Hope this helps.

 

[Blizzii]

You may also try the following 'Microsoft Fixit'; and try updating 'Windows' to see if anything changes. Also observe the system for any crashes: Temporary connection-related errors may occur when you use Windows Update or Microsoft Update

Hope this helps.

I installed Microsoft Fixit and it had to repair my Windows Update. Could this be the reason for BSOD?

 

[Saurabh A]

Hi Blizzii,

Fatal error(s) in 'Windows Updates' is a 'likely symptom' for 'Bluescreen errors'; however there may be other possible reasons as well. I would suggest you to observe the system for a while and see if it crashes again.

Do reply with the findings.

 

[Blizzii]

Hello Saurabh,

I want to thank you for your time!

Every time when i execute Microsoft Fixit he finds the same problem - something in Windows Update. When i fix it, it says it's fixed but when I start the programm again, the error shows up again. What happened there?

 

[Blizzii]

1) Hardware is not overclocked
2) Ensure that the machine is adequately cooled:

(Temp 1 is CPU)
3) All drivers are up to date
4) BIOS is up to date
5) Windows is up to date
6) RAM & HDD: No errors occured

I found out, that the graphic card gets really loud when the computer restarts by itself. Therefore, I tried to move the graphic card back- and foward in order to check if there is any loose contact.

The computer restarted. I didn't get a BSOD - it just restarted and said there was a BSOD after logging in.
After that I disconnected the graphic card from the motherboard, removed the dust and connected it again. I'm not sure if it's the problem of the graphic card or the motherboard. But I have no BSOD so far.

 

[Saurabh A]

Hi Blizzii,

Thank you for the response.

The Bug Check points at a possible hardware failure:

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

WHEA_UNCORRECTABLE_ERROR (124)
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.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8008ac12b8, 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.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031a25b0 fffff800`02f10ca9 : fffffa80`08ac1290 fffffa80`067ccb50 00000000`00000009 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031a2ad0 fffff800`02df1077 : fffffa80`08ac1290 fffff800`02e6b2d8 fffffa80`067ccb50 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031a2b00 fffff800`02d58435 : fffff800`02eccae0 00000000`00000001 fffffa80`088226e0 fffffa80`067ccb50 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031a2b40 fffff800`02ccdca9 : fffff880`010cee00 fffff800`02d58410 fffffa80`067ccb00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031a2b70 fffff800`02f6534a : 00000000`00000000 fffffa80`067ccb50 00000000`00000080 fffffa80`066e8040 : nt!ExpWorkerThread+0x111
fffff880`031a2c00 fffff800`02cb5946 : fffff880`009b3180 fffffa80`067ccb50 fffff880`009be040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a2c40 00000000`00000000 : fffff880`031a3000 fffff880`0319d000 fffff880`031a2550 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

Followup: MachineOwner
---------

4: kd> !errrec fffffa8008ac12b8
===============================================================================
Common Platform Error Record @ fffffa8008ac12b8
-------------------------------------------------------------------------------
Record Id     : 01ce153406507d47
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 2/27/2013 21:47:39
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8008ac1338
Section       @ fffffa8008ac1410
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    @ fffffa8008ac1380
Section       @ fffffa8008ac14d0
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  @ fffffa8008ac14d0

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8008ac13c8
Section       @ fffffa8008ac1550
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xfe00000000070f0f
  Address     : 0x00000000f0a48000
  Misc.       : 0xc00a0fff01000000

Please run diagnostics on the 'processor & video card' and share results:
http://www.sevenforums.com/tutorials/220743-cpu-stress-test-using-intelburntest.html
http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

Do reply with the findings.

 

[Blizzii]

- Video card:

- CPU:

Standard:

High:

Very High shows the same result.

Temp (+ 10°C each test):

This shows that my cooling system is alright, right?

 

[Blizzii]

okay what the hell?? is this mainboard or video card?!!!! PLEASE HELP

 

[Saurabh A]

Hi Blizzii,

It may be the 'video card' or the 'motherboard'.

In one of the earlier thread conversation, you shared that all drivers are updated. However, you may try re-installing the 'display drivers' to see if that makes any difference.

If the issue persists, you may try removing the 'discrete card' and use the system through the 'Integrated display'; and check if the issue duplicates. The motherboard (ASUS M5A78L-M/USB3) in your system appears to give you that option:

Do reply with the findings.

 

[Blizzii]

I guess I found the problem..

There was a problem between the PCI-E of the power supply and the video card.. I disconnected it, cleaned the dust and connected it again.. could this be the reason?

I had 3 BSOD in a row after booting W7. After the third BSOD the screen said, that i have to plug in the power or something like that ..

But I still don't know if it's the problem of the PCI-E cable or the video card.. did anyone have this problem before?

 

[Saurabh A]

Hi Blizzii,

The 'power supply' message reflects an issue with either the inability of the 'Power Supply Unit' to meet the power requirement of the graphic card; or the graphic card not getting sufficient power due to either a loose physical connection, faulty power supply unit or a damaged cable/connector. Please ensure that the physical connections are properly seated. You may want to refer to the 'Installation Manual' of the display adapter: http://www.nvidia.com/content/PDF/GeForce-GTX-660Ti.pdf (You may want to check safety instructions in the manual)

Please share the make/model of the Power supply unit being used. As I stated in my previous post, try running the display through the 'Integrated display'; should give us a fair idea about the 'Motherboard health'. You may also try using the 'nVidia GTX 660 TI adapter' with another PC, if available. That may help you to isolate the 'GPU' as the possible cause of failure. You may also want to check if you could arrange another 'Power Supply Unit' to test with this unit. It will clarify your doubt about the power cables/connectors being the culprit.

Do reply with the findings.