Hello, so this problem has been happening for a very long time and im just now getting around to it. My computer randomly BSODS or freezes while im watching twitch.tv streams or playing certaint games, sometimes just browsing. The BSOD isnt always the same but the most common one is driver_iqrl_not_less_or_equal. I will be including the most recent minidump file soon, Thanks
Navigation
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
More options
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
BSOD: driver_iqrl_not_less_or_equal while watching streams or playing video games
- Thread starter Sergent
- Start date
Hi,
Please refer to the following and reply back here accordingly - https://www.sysnative.com/forums/bs...structions-windows-8-7-and-windows-vista.html
Regards,
Patrick
Please refer to the following and reply back here accordingly - https://www.sysnative.com/forums/bs...structions-windows-8-7-and-windows-vista.html
Regards,
Patrick
Thanks!
We have various attached bug checks from the DMP's:
INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
This bug check appears very infrequently. It's usually only associated / shows up with hardware issues.
IRQL_NOT_LESS_OR_EQUAL (a)
This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high. The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This indicates that a system thread generated an exception which the error handler did not catch.
DEFAULT_BUCKET_ID: STATUS_PRIVILEGED_INSTRUCTION
^^ Executing an instruction not allowed in current machine mode.
KMODE_EXCEPTION_NOT_HANDLED (1e)
This indicates that a kernel-mode program generated an exception which the error handler did not catch.
Probably caused by : hardware
------------------------
With all of this said, this is more than likely at first glance a hardware issue. Let's start off with a Memtest for NO LESS than ~8 passes (several hours). If it goes at least 8 without errors, let's move onto chkdsk and then Seatools for hard disk testing:
Memtest86+:
Download Memtest86+ here:
Memtest86+ - Advanced Memory Diagnostic Tool
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:
FAQ : please read before posting
-------------------------------------------------------------------------------------------------------------
Chkdsk:
Chkdsk:
There are various ways to run Chkdsk~
Method 1:
Start > Search bar > Type cmd (right click run as admin to execute Elevated CMD)
Elevated CMD should now be opened, type the following:
chkdsk x: /r
x implies your drive letter, so if your hard drive in question is letter c, it would be:
chkdsk c: /r
Restart system and let chkdsk run.
Method 2:
Open the "Computer" window
Right-click on the drive in question
Select the "Tools" tab
In the Error-checking area, click <Check Now>.
If you'd like to get a log file that contains the chkdsk results, do the following:
Press Windows Key + R and type powershell.exe in the run box
Paste the following command and press enter afterwards:
get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt
This will output a .txt file on your Desktop containing the results of the chkdsk.
If chkdsk turns out okay, run Seatools -
SeaTools | Seagate
You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be device driver related issues that may cause conflicts or false positive, it may be a wise decision to choose the most minimal testing environment (DOS).
Run all tests EXCEPT: Fix All, Long Generic, and anything Advanced.
Regards,
Patrick
We have various attached bug checks from the DMP's:
INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
This bug check appears very infrequently. It's usually only associated / shows up with hardware issues.
IRQL_NOT_LESS_OR_EQUAL (a)
This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high. The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This indicates that a system thread generated an exception which the error handler did not catch.
DEFAULT_BUCKET_ID: STATUS_PRIVILEGED_INSTRUCTION
^^ Executing an instruction not allowed in current machine mode.
KMODE_EXCEPTION_NOT_HANDLED (1e)
This indicates that a kernel-mode program generated an exception which the error handler did not catch.
Probably caused by : hardware
------------------------
With all of this said, this is more than likely at first glance a hardware issue. Let's start off with a Memtest for NO LESS than ~8 passes (several hours). If it goes at least 8 without errors, let's move onto chkdsk and then Seatools for hard disk testing:
Memtest86+:
Download Memtest86+ here:
Memtest86+ - Advanced Memory Diagnostic Tool
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:
FAQ : please read before posting
-------------------------------------------------------------------------------------------------------------
Chkdsk:
Chkdsk:
There are various ways to run Chkdsk~
Method 1:
Start > Search bar > Type cmd (right click run as admin to execute Elevated CMD)
Elevated CMD should now be opened, type the following:
chkdsk x: /r
x implies your drive letter, so if your hard drive in question is letter c, it would be:
chkdsk c: /r
Restart system and let chkdsk run.
Method 2:
Open the "Computer" window
Right-click on the drive in question
Select the "Tools" tab
In the Error-checking area, click <Check Now>.
If you'd like to get a log file that contains the chkdsk results, do the following:
Press Windows Key + R and type powershell.exe in the run box
Paste the following command and press enter afterwards:
get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt
This will output a .txt file on your Desktop containing the results of the chkdsk.
If chkdsk turns out okay, run Seatools -
SeaTools | Seagate
You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be device driver related issues that may cause conflicts or false positive, it may be a wise decision to choose the most minimal testing environment (DOS).
Run all tests EXCEPT: Fix All, Long Generic, and anything Advanced.
Regards,
Patrick
Sadly there was no problems found, could it be a graphics issue?Thanks!
We have various attached bug checks from the DMP's:
INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
This bug check appears very infrequently. It's usually only associated / shows up with hardware issues.
IRQL_NOT_LESS_OR_EQUAL (a)
This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high. The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This indicates that a system thread generated an exception which the error handler did not catch.
DEFAULT_BUCKET_ID: STATUS_PRIVILEGED_INSTRUCTION
^^ Executing an instruction not allowed in current machine mode.
KMODE_EXCEPTION_NOT_HANDLED (1e)
This indicates that a kernel-mode program generated an exception which the error handler did not catch.
Probably caused by : hardware
------------------------
With all of this said, this is more than likely at first glance a hardware issue. Let's start off with a Memtest for NO LESS than ~8 passes (several hours). If it goes at least 8 without errors, let's move onto chkdsk and then Seatools for hard disk testing:
Memtest86+:
Download Memtest86+ here:
Memtest86+ - Advanced Memory Diagnostic Tool
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:
FAQ : please read before posting
-------------------------------------------------------------------------------------------------------------
Chkdsk:
Chkdsk:
There are various ways to run Chkdsk~
Method 1:
Start > Search bar > Type cmd (right click run as admin to execute Elevated CMD)
Elevated CMD should now be opened, type the following:
chkdsk x: /r
x implies your drive letter, so if your hard drive in question is letter c, it would be:
chkdsk c: /r
Restart system and let chkdsk run.
Method 2:
Open the "Computer" window
Right-click on the drive in question
Select the "Tools" tab
In the Error-checking area, click <Check Now>.
If you'd like to get a log file that contains the chkdsk results, do the following:
Press Windows Key + R and type powershell.exe in the run box
Paste the following command and press enter afterwards:
get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt
This will output a .txt file on your Desktop containing the results of the chkdsk.
If chkdsk turns out okay, run Seatools -
SeaTools | Seagate
You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be device driver related issues that may cause conflicts or false positive, it may be a wise decision to choose the most minimal testing environment (DOS).
Run all tests EXCEPT: Fix All, Long Generic, and anything Advanced.
Regards,
Patrick
I'm sorry, but did you really go through 8 passes of Memtest, chkdsk, and Seatools, all in under an hour? 8 passes of Memtest alone can take more than several hours. Can I see the chkdsk log? What were the Seatools results?
Regards,
Patrick
Regards,
Patrick
Last edited:
I went thorough the memtest just yesterday, ill post the chkdisk soon. And all Seatool tests passedI'm sorry, but did you really go through 8 passes of Memtest, chkdsk, and Seatools, all in under an hour? 8 passes of Memtest alone can take more than several hours. Can I see the chkdsk log? What were the Seatools results?
Regards,
Patrick
Attachments
Oh, okay. Understood. As long as it went at least 8 passes with no errors that's fine. Chkdsk looks good, and good to hear on Seatools. Faulty GPU is possible, yes. Have you tried running Furmark yet? If you run it, watch for artifacts or crashes when running it. Either that, or if you have access to integrated graphics you can uninstall your video card drivers, shut down, physically remove video card, install latest integrated graphics drivers, and use the system as you would regularly. If no crashes, it's GPU related.
Regards,
Patrick
Regards,
Patrick
No errrors, however my BURN-IN SCORE was really low compared to the others with the 6670Oh, okay. Understood. As long as it went at least 8 passes with no errors that's fine. Chkdsk looks good, and good to hear on Seatools. Faulty GPU is possible, yes. Have you tried running Furmark yet? If you run it, watch for artifacts or crashes when running it. Either that, or if you have access to integrated graphics you can uninstall your video card drivers, shut down, physically remove video card, install latest integrated graphics drivers, and use the system as you would regularly. If no crashes, it's GPU related.
Regards,
Patrick
Mine: BURN-IN SCORE: 604 points
Others: FurMark 1.9.2+ burn-in scores - OpenGL benchmark and VGA Stress Test - Scores | oZone3D.Net
What else could be the problem?
Edit: Forgot to mention, idk if its normal but i only got 5 FPS through the entire test.
Let's enable Driver Verifier to be absolutely sure we aren't dealing with any possible device drivers causing corruption:
Driver Verifier:
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:
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8 - Restore Point - Create in Windows 8
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 & 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 24 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 %systemroot%\Minidump
Any other questions can most likely be answered by this article:
Using Driver Verifier to identify issues with Windows drivers for advanced users
Regards,
Patrick
Driver Verifier:
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:
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8 - Restore Point - Create in Windows 8
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 & 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 24 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 %systemroot%\Minidump
Any other questions can most likely be answered by this article:
Using Driver Verifier to identify issues with Windows drivers for advanced users
Regards,
Patrick
Here we go, now we're seeing a culprit:
PAGE_FAULT_BEYOND_END_OF_ALLOCATION (cd)
This indicates that the system accessed memory beyond the end of some driver's pool allocation.
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
FAILURE_BUCKET_ID: X64_0xCD_VRF_CFRMD+3f55
^^ COMODO Safe Delete Filter. Uninstall COMODO ASAP.
Regards,
Patrick
PAGE_FAULT_BEYOND_END_OF_ALLOCATION (cd)
This indicates that the system accessed memory beyond the end of some driver's pool allocation.
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
Code:
3: kd> kv
Child-SP RetAddr : Args to Child : Call Site
fffff880`0ab15c38 fffff800`03101bf0 : 00000000`00000050 fffff980`15ccf000 00000000`00000000 fffff880`0ab15da0 : nt!KeBugCheckEx
fffff880`0ab15c40 fffff800`03081cee : 00000000`00000000 fffff980`15ccf000 fffff880`018bb100 fffff980`15cceff0 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`0ab15da0 fffff800`030c3127 : fffff880`018b3000 00000000`00000000 00000000`073a33c0 fffff880`00000001 : nt!KiPageFault+0x16e (TrapFrame @ fffff880`0ab15da0)
fffff880`0ab15f30 fffff800`030c3745 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!output_l+0x2ef
fffff880`0ab161f0 fffff800`030c378d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!vsnprintf_l+0x75
fffff880`0ab16260 fffff800`030c2dd8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!vsnprintf+0x11
fffff880`0ab162a0 fffff800`030c3876 : 00000000`000001ff fffff880`018b82d0 fffffa80`10159e90 fffff781`c0000000 : nt!DbgPrompt+0x78
fffff880`0ab162d0 fffff800`030c383b : 00000000`00000064 fffff6fc`c00ae670 fffff781`c0000000 fffff6fc`c00ae5d0 : nt!RtlStringCbVPrintfA+0x26
fffff880`0ab16310 fffff800`030be878 : 00000000`00000014 00000000`0000007c 00000000`55534331 00000000`073a33cc : nt! ?? ::FNODOBFM::`string'+0xc1ab
fffff880`0ab165c0 fffff880`018b6f55 : fffff880`018ba4a0 00000000`00000000 fffff880`018b82d0 fffff980`15cceff0 : nt!DbgPrintEx+0x30
fffff880`0ab16600 fffff880`018ba4a0 : 00000000`00000000 fffff880`018b82d0 fffff980`15cceff0 fffff880`018ba478 : [COLOR=#ff0000][I][B]CFRMD[/B][/I][/COLOR]+0x3f55
fffff880`0ab16608 00000000`00000000 : fffff880`018b82d0 fffff980`15cceff0 fffff880`018ba478 fffffa80`16936320 : [COLOR=#ff0000][I][B]CFRMD[/B][/I][/COLOR]+0x74a0FAILURE_BUCKET_ID: X64_0xCD_VRF_CFRMD+3f55
^^ COMODO Safe Delete Filter. Uninstall COMODO ASAP.
Regards,
Patrick
So far 20 mins into watching my stream, it usually crashes after 5.Here we go, now we're seeing a culprit:
PAGE_FAULT_BEYOND_END_OF_ALLOCATION (cd)
This indicates that the system accessed memory beyond the end of some driver's pool allocation.
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
Code:3: kd> kv Child-SP RetAddr : Args to Child : Call Site fffff880`0ab15c38 fffff800`03101bf0 : 00000000`00000050 fffff980`15ccf000 00000000`00000000 fffff880`0ab15da0 : nt!KeBugCheckEx fffff880`0ab15c40 fffff800`03081cee : 00000000`00000000 fffff980`15ccf000 fffff880`018bb100 fffff980`15cceff0 : nt! ?? ::FNODOBFM::`string'+0x4518f fffff880`0ab15da0 fffff800`030c3127 : fffff880`018b3000 00000000`00000000 00000000`073a33c0 fffff880`00000001 : nt!KiPageFault+0x16e (TrapFrame @ fffff880`0ab15da0) fffff880`0ab15f30 fffff800`030c3745 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!output_l+0x2ef fffff880`0ab161f0 fffff800`030c378d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!vsnprintf_l+0x75 fffff880`0ab16260 fffff800`030c2dd8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!vsnprintf+0x11 fffff880`0ab162a0 fffff800`030c3876 : 00000000`000001ff fffff880`018b82d0 fffffa80`10159e90 fffff781`c0000000 : nt!DbgPrompt+0x78 fffff880`0ab162d0 fffff800`030c383b : 00000000`00000064 fffff6fc`c00ae670 fffff781`c0000000 fffff6fc`c00ae5d0 : nt!RtlStringCbVPrintfA+0x26 fffff880`0ab16310 fffff800`030be878 : 00000000`00000014 00000000`0000007c 00000000`55534331 00000000`073a33cc : nt! ?? ::FNODOBFM::`string'+0xc1ab fffff880`0ab165c0 fffff880`018b6f55 : fffff880`018ba4a0 00000000`00000000 fffff880`018b82d0 fffff980`15cceff0 : nt!DbgPrintEx+0x30 fffff880`0ab16600 fffff880`018ba4a0 : 00000000`00000000 fffff880`018b82d0 fffff980`15cceff0 fffff880`018ba478 : [COLOR=#ff0000][I][B]CFRMD[/B][/I][/COLOR]+0x3f55 fffff880`0ab16608 00000000`00000000 : fffff880`018b82d0 fffff980`15cceff0 fffff880`018ba478 fffffa80`16936320 : [COLOR=#ff0000][I][B]CFRMD[/B][/I][/COLOR]+0x74a0
FAILURE_BUCKET_ID: X64_0xCD_VRF_CFRMD+3f55
^^ COMODO Safe Delete Filter. Uninstall COMODO ASAP.
Regards,
Patrick
Also, i previously used to use AVG and my computer still crashed, can i just not have any antivirus? Lol
The latest attached is a *3b with a hardware fault tag again. There's one last software thing we can try before concluding this a faulty video card, and that's disabling Hardware Acceleration given you said this happens with streams.
IE - Internet Explorer GPU Hardware Acceleration - Turn On or Off - Windows 7 Help Forums
Firefox - https://support.mozilla.org/en-US/k...fix-problems#w_turn-off-hardware-acceleration
Chrome - Chrome GPU Hardware Acceleration - Turn On or Off - Windows 7 Help Forums
Regards,
Patrick
IE - Internet Explorer GPU Hardware Acceleration - Turn On or Off - Windows 7 Help Forums
Firefox - https://support.mozilla.org/en-US/k...fix-problems#w_turn-off-hardware-acceleration
Chrome - Chrome GPU Hardware Acceleration - Turn On or Off - Windows 7 Help Forums
Regards,
Patrick
That can explain the reason it crashes while watching streams but what about just playing games or doing other stuff that doesn't relate to chrome?The latest attached is a *3b with a hardware fault tag again. There's one last software thing we can try before concluding this a faulty video card, and that's disabling Hardware Acceleration given you said this happens with streams.
IE - Internet Explorer GPU Hardware Acceleration - Turn On or Off - Windows 7 Help Forums
Firefox - https://support.mozilla.org/en-US/k...fix-problems#w_turn-off-hardware-acceleration
Chrome - Chrome GPU Hardware Acceleration - Turn On or Off - Windows 7 Help Forums
Regards,
Patrick
Ah, forgive me, I forgot you were also crashing during games as well. This appears to universally be a video card issue. Are you using a laptop or a desktop? If you are using a laptop, it'll need to be repaired or replaced entirely by the manufacturer. If you're using a desktop, the only thing left to try as I said earlier is if you have access to integrated graphics you can uninstall your video card drivers, shut down, physically remove video card, install latest integrated graphics drivers, and use the system as you would regularly. If no crashes, it's GPU related.
Regards,
Patrick
Regards,
Patrick
I'm using a desktop and i have no integrated graphics, ill get a new one is a month or so.Ah, forgive me, I forgot you were also crashing during games as well. This appears to universally be a video card issue. Are you using a laptop or a desktop? If you are using a laptop, it'll need to be repaired or replaced entirely by the manufacturer. If you're using a desktop, the only thing left to try as I said earlier is if you have access to integrated graphics you can uninstall your video card drivers, shut down, physically remove video card, install latest integrated graphics drivers, and use the system as you would regularly. If no crashes, it's GPU related.
Regards,
Patrick
Also, it crashed again while i was watching the stream. However this time right when i clicked on steam my computer froze, not BSOD. How can steam be realeted to this, everytime ive opened it while watching the stream my comp has crashed. Could it just be a coincidence?
Has Sysnative Forums helped you? Please consider donating to help us support the site!