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 please help


  • Please log in to reply
12 replies to this topic

#1 phixer

phixer

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:05:08 AM

Posted 18 December 2016 - 02:15 PM

Hi, I have been getting BSOD every now and then since 28.11. I ran driver verifier and I got BSOD even before the login into windows: DRIVER_VERIFIER_IOMANAGER_VIOLATION, MODULE_NAME: dadder, IMAGE_NAME:  dadder.sys(121616-68843-01.dmp in the attachment). So I deleted dadder.sys since I don't use DeathAdder mouse anymore and turned off driver verifier, but BSOD striked again. I tried driver verifier again and so far nothing is happening, even though it's been running the whole day. Other than that I tried to test RAM with the Windows built in program(2 passes on standart), uninstalled and installed the newest drivers for everything, ran TDSSKILLER and sfc scannow. Also i did full scan with ESET nod32 antivirus that I use. All my PC parts are 2 months old(I built the computer) and I didn't overclock anything.

 

OS:Windows 8.1 x64

CPU: Intel i5-6500

Video cart: MSI GeForce GTX 1060 3GB OC

Motherboard: MSI B150M Mortar

Power supply:Seasonic SS-500ET, T3 500W OEM

 

Thanks in advance.

Attached Files


Edited by phixer, 19 December 2016 - 08:01 AM.


BC AdBot (Login to Remove)

 


#2 phixer

phixer
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:05:08 AM

Posted 19 December 2016 - 08:00 AM

And I don't know if it has any connection with it, but my mouse unplugs and plugs back in immediately randomly.



#3 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:12:08 AM

Posted 20 December 2016 - 06:05 PM

The mouse thing sounds like a problem with the USB plugs

If the mouse is plugged into the front of the case, try plugging it into the back of the case (or vice versa)

Does that help?

 

Your UEFI/BIOS dates from 2016.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a more recent update.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  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.

MSI Afterburner (along with EVGA Precision and Riva Tuner) are known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys).  Please un-install them immediately!

If you're overclocking, please stop the overclock while we're troubleshooting.  Feel free to resume the overclock once the system has been stabilized.

 

Please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

If it doesn't crash within 36 hours, post back and we'll suggest other tests.

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
*************************Sat Dec 17 18:47:53.568 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121816-16484-01.dmp]
Windows 8.1 Kernel Version 9600 MP (4 procs) Free x64
Built by: 9600.18505.amd64fre.winblue_ltsb.160930-0600
System Uptime:0 days 23:53:31.239
Probably caused by :ntkrnlmp.exe ( nt!KiCancelTimer+e5 )
BugCheck A, {ffffe0015ff37780, 2, 0, fffff80350ae3351}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: ffffe0015ff37780, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80350ae3351, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  audiodg.exe
FAILURE_BUCKET_ID: AV_nt!KiCancelTimer
CPUID:        "Intel® Core™ i5-6500 CPU @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3192
  BIOS Version                  C.60
  BIOS Release Date             07/22/2016
  Manufacturer                  MSI
  Product Name                  MS-7972
  Baseboard Product             B150M MORTAR (MS-7972)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Dec 16 16:41:27.600 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121616-68843-01.dmp]
Windows 8.1 Kernel Version 9600 MP (4 procs) Free x64
Built by: 9600.18505.amd64fre.winblue_ltsb.160930-0600
System Uptime:0 days 0:00:17.302
*** ERROR: Module load completed but symbols could not be loaded for hidusb.sys
*** WARNING: Unable to verify timestamp for dadder.sys
*** ERROR: Module load completed but symbols could not be loaded for dadder.sys
Probably caused by :dadder.sys ( dadder+24e0 )
BugCheck C9, {23e, fffff801d76904e0, ffffcf80c5c4e8b0, 0}
BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
Arguments:
Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: fffff801d76904e0, The address in the driver's code where the error was detected.
Arg3: ffffcf80c5c4e8b0, IRP address.
Arg4: 0000000000000000, Status code.
BUGCHECK_STR:  0xc9_23e
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0xc9_23e_VRF_dadder!unknown_function
CPUID:        "Intel® Core™ i5-6500 CPU @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3192
  BIOS Version                  C.60
  BIOS Release Date             07/22/2016
  Manufacturer                  MSI
  Product Name                  MS-7972
  Baseboard Product             B150M MORTAR (MS-7972)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Dec 16 09:21:51.225 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121616-62250-01.dmp]
