Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: PC Constant BSOD when generally using.

06 Jun 2013   #1
z4rco

Windows 7 Ultimate x64
 
 
PC Constant BSOD when generally using.

So ever since i have built the pc ive been having constant BSOD. At first it used to be when gaming, and playing graphic intensive games but not its BSOD when I watch youtube and generally just using the PC. Also I had this really weird patch of time where I could not shut the PC down. If I shut the PC down and then started it up 100% of the time right after starting it up after about 1 minute of usuage it would BSOD. The second forced shutdown didnt yield an instant BSOD. I've changed the slots of the RAM and added new ram, new PSU and a new GFX card which "seemed" to have stopped the BSOD... but now theyre back again and this time I had like 5 BSOD in a row within 5 minutes.... Anyways heres all the stuff:

WHO Crashed:

Code:
On Thu 06/06/2013 18:22:53  GMT your computer crashed
crash dump file:  C:\Windows\Minidump\060613-17222-01.dmp
This was probably caused by the  following module: ntoskrnl.exe (nt+0x75C00) 
Bugcheck code: 0x18  (0xFFFFFA800CDEB8F0, 0xFFFFFA800D93E1F0, 0x1, 0x800000000000000)
Error: REFERENCE_BY_POINTER
file path:  C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel &  System
Bug check description: This indicates that the reference count of an  object is illegal for the current state of the object.
This appears to be a  typical software driver bug and is not likely to be caused by a hardware  problem. This might be a case of memory corruption. More often memory corruption  happens because of software errors in buggy drivers, not because of faulty RAM  modules. 
The crash took place in the Windows kernel. Possibly this problem  is caused by another driver that cannot be identified at this time.  



