Tech Support banner

Status
Not open for further replies.
1 - 20 of 26 Posts

·
Registered
Joined
·
15 Posts
Discussion Starter #1 (Edited)
I've been having a lot of BSODs recently after upgraded my hardware.

After I upgraded to my new hardware I have been getting a lot of BSODs almost at random from the feel of it, latest one was today and the error message was "IRQL_NOT_LESS_OR_EQUAL".
I already had set up a minidump file in case of them continuing after I tried updating drivers, did the chkdsk command to check all my drives, checked for corrupt system files.
I will leave the minidump and hopefully someone could help me figure this out, thanks!

Any extra info needed just ask me

View attachment 030319-8093-01.rar
 

·
Registered
Joined
·
15 Posts
Discussion Starter #3
After I upgraded to my new hardware I have been getting a lot of BSODs almost at random from the feel of it, latest one was today and the error message was "IRQL_NOT_LESS_OR_EQUAL".
It also for some reason makes me incapable of playing most modern resource intensive games, I just bought AC Odyssey and was playing and it BSODs a lot with it and it also sometimes just crashes the game but not the PC.

-OS: Windows 10 Home
-X64
-There was no original OS
-Full Retail Version
-Age of Hardware is less than 3 years.
-OS installation happened recently around a couple weeks.
-I have reinstalled it a few times to check for if the issue was with my installation.

-AMD FX-8320E Eight-Core Processor
-NVIDIA GTX 1060 6GB.
-ASRock 970A-G/3.1
-Jaguar 750W Eagle Warrior PS2

-Desktop



View attachment SysnativeFileCollectionApp.zip
 

·
Administrator, Team Manager, Gaming, Team Manager,
Joined
·
54,076 Posts
All 3 dmps in the upload were attributed to Memory Corruption

Run Memtest86> https://www.techsupportforum.com/21777-how-to-perform-a-memtest86-test-2/

…………………………………………………………………………………………………………………………………………………………………………………………………………………………




Code:
Debug session time: Sun Mar  3 15:51:39.135 2019 (UTC - 5:00)
Loading Dump File [C:\BSOD APP\SysnativeBSODApps\030319-10125-01.dmp]
System Uptime: 0 days 0:09:21.922
Probably caused by : memory_corruption
BugCheck A, {26, 2, 1, fffff8017ae6ade5}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000000A]IRQL_NOT_LESS_OR_EQUAL (a)[/url]
Bugcheck code 0000000A
Arguments: 
Arg1: 0000000000000026, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff8017ae6ade5, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  ACOdyssey.exe
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Mar  3 14:48:07.154 2019 (UTC - 5:00)
Loading Dump File [C:\BSOD APP\SysnativeBSODApps\030319-8406-01.dmp]
System Uptime: 0 days 0:51:06.940
*** WARNING: Unable to verify timestamp for PSINKNC.sys
*** ERROR: Module load completed but symbols could not be loaded for PSINKNC.sys
*** WARNING: Unable to verify timestamp for NNSTLSC.sys
*** ERROR: Module load completed but symbols could not be loaded for NNSTLSC.sys
Probably caused by : PSINKNC.sys ( PSINKNC+222ed )
BugCheck A, {68, 2, 1, fffff80056113eec}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000000A]IRQL_NOT_LESS_OR_EQUAL (a)[/url]
Bugcheck code 0000000A
Arguments: 
Arg1: 0000000000000068, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80056113eec, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  AV_PSINKNC!unknown_function
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Mar  3 13:56:18.939 2019 (UTC - 5:00)
Loading Dump File [C:\BSOD APP\SysnativeBSODApps\030319-8093-01.dmp]
System Uptime: 0 days 15:38:45.728
*** WARNING: Unable to verify timestamp for NNSNAHSL.sys
*** ERROR: Module load completed but symbols could not be loaded for NNSNAHSL.sys
Probably caused by : memory_corruption
BugCheck A, {ffff88040a24e231, ff, 53, fffff80229647a04}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000000A]IRQL_NOT_LESS_OR_EQUAL (a)[/url]
Bugcheck code 0000000A
Arguments: 
Arg1: ffff88040a24e231, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000053, 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: fffff80229647a04, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

*** 3rd PARTY DRIVER LIST ***
*** 3rd PARTY DRIVER LIST ***