Windows 8.1 Kernel Version 9600 MP (4 procs) Free x64
Built by: 9600.18505.amd64fre.winblue_ltsb.160930-0600
System Uptime:1 days 4:17:25.897
*** WARNING: Unable to verify timestamp for cfosspeed6.sys
*** ERROR: Module load completed but symbols could not be loaded for cfosspeed6.sys
Probably caused by :cfosspeed6.sys ( cfosspeed6+17cfa2 )
BugCheck A, {ffffe0018ee23778, 2, 0, fffff801e6f220bb}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: ffffe0018ee23778, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff801e6f220bb, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: AV_cfosspeed6!unknown_function
CPUID:        "Intel® Core™ i5-6500 CPU @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3192
  BIOS Version                  C.60
  BIOS Release Date             07/22/2016
  Manufacturer                  MSI
  Product Name                  MS-7972
  Baseboard Product             B150M MORTAR (MS-7972)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
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:

**************************Sat Dec 17 18:47:53.568 2016 (UTC - 5:00)**************************
intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
I2cHkBurn.sys               Mon Feb 17 20:34:54 2014 (5302B8BE)
SteelBus64.sys              Tue May 27 12:42:05 2014 (5384C05D)
iusb3adp.sys                Wed Jul 15 10:49:44 2015 (55A67308)
em015_64.dat                Thu Aug  6 05:05:59 2015 (55C32377)
cfosspeed6.sys              Mon Sep 28 10:12:31 2015 (56094ACF)
NTIOLib_X64.sys             Tue Apr 12 03:04:16 2016 (570C9DF0)
Rt630x64.sys                Fri Apr 22 02:47:57 2016 (5719C91D)
TeeDriverW8x64.sys          Wed Jul 13 12:52:17 2016 (578671C1)
iaLPSS2_I2C.sys             Mon Aug  8 22:22:40 2016 (57A93E70)
iaLPSS2_UART2.sys           Mon Aug  8 22:22:53 2016 (57A93E7D)
iaLPSS2_GPIO2.sys           Mon Aug  8 22:22:56 2016 (57A93E80)
nvhda64v.sys                Thu Sep 29 09:25:06 2016 (57ED1632)
BEDaisy.sys                 Sun Oct  2 03:06:55 2016 (57F0B20F)
nvvad64v.sys                Tue Oct  4 03:20:09 2016 (57F35829)
em006_64.dat                Fri Oct  7 08:39:14 2016 (57F79772)
eamonm.sys                  Mon Oct 17 08:22:19 2016 (5804C27B)
edevmon.sys                 Mon Oct 17 08:22:19 2016 (5804C27B)
ehdrv.sys                   Mon Oct 17 08:23:22 2016 (5804C2BA)
epfwwfpr.sys                Mon Oct 17 08:24:18 2016 (5804C2F2)
RTKVHD64.sys                Tue Oct 18 07:20:52 2016 (58060594)
nvlddmkm.sys                Sun Dec 11 13:14:23 2016 (584D977F)
em018_64.dat                Tue Dec 13 07:44:43 2016 (584FED3B)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Dec 16 16:41:27.600 2016 (UTC - 5:00)**************************
dadder.sys                  Thu Aug  2 05:33:03 2007 (46B1A4CF)
SAlpham64.sys               Tue May 27 12:46:34 2014 (5384C16A)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec 11 12:52:22.890 2016 (UTC - 5:00)**************************
nvlddmkm.sys                Thu Dec  1 11:35:09 2016 (5840513D)
em018_64.dat                Tue Dec  6 05:48:26 2016 (5846977A)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec  4 15:03:15.797 2016 (UTC - 5:00)**************************
iaLPSS2_I2C.sys             Mon May  4 08:41:19 2015 (554768EF)
iaLPSS2_GPIO2.sys           Mon May  4 08:41:36 2015 (55476900)
nvlddmkm.sys                Thu Nov 24 14:01:49 2016 (5837391D)
em018_64.dat                Mon Nov 28 04:30:15 2016 (583BF927)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Nov 28 15:22:12.602 2016 (UTC - 5:00)**************************
em018_64.dat                Mon Nov 14 04:31:56 2016 (5829848C)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Nov 28 09:11:02.614 2016 (UTC - 5:00)**************************
TeeDriverW8x64.sys          Mon Mar 28 14:59:41 2016 (56F97F1D)
RTKVHD64.sys                Tue Aug 16 08:14:34 2016 (57B303AA)
nvvad64v.sys                Thu Sep 22 12:46:30 2016 (57E40AE6)
nvlddmkm.sys                Wed Nov 16 19:25:32 2016 (582CF8FC)


