Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD, mostly when gaming with twitch.tv stream on second monitor

09 Oct 2013   #1
Mazgruka

windows 7 home premium sp1
 
 
BSOD, mostly when gaming with twitch.tv stream on second monitor

Here's my .dmp files as well as the SF diagnostic folder


My System SpecsSystem Spec
.
10 Oct 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

That is some stressful situation for the PS for sure.

The recent BSOD crash dumps are indicating to display failure, as well as some hints to storage malfunctioning.

Make it sure that the SanDisk 120 GB SSD is running with the up-to-date firmware.

Update JMicron JMB36X Controller from ftp://driver.jmicron.com.tw/SATA_Controller/Windows/

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator

Install the NVIDIA DRIVERS 314.22WHQL only.
  • Uninstall All nvidia items in Control Panel > Programs and features
    • 3D Vision Control Driver
    • 3D Vision Driver
    • Graphics Driver
    • HD Audio Driver
    • PhysX
    • nvidia Update
    (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
  • Now follow Drivers - Clean Left over Files after Uninstalling
  • Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

Let us know the results.

________________________________________________________________________________
Code:
BugCheck 1000007E, {ffffffffc0000005, fffff800034c5642, fffff880031fd6d8, fffff880031fcf30}

Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )

Followup: MachineOwner
--------------------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff800034ab642, fffff8800d8da050, 0}

Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )

Followup: MachineOwner
---------
My System SpecsSystem Spec
10 Oct 2013   #3
Mazgruka

windows 7 home premium sp1
 
 

Updated the JBM36X driver, lesson learned don't trust the MB software to always find the newest drivers for you. It's never been a hot running computer. When I first put it together i ran evga precision x while gaming to make sure that the minor overclock i had put on my gtx 670's wasn't causing too much heat, attached a screen shot of speccy after a while of being on and about 5-10 minutes after running furmark burn-in test, which it remained very stable even when reaching 77 celcius. Cleared out all of my nvidia drivers and rolled back to the 314.22 drivers you linked me. I ran one pass on the memory test just to check really quick, with no faults, I'll run it overnight to do a full test. As for the PS, I plugged in my system into the calculator and it recommends 495-545 minimum (depending if im running into capacitor aging, it's a fairly new psu maybe 6 months old) and 545-595 recommended, I'm running a 650w psu, according to the calculator even if i manage to hit 100% load with a 10% capacitor aging my psu should still be up to par. And I just found updated firmware for my ssd so I'll get to installing that now.
Hopefully it was just a combination of an old MB driver and old firmware on my ssd. Crossing my fingers!
Edit: also just set my second monitor to the same refresh rate as my primary, just for the chance it had anything to do with it
My System SpecsSystem Spec
.

11 Oct 2013   #4
Mazgruka

windows 7 home premium sp1
 
 

Uploading fresh crash report data from this evening after the above changes. It happened even when just league of legends open, and once when restarting after a bsod
My System SpecsSystem Spec
11 Oct 2013   #5
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

I am having some technical problem to read your files ... so asked for some more help.

Hopefully some other person will check those shortly.
My System SpecsSystem Spec
11 Oct 2013   #6
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Same here I guess..
Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\SF_10-10-2013\SF_10-10-2013\101013-14742-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`03415000 PsLoadedModuleList = 0xfffff800`036586d0
Debug session time: Fri Oct 11 10:34:59.323 2013 (UTC + 6:00)
System Uptime: 0 days 1:44:59.993
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

***** 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+75b90 )

Followup: MachineOwner
---------
My System SpecsSystem Spec
11 Oct 2013   #7
Mazgruka

windows 7 home premium sp1
 
 

Thats the same problems i was getting when trying to read the .dmp files myself. Which is why i came here. Here is the .dmp files straight from the minidump folder. Maybe better luck with these
My System SpecsSystem Spec
11 Oct 2013   #8
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

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


Loading Dump File [C:\Users\USER\Downloads\101013-14648-01\101013-14305-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`03404000 PsLoadedModuleList = 0xfffff800`036476d0
Debug session time: Fri Oct 11 08:49:40.550 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:19.220
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800034aa622, fffff8800d3549d0, 0}

***** 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+a6622 )

Followup: MachineOwner
---------
Same thing
My System SpecsSystem Spec
11 Oct 2013   #9
x BlueRobot

 

Have you tried .symfix and then .reload?
My System SpecsSystem Spec
13 Oct 2013   #10
Mazgruka

windows 7 home premium sp1
 
 

.symfix and .reload? cmd prompts? I'm pretty computer savvy, but when we get this deep into troubleshooting i'm in over my head
My System SpecsSystem Spec
Reply

 BSOD, mostly when gaming with twitch.tv stream on second monitor




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSODs @ various situations (Youtube, gaming, twitch)
Hi i have been experiencing BSODs on my computer. They seem to happen somewhat randomly but twitch.tv almost always causes bsod. My computer is a custom build by my friend. Is it possible that there is bad connection somewhere which is causing these BSODs? How do i find it? Im not expert with...
BSOD Help and Support
BSOD while gaming and watching stream
Hello i just got a BSOD while i was playing Hearthstone and watching some streams from twitch.tv. Right after i got the BSOD and i tried to restart pc it wasnt starting , the MSI motherboard wallpaper didnt appear on screen but it got in DOS (never happened before) and all the devices were loading,...
BSOD Help and Support
Why did I get this BSOD error while gaming and listening to a stream?
Hmm...Just add 4 gigs of ram this weekend and according to crystal disk info the hard drive with my OS has error on it. :eek:
BSOD Help and Support
BSOD while watching Twitch Stream, error 1000007e
Hello, I updated my hardware(New CPU, GPU, and Motherboard) recently this past Wednesday and after everything is installed and running it seems to run fine. I attempted some Overclocking of my CPU and got my first BSOD(Unfortunately Windows did not save the dump file of this event) so I stopped...
BSOD Help and Support
BSOD playing Simcity while watching Twitch stream
Hello, A bsod has occured twice in the last week and I am requesting some diagnostics on the cause of them. I have a suspicion that it is my video drivers.
BSOD Help and Support
BSOD When playing a game and watching a stream on Twitch
In addition to title info, my computer only crashes while watching the stream and gaming at the same time. If I do either independently I don't crash ever it seems like. Same for gaming and streaming my game from Xsplit or FFSplit. Since I can do either independently it isn't really a pressing...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 15:45.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App