BSOD Driver IRQL NOT LESS OR EQUAL tcpip.sys Windows 8 BSOD
I have had a BSOD issue a couple times before but those only happened once at a time and didnt really pose a problem. I have a HP Envy dv6 running on windows 8 and ive gotten this error twice already. Please help me!
Link to dump: https://skydrive.live.com/redir?resid=163610A1C0B75995!689&authkey=!AGz23KYRto8KVHw
This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.
The attached DMP files are of the DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) bugcheck.
A kernel-mode driver attempted to access pageable memory at a process IRQL (Interrupt Request Level) that was too high.
Usual causes are a device driver has a bug and attempted to access invalid memory, the pagefile has been corrupted or there is a memory problem.
tcpip.sys is labeled as the culprit in both of the dumps which is the Microsoft TCP/IP driver (networking related), however it is not the true cause as it's a system file and another device driver or form of hardware is faulting it.
Usually with network related BSOD's they are caused mostly by 3rd party antivirus of firewall conflicts, however as I said above, different device driver bugs / corruption and hardware are possible as well, just not as frequent.
Remove and replace AVG with Windows 8's built-in Windows Defender for temporary troubleshooting purposes:
In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.
If the above does not help, please enable Driver Verifier to look for further possible driver issues:
What is Driver Verifier?
Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode
components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.
Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.
Before enabling Driver Verifier, it is recommended to create a System Restore Point:
Start > type "verifier" without the quotes > Select the following options -
1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7)
- Concurrentcy Stress Test (Windows 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is [B]NOT[/B] provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
Important information regarding Driver Verifier:
- If Driver Verifier finds a violation, the system will BSOD.
- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause /
force a BSOD.
If this happens, do not panic, do the following:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > type "system restore" without the quotes.
- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:
- Start > Search > type "cmd" without the quotes.
- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・ Restart and boot into normal Windows.
How long should I keep Driver Verifier enabled for?
It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.
My system BSOD'd, where can I find the crash dumps?