Code:
NNSALPC.sys                 Fri Dec 14 04:57:30 2018 (5C137E8A)
NNSDNS.sys                  Fri Dec 14 07:24:27 2018 (5C13A0FB)
NNSHTTP.sys                 Fri Dec 14 05:29:27 2018 (5C138607)
NNSHTTPS.sys                Fri Dec 14 06:58:38 2018 (5C139AEE)
NNSIDS.sys                  Fri Dec 14 06:27:52 2018 (5C1393B8)
NNSNAHSL.sys                Fri Jul  6 09:13:22 2018 (5B3F6AF2)
NNSPICC.sys                 Fri Dec 14 05:31:19 2018 (5C138677)
NNSPIHSW.sys                Fri Dec 14 06:55:00 2018 (5C139A14)
NNSPOP3.sys                 Fri Dec 14 06:32:27 2018 (5C1394CB)
NNSPROT.sys                 Fri Dec 14 06:22:38 2018 (5C13927E)
NNSPRV.sys                  Fri Dec 14 03:36:38 2018 (5C136B96)
NNSSMTP.sys                 Fri Dec 14 06:38:33 2018 (5C139639)
NNSSTRM.sys                 Fri Dec 14 05:04:13 2018 (5C13801D)
NNSTLSC.sys                 Fri Dec 14 04:59:37 2018 (5C137F09)
PSINAflt.sys                Sun Jan 13 11:47:54 2019 (5C3B6BBA)
PSINFile.sys                Sun Jan 13 11:51:49 2019 (5C3B6CA5)
PSINKNC.sys                 Thu Dec 13 09:13:24 2018 (5C126904)
PSINProc.sys                Sun Jan 13 11:56:30 2019 (5C3B6DBE)
PSINProt.sys                Sun Jan 13 11:58:56 2019 (5C3B6E50)
PSINReg.sys                 Tue Dec 18 18:55:44 2018 (5C198900)
PSKMAD.sys                  Mon May 22 03:15:48 2017 (59229024)
RTKVHD64.sys                Tue Feb 19 06:13:51 2019 (5C6BE4EF)
SgrmAgent.sys               Thu Feb  2 09:30:36 2012 (4F2A9E0C)
aftap0901.sys               Mon Nov  6 17:06:57 2017 (5A00DD01)
afunix.sys                  Tue Apr 18 10:12:59 2017 (58F61EEB)
amd_sata.sys                Thu Mar 19 02:43:08 2015 (550A6FFC)
amd_xata.sys                Thu Mar 19 02:43:10 2015 (550A6FFE)
amdide64.sys                Tue Dec  4 04:49:28 2012 (50BDC728)
asmthub3.sys                Thu Oct 25 04:32:41 2018 (5BD17FA9)
asmtxhci.sys                Thu Oct 25 04:32:18 2018 (5BD17F92)
nvhda64v.sys                Wed Jan 16 01:44:16 2019 (5C3ED2C0)
nvlddmkm.sys                Wed Feb 20 06:11:44 2019 (5C6D35F0)
nvvad64v.sys                Wed Aug 22 05:44:24 2018 (5B7D3078)
panda_url_filteringd.sys    Wed Mar 19 16:23:04 2014 (5329FCA8)
rt640x64.sys                Wed Dec  5 21:27:39 2018 (5C08891B)
 

·
Registered
Joined
·
15 Posts
Discussion Starter #6
All 3 dmps in the upload were attributed to Memory Corruption

Run Memtest86> https://www.techsupportforum.com/21777-how-to-perform-a-memtest86-test-2/

…………………………………………………………………………………………………………………………………………………………………………………………………………………………




