Repetitive Bluescreens - Blue screen crash on Team speak startup.

[flynch]

Hi all!

I have been experiencing a a blue screen crash when i open team speak up. This usually happens from about 1- 10 seconds after opening team speak. I have tried a fresh install of Windows and Team speak. I have tried system restore and other methods any one with any idea or has had the same problem before by any chance could give me some advice thanks!



I have a blue screen report included in attached files and 08122015 is my most recent txt file I could find with hopefully some info that someone could use.

Thanks in advance to anyone!
Cheers

 

[5050]

Can you catch the screen, even from phone, to have the name of the driver or file which crashed ?
It helps to know which part is in fault. (note : if it flash for only a short time, "pause" key usually locks it).

If it happens exclusively with teamspek, I would first suspect something from audio (driver, or codec). I did not used teamspeak for long time, but you may try to select another codec and try again... or you can also try another previous release of teamspeak.

But it can also come from anything else, like ram failure. Think to do a run of memtest86+ (free at Memtest86+ - Advanced Memory Diagnostic Tool ), to ensure ram is out of suspicion.

 

[flynch]

bluescreen screenshot

There is the screenshot. I am doing the MEMTEST now.

Thanks for your help

 

[flynch]

I have completed a Memtest and it has returned no errors

 

[5050]

bluescreen screenshot

Thanks (ironical) to microsoft, there is here nothing here to help.
More the windows version increases, less it gives infos to help.

Sorry, it is now out of my knowledge.
May be, try to ask for help in teamspeak forum : they are at first place about knowledge of its potentials problems.

 

[axe0]

With every bluescreen, no minidump could be created which is why no dump is present.

Event[3119]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2015-12-10T20:45:55.000
  Event ID: 1005
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Finton-PC
  Description: 
[COLOR="Red"]Unable to produce a minidump file from the full dump file[/COLOR].

Please make sure your pc is configured for small dump files http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

 

[flynch]

I have had a more tech savvy friend come have a look, he thinks its bad ram. he blue screen crashes when i watch a video on facebook as well. One stick wouldn't boot the computer, ( It kept powering on then the fans would stop after a second followed by the power turning off, then the computer would try to boot again and this process would repeat.

So now I'm on one 8gb ram stick ( half of what i have) with the "good" ram stick in but bluescreens are still happening.

 

[axe0]

http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[flynch]

Hi all , soo an update...

Have wiped my computer with a fresh install of windows 7. Installed only LAN driver (for internet), chrome ( to download team speak) and Team speak ( to test the original blue screen cause). I am still getting crashes. I did a memtest over night last night and ran 10 passes with no errors. I have attatched latest bluescreen text file from bluescreen viewer, it doesnt give me much information, hoping anyone knows anything at all. All i know is that it is a 0x00000124 error.

Hopefully borrowing a mates ram to test and rule that out completely.

Cheers

 

[flynch]

http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

Here is a DM Log collector report, my latest one.

 

[axe0]

The dump doesn't contain much more then following what I believe means it hasn't been documented publicly.
Please follow instructions below.

4: kd> !errrec fffffa8007eef028
===============================================================================
Common Platform Error Record @ fffffa8007eef028
-------------------------------------------------------------------------------
Record Id     : 01d136c646a8b0e5
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 12/15/2015 1:25:48 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007eef0a8
Section       @ fffffa8007eef180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000004

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

Local APIC Id : 0x0000000000000004
CPU Id        : c3 06 03 00 00 08 10 04 - ff fb fa 7f ff fb eb bf
                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  @ fffffa8007eef240

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

[COLOR="Red"]Error         : Internal unclassified (Proc 4 Bank 4)[/COLOR]
  Status      : 0xba00000052000402

STOP 0x124 Troubleshooting

Read carefully before proceeding.

   Warning

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

   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

ONE

 CPU TEST

Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 7 Help Forums

   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.

TWO

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Help Forums

   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.

THREE

 HDD TEST

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

   Note

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

Run chkdsk
Disk Check - Windows 7 Help Forums

Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
Let me know what the results are

• of the error scan,
• make a screenshot of the health of every hard drive and post the screenshots,
• post screenshots with the benchmark of the
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

FOUR

 GPU TEST

Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 7 Help Forums

   Note

Run Furmark for around 30 minutes.

   Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.