BSOD- IRQL not less or equal

[bladejones]

This is my first time posting so not really sure if im doing it right but anyways my mothers computer started crashing a while back and i thought it was a virus but after multiple factory resets, the problem still persisted.

She would turn it on and about 10 seconds after it got to the desktop she would get the BSOD and it would go through multiple rounds of restarting and BSODs until it would finally stop and she could use the internet and then it would continue maybe a few hours later.

I'm not sure if she did anything to start the problem but she does like to download things without knowing what they are so i finally decided to just post the problem here. I dont really think there is a one stop solution so please forgive me if the problem has already been solved. Any help is greatly appreciated, thank you.

 

[koolkat77]

Hard Drive/Storage
Post disk summary using CrystalDiskInfo software - CrystalDiskInfo

:info: For how to upload a screenshot or file, read here

Make a Hard Drive test from the mfg website: Hard Drive Diagnostic Procedure

For errors on your Hard drive(s): Disk Check

Heat:
-Only use the laptop on a hard surface with nothing blocking any of the vents.
-Use a laptop cooling pad if possible
-Blow out all vents with canned air (DO NOT use a vacuum cleaner or an air compressor, they can damage the components).
-Ensure that the fan comes on and is blowing air out of the vent (may not happen at startup, but should happen after using it for a while).

System Temperature

Ensure that there are no heat issues, For monitoring heat of the system use Piriform - Speccy or Hardware Monitorhttp://www.cpuid.com/softwares/hwmonitor.html

Start up
Keep less stuff at the start-up. Only anti-virus, this helps avoid driver conflicts and improves time to log in to windows.

Performing a Clean Startup
Startup Programs - Change

Virus check
Scan your system with the following:

Kaspersky TDSSKiller - TDSSKiller Rootkit Removal Utility Free Download | Kaspersky Lab US

ESET online scanner - Online Virus Scanner Eset

Windows Defender Offline (optional)/in case above two show infection) - Run Windows Defender Offline

SFC /scannow

1. Click Start

2. In the search box, type Command Prompt
3. In the list that appears, right-click on cmd.exe and choose Run as administrator
4. In the command window that opens, type

sfc /scannow

5. Hit enter
System File Checker

Memtest86+
Run Memtest86+ for at least 8-10 passes. It may take up to 20 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.
:info: How to test and diagnose RAM issues with Memtest86+

   Note

Pay close attention to part 3 of the tutorial in order to rule the faulty RAM stick out.

   Tip

Do this test overnight.

BSOD BUGCHECK SUMMARY

