Go Back   Tech Support Forum > Microsoft Support > BSOD, App Crashes And Hangs


BSOD irql_not_less_or_equal

This is a discussion on BSOD irql_not_less_or_equal within the BSOD, App Crashes And Hangs forums, part of the Tech Support Forum category. I have no idea whats causing these constant crashes. BSOD irql_not_less_or_equal, usually caused by ntoskrnl.exe. There are lots of different


Reply
 
Thread Tools Search this Thread
Old 06-16-2017, 08:43 AM   #1
Registered Member
 
Join Date: Jun 2017
Posts: 7
OS: Windows 10



I have no idea whats causing these constant crashes. BSOD irql_not_less_or_equal, usually caused by ntoskrnl.exe. There are lots of different crashes too. It all started after I made my new build and installed Windows 10. Driver verifier said it is caused by Logitech Gaming Software, but I have done everything and my computer still BSODs all the time, sometimes between 30minutes and long as 6hour periods.

I have Windows 10 and here is my DxDiag and latest BSOD and some older dumps:
https://www.mediafire.com/?h6zawz6vxkoes9y
Zanttu is offline   Reply With Quote
Sponsored Links
Advertisement
 
Old 06-17-2017, 12:51 PM   #2
Team Manager, Microsoft Support
BSOD Kernel Dump Expert
 
jcgriff2's Avatar
 
Join Date: Sep 2007
Location: New Jersey Shore
Posts: 33,373
OS: Windows 10, 8.1, 7 + Windbg :)



Please be sure to run --> Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 & Vista

Attach the output to your next post in this thread.

Regards. . .

jcgriff2

`
jcgriff2 is offline   Reply With Quote
Old 06-18-2017, 06:02 AM   #3
Registered Member
 
Join Date: Jun 2017
Posts: 7
OS: Windows 10



Quote:
Originally Posted by jcgriff2 View Post
Please be sure to run --> Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 & Vista

Attach the output to your next post in this thread.

Regards. . .

jcgriff2

`
Here are the reports.

ps. I have disabled Logitech Gaming Virtual Mouse myself.
Attached Files
File Type: zip Perfmon.zip (161.7 KB, 4 views)
File Type: zip SysnativeFileCollectionApp.zip (1.57 MB, 4 views)
Zanttu is offline   Reply With Quote
Old 06-18-2017, 06:04 AM   #4
Registered Member
 
Join Date: Jun 2017
Posts: 7
OS: Windows 10



Sorry, I'm not sure if my reply came to you. I'm still bit new to this forum.
Zanttu is offline   Reply With Quote
Old 06-19-2017, 10:35 AM   #5
Team Manager, Microsoft Support
BSOD Kernel Dump Expert
 
jcgriff2's Avatar
 
Join Date: Sep 2007
Location: New Jersey Shore
Posts: 33,373
OS: Windows 10, 8.1, 7 + Windbg :)



Hi. . .

Your reply was fine.

The 5 dumps had 4 different bugchecks (STOP error codes) and all 5 named Microsoft Windows drivers as the probable cause. These Microsoft drivers are not the cause; rather just defaults. This means that we are dealing with unknown hardware failure as the cause.

Unfortunately, the dumps are incapable of telling us which piece of hardware has failed. Dumps are only good for figuring out software problems.

All I can really do here is to give you some hardware diagnostic programs to run.
The problem may also be with other hardware parts such as the motherboard or PSU for which there are no software tests.

If you are encountering a specific hardware issue, feel free to post in our Hardware Forum - Motherboards, Bios & CPU

Regards. . .

jcgriff2

