Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

bsod some time after startup


  • Please log in to reply
3 replies to this topic

#1 sabriel123

sabriel123

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:10:37 PM

Posted 21 October 2016 - 07:10 AM

So i recently built a new pc and the weirdest thing is that i get a blue screen of death about 20-30min after i start the pc but only if i start gaming. if not it can run without any problems. Now the funny thing is that this only happens once and after the blue screen i can start the pc again and it wont crash even if it runs for a few days straight while doing absolutely anything on it. it has some decent specs, temperature is not a problem, the hardware is brand new.

 

Im kinda new to all this so i will do my best to give you any information needed and english isnt my native language so i apologize for any mistakes.

Thanks for any answers!

 

also im running updated windows 7 

 

might aswell add some specs it cant hurt;

 

intel core i5 6600 3,3 GHz

16GB ripjaws ram

64bit operating system

gtx 1060 3GB

 

 

also i was already looking at some of the errors in event viewer and this seems to be one of the crashes;

  System
    - Provider
      [ Name] Microsoft-Windows-Kernel-Power       [ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
      EventID 41       Version 2       Level 1       Task 63       Opcode 0       Keywords 0x8000000000000002     - TimeCreated
      [ SystemTime] 2016-10-18T12:43:24.732400000Z
      EventRecordID 7132       Correlation     - Execution
      [ ProcessID] 4       [ ThreadID] 8
      Channel System       Computer Jure-nov     - Security
      [ UserID] S-1-5-18
- EventData
    BugcheckCode 59     BugcheckParameter1 0xc0000096     BugcheckParameter2 0xfffff9600008c688     BugcheckParameter3 0xfffff8800885de80     BugcheckParameter4 0x0     SleepInProgress false     PowerButtonTimestamp 0

Edited by sabriel123, 21 October 2016 - 07:17 AM.


BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:04:37 PM

Posted 23 October 2016 - 04:30 AM

Please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum)   http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
FYI - I don't often use the Perfmon report, so if it doesn't work please just let me know.
NOTE:  On problem systems it can take up to 20 minutes for the log files to complete.  Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR or other compression utilities. 
.ZIP is the type file that can be uploaded to the forums.

 


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 sabriel123

sabriel123
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:10:37 PM

Posted 24 October 2016 - 07:32 AM

i hope this is what you were looking for? thanks for the help in advance!

Attached Files



#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:04:37 PM

Posted 26 October 2016 - 03:51 PM

Unfortunately it appears that the system has pirated software.
Please get a legitimate copy installed and we'll be glad to help.

Here's suggestions on how to ensure that your version is legitimate:  http://windows.microsoft.com/en-us/windows/genuine

Please be aware that we may not be able to fix it (as the hacks that were done to activate it will cause the OS to behave differently than we expect it to). If that's the case, our efforts to help may just waste your time. Secondly, the forum rules prohibit assisting with pirated software - so the topic would be closed if that is the case.

As a courtesy, I will offer an analysis of your issues using the reports you provided.
I will not answer any questions about the analysis until the system is made legitimate.
If you do make it legitimate, please submit a new set of reports for us to check.

Just FYI, sometimes the owner won't know about this.  So here's 2 scenarios that might ring a bell:
- if they had a "friend" help with the computer - and the "friend" installed a pirated copy.
- or they used a copy that they had from another OEM computer.  The OEM license is tied to the hardware that it came from - so you can't just use it on another system (that means that it's pirated).

And here's the analysis:

Only 262 Windows Update hotfixes installed.  Most systems with SP1 have 350-400 or more.  Please visit Windows Update and get ALL available updates (it may take several trips to get them all).
The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

Out of 12 memory dumps there were 6 different BSOD  (aka STOP or BugCheck) error codes.  The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things (the list is not in any sort of order):
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- dirt/dust/hair/fur/crud inside the case.  Blow out the case/vents with canned air (DO NOT use an air compressor or vacuum as they can cause damage to the system)
- missing Windows Updates
- compatibility issues (3rd party hardware/drivers), older systems, or even pirated systems
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from http://www.carrona.org/initdiag.html or http://www.carrona.org/hwdiag.html ).

Please get a head start on the hardware diagnostics - they are located here:  http://www.carrona.org/hwdiag.html

NTIOLib_X64.sys is known to cause BSOD's on some Windows systems.

Go here to see the programs that it's associated with and uninstall those programs from your system:  http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys

 

WinRing0x64.sys is known to cause BSOD's on some Windows systems.

