BSOD Mostly while playing or watching videos

Hello all.

Recently after getting my new desktop (it's a week old) 2 days after getting it I started getting some random BSODs (As said in the title, mostly when playing or watching videos). I basically get the BSOD and then, of course, the pc reboots. My OS is windows 8.1 so I tried to update with all the latest updates but no luck. I also updated my drivers to the latest ones (Atleast I think I did it right) Hope you guys will be able to help me out and thanks for your time!

Attachment 342282

Golden said:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C2, {9b, 200, 10, fffff800c10d1121}

*** WARNING: Unable to verify timestamp for VerifierExt.sys
*** ERROR: Module load completed but symbols could not be loaded for VerifierExt.sys
Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c )

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

Ensure Windows is fully updated.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff8025fa5b895, 0, 232}

Probably caused by : memory_corruption

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

Run a minimum of 8 passes, preferably overnight, or until errors occur using MemTest86+.

Reference this tutorial to help you use MemTest86+:
RAM - Test with Memtest86+

Uninstall this program - not needed.

Code:

Start Menu\Programs\Driver Booster 2    Public:Start Menu\Programs\Driver Booster 2    Public

Code:

Start Menu\Programs\Ultimate Boob Wars!! ~Big Breasts vs Flat Chests~    Public:Start Menu\Programs\Ultimate Boob Wars!! ~Big Breasts vs Flat Chests~    Public
Start Menu\Programs\ƒtƒŠƒ‹ƒ{�[ƒC    IPE7ER\iPe7eR:Start Menu\Programs\ƒtƒŠƒ‹ƒ{�[ƒC    IPE7ER\iPe7eR
Start Menu\Programs\ƒtƒŠƒ‹ƒ{�[ƒC\˜T�*”N‚Í’j‚Ì–º�iDL”Å�j    IPE7ER\iPe7eR:Start Menu\Programs\ƒtƒŠƒ‹ƒ{�[ƒC\˜T�*”N‚Í’j‚Ì–º�iDL”Å�j    IPE7ER\iPe7eR

Perform a malware scan using this link:
Free Virus Scan | Online Virus Scanner from ESET

Ok thanks for the quick reply! btw those you specified for the virus scan are just some Japanese Visual Novels (Eroges as you can probably hint from one of the titles heheh ) and got them from trusthoworthy sites but I will scan anyway

Gonna run memtest this night and report back later for letting you know! And the only update I get for windows when checking is a windows defender update so I guess it's fully updated?

Well, thanks for the fast reply anyways! Will report back later

Ok so I did all the suggested things. Ran the malware test and removed all found issues, updated with all windows updates and lastly ran memtest. And here a weird thing happened. I went to bed letting memtest on for whole night (almost 9 hours) when I woke up this morning and checked, it completed only 2 passes(without errors) ? I think that's not supposed to happen after 9 hours of testing.

Had 2 more BSODs too today, one was this

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\120614-46546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 8 Kernel Version 9600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17415.amd64fre.winblue_r4.141028-1500
Machine Name:
Kernel base = 0xfffff800`cb889000 PsLoadedModuleList = 0xfffff800`cbb62250
Debug session time: Sat Dec 6 18:16:39.593 2014 (UTC + 1:00)
System Uptime: 0 days 2:53:17.303
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
..............
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {b500190645, ffffd00021918018, ffffd00021917820, fffff800cba6c485}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+1e3485 )

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



The other one was a little bit weird. I was playing and suddenly the pc froze with audio looping and without giving a BSOD and it didn't even give a minidump In the system registry it got registered though, and as Kernel Power Error 41 (63) as all the others I got till now.

I just had to do a windows 8 fresh install cause the pc kept freezing without even giving BSOD... And i honestly couldn't do anything.

Now the freezing is gone, but guess what? Got another BSOD 5 mins ago.. Here's the zip.

Attachment 342393

Golden said:

Run a minimum of 8 passes, preferably overnight, or until errors occur using MemTest86+.

Reference this tutorial to help you use MemTest86+:
RAM - Test with Memtest86+

Don't do anything else except testing Memory.

Ok thanks for the quick reply.

And just had a freeze, no BSOD, nothing, just the pc freezing, had to hard reboot cause nothing would work... Gonna run memtest and report back.

Running memtest and after a mere 40 minutes 2799 errors popped up. I guess this is pretty bad. Will let it run for more time but I guess that's already a pretty bad sign.