`

Code:

Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061717-38734-01.dmp]
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Debug session time: Sat Jun 17 04:52:37.272 2017 (UTC - 4:00)
System Uptime: 0 days 10:31:33.883
BugCheck F7, {d8daa4bb9d46, d8daae570106, ffff272551a8fef9, 0}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0xF7
PROCESS_NAME:  nvcontainer.ex
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE
Bugcheck code 000000F7
Arguments 0000d8da`a4bb9d46 0000d8da`ae570106 ffff2725`51a8fef9 00000000`00000000
BiosVersion = P2.80
BiosReleaseDate = 05/31/2016
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061717-45843-01.dmp]
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Debug session time: Sat Jun 17 05:20:12.952 2017 (UTC - 4:00)
System Uptime: 0 days 0:26:45.649
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000005_R
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  TiWorker.exe
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff803`58deeef7 00000000`00000000 ffffffff`ffffffff
BiosVersion = P2.80
BiosReleaseDate = 05/31/2016
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061817-32531-01.dmp]
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Debug session time: Sat Jun 17 16:02:27.484 2017 (UTC - 4:00)
System Uptime: 0 days 6:30:48.041
BugCheck F7, {427ee3f5bb01, d45d5e6bf45, fffff2ba2a1940ba, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0xF7
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BYTE
Bugcheck code 000000F7
Arguments 0000427e`e3f5bb01 00000d45`d5e6bf45 fffff2ba`2a1940ba 00000000`00000000
BiosVersion = P2.80
BiosReleaseDate = 05/31/2016
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061817-47484-01.dmp]
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Debug session time: Sun Jun 18 08:40:06.932 2017 (UTC - 4:00)
System Uptime: 0 days 0:48:15.629
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x139
PROCESS_NAME:  Spotify.exe
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BYTE
Bugcheck code 00000139
Arguments 00000000`00000003 ffffd680`d44be670 ffffd680`d44be5c8 00000000`00000000
BiosVersion = P2.80
BiosReleaseDate = 05/31/2016
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061717-34484-01.dmp]
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Debug session time: Sat Jun 17 09:30:56.320 2017 (UTC - 4:00)
System Uptime: 0 days 0:40:35.018
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  AV
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_STRIDE
Bugcheck code 0000000A
Arguments 00000000`b7d10000 00000000`00000002 00000000`00000000 fffff803`d4258bbd
BiosVersion = P2.80
BiosReleaseDate = 05/31/2016
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
  
jcgriff2 is offline   Reply With Quote
Old 06-19-2017, 11:07 AM   #6
Registered Member
 
Join Date: Jun 2017
Posts: 7
OS: Windows 10


Quote:
Originally Posted by jcgriff2 View Post
Hi. . .

Your reply was fine.

The 5 dumps had 4 different bugchecks (STOP error codes) and all 5 named Microsoft Windows drivers as the probable cause. These Microsoft drivers are not the cause; rather just defaults. This means that we are dealing with unknown hardware failure as the cause.

Unfortunately, the dumps are incapable of telling us which piece of hardware has failed. Dumps are only good for figuring out software problems.

All I can really do here is to give you some hardware diagnostic programs to run.
The problem may also be with other hardware parts such as the motherboard or PSU for which there are no software tests.

If you are encountering a specific hardware issue, feel free to post in our Hardware Forum - Motherboards, Bios & CPU

Regards. . .

jcgriff2

`

Code:
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061717-38734-01.dmp]
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Debug session time: Sat Jun 17 04:52:37.272 2017 (UTC - 4:00)
System Uptime: 0 days 10:31:33.883
BugCheck F7, {d8daa4bb9d46, d8daae570106, ffff272551a8fef9, 0}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0xF7
PROCESS_NAME:  nvcontainer.ex
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE
Bugcheck code 000000F7
Arguments 0000d8da`a4bb9d46 0000d8da`ae570106 ffff2725`51a8fef9 00000000`00000000
BiosVersion = P2.80
BiosReleaseDate = 05/31/2016
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061717-45843-01.dmp]
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Debug session time: Sat Jun 17 05:20:12.952 2017 (UTC - 4:00)
System Uptime: 0 days 0:26:45.649
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000005_R
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  TiWorker.exe
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff803`58deeef7 00000000`00000000 ffffffff`ffffffff
BiosVersion = P2.80
BiosReleaseDate = 05/31/2016
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061817-32531-01.dmp]
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Debug session time: Sat Jun 17 16:02:27.484 2017 (UTC - 4:00)
System Uptime: 0 days 6:30:48.041
BugCheck F7, {427ee3f5bb01, d45d5e6bf45, fffff2ba2a1940ba, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0xF7
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BYTE
Bugcheck code 000000F7
Arguments 0000427e`e3f5bb01 00000d45`d5e6bf45 fffff2ba`2a1940ba 00000000`00000000
BiosVersion = P2.80
BiosReleaseDate = 05/31/2016
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061817-47484-01.dmp]
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Debug session time: Sun Jun 18 08:40:06.932 2017 (UTC - 4:00)
System Uptime: 0 days 0:48:15.629
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x139
PROCESS_NAME:  Spotify.exe
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BYTE
Bugcheck code 00000139
Arguments 00000000`00000003 ffffd680`d44be670 ffffd680`d44be5c8 00000000`00000000
BiosVersion = P2.80
BiosReleaseDate = 05/31/2016
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061717-34484-01.dmp]
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Debug session time: Sat Jun 17 09:30:56.320 2017 (UTC - 4:00)
System Uptime: 0 days 0:40:35.018
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  AV
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_STRIDE
Bugcheck code 0000000A
Arguments 00000000`b7d10000 00000000`00000002 00000000`00000000 fffff803`d4258bbd
BiosVersion = P2.80
BiosReleaseDate = 05/31/2016
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Okay, thanks a lot for helping me! I really appreciate it. I uninstalled and installed the logitech mouse many times yesterday and I think I found out a workaround rather than a real solution. Note: I need LGS in my daily computer usage. I can't and wont use my mouse without it.