Code:
Debug session time: Sun Mar  3 15:51:39.135 2019 (UTC - 5:00)
Loading Dump File [C:\BSOD APP\SysnativeBSODApps\030319-10125-01.dmp]
System Uptime: 0 days 0:09:21.922
Probably caused by : memory_corruption
BugCheck A, {26, 2, 1, fffff8017ae6ade5}
BugCheck Info: [URL="https://www.carrona.org/bsodindx.html#0x0000000A"]IRQL_NOT_LESS_OR_EQUAL (a)[/URL]
Bugcheck code 0000000A
Arguments: 
Arg1: 0000000000000026, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff8017ae6ade5, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  ACOdyssey.exe
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Mar  3 14:48:07.154 2019 (UTC - 5:00)
Loading Dump File [C:\BSOD APP\SysnativeBSODApps\030319-8406-01.dmp]
System Uptime: 0 days 0:51:06.940
*** WARNING: Unable to verify timestamp for PSINKNC.sys
*** ERROR: Module load completed but symbols could not be loaded for PSINKNC.sys
*** WARNING: Unable to verify timestamp for NNSTLSC.sys
*** ERROR: Module load completed but symbols could not be loaded for NNSTLSC.sys
Probably caused by : PSINKNC.sys ( PSINKNC+222ed )
BugCheck A, {68, 2, 1, fffff80056113eec}
BugCheck Info: [URL="https://www.carrona.org/bsodindx.html#0x0000000A"]IRQL_NOT_LESS_OR_EQUAL (a)[/URL]
Bugcheck code 0000000A
Arguments: 
Arg1: 0000000000000068, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80056113eec, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  AV_PSINKNC!unknown_function
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Mar  3 13:56:18.939 2019 (UTC - 5:00)
Loading Dump File [C:\BSOD APP\SysnativeBSODApps\030319-8093-01.dmp]
System Uptime: 0 days 15:38:45.728
*** WARNING: Unable to verify timestamp for NNSNAHSL.sys
*** ERROR: Module load completed but symbols could not be loaded for NNSNAHSL.sys
Probably caused by : memory_corruption
BugCheck A, {ffff88040a24e231, ff, 53, fffff80229647a04}
BugCheck Info: [URL="https://www.carrona.org/bsodindx.html#0x0000000A"]IRQL_NOT_LESS_OR_EQUAL (a)[/URL]
Bugcheck code 0000000A
Arguments: 
Arg1: ffff88040a24e231, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000053, 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: fffff80229647a04, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** 3rd PARTY DRIVER LIST ***
*** 3rd PARTY DRIVER LIST ***



Code:
NNSALPC.sys                 Fri Dec 14 04:57:30 2018 (5C137E8A)
NNSDNS.sys                  Fri Dec 14 07:24:27 2018 (5C13A0FB)
NNSHTTP.sys                 Fri Dec 14 05:29:27 2018 (5C138607)
NNSHTTPS.sys                Fri Dec 14 06:58:38 2018 (5C139AEE)
NNSIDS.sys                  Fri Dec 14 06:27:52 2018 (5C1393B8)
NNSNAHSL.sys                Fri Jul  6 09:13:22 2018 (5B3F6AF2)
NNSPICC.sys                 Fri Dec 14 05:31:19 2018 (5C138677)
NNSPIHSW.sys                Fri Dec 14 06:55:00 2018 (5C139A14)
NNSPOP3.sys                 Fri Dec 14 06:32:27 2018 (5C1394CB)
NNSPROT.sys                 Fri Dec 14 06:22:38 2018 (5C13927E)
NNSPRV.sys                  Fri Dec 14 03:36:38 2018 (5C136B96)
NNSSMTP.sys                 Fri Dec 14 06:38:33 2018 (5C139639)
NNSSTRM.sys                 Fri Dec 14 05:04:13 2018 (5C13801D)
NNSTLSC.sys                 Fri Dec 14 04:59:37 2018 (5C137F09)
PSINAflt.sys                Sun Jan 13 11:47:54 2019 (5C3B6BBA)
PSINFile.sys                Sun Jan 13 11:51:49 2019 (5C3B6CA5)
PSINKNC.sys                 Thu Dec 13 09:13:24 2018 (5C126904)
PSINProc.sys                Sun Jan 13 11:56:30 2019 (5C3B6DBE)
PSINProt.sys                Sun Jan 13 11:58:56 2019 (5C3B6E50)
PSINReg.sys                 Tue Dec 18 18:55:44 2018 (5C198900)
PSKMAD.sys                  Mon May 22 03:15:48 2017 (59229024)
RTKVHD64.sys                Tue Feb 19 06:13:51 2019 (5C6BE4EF)
SgrmAgent.sys               Thu Feb  2 09:30:36 2012 (4F2A9E0C)
aftap0901.sys               Mon Nov  6 17:06:57 2017 (5A00DD01)
afunix.sys                  Tue Apr 18 10:12:59 2017 (58F61EEB)
amd_sata.sys                Thu Mar 19 02:43:08 2015 (550A6FFC)
amd_xata.sys                Thu Mar 19 02:43:10 2015 (550A6FFE)
amdide64.sys                Tue Dec  4 04:49:28 2012 (50BDC728)
asmthub3.sys                Thu Oct 25 04:32:41 2018 (5BD17FA9)
asmtxhci.sys                Thu Oct 25 04:32:18 2018 (5BD17F92)
nvhda64v.sys                Wed Jan 16 01:44:16 2019 (5C3ED2C0)
nvlddmkm.sys                Wed Feb 20 06:11:44 2019 (5C6D35F0)
nvvad64v.sys                Wed Aug 22 05:44:24 2018 (5B7D3078)
panda_url_filteringd.sys    Wed Mar 19 16:23:04 2014 (5329FCA8)
rt640x64.sys                Wed Dec  5 21:27:39 2018 (5C08891B)