Go here to see the programs that it's associated with and uninstall those programs from your system: http://www.carrona.org/drivers/driver.php?id=WinRing0x64.sys

 


Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Mon Oct 24 08:24:54.448 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\102416-8455-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.23564.amd64fre.win7sp1_ldr.160930-0600
System Uptime:0 days 0:04:18.587
Probably caused by :ntkrnlmp.exe ( nt!ObpCaptureHandleInformation+55 )
BugCheck 3B, {c0000005, fffff800031ec895, fffff8800be85c10, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800031ec895, Address of the instruction which caused the bugcheck
Arg3: fffff8800be85c10, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  Steam.exe
FAILURE_BUCKET_ID: X64_0x3B_nt!ObpCaptureHandleInformation+55
CPUID:        "Intel® Core™ i5-6600 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3312
  BIOS Version                  5.40
  BIOS Release Date             05/23/2016
  Manufacturer                  MSI
  Product Name                  MS-7994
  Baseboard Product             H110M GAMING (MS-7994)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Oct 23 15:43:32.742 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\102316-7753-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.23564.amd64fre.win7sp1_ldr.160930-0600
System Uptime:0 days 0:08:32.882
Probably caused by :win32k.sys ( win32k+79dec )
BugCheck 3B, {c0000005, fffff960000a9dec, fffff88008a55cb0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960000a9dec, Address of the instruction which caused the bugcheck
Arg3: fffff88008a55cb0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  LoLPatcher.exe
FAILURE_BUCKET_ID: X64_0x3B_win32k+79dec
CPUID:        "Intel® Core™ i5-6600 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3312
  BIOS Version                  5.40
  BIOS Release Date             05/23/2016
  Manufacturer                  MSI
  Product Name                  MS-7994
  Baseboard Product             H110M GAMING (MS-7994)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct 21 08:52:45.950 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\102116-8439-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.23564.amd64fre.win7sp1_ldr.160930-0600
System Uptime:0 days 0:02:49.715
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :win32k.sys ( win32k+b1684 )
BugCheck 50, {fffff90135608874, 0, fffff960000d1684, 5}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Arguments:
Arg1: fffff90135608874, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960000d1684, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID: X64_0x50_win32k+b1684
CPUID:        "Intel® Core™ i5-6600 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3312
  BIOS Version                  5.40
  BIOS Release Date             05/23/2016
  Manufacturer                  MSI
  Product Name                  MS-7994
  Baseboard Product             H110M GAMING (MS-7994)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.

Spoiler




3rd Party Drivers:
The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Mon Oct 24 08:24:54.448 2016 (UTC - 4:00)**************************
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
VClone.sys                  Wed Jul 24 11:02:46 2013 (51EFEC96)
ElbyCDIO.sys                Wed Dec 17 18:30:51 2014 (5492122B)
iusb3hub.sys                Mon Jun 15 09:54:03 2015 (557ED8FB)
iusb3xhc.sys                Mon Jun 15 09:54:05 2015 (557ED8FD)
asmtxhci.sys                Thu Sep 10 05:38:13 2015 (55F14F85)
asmthub3.sys                Thu Sep 10 05:38:17 2015 (55F14F89)
iqvw64e.sys                 Thu Oct 29 17:44:49 2015 (56329351)
e1d62x64.sys                Tue Nov 24 14:09:03 2015 (5654B5CF)
RTKVHD64.sys                Tue Jan 26 06:03:05 2016 (56A75269)
TeeDriverx64.sys            Wed Feb  3 17:40:35 2016 (56B281E3)
nvhda64v.sys                Tue May 10 04:59:01 2016 (5731A2D5)
nvvad64v.sys                Fri Jul  1 09:12:29 2016 (57766C3D)
MpFilter.sys                Mon Aug  8 19:01:17 2016 (57A90F3D)
nvlddmkm.sys                Sat Oct  1 15:06:38 2016 (57F0093E)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Oct  8 02:39:30.738 2016 (UTC - 4:00)**************************
WinRing0x64.sys             Sat Jul 26 09:29:37 2008 (488B26C1)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct  7 13:53:25.595 2016 (UTC - 4:00)**************************
NTIOLib_X64.sys             Thu Oct 25 06:27:58 2012 (5089142E)
nvvad64v.sys                Tue Apr 12 04:46:52 2016 (570CB5FC)
NvStreamKms.sys             Fri Jun  3 07:28:21 2016 (575169D5)


http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=VClone.sys
http://www.carrona.org/drivers/driver.php?id=ElbyCDIO.sys
http://www.carrona.org/drivers/driver.php?id=iusb3hub.sys
http://www.carrona.org/drivers/driver.php?id=iusb3xhc.sys
http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys
http://www.carrona.org/drivers/driver.php?id=asmthub3.sys
http://www.carrona.org/drivers/driver.php?id=iqvw64e.sys
http://www.carrona.org/drivers/driver.php?id=e1d62x64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=WinRing0x64.sys
http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys



XXXXX
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users