I tried to install old versions of Logitech Gaming Software (lgs) but they wouldn't let me install. I got an error message every time. Then I downloaded 64bit version of the current lgs. I think the automated start at launch caused the lgs bluescreen, so I disabled it. Then I launched the software manually snd got a bluescreen telling me that "interrupt exception not handled". After that I re-installed the software.

After re-installing the software, I downloaded AMDs latest chipset and ran SFC /scannow. SFC didn't find anything and after restarting I haven't gotten any Bluescreens. It's pretty odd if the LGS was causing these bluescreens since I have gotten BSODs in safemode and after uninstalling the software many times before. Only time will tell.

I will update if I still get BSODs
Zanttu is offline   Reply With Quote
Old Yesterday, 07:23 PM   #7
Team Manager, Microsoft Support
BSOD Kernel Dump Expert
 
jcgriff2's Avatar
 
Join Date: Sep 2007
Location: New Jersey Shore
Posts: 33,373
OS: Windows 10, 8.1, 7 + Windbg :)



OK... sounds like a plan.

It could be that the Logitech software/driver is not compatible with your version of Windows.

Regards. . .

jcgriff2

`
jcgriff2 is offline   Reply With Quote
Old Yesterday, 07:42 PM   #8
Registered Member
 
Join Date: Jun 2017
Posts: 7
OS: Windows 10


Hmm, I still get bluescreens, even while iv been trying to live without the software. I have uninstalled it. The BSODs are less frequent but they still occur.
Zanttu is offline   Reply With Quote
Old Today, 01:01 PM   #9
Team Manager, Microsoft Support
BSOD Kernel Dump Expert
 
jcgriff2's Avatar
 
Join Date: Sep 2007
Location: New Jersey Shore
Posts: 33,373
OS: Windows 10, 8.1, 7 + Windbg :)



Did you run the hardware diag tests?

Your BSODs seem to be related to unknown hardware failure.
jcgriff2 is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] BSOD BSOD Everywhere. Geforce GTX570
Hey Guys и Windows 7 и 64 bit и Windows 7и Not preinstalled и 2 year old system и OS installed 6 months ago? и Intel Core i5-2500k CPu @3.30ghz и Gigabyte Geforce GTX570
wiseh BSOD, App Crashes And Hangs 12 07-17-2013 05:28 PM
GenuineIntel BSOD
Hello, I've been scouring through dumpfiles trying to diagnose the bsod I've been getting ever since installing my new graphics card (Sapphire 7970 Vapor-x) and was hoping somebody else would have a better idea about it than me. To begin with, when I first installed the card, I was getting a...
Stumpedify BSOD, App Crashes And Hangs 23 06-21-2013 10:33 PM
BSOD after installing graphicscard drivers
Hi, After an evening and a day wasted googling for the solution, i give up and hope you guys can help me. I'm getting an BSOD 116 igdkmd64.sys after i try to update my ATI graphics card driver. now the problem is that everytime i update the drivers, they install and a reboot gets...
FreekNL BSOD, App Crashes And Hangs 6 01-16-2012 08:23 AM
BSOD and a System Upgrade question (Moved from MS Support)
Yesterday I had 1 bsod and then also a screen freeze with me doing a hard restart. This happened during the time I was changing my drivers for 4870. I'm assuming the bsod was caused because of the driver change. Since then it seems to be running fine, with no more freezes or bsod. Now i just...
nickskip Motherboards, Bios & CPU 2 05-05-2011 05:52 AM
BSOD, very random
Hi Im having BSOD problems, of course. I got a BSOD a couple weeks ago, restarted, and it worked fine, i didnt pay it much attention since I very very very rarely get them, and it was fine afterwards last night while playing a game, it BSOD'd again, i restarted, and immediately after logging...
player2 BSOD, App Crashes And Hangs 1 02-28-2011 12:44 AM

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is on
Smilies are on
[IMG] code is on
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Post a Question


» Site Navigation
 > FAQ
  > 10.0.0.2


All times are GMT -7. The time now is 06:56 PM.


vBulletin Security provided by vBSecurity v2.2.2 (Pro) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
Copyright 2001 - 2015, Tech Support Forum

Windows 7 - Windows XP - Windows Vista - Trojan Removal - Spyware Removal - Virus Removal - Networking - Security - Top Web Hosts

 

Partially Powered By Products Found At Lampwrights.com