On  Sat 25/05/2013 02:47:30 GMT your computer crashed
crash dump file:  C:\Windows\Minidump\052513-7987-01.dmp
This was probably caused by the  following module: asio.sys  (AsIO+0x100E) 
Bugcheck code: 0x3B (0xC0000096, 0xFFFFF88004BAF00E,  0xFFFFF88004193E70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path:  C:\Windows\SysWow64\drivers\AsIO.sys
Bug check description: This indicates  that an exception happened while executing a routine that transitions from  non-privileged code to privileged code. 
This appears to be a typical  software driver bug and is not likely to be caused by a hardware problem. 
A  third party driver was identified as the probable root cause of this system  error. It is suggested you look for an update for the following driver: asio.sys  . 
Google query: asio.sys  SYSTEM_SERVICE_EXCEPTION



On Sat 11/05/2013 13:19:10 GMT your computer  crashed
crash dump file: C:\Windows\Minidump\051113-7800-01.dmp
This  was probably caused by the following module: ntoskrnl.exe (nt+0x75C00) 
Bugcheck code: 0x44  (0xFFFFFA8010449260, 0x1D7B, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
file path:  C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel &  System
Bug check description: This indicates that a driver has tried to  requested an IRP be completed that is already complete.
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  Fri 03/05/2013 11:34:12 GMT your computer crashed
crash dump file:  C:\Windows\Minidump\050313-7503-01.dmp
This was probably caused by the  following module: ntfs.sys  (Ntfs+0x4688) 
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88009E8C478,  0xFFFFF88009E8BCD0, 0xFFFFF80002EEEADE)
Error: NTFS_FILE_SYSTEM
file path:  C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System  Driver
Bug check description: This indicates a problem occurred in the NTFS  file system. 
The crash took place in a standard Microsoft module. Your  system configuration may be incorrect. Possibly this problem is caused by  another driver on your system that cannot be identified at this time.  



On  Thu 02/05/2013 10:12:09 GMT your computer crashed
crash dump file:  C:\Windows\Minidump\050213-6489-01.dmp
This was probably caused by the  following module: netio.sys (NETIO+0x36E0) 
Bugcheck code: 0xBE  (0xFFFFF88001F0B6E0, 0x48B0121, 0xFFFFF8800852BB40, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path:  C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O  Subsystem
Bug check description: This is issued if a driver attempts to write  to a read-only memory segment.
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 a standard Microsoft module. Your system configuration may be  incorrect. Possibly this problem is caused by another driver on your system that  cannot be identified at this time. 
Minidumps: (ive attached them)
060613-17222-01.dmp is the 6/6/2013 one

The z4roc.zip contains everything from the SF diagnostic tool.

Thank you for your time, constant bsod are really aggrovating. And the one which keeps popping up the most is the ntfs.sys and ntoskrnl.exe.

Additional Notes:

I have carried out memtest for a whole day when I just had the x2 ripjaws alone and it went to completion with all passes and no errors.

IMO I think the problem lies with the mobo, I dont think its a good one or maybe the psu being inadequate or the fact that I had so many BSOD it may have corrupted the windows 7 files so I may need to completely reinstall my OS... helps if I still had the disc.



My System SpecsSystem Spec
.
07 Jun 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Hello z4rco.

Make it sure that Your Kingston SSD (KINGSTON SVP200S3120G) is running with the up-to-date firmware.
Download svp200_503fw_win, for svp200s3 | Kingston Technology

Update JMicron JMB36X (SCSI) Controller. It is very old.
Code:
fffff880`00e5a000 fffff880`00e7b000   jraid      (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\jraid.sys
    Image name: jraid.sys
    Timestamp:        Thu Nov 25 08:57:17 2010 (4CEDD795)
    CheckSum:         0002CCCE
    ImageSize:        00021000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Get the latest one from ftp://driver.jmicron.com.tw/SATA_Controller/Windows/. And, if you are using RAID, disable RAID in BIOS. What we have found that RAID is always problematic.

Update AMD SATA (AHCI) Controller, too. It is also very old.
Code:
fffff880`00c85000 fffff880`00c9c000   amd_sata   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\amd_sata.sys
    Image name: amd_sata.sys
    Timestamp:        Sat Mar 05 02:15:41 2011 (4D714F75)
    CheckSum:         000202DD
    ImageSize:        00017000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Get it either from M5A97 PRO - Motherboards - ASUS or from Support & Drivers .

Let us know the results.
_________________________________________________________________________________
BSOD ANALYSIS:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 18, {fffffa800cdeb8f0, fffffa800d93e1f0, 1, 800000000000000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48d8a )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

REFERENCE_BY_POINTER (18)
Arguments:
Arg1: fffffa800cdeb8f0, Object type of the object whose reference count is being lowered
Arg2: fffffa800d93e1f0, Object whose reference count is being lowered
Arg3: 0000000000000001, Reserved
Arg4: 0800000000000000, Reserved
    The reference count of an object is illegal for the current state of the object.
    Each time a driver uses a pointer to an object the driver calls a kernel routine
    to increment the reference count of the object. When the driver is done with the
    pointer the driver calls another kernel routine to decrement the reference count.
    Drivers must match calls to the increment and decrement routines. This bugcheck
    can occur because an object's reference count goes to zero while there are still
    open handles to the object, in which case the fourth parameter indicates the number
    of opened handles. It may also occur when the object’s reference count drops below zero
    whether or not there are open handles to the object, and in that case the fourth parameter
    contains the actual value of the pointer references count.

Debugging Details:
------------------


OVERLAPPED_MODULE: Address regions for 'ndiswan' and 'atikmpag.sys' overlap

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x18

PROCESS_NAME:  autochk.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000306bdbd to fffff800030c5c00

STACK_TEXT:  
fffff880`036c5e28 fffff800`0306bdbd : 00000000`00000018 fffffa80`0cdeb8f0 fffffa80`0d93e1f0 00000000`00000001 : nt!KeBugCheckEx
fffff880`036c5e30 fffff800`033681e1 : 00000000`00000000 00000000`0008c081 fffffa80`0d93d640 fffffa80`0d93d640 : nt! ?? ::FNODOBFM::`string'+0x48d8a
fffff880`036c5e90 fffff800`0309313b : fffffa80`0d93d6c0 00000000`00000000 fffffa80`0d93d6c0 fffffa80`0d93d6c0 : nt!MiSegmentDelete+0xa1
fffff880`036c5ed0 fffff800`03093862 : 00000000`00000000 00000000`00000011 00000000`00000000 00000000`00000000 : nt!MmPurgeSection+0x71b
fffff880`036c5fc0 fffff880`01a887ef : fffffa80`0d93f0c8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CcPurgeCacheSection+0x172
fffff880`036c6030 fffff880`01a9f75e : fffffa80`0d536d10 fffffa80`0d61c180 fffff8a0`00220a01 00000000`00000001 : Ntfs!NtfsFlushVolume+0x5cf
fffff880`036c6160 fffff880`01ab57a9 : fffffa80`0d536d10 00000000`00000000 00000000`c00000d8 fffffa80`0e3b0c60 : Ntfs!NtfsCommonVolumeOpen+0x7f5
fffff880`036c6330 fffff880`018bfbcf : fffffa80`0d61c030 fffffa80`0e3b0c60 00000000`00000000 00000000`00000000 : Ntfs!NtfsFsdCreate+0x1c9
fffff880`036c64e0 fffff880`018df2b9 : fffffa80`0e3b0c60 fffffa80`0d705800 fffffa80`0e3b0c00 fffffa80`0d501890 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`036c6570 fffff800`033c6fdc : 00000000`00000025 fffffa80`0dc091c8 fffffa80`0e390930 00000000`00000000 : fltmgr!FltpCreate+0x2a9
fffff880`036c6620 fffff800`033c2958 : fffffa80`0d4ed940 fffff800`00000000 fffffa80`0dc09010 fffffa80`00000001 : nt!IopParseDevice+0x14d3
fffff880`036c6780 fffff800`033c3b76 : 00000000`00000000 fffffa80`0dc09010 fffff8a0`02162bc0 fffffa80`0cdeb8f0 : nt!ObpLookupObjectName+0x588
fffff880`036c6870 fffff800`033c547c : 00000000`00000400 00000000`00000000 fffffa80`0e34a901 fffff880`036c6958 : nt!ObOpenObjectByName+0x306
fffff880`036c6940 fffff800`033afa84 : 00000000`0023f750 fffff8a0`00100003 00000000`001ac940 00000000`001ac930 : nt!IopCreateFile+0x2bc
fffff880`036c69e0 fffff800`030c4e93 : fffffa80`0db5f060 00000000`00000001 fffffa80`0db5fa60 fffff800`033be884 : nt!NtOpenFile+0x58
fffff880`036c6a70 00000000`771a164a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001ac8c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771a164a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+48d8a
fffff800`0306bdbd cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+48d8a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

FAILURE_BUCKET_ID:  X64_0x18_CORRUPT_REF_COUNT_nt!_??_::FNODOBFM::_string_+48d8a

BUCKET_ID:  X64_0x18_CORRUPT_REF_COUNT_nt!_??_::FNODOBFM::_string_+48d8a

Followup: MachineOwner
---------
My System SpecsSystem Spec
07 Jun 2013   #3
z4rco

Windows 7 Ultimate x64
 
 

Hey bro thank you!! for the fast and constructive response, it really means a lot to me so from the bottom of my heart thank you. This thing has been with me like the plague.

So I've updated a lot of the controllers and HDD based software/ drivers. The kingston doesnt have any new firmware for itself.

I had a new BSOD this time:

On Fri 07/06/2013 12:46:31 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF88005E75630)
Bugcheck code: 0xD1 (0xE46E200, 0x2, 0x1, 0xFFFFF88005E75630)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: DRIVER_IRQL_NOT_LESS_OR_EQUAL

The BSOD actually told me that atikmdag.sys was the culprit.
My System SpecsSystem Spec
.

07 Jun 2013   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

My System SpecsSystem Spec
07 Jun 2013   #5
z4rco

Windows 7 Ultimate x64
 
 

Sure I've attached it.
My System SpecsSystem Spec
08 Jun 2013   #6
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

The crash dump is not very clear about the cause of the BSOD, but the failing modules are Ntfs.sys, fltmgr.sys and fileinfo.sys. That means somehow the storage operations are facing issues. It may be caused either by a virus, or by the filter monitoring mechanism of an antivirus, or by any failig storage, or by any failing storage controller. Let us check.

Scan the system for possible virus infection with the following programs.
You have Kaspersky installed.
Code:
Start Menu\Programs\Kaspersky Internet Security 2013
Uninstall Kaspersky using Kaspersky Removal Tool, at least as a test. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Check for any available firmware update:
The JMicron JMB36X (SCSI) Controller is very old.
Code:
fffff880`00e40000 fffff880`00e61000   jraid      (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\jraid.sys
    Image name: jraid.sys
    Timestamp:        Thu Nov 25 08:57:17 2010 (4CEDD795)
    CheckSum:         0002CCCE
    ImageSize:        00021000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Update it from ftp://driver.jmicron.com.tw/SATA_Controller/Windows/

And the AMD SATA (AHCI) Controller is also very old.
Code:
fffff880`00dc4000 fffff880`00ddb000   amd_sata   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\amd_sata.sys
    Image name: amd_sata.sys
    Timestamp:        Sat Mar 05 02:15:41 2011 (4D714F75)
    CheckSum:         000202DD
    ImageSize:        00017000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
1: kd> !sysinfo machineid
Machine ID Information [From Smbios 2.7, DMIVersion 39, Size=2521]
Update it from M5A97 PRO - Motherboards - ASUS

Let us know the results.
_____________________________________________________________________________________
BSOD ANALYSIS:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 18, {fffffa800cdeb8f0, fffffa800d93e1f0, 1, 800000000000000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48d8a )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

REFERENCE_BY_POINTER (18)
Arguments:
Arg1: fffffa800cdeb8f0, Object type of the object whose reference count is being lowered
Arg2: fffffa800d93e1f0, Object whose reference count is being lowered
Arg3: 0000000000000001, Reserved
Arg4: 0800000000000000, Reserved
    The reference count of an object is illegal for the current state of the object.
    Each time a driver uses a pointer to an object the driver calls a kernel routine
    to increment the reference count of the object. When the driver is done with the
    pointer the driver calls another kernel routine to decrement the reference count.
    Drivers must match calls to the increment and decrement routines. This bugcheck
    can occur because an object's reference count goes to zero while there are still
    open handles to the object, in which case the fourth parameter indicates the number
    of opened handles. It may also occur when the object’s reference count drops below zero
    whether or not there are open handles to the object, and in that case the fourth parameter
    contains the actual value of the pointer references count.

Debugging Details:
------------------


OVERLAPPED_MODULE: Address regions for 'ndiswan' and 'atikmpag.sys' overlap

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x18

PROCESS_NAME:  autochk.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000306bdbd to fffff800030c5c00

STACK_TEXT:  
fffff880`036c5e28 fffff800`0306bdbd : 00000000`00000018 fffffa80`0cdeb8f0 fffffa80`0d93e1f0 00000000`00000001 : nt!KeBugCheckEx
fffff880`036c5e30 fffff800`033681e1 : 00000000`00000000 00000000`0008c081 fffffa80`0d93d640 fffffa80`0d93d640 : nt! ?? ::FNODOBFM::`string'+0x48d8a
fffff880`036c5e90 fffff800`0309313b : fffffa80`0d93d6c0 00000000`00000000 fffffa80`0d93d6c0 fffffa80`0d93d6c0 : nt!MiSegmentDelete+0xa1
fffff880`036c5ed0 fffff800`03093862 : 00000000`00000000 00000000`00000011 00000000`00000000 00000000`00000000 : nt!MmPurgeSection+0x71b
fffff880`036c5fc0 fffff880`01a887ef : fffffa80`0d93f0c8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CcPurgeCacheSection+0x172
fffff880`036c6030 fffff880`01a9f75e : fffffa80`0d536d10 fffffa80`0d61c180 fffff8a0`00220a01 00000000`00000001 : Ntfs!NtfsFlushVolume+0x5cf
fffff880`036c6160 fffff880`01ab57a9 : fffffa80`0d536d10 00000000`00000000 00000000`c00000d8 fffffa80`0e3b0c60 : Ntfs!NtfsCommonVolumeOpen+0x7f5
fffff880`036c6330 fffff880`018bfbcf : fffffa80`0d61c030 fffffa80`0e3b0c60 00000000`00000000 00000000`00000000 : Ntfs!NtfsFsdCreate+0x1c9
fffff880`036c64e0 fffff880`018df2b9 : fffffa80`0e3b0c60 fffffa80`0d705800 fffffa80`0e3b0c00 fffffa80`0d501890 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`036c6570 fffff800`033c6fdc : 00000000`00000025 fffffa80`0dc091c8 fffffa80`0e390930 00000000`00000000 : fltmgr!FltpCreate+0x2a9
fffff880`036c6620 fffff800`033c2958 : fffffa80`0d4ed940 fffff800`00000000 fffffa80`0dc09010 fffffa80`00000001 : nt!IopParseDevice+0x14d3
fffff880`036c6780 fffff800`033c3b76 : 00000000`00000000 fffffa80`0dc09010 fffff8a0`02162bc0 fffffa80`0cdeb8f0 : nt!ObpLookupObjectName+0x588
fffff880`036c6870 fffff800`033c547c : 00000000`00000400 00000000`00000000 fffffa80`0e34a901 fffff880`036c6958 : nt!ObOpenObjectByName+0x306
fffff880`036c6940 fffff800`033afa84 : 00000000`0023f750 fffff8a0`00100003 00000000`001ac940 00000000`001ac930 : nt!IopCreateFile+0x2bc
fffff880`036c69e0 fffff800`030c4e93 : fffffa80`0db5f060 00000000`00000001 fffffa80`0db5fa60 fffff800`033be884 : nt!NtOpenFile+0x58
fffff880`036c6a70 00000000`771a164a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001ac8c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771a164a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+48d8a
fffff800`0306bdbd cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+48d8a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

FAILURE_BUCKET_ID:  X64_0x18_CORRUPT_REF_COUNT_nt!_??_::FNODOBFM::_string_+48d8a

BUCKET_ID:  X64_0x18_CORRUPT_REF_COUNT_nt!_??_::FNODOBFM::_string_+48d8a

Followup: MachineOwner
---------
Child-SP          RetAddr           Call Site
fffff880`036c5e28 fffff800`0306bdbd nt!KeBugCheckEx
fffff880`036c5e30 fffff800`033681e1 nt! ?? ::FNODOBFM::`string'+0x48d8a
fffff880`036c5e90 fffff800`0309313b nt!MiSegmentDelete+0xa1
fffff880`036c5ed0 fffff800`03093862 nt!MmPurgeSection+0x71b
fffff880`036c5fc0 fffff880`01a887ef nt!CcPurgeCacheSection+0x172
fffff880`036c6030 fffff880`01a9f75e Ntfs!NtfsFlushVolume+0x5cf
fffff880`036c6160 fffff880`01ab57a9 Ntfs!NtfsCommonVolumeOpen+0x7f5
fffff880`036c6330 fffff880`018bfbcf Ntfs!NtfsFsdCreate+0x1c9
fffff880`036c64e0 fffff880`018df2b9 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`036c6570 fffff800`033c6fdc fltmgr!FltpCreate+0x2a9
fffff880`036c6620 fffff800`033c2958 nt!IopParseDevice+0x14d3
fffff880`036c6780 fffff800`033c3b76 nt!ObpLookupObjectName+0x588
fffff880`036c6870 fffff800`033c547c nt!ObOpenObjectByName+0x306
fffff880`036c6940 fffff800`033afa84 nt!IopCreateFile+0x2bc
fffff880`036c69e0 fffff800`030c4e93 nt!NtOpenFile+0x58
fffff880`036c6a70 00000000`771a164a nt!KiSystemServiceCopyEnd+0x13
00000000`001ac8c8 00000000`00000000 0x771a164a
My System SpecsSystem Spec
08 Jun 2013   #7
z4rco

Windows 7 Ultimate x64
 
 

I have updated ALL the drivers you told me to, I dont know why the bugcheck is showed they are old when I go through the systemroots they have all been updated to versions 2012+.

I added a new PSU, put the gfx card in another slot and then for about 10 minutes the computer was constantly blue screening, and restarting itself. Everytime it restart itself it wanted to run checkdisk???!!

I have added my minidump - note it is named z4rcoversion3 incase you are looking at the old minidump.
My System SpecsSystem Spec
08 Jun 2013   #8
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Quote   Quote: Originally Posted by z4rco View Post
I have updated ALL the drivers you told me to,
But you havent taken all the suggestions.

Kaspersky is crashing there, continuously.
Code:
fffff880`03b68298  fffff880`0485000eUnable to load image \SystemRoot\system32\DRIVERS\klif.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
 klif+0x2300e
Description here: Driver Reference Table - klif.sys

Uninstall Kaspersky using Kaspersky Removal Tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

If you dont take this suggestion even after it, I would say you that dump analysis will not go to an end, if the outcome is not followed. Best of luck.
My System SpecsSystem Spec
08 Jun 2013   #9
z4rco

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by Arc View Post
Quote   Quote: Originally Posted by z4rco View Post
I have updated ALL the drivers you told me to,
But you havent taken all the suggestions.

Kaspersky is crashing there, continuously.
Code:
fffff880`03b68298  fffff880`0485000eUnable to load image \SystemRoot\system32\DRIVERS\klif.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
 klif+0x2300e
Description here: Driver Reference Table - klif.sys

Uninstall Kaspersky using Kaspersky Removal Tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

If you dont take this suggestion even after it, I would say you that dump analysis will not go to an end, if the outcome is not followed. Best of luck.
I uninstalled Kaspersky. After I posted I didnt want to install MSE and MWB on the current build I have after wiping kaspesky, it didnt feel right. So I completely re-formatted my disk re-installed win 7, used my key, and then only used a prepped USB to install ONLY the latest drivers to everything. If I installed mse only too format the drive.... D: Then I installed MSE and Malware bytes, so be assured I took your advice, I just wanted to use it on a clean sheet of paper.

I did memtest and the windows memory thing, and it came out clear. All pass at every level. I checked the harddisks, all passes. I multimetered the new psu and it runs stable at high load. I bought and replaced ALL cabling, and re-greased the CPU and GPU/ stress tested the gpu and it passed. I am 100% sure now my hardware is not the cause of this. Kaspersky is also removed. If it bsod again im buying a mac.

I will update ANY security from windows update as im not stupid and dont go on porn/ site where malware/ spyware will be infested with and i honestly dont trust microsoft updates. The bsods started happening when I started installing the updates.

Thank you.
My System SpecsSystem Spec
Reply

 PC Constant BSOD when generally using.




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD's while generally running PC, several different error codes.
Hi all, Hope you can help, I have bought my PC in January & it ran fine for a few months. I then started to get the odd BSOD until July when it started to BSOD everyday. I thought it was a RAM issue so removed one of the chips & it has worked fine up till the last week when it started to BSOD...
BSOD Help and Support
BSOD on shutdown, generally after HDMI use, 0x0000009F
Hello, I have an Asus N53SV running windows home premium 64bit. I have been having BSOD problems for the last year however recently they have been occurring much more frequently. I have looked through a lot of threads and tried a few different programs. Also googled the stop codes to no avail of...
BSOD Help and Support
BSOD Random - Generally just in Firefox/Desktop
Hey guys, I've had my computer for a few months now and I've been having issues with it just BSOD and rebooting on me every now and then. I've only had it occur while open in Firefox or if I leave my desktop open. It has yet to crash on me in game. When I first built the computer I was having...
BSOD Help and Support
BSOD whilst generally using computer local ID: 2057
Hi, whilst generally using my computer it will blue screen and state that it is dumping memory, there have been several codes but the latest is: Local ID: 2057 Additional information about the problem: BCCode: 1000007e BCP1: FFFFFFFFC0000005 BCP2: FFFFF800037B3DE0 ...
BSOD Help and Support
BSOD generally at startup, errors: 0x0000000a and 0x0000003b.
Hi guys, I have been experiencing BSOD crashes for a few months now. I wasn't really sure what to do but now that they have become more frequent (normally 1-3 a day) I have come to you guys for help. I'm not completely computer illiterate and I've followed the appropriate error posting...
BSOD Help and Support
BSOD While doing generally anything
Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.768.3 Locale ID: 1033 Additional information about the problem: BCCode: 1000007e BCP1: FFFFFFFFC0000005 BCP2: FFFFF80002A777A5 BCP3: FFFFF88002883958
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 08:01.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App