Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › Several BSODs since last week
New Posts  All Forums:Forum Nav:

Several BSODs since last week

post #1 of 26
Thread Starter 

Since last week I have been experiencing 5 BSODs when playing games. They don't happen every time though. Sometimes the system crashed quickly after starting the game and sometimes only after longer periods. Other times I can play for hours without issues. Crashes occur in different games.

While writing this thread I had the system freeze for the first time. There was no error message or blue screen. The computer just froze on the desktop as I was opening Speccy to check my hardware info. I had no games running and so far this was the first crash outside of a game.

I have already run Memtest which found no errors and I have updated my video drivers but the problem persists. Also I did not find newer drivers for my mainboard than the ones I have already installed.

My system:

Windows 7 x64, desktop PC running a retail version of Windows which I installed myself (running without problems for about 18 months until the problems started last week).

· CPU: Intel Core i5 2500K @ 3.30GHz
· Video Card: 1280MB NVIDIA GeForce GTX 560 Ti (ZOTAC International)
· MotherBoard: ASRock P67 Pro3
· Power Supply: be quiet, 730W

I have added the required files, the jcgriff2 tool did not finish but was stuck repeatedly displaying the message "Waiting for SystemInfo" and nothing happens. Unfortunately, the Perfmon report appears to be in German but I hope it can still be of use to you. I have no idea why it says that no anti virus is installed because I'm using MS Security Essentials.

Windows7_Vista_jcgriff2.zip 2478k .zip file
report.zip 141k .zip file

If there is anything missing, I'd be happy to provide more details. I hope somebody can help me figure out the problem.

Thanks in advance!
post #2 of 26

All of the attached DMP files are of the DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) bugcheck and appear to be faulting tcpip.sys throughout the dump and on the call stacks.

tcpip.sys is the Microsoft TCP/IP Driver and is not the true cause of the crash, but likely another device driver is conflicting and causing it to fault. Usually, in *D1 cases, if we have a Microsoft system drive as the fault and it's networking related, it's being caused by a 3rd party antivirus or software conflicting with the NETBIOS ports, etc. However, as I said, it can be just device driver related in general.

I cannot read German, so I can't check for an antivirus, but through your modules list I can't seem to locate any antivirus related drivers. I do however see:
MtiCtwl fffff880`041f7000 fffff880`04200000 Tue Nov 04 02:40:50 2008 (490ffc82) 0000b926 MtiCtwl.sys

^^ MagicTunePremium or PortTalk Driver by Samsung Electronics, Inc or Beyond Logic. It's dated from 2008, and I would recommend checking for an update -




If no update is available, please uninstall this driver. I have a feeling this is possibly the culprit.


post #3 of 26
Thread Starter 
Thanks for your reply.

It's strange that you don't see any anti virus modules. Just to make sure I uninstalled and reinstalled MSSE today but perfmon still says that none is installed. In the windows control panel my anti virus is detected, however (where you see warnings if no anti virus or firewall is detected etc).

So I focussed on the other issue you mentioned. I couldn't find a newer version of Magic Tune Premium than the one I had before. Since I did not find any mention of it in the control panel I installed it again only to have my computer BSOD right after the required reboot. Following that I removed Magic Tune again but I guess the MtiCtwl.sys file will still be present. How do I remove it? As I said, I already removed Magic Tune but I'll have to manually deal with that file.

I have attached the minidump from today's BSOD. It was the first one I had on the windows desktop.
080713-6411-01.zip 26k .zip file
post #4 of 26
I guess the MtiCtwl.sys file will still be present. How do I remove it? As I said, I already removed Magic Tune but I'll have to manually deal with that file.

If the software itself is not installed, it will not hurt to do the following method. Just to be sure though, as always, let's make a system restore point:

Windows 7 - START | type create | select "Create a Restore Point"

After creating a restore point, navigate to %systemroot%\Windows\System32\Drivers, find MtiCtwl.sys and rename it to MtiCtwl.old, restart. Since it no longer has a .sys extension, it won't load. Since the software for the driver itself isn't installed, it won't break any programs and therefore is a harmless method of stopping a driver from loading.


post #5 of 26
Thread Starter 
Thanks for the instruction. That was very helpful. Now I'll have to wait and see if I still get BSODs.
post #6 of 26
Thread Starter 
Unfortunately, I had no luck. I had one more bluescreen while booting after renaming the driver and another one seconds after the desktop had loaded. Windows was still searching for a solution to the previous bluescreen. Another reboot later the systems is at least stable enough that I can post this but obviously something is still not right. I have attached both minidump files again.

Minidumps.zip 45k .zip file

I just remembered another issue I sometimes have. I don't know if it's related but occasionally the computer won't properly turn off when I shut it down. The screen goes dark as well as the connected USB devices but you can still hear the fans running and I don't think it's heat related.
I have had these issues long before the bluescreens started happening but they are happening very infrequently so I never paid much attention to them.
Edited by Kupferstecher - 8/7/13 at 3:35pm
post #7 of 26

I am still seeing *D1 tcpip.sys culprits, so I am going to recommend enabling Driver Verifier to see if we can catch any conflicting device drivers:

Driver Verifier:
What is Driver Verifier?
Driver Verifier is included in Windows 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 by flagging it and causing your system to BSOD.
Before enabling Driver Verifier, it is recommended to create a System Restore Point:
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
How to enable Driver Verifier:
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 NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.
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 36-48 hours. If you don't BSOD by then, disable Driver Verifier.
My system BSOD'd, where can I find the crash dumps?
They will be located in C:\Windows\Minidump
Any other questions can most likely be answered by this article:


post #8 of 26
Thread Starter 
I got a BSOD one hour after enabling Driver Verifier while I was browsing the web and had a game minimized in the background (hoping to force a BSOD - which worked). I have attached the minidump. Hopefully it provides more information this time.

080813-7519-01.zip 21k .zip file
post #9 of 26

It is a verifier enabled dump, however, it's failing to catch a device driver culprit. We are likely dealing with a hardware issue. Let's run a Memtest (run for no less than ~8 passes which is SEVERAL hours).

Download Memtest86+ here:


Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:



post #10 of 26
Thread Starter 
So far Memtest hasn't found any errors after 5 passes. I'll let it run some more tonight.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Crash Analysis and Debugging
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › Several BSODs since last week