Continual BSOD's often starting with games & streams

Welcome to the Forum.

Code:

Start Menu\Programs\Norton Internet Security	Public:Start Menu\Programs\Norton Internet Security	Public

Norton is known to cause BSOD's. Please remove it for testing purpose. Use Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

Microsoft Security Essentials - Free Antivirus for Windows

Malwarebytes - Free

Good and Free system security combination.

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows leftover registry removal:Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Reduce items at start-up: Startup Programs - Change

Perform a clean boot: Troubleshoot Application Conflicts by Performing a Clean Startup

Run a System file check (SFC): SFC /SCANNOW Command - System File Checker

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

Follow this:

Code:

Model	OCZ-VERTEX3

writhziden said:

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Run Disk Check on your Hard Drive(s): Disk Check

Check for heating issues using Speccy or HWmonitor

Upload a screen shot: Screenshots and Files - Upload and Post in Seven Forums

Post screenshot(s) of your Hard Drive(s) using Crystal Disk Info Software: CrystalDiskInfo - Software - Crystal Dew World

Run a Hard Drive test: SeaTools for DOS and Windows - How to Use

Code:

BugCheck 3B, {c0000005, fffff80002f52bc5, fffff88009af30e0, 0}
Probably caused by : ntkrnlmp.exe ( nt!NtQueryVirtualMemory+1d3 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 3B, {c0000005, fffff80002cc7e46, fffff880096be140, 0}
Probably caused by : hardware ( nt!NtWaitForWorkViaWorkerFactory+2c5 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck FE, {5, fffffa8009deb1a0, 80863b3c, fffffa800adc6c48}
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 50, {fffff880089c10b8, 0, fffff80002c91e5b, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 34, {50853, fffff8800373f208, fffff8800373ea60, fffff80002cba27a}
Probably caused by : ntkrnlmp.exe ( nt!ExfWakePushLock+2a )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 18, {0, fffffa800bfb2ee0, 2, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48de1 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 3B, {c0000005, fffff96000186e0a, fffff880089a2900, 0}
Probably caused by : win32k.sys ( win32k!FreeObject+12 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 4E, {2, 192fb7, 23ffff, 1}
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+8d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 10E, {1f, fffff8a01eedd090, 0, 3b70c}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffffc0000005, fffff80002cb82df, fffff8800378c7f8, fffff8800378c050}
Probably caused by : ntkrnlmp.exe ( nt!KiSignalThread+43 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck FE, {5, fffffa8009e1d1a0, 80863b34, fffffa8006d2e438}
Probably caused by : usbehci.sys ( usbehci!EHCI_PollActiveControlEndpoint+57 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck FE, {5, fffffa8009dcf1a0, 80863b3c, fffffa800b2682d8}
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 3B, {c0000005, fffff80002c88410, fffff88002f1eba0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+2ce )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1E, {ffffffffc0000005, fffff80002c89fa6, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!KiInsertQueue+3a7 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 50, {fffffa80cae49af0, 1, fffff80002c94cc4, 5}
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireResourceExclusiveLite+54 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 19, {22, 1000000000000000, 0, 0}
Probably caused by : atikmdag.sys ( atikmdag+37c9a )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck FE, {5, fffffa8009df81a0, 80863b3c, fffffa800b29d258}
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {2, 192fb7, 23ffff, 1}

Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+8d )

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

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000002, A list entry was corrupt
Arg2: 0000000000192fb7, entry in list being removed
Arg3: 000000000023ffff, highest physical page number
Arg4: 0000000000000001, reference count of entry being removed

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


BUGCHECK_STR:  0x4E_2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002ca12ed to fffff80002c90bc0

STACK_TEXT:  
fffff880`037e0ac8 fffff800`02ca12ed : 00000000`0000004e 00000000`00000002 00000000`00192fb7 00000000`0023ffff : nt!KeBugCheckEx
fffff880`037e0ad0 fffff800`02cc8f14 : 00000000`00000000 fffff800`02dc4d0e 00000000`00000000 fffffa80`000000e1 : nt!MiUnlinkPageFromLockedList+0x8d
fffff880`037e0b50 fffff800`02cc99c0 : 00000000`00000000 fffffa80`09ddad00 fffffa80`09ddad98 00000000`00000000 : nt!MiGatherMappedPages+0x104
fffff880`037e0c50 fffff800`02f2d2ea : fffffa80`06d3cb50 00000000`00000080 fffffa80`06d27740 00000000`00000000 : nt!MiMappedPageWriter+0x198
fffff880`037e0d40 fffff800`02c818e6 : fffff800`02e0be80 fffffa80`06d3cb50 fffff800`02e19cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`037e0d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiUnlinkPageFromLockedList+8d
fffff800`02ca12ed cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiUnlinkPageFromLockedList+8d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_2_nt!MiUnlinkPageFromLockedList+8d

BUCKET_ID:  X64_0x4E_2_nt!MiUnlinkPageFromLockedList+8d

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

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

Hi Notus, I would like to ask a few questions. When you try to start the laptop, do you hear any beeps? When you try to start it are you able to see the HP logo at the start? Can you try to boot into bios and see if you have any display in bios. If you do, please look around there and see if bios recognizes your ram, and how much as well as recognizes your hard drive and graphics card.

I would also like you to try to run memtest86+ again and see if there are graphics there. If you get graphics there, let the test run for 8 full passes or overnight if it will, or until you get errors. If you get errors you can stop the test.

Also, laptop memory can be tricky to install and it is easy to install it without it being completely seated. Could you check and see if it is completely installed? If that does not help, try putting both sticks of ram back in, just like it was before. See if that makes a difference. If that does no good, please uninstall all the ram and try to start the laptop. With no ram installed, it will not start, but you should hear a long serise of beeps indicating no ram. That will be good. What that will tell us is that your motherboard is doing what it is supposed to do. If you do not hear any beeps, that will indicate to us us that your motherboard is not doing what it should do. I hope all of this makes sense to you. If not feel free to ask any questions. What all of this is about is trying to see if you have software or hardware problems and which type of hardware problems you have.

Did it crash during memtest? running memtest will not harm a computer. It runs from ram and the Operating system or hard drive is not involved at all. Did you receive any errors during the test? What happens when you try to starthe laptop?