http://www.carrona.org/drivers/driver.php?id=intelppm.sys
I2cHkBurn.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=SteelBus64.sys
http://www.carrona.org/drivers/driver.php?id=iusb3adp.sys
http://www.carrona.org/drivers/driver.php?id=em015_64.dat
http://www.carrona.org/drivers/driver.php?id=cfosspeed6.sys
http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys
http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
iaLPSS2_I2C.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
iaLPSS2_UART2.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=iaLPSS2_GPIO2.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=BEDaisy.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=em006_64.dat
http://www.carrona.org/drivers/driver.php?id=eamonm.sys
http://www.carrona.org/drivers/driver.php?id=edevmon.sys
http://www.carrona.org/drivers/driver.php?id=ehdrv.sys
http://www.carrona.org/drivers/driver.php?id=epfwwfpr.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=em018_64.dat
http://www.carrona.org/drivers/driver.php?id=dadder.sys
http://www.carrona.org/drivers/driver.php?id=SAlpham64.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=em018_64.dat
iaLPSS2_I2C.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=iaLPSS2_GPIO2.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=em018_64.dat
http://www.carrona.org/drivers/driver.php?id=em018_64.dat
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys

 
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.

#4 phixer

phixer
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:05:08 AM

Posted 21 December 2016 - 06:05 AM

No, I tried every USB port on my computer and the problem still remains. I have the latest BIOS version and there are no Windows updates. I'll uninstall MSI afterburner, but I never used it anyway and I don't have anything overclocked. I tried to run driver verifier for a whole day and no BSOD. The thing is that with driver verifier everything is so slow, I can't play games, streams are lagging etc. so is there a point in using it, when I won't do what I would usually do? Also i feel like the BSOD are only happening when I'm gaming.



#5 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:12:08 AM

Posted 21 December 2016 - 08:30 AM

From the reports that you posted, your system can go up to 7 days between BSOD's

As such, I'd actually suggest that (for a thorough test) you run Driver Verifier for at least 7 days - but that's a bit too much IMO (due to the performance issues).

 

If Driver Verifier doesn't cause a crash, then we assume that this isn't a driver problem.

If you used my suggested settings, then we presume that it's not a 3rd party driver problem.

This often suggests that the problem is related to a problem with your hardware.

As such, start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

Please finish ALL of the diagnostics and let  us know the results.

 

2 other things I noticed:

1)  The NTIOLib_X64.sys driver is known to cause BSOD's on some Windows systems.

Please uninstall the MSI OC Kit.

2)  I have seen problems with cFosSpeed - The Internet Accelerator (Also a part of Asus TurboLAN)

Please uninstall it.


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.

#6 phixer

phixer
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:05:08 AM

Posted 23 December 2016 - 03:27 PM

I uninstalled the programs, but they most likely weren't the problem since I installed them after the BSOD started hapenning. I installed them when I was reinstalling all my drivers and saw them on the MSI website for my motherboard and wanted to check them out. But i never really used them.
 
I ran quick and extended test for hard drive with Western Digital Data LifeGuard Diagnostics for Windows and 5 passes with MemTest86+ for RAM. Then I did stress test for CPU with Prime95. 2 hours of Small FFTs with max. temperature 82°C and 7 hours of In-place large FTTs with max. temperature 84°C. I didn't do Blend, because I already checked RAM with MemTest. After that, I did stress test for GPU with FurMark on 1920x1080 and everything ticked in the settings, except dynamic camera, for 15 minutes. Average fps 36 and max. temperature 72°C. No errors or problems anywhere. Is the duration of the tests good? And are these temperatures ok? When I'm playing Overwatch my CPU is at roughly 62°C and GPU 61°C, so I don't think there is a problem.


