BSODs generally happening when listening to music/watching videos on my desktop

[hg3300]

Not sure if it's related to that, but one time I was watching a video in iTunes, and when it ended, the computer crashed...today I was playing a song and near the end the computer crashed.

Here are all my minidump files, hope this helps identify the problem.

 

[TrainableMan]

Please start by scanning your computer for viruses in safe mode. If your current A/V runs in safe mode you can use that. See my recommended method at the start of my post HERE. If anything is found please post result logs so we can see exactly what was found.

Most of the DMPs mention memory management. How old is the computer? I see DMPs going back about a month, is that when the problems first started? Have you added/changed any memory or the timings/voltages? Please post the CPU-Z screen shots as explained HERE. Consider running Memtest86+ overnight for 8-10 passes to stress test your RAM.

You video driver is only two months old (March 4, 2014) but it wouldn't hurt to see if there is a more current Nvidia video driver.

 

[Shintaro]

Mate,
Could you please run this command from a command prompt as Administrator

wmic recoveros set DebugInfoType = 2

Currently the crash dumps are set to mini dumps and they need to be set as Kernal dumps.

 

[hg3300]

Please start by scanning your computer for viruses in safe mode. If your current A/V runs in safe mode you can use that. See my recommended method at the start of my post HERE. If anything is found please post result logs so we can see exactly what was found.

Most of the DMPs mention memory management. How old is the computer? I see DMPs going back about a month, is that when the problems first started? Have you added/changed any memory or the timings/voltages? Please post the CPU-Z screen shots as explained HERE. Consider running Memtest86+ overnight for 8-10 passes to stress test your RAM.

You video driver is only two months old (March 4, 2014) but it wouldn't hurt to see if there is a more current Nvidia video driver.

I will do all that and get back to you. My computer is over 4 years old, the old DMPs have been deleted and I just started using the computer about a month ago, I had it hooked up to my TV when I came home from college a year ago, but I hardly ever used it.

Yes, I've had problems with it before, I think it could possibly be related to old drivers like an HP printer driver I thought I removed, or camera/scanner drivers which I've had issues with before.

 

[Shintaro]

Could you please add the following options when you run TDSSKiller:

[*]Select "Change Parameters" and Select:

• Verify file digital signatures
• Detect TDLFS file system
• Use KSN to scan objects

[*]When the scan is complete the log file is in C:\ It will have a name like "TDSSKiller.3.0.0.34_04.05.2014_08.05.16_log.txt". Please upload it to the forum.

Also the log file from MalwareBytes is located C:\ProgramData\Malwarebytes\Malwarebytes Anti-Malware\Logs
Please upload them to forum as well.

 

[hg3300]

The virus scans found absolutely nothing.

I am still getting BSODs. Just got around to doing this.

Also for some reason, my computer won't boot from CD to run memtest. It simply says "insert bootable device" or something like that. I tried using a CD and USB, neither worked.

Here are my CPU-Z files as requested.

 

[Shintaro]

Mate,

Can you post a couple of the latest crash files to the forum please.

 

[hg3300]

Here you go.

 

[Shintaro]

Ok,mate, it doesn't look good. The problem is with your CPU or your motherboard. Sorry I need to do a bit more digging/reading.

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: 00000000, Machine Check Exception
Arg2: 8737b8fc, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------
BUGCHECK_STR:  0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
STACK_TEXT:  
8dd87cc4 832ed86d 8737b8e0 83384988 83384980 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8dd87ce4 832ee689 83384980 8737b8e0 833849b0 nt!WheapProcessWorkQueueItem+0x56
8dd87d00 8329914b 83384980 00000000 858c4d48 nt!WheapWorkQueueWorkerRoutine+0x1f
8dd87d50 83425141 00000001 aa1b5577 00000000 nt!ExpWorkerThread+0x10d
8dd87d90 832cc559 8329903e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: AuthenticAMD
IMAGE_NAME:  AuthenticAMD
DEBUG_FLR_IMAGE_TIMESTAMP:  0
IMAGE_VERSION:  
FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_bus_prv
FAILURE_ID_HASH:  {6fd7875b-9a1b-9e09-d6d6-816026a875c8}

So when I dig in to the error it show's the following:

===============================================================================
Common Platform Error Record @ 8737b8fc
-------------------------------------------------------------------------------
Record Id  : 01cf8a8a8d358a91
Severity  : Fatal (1)
Length  : 928
Creator  : Microsoft
Notify Type  : Machine Check Exception
Timestamp  : 6/18/2014 0:16:35 (UTC)
Flags  : 0x00000002 PreviousError