I ran the memory test and it dected no errors, it only did this [NOTE] RAM may be vulunerable to high frequency row hammer bot flips.


But appart from that it didn't mark any issues I ran the test with 1 core as it had by default
 

·
Registered
Joined
·
15 Posts
Discussion Starter #8
Try removing Panda Security and using the free Microsoft Windows Defender to see if the errors stop

I tried doing that, it didn't help it still Blue Screened again, honestly at this point I am very much ready to give up on this hardware and go back to what I used to have, I have been struggling with this issue for 2 months now with no end in sight.
 

·
Administrator, Manager, Microsoft Support, Acting
Joined
·
34,370 Posts
Hi. . .

Removing Panda Internet Security per wrench97's recommendation should have helped to some degree as 2 of the dumps actually named Panda Internet Security as the probable cause of the BSODs.

Make sure to use the Panda Internet Security Removal Tool - https://support.eset.com/kb146/#p - to assure that all boot drivers and kernel mode drivers have been removed from your system. A regular uninstall via Control Panel often misses these drivers and they continue to load into RAM and cause problems.

Please be sure to fully answer wrench97's questions as he is the undisputed hardware expert here. I sit on the software side of the fence.

Regards. . .

jcgriff2

p.s. Please upload any new BSOD dumps. Go to \windows\minidump, copy out the new dump(s) (file name = date) to Documents or Desktop; zip it/them up and attach to your next post. You cannot zip in the \windows directory.

`
 

·
Administrator, Team Manager, Gaming, Team Manager,
Joined
·
54,076 Posts
Also lets get a look at the temps and voltages.
Use the free program Hardware Monitor from CPUz > https://www.cpuid.com/softwares/hwmonitor.html

Run HWM and do some gaming Atl/Tab back to HWM and grab a screen shot using the snipping tool, upload the screen shot as a attachment in the Advanced reply box.
 

·
Registered
Joined
·
15 Posts
Discussion Starter #13
Hi. . .

Removing Panda Internet Security per wrench97's recommendation should have helped to some degree as 2 of the dumps actually named Panda Internet Security as the probable cause of the BSODs.

Make sure to use the Panda Internet Security Removal Tool - https://support.eset.com/kb146/#p - to assure that all boot drivers and kernel mode drivers have been removed from your system. A regular uninstall via Control Panel often misses these drivers and they continue to load into RAM and cause problems.

Please be sure to fully answer wrench97's questions as he is the undisputed hardware expert here. I sit on the software side of the fence.

Regards. . .

jcgriff2

p.s. Please upload any new BSOD dumps. Go to \windows\minidump, copy out the new dump(s) (file name = date) to Documents or Desktop; zip it/them up and attach to your next post. You cannot zip in the \windows directory.

`

I just had a blue screen again.
Here is the Minidump file zipped
View attachment 030519-8109-01.zip
 

·
Registered
Joined
·
15 Posts
Discussion Starter #14

·
Administrator, Team Manager, Gaming, Team Manager,
Joined
·
54,076 Posts
CPU seems a little warm, I'd like to see internal core temps that HWM is not showing try HWiNFO> https://www.hwinfo.com/ or Core Temp > https://www.alcpu.com/CoreTemp/

The 8320 e should not be running over 70c it'll start throttling speeds back around 75c and shut down at 81c
 

·
Registered
Joined
·
15 Posts
Discussion Starter #17

·
Administrator, Team Manager, Gaming, Team Manager,
Joined
·
54,076 Posts
The cores appear to be ok temp wise but the motherboard CPU temp sensor (CPUIN in the HWM report CPU under the motherboard category in the HWiNFO report) is reporting rather high it may just be a erroneous reading. What cooler are you using the stock AMD cooler or a different unit?
 

·
Registered
Joined
·
15 Posts
Discussion Starter #19
The cores appear to be ok temp wise but the motherboard CPU temp sensor (CPUIN in the HWM report CPU under the motherboard category in the HWiNFO report) is reporting rather high it may just be a erroneous reading. What cooler are you using the stock AMD cooler or a different unit?

I am using the stock factory issue cooler that came with it, I am considering a new one or to buy a liquid cooling unit.
 
1 - 20 of 26 Posts
Status
Not open for further replies.
Top