#7 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:12:08 AM

Posted 24 December 2016 - 01:47 PM

Tests are good.  The temps aren't bad.  I wouldn't worry about them as a cause for the BSOD's though.

Please run Prime95's Blend test - it tests RAM differently than MemTest (and I have seen systems fail Prime95 Blend even after passing MemTest).

 

Did you run the Intel Processor Diagnostic test?  How about the other video tests?

If they all passed, then we've reached a decision point.

 

Either wipe the system and reinstall Windows "clean" ( http://www.carrona.org/canned.html#clean ) - or run this procedure to help rule out hardware components ( http://www.carrona.org/strpdown.html )

Installing Windows "clean" will help to rule out 3rd party program problems (as none will be installed) and Windows problems (as it'll only be Windows that's installed).

As such, if the problems continue, then it's almost certainly a hardware issue.  If the problems don't continue, then it was either a 3rd party software problem or a Windows problem.


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.

#8 phixer

phixer
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:05:08 AM

Posted 09 January 2017 - 08:54 AM

So instead of that I changed my mouse and I haven't had BSOD for almost 3 weeks now. Don't know how mouse can cause BSOD, but I think that was the reason. I'm gonna buy a new good mouse and hope that the problem is solved.



#9 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:12:08 AM

Posted 11 January 2017 - 06:44 AM

I'm glad that you figured it out.

What caused you to suspect the mouse?

 

Anyhow, thanks for letting us know.

It'll help others who come looking for help with similar problems!


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.

#10 phixer

phixer
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:05:08 AM

Posted 16 January 2017 - 02:08 PM

The mouse was unplugging and plugging in back again by itself.



#11 shadow_647

shadow_647

  • Banned
  • 1,430 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:08 PM

Posted 16 January 2017 - 02:57 PM

 

 

I ran quick and extended test for hard drive with Western Digital Data LifeGuard Diagnostics for Windows and 5 passes with MemTest86+ for RAM. Then I did stress test for CPU with Prime95. 2 hours of Small FFTs with max. temperature 82°C and 7 hours of In-place large FTTs with max. temperature 84°C. I didn't do Blend, because I already checked RAM with MemTest. After that, I did stress test for GPU with FurMark on 1920x1080 and everything ticked in the settings, except dynamic camera, for 15 minutes. Average fps 36 and max. temperature 72°C. No errors or problems anywhere. Is the duration of the tests good? And are these temperatures ok? When I'm playing Overwatch my CPU is at roughly 62°C and GPU 61°C, so I don't think there is a problem.

 

 

 

Tests are good.  The temps aren't bad.  I wouldn't worry about them as a cause for the BSOD's though.

 

Sorry to point this out but max recomended temp for the cpu is 71c , so 84c is trash and im guessing stock intel cooler.

 

https://ark.intel.com/products/88184/Intel-Core-i5-6500-Processor-6M-Cache-up-to-3_60-GHz



#12 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:12:08 AM

Posted 20 January 2017 - 09:30 AM

I disagree with your interpretation of the Intel specifications, and additionally I have my practical experience over the last 10 years to back that up.

I submit this link to backup my position:  http://www.intel.com/content/www/us/en/support/processors/000005597.html

 

It is my opinion that the temp you cite is the temp (at the heat spreader) that's recommended for optimal system operation and long-term reliability.

High temps in a stress test may indicate a need for a better cooling solution - but they don't cause BSOD's (in my experience) until the heat gets well into the upper 90's (or even higher - it's different for each CPU).

Also, if the BSOD's are caused by heat, it's a simple matter to just run the stress test(s) and watch the BSOD occur at the same time/temp during the test

 

As I don't want to involve the original poster(s) in our disagreement, I shall refrain from posting in any topic which you have replied to.


Edited by usasma, 20 January 2017 - 09:34 AM.

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.

#13 phixer

phixer
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:05:08 AM

Posted 21 January 2017 - 07:48 AM

Well, it wasn't the cause of BSOD, but should I be worried about these temps or not? And yes, I do only have stock intel cooler.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users