===============================================================================
Section 0  : Processor Generic
-------------------------------------------------------------------------------
Descriptor  @ 8737b97c
Section  @ 8737ba54
Offset  : 344
Length  : 192
Flags  : 0x00000001 Primary
Severity  : Fatal

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

===============================================================================
Section 1  : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor  @ 8737b9c4
Section  @ 8737bb14
Offset  : 536
Length  : 128
Flags  : 0x00000000
Severity  : Fatal

Local APIC Id : 0x0000000000000000
CPU Id  : 42 0f 10 00 00 08 04 00 - 09 20 80 00 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  @ 8737bb14

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

Error  : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
  Status  : 0xf200000000070f0f

 

[hg3300]

Ok,mate, it doesn't look good. The problem is with your CPU or your motherboard. Sorry I need to do a bit more digging/reading.

Yes, please do. Because that doesn't seem right at all.

 

[hg3300]

I've examined ALL bugchecks in Event Viewer (dating back to October of last year) and I've found a few things in common.

There are 3 bugchecks that have occurred several times since October:
-MEMORY_MANAGEMENT (0x0000001a) which has occurred 19 times, common parameters start with either 0x00000411 or 0x00041201
-PFN_LIST_CORRUPT (0x0000004e) which has occurred 7 times, parameters always start with 0x00000099
-WHEA_UNCORRECTABLE_ERROR (0x00000124), has occurred 7 times, parameters always start with 0x00000000

All told, there's about 36 BSODs listed in Event Viewer, dating from October. They don't become regular events until April, which is around the time I started using my computer regularly.

I have linked the list of Bugchecks and parameters for you to look at.

 

[Shintaro]

Did you set the following from a command prompt with Administrator privileges:

wmic recoveros set DebugInfoType = 2

Unfortunately I need a more detailed crash dump to try and interpret the error record in the crash dump. Typically the crash dump I would be looking for is around 500 Mb in size.

In any case, I have been reading that a faulty video card can cause the error.
Are you able to remove the video card and use the on-board video, then re-test?

The other thing to do is to test the Memory with memtest86 link is HERE.

 

[hg3300]

Did you set the following from a command prompt with Administrator privileges:

wmic recoveros set DebugInfoType = 2

Unfortunately I need a more detailed crash dump to try and interpret the error record in the crash dump. Typically the crash dump I would be looking for is around 500 Mb in size.

In any case, I have been reading that a faulty video card can cause the error.
Are you able to remove the video card and use the on-board video, then re-test?

The other thing to do is to test the Memory with memtest86 link is HERE.

I have run that in CMD so it should be working properly.

Yes, I can try to remove the video card, perhaps reseat it even. What I cannot do is run Memtest. I stated a few posts earlier that I would not run from CD or USB.

Also, the link you provide simply redirects me to another random site (Dell, Amazon, MyCleanPC, etc)
The forum states to go to www.memtest.org, no 86 in the URL. https://www.w7forums.com/threads/memtest86-memory-testing.9067/

 

[Shintaro]

Correct, it is just memtest.org.
In regards to booting off the USB or CD for memtest, you will need to look in your motherboards manual for boot order options.
I didn't link to the forums memtest article because memtests interface has changed.
Is there a file called memory.dmp?

 

[hg3300]

Correct, it is just memtest.org.
In regards to booting off the USB or CD for memtest, you will need to look in your motherboards manual for boot order options.
I didn't link to the forums memtest article because memtests interface has changed.
Is there a file called memory.dmp?

I tried modifying the boot order, but it simply wouldn't boot from the CD. And I've used the CD before with no trouble, so I don't know what the problem is.

My memory dump file is too large to upload.

 

[hg3300]

I tried modifying the boot order, but it simply wouldn't boot from the CD. And I've used the CD before with no trouble, so I don't know what the problem is.

My memory dump file is too large to upload.

y'know what, here you go...I copied it to my dropbox folder

https://www.dropbox.com/s/ukaxxk26ad7njm9/MEMORY.DMP

 

[Shintaro]

Did you follow the procedure for creating a Memtest86 bootable disk in the forum Article HERE? Just remember that the Memtest interface is different on the new version.

If the computer is saying "Insert Bootable device" then the CD possibly wasn't created properly for some reason. Are you able to test the CD on another computer?

 

[Shintaro]

Also that file Memory.dmp is corrupt. Could you try again please. But this time put it in a zip file first.

 

[hg3300]

Forget the memory.dmp file then, that's directly from my computer. If it's corrupt, I can't provide you with a better file.

 

[Shintaro]

Next time it crashes it will overwrite Memory.dmp and also create a dump file in the c:\Windows\Minidump directory.

Just zip them up together and upload them to dropbox. After that just the smaller dump files to the forum will do.