1.

Solve : BSOD Caused by drivers, Windows 7?

Answer»

For reasons unknown my computer has been bluescreening on me for around a month at different times for different drivers and such. I had a problem similar when I installed a new HARD drive where after a short while my computer would BSOD and I tracked the problem to that hard drive and REMOVED it. A while after I STILL get BSOD but not as frequent and most recently with the STOP 0x0000007a. I have checked all drivers and ran chckdsk and have had no luck and simply don't know what to do at this point.

Results from my most recent WhoCrashed:

On Mon 02/07/2018 20:11:05 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070218-6318-01.dmp
This was PROBABLY caused by the following module: ntoskrnl.exe (nt+0xA48A0)
Bugcheck code: 0xC4 (0x0, 0x0, 0x0, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. The driver requested a zero-byte pool allocation.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 02/07/2018 20:11:05 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!NlsLeadByteInfo+0x97D4)
Bugcheck code: 0xC4 (0x0, 0x0, 0x0, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. The driver requested a zero-byte pool allocation.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply==================================================
Dump File : 070218-6318-01.dmp
Crash Time : 02/07/2018 20:11:05
Bug Check String : DRIVER_VERIFIER_DETECTED_VIOLATION
Bug Check Code : 0x000000c4
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : tcpipreg.sys
Caused By Address : tcpipreg.sys+35a5
File Description : TCP/IP Registry Compatibility Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.23496 (win7sp1_ldr.160707-0600)
Processor : x64
Crash Address : ntoskrnl.exe+a48a0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070218-6318-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 415,280
Dump File Time : 02/07/2018 20:16:44
==================================================

see if this helps: https://support.microsoft.com/en-us/help/2550576/stop-0xc4-may-occur-in-tcpipreg-sys-following-a-reboot-after-driver-ve



Discussion

No Comment Found