[FONT="Lucida Console"]Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sun Jul  7 20:05:40.538 2013 (UTC + 6:00)
System Uptime: 0 days 0:10:34.707
BugCheck 1E, {ffffffffc0000005, fffffa80049f5bb0, 0, 7efa8000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48d2d )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sun Jul  7 19:53:02.937 2013 (UTC + 6:00)
System Uptime: 0 days 0:06:23.138
BugCheck 1E, {ffffffffc0000005, fffffa80049f9bb0, 0, fffa8000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48d2d )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  mscorsvw.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sun Jul  7 19:41:21.662 2013 (UTC + 6:00)
System Uptime: 0 days 0:05:16.847
BugCheck A, {760b7, 2, 1, fffff800030f8045}
Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+115 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sun Jul  7 19:35:28.309 2013 (UTC + 6:00)
System Uptime: 0 days 0:03:54.494
BugCheck A, {75837, 2, 1, fffff80003103045}
Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+115 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sun Jul  7 19:30:49.067 2013 (UTC + 6:00)
System Uptime: 0 days 0:05:06.252
BugCheck A, {de, 2, 1, fffff80003108045}
Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+115 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sun Jul  7 19:24:49.148 2013 (UTC + 6:00)
System Uptime: 0 days 0:05:38.349
BugCheck A, {40, 2, 1, fffff800030df2a8}
Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+28 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sun Jul  7 19:15:42.490 2013 (UTC + 6:00)
System Uptime: 0 days 11:07:30.675
BugCheck 1E, {ffffffffc0000005, fffff8000306e32f, 0, 7efa0000}
Probably caused by : ntkrnlmp.exe ( nt!RtlImageNtHeaderEx+3f )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Jul  6 17:53:54.651 2013 (UTC + 6:00)
System Uptime: 0 days 0:04:08.695
BugCheck 1E, {ffffffffc0000005, fffff8000306532f, 0, 7efa0000}
Probably caused by : ntkrnlmp.exe ( nt!RtlImageNtHeaderEx+3f )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Jul  6 17:49:11.490 2013 (UTC + 6:00)
System Uptime: 0 days 0:03:59.675
BugCheck 3B, {c0000005, fffff800030dac65, fffff88008f80880, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  WmiPrvSE.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Jul  6 17:44:09.052 2013 (UTC + 6:00)
System Uptime: 0 days 0:03:51.237
BugCheck A, {40, 2, 1, fffff8000308e2a8}
Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+28 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Jul  6 17:39:15.174 2013 (UTC + 6:00)
System Uptime: 0 days 0:03:11.359
BugCheck 1E, {ffffffffc0000005, fffff800030cd45b, 0, 3a0}
Probably caused by : ntkrnlmp.exe ( nt!output_l+31b )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Jul  6 17:35:00.754 2013 (UTC + 6:00)
System Uptime: 0 days 0:03:46.939
BugCheck A, {dd, 2, 1, fffff80003102045}
Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+115 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Jul  6 13:43:01.715 2013 (UTC + 6:00)
System Uptime: 0 days 0:04:25.885
BugCheck 1E, {ffffffffc0000096, fffff800031100ea, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+1ba )
BUGCHECK_STR:  0x1E_c0000096
PROCESS_NAME: NOT FOUND
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Jul  6 13:37:31.982 2013 (UTC + 6:00)
System Uptime: 0 days 0:03:46.167
BugCheck A, {104114268, 2, 1, fffff800030a44f0}
Probably caused by : tcpip.sys ( tcpip!TcpRemoveTcb+b7 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Jul  6 13:32:43.529 2013 (UTC + 6:00)
System Uptime: 0 days 0:13:58.714
BugCheck 9F, {3, fffffa80053dca00, fffff80000b9c518, fffffa8003886710}
Probably caused by : usbccgp.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Jul  6 13:18:10.199 2013 (UTC + 6:00)
System Uptime: 0 days 0:04:33.384
BugCheck 1E, {ffffffffc0000005, fffff800030b6045, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+115 )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Jul  6 13:12:33.994 2013 (UTC + 6:00)
System Uptime: 0 days 0:04:07.163
BugCheck A, {5800ee, 2, 1, fffff80003112045}
Probably caused by : fvevol.sys ( fvevol+153c )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Jul  6 13:07:50.200 2013 (UTC + 6:00)
System Uptime: 0 days 0:03:08.385
BugCheck 1E, {ffffffffc0000005, fffff800033d37da, 1, 18}
Probably caused by : ntkrnlmp.exe ( nt!ObpCreateHandle+29a )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  WLIDSVC.EXE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Jul  6 05:36:30.626 2013 (UTC + 6:00)
System Uptime: 0 days 0:03:37.826
BugCheck A, {0, 2, 0, fffff80003094052}
Probably caused by : ntkrnlmp.exe ( nt!KiSignalSynchronizationObject+42 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Jul  6 05:26:36.317 2013 (UTC + 6:00)
System Uptime: 0 days 0:03:21.361
BugCheck 1E, {ffffffffc0000005, fffff8000310a45b, 0, 2e0}
Probably caused by : ntkrnlmp.exe ( nt!output_l+31b )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Thu Jul  4 08:40:05.316 2013 (UTC + 6:00)
System Uptime: 0 days 0:03:58.501
BugCheck A, {dc, 2, 1, fffff800030af045}
Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+115 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Thu Jul  4 08:35:19.868 2013 (UTC + 6:00)
System Uptime: 0 days 0:08:01.053
BugCheck 1E, {ffffffffc0000005, fffff800030c232f, 0, 7efa0000}
Probably caused by : ntkrnlmp.exe ( nt!RtlImageNtHeaderEx+3f )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Mon Jul  1 18:23:32.726 2013 (UTC + 6:00)
System Uptime: 0 days 6:51:59.911
BugCheck 1E, {ffffffffc0000005, fffffa8004b49bb0, 0, 7efa8000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48d2d )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

 

[bladejones]

Heres the disk check. I used it in safe mode with networking if that matters because the computer wouldnt stay on with normal start up.

View attachment 275515

Also since i started using the safe mode with networking option it didnt BSOD on me every time but it did start to do it three times in a row when i started google chrome browser. Im currently in safe mode now on that computer with chrome up and it hasnt crashed yet so im not sure if that is relevant to the problem yet.

And i will start on the virus scans and memtest once i get a chance to to pull up the links on that computer.

 

[koolkat77]

Okay. Do perform HDD diagnostics and Keep us posted.

The caution indication can be converted to good using CrystalDiscInfo. Click on the caution Button, you will get another window ....

In the resulting window, there are three sliders in the left. Drag them to the ultimate left, and notice the values at the right side are converting to zeros.

Now click the apply button, and notice that the caution is gone.

After these, observe the situation that it is causing more BSODs or not.

 

[koolkat77]

Any updates?