BSOD F4 has me stumped need some help

C

c7c4c7

BSOD Enthusiast
Joined
Oct 18, 2012
Posts
19
This has been going on for some time an I finally have to ask for help. I have included several of the crash dumps, I've looked at all of them and cannot find any useful data to help me solve the problem, so it's time to ask the experts....... Any help is appreciated

The last crash happened with Driver Verifier active but I don't see anything in it that is anything different than the other dumps. I currently have memcheck running on the machine to see if it finds anything

Most drivers have been updatedView attachment Dumps.zip

I've attached as much info as I can if you need anything else let me know, good hunting


· OS - Windows 8.1, 8, 7, Vista ? - Windows 7 Pro

· x86 (32-bit) or x64 ? - 64 bit
· What was original installed OS on system? - Windows 7 Pro
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? - Retail version
· Age of system (hardware) - About 1 year
· Age of OS installation - have you re-installed the OS? - about 1 year

· CPU - 3.40 gigahertz Intel Core i7-2600
· Video Card -NVIDIA Quadro 2000D
[TABLE="width: 100%"]
[TR]
[TD="width: 4%"][/TD]
[TD="width: 48%, align: left"][/TD]
[/TR]
[/TABLE]
· MotherBoard - Intel Corporation DH67GD AAG10206-210· Power Supply - brand & wattage (if laptop, skip this one) -

· System Manufacturer - Built myself
· Exact model number (if laptop, check label on bottom) Built myself

See Below for more info
[TABLE="width: 100%"]
[TR]
[TD="width: 48%, bgcolor: #EFEFEF, align: center"]Operating System
[/TD]
[TD="width: 4%"][/TD]
[TD="width: 48%, bgcolor: #EFEFEF, align: center"]System Model
[/TD]
[/TR]
[TR]
[TD="width: 48%, align: left"]Windows 7 Professional (x64) Service Pack 1 (build 7601)
Install Language: English (United States)
System Locale: English (United States)
Installed: 10/3/2011 1:38:15 PM
[/TD]
[TD="width: 4%"][/TD]
[TD="width: 48%, align: left"]Enclosure Type: Desktop
[/TD]
[/TR]
[TR]
[TD="width: 48%, bgcolor: #EFEFEF, align: center"]Processor a
[/TD]
[TD="width: 4%"][/TD]
[TD="width: 48%, bgcolor: #EFEFEF, align: center"]Main Circuit Board b
[/TD]
[/TR]
[TR]
[TD="width: 48%, align: left"]3.40 gigahertz Intel Core i7-2600
256 kilobyte primary memory cache
1024 kilobyte secondary memory cache
8192 kilobyte tertiary memory cache
64-bit ready
Multi-core (4 total)
Hyper-threaded (8 total)
[/TD]
[TD="width: 4%"][/TD]
[TD="width: 48%, align: left"]Board: Intel Corporation DH67GD AAG10206-210
Serial Number: BTGD216002AN
Bus Clock: 100 megahertz
BIOS: Intel Corp. BLH6710H.86A.0156.2012.0615.1908 06/15/2012
[/TD]
[/TR]
[TR]
[TD="width: 48%, bgcolor: #EFEFEF, align: center"]Drives
[/TD]
[TD="width: 4%"][/TD]
[TD="width: 48%, bgcolor: #EFEFEF, align: center"]Memory Modules c,d
[/TD]
[/TR]
[TR]
[TD="width: 48%, align: left"]1590.23 Gigabytes Usable Hard Drive Capacity
1383.09 Gigabytes Hard Drive Free Space

ATAPI iHAS124 B ATA Device [Optical drive]

Corsair Force 3 SSD [Hard drive] (90.03 GB) -- drive 2, s/n 1132820200000712017B, rev 1.3, SMART Status: Healthy
ST31000524AS [Hard drive] (1000.20 GB) -- drive 1, s/n 5VP8V4FD, rev JC45, SMART Status: Healthy
ST500DM002-1BC142 [Hard drive] (500.11 GB) -- drive 0, s/n S2A04DRJ, rev JC4B, SMART Status: Healthy
[/TD]
[TD="width: 4%"][/TD]
[TD="width: 48%, align: left"]8162 Megabytes Usable Installed Memory

Slot 'DIMM3' is Empty
Slot 'DIMM1' has 4096 MB (serial number 441FBC0A)
Slot 'DIMM4' is Empty
Slot 'DIMM2' has 4096 MB (serial number 451FB90A)
[/TD]
[/TR]
[TR]
[TD="width: 4%"][/TD]
[TD="width: 48%, bgcolor: #EFEFEF, align: center"]Local Drive Volumes
[/TD]
[/TR]
[TR]
[TD="width: 4%"][/TD]
[TD="width: 48%, align: left"]
[TABLE="width: 100%"]
[TR]
[TD="width: 45%"][/TD]
[TD="width: 15%"][/TD]
[TD="width: 20%"][/TD]
[TD="width: 5%"][/TD]
[TD="width: 15%"][/TD]
[/TR]
[TR]
[TD]c: (NTFS on drive 2) *
[/TD]
[TD="align: right"]89.92 GB
[/TD]
[TD="align: right"]28.82 GB free
[/TD]
[TD][/TD]
[TD][/TD]
[/TR]
[TR]
[TD]d: (NTFS on drive 1)
[/TD]
[TD="align: right"]1000.20 GB
[/TD]
[TD="align: right"]899.81 GB free
[/TD]
[TD][/TD]
[TD][/TD]
[/TR]
[TR]
[TD]h: (NTFS on drive 0)
[/TD]
[TD="align: right"]500.11 GB
[/TD]
[TD="align: right"]454.45 GB free
[/TD]
[TD][/TD]
[TD][/TD]
[/TR]
[/TABLE]

[/TD]
[/TR]
[/TABLE]

 

Attachments

I see you have a SSD, have you updated to the latest firmware? I'll check the dump files now. The latest dump files seem to be all Stop 0xF4's, and Stop 0xF4's don't really contain much useful information. They've been seen to caused by anti-virus programs and hard-disks.
 
Last edited:
Hi c7c4c7! :smile9:
If warranty is still active, maybe it's better to bring the pc to the assistance.
If not, have you already tried to open your pc and remove gently and carefully the dust inside it (especially every fans, but the other components too)?

:wave:
 
x BlueRobot said:
I see you have a SSD, have you updated to the latest firmware? I'll check the dump files now. The latest dump files seem to be all Stop 0xF4's, and Stop 0xF4's don't really contain much useful information. They've been seen to caused by anti-virus programs and hard-disks.
Click to expand...
 
Yes, update for SSD has been applied.

the 0xF4 is not of much help. I've tried everything I can think of at this point.
 
Hi,

First off, as mentioned, we have a CRITICAL_OBJECT_TERMINATION (f4) bug check.

This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

However, as opposed to your traditional 0xc0000006 which occurs when data cannot be placed into memory due to an I/O error (usually a sign of SSD firmware needing to be updated, faulty HDD / SSD, etc), the string is: BUGCHECK_STR: 0xF4_C0000005

This indicates an access violation occurred, which generally is caused by a driver causing corruption. Unfortunately, from the *F4 dump, we are getting very little to no information.

FAILURE_BUCKET_ID: X64_0xF4_C0000005_VRF_IMAGE_wininit.exe

^^ The FBID doesn't tell us anything other than the system had verifier enabled at the time of the crash, and the process that unexpectedly ceased to exist was winnit.exe.

------------------------

THANKFULLY, we have another bug check among the dumps which DOES give us info, and that's DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1).

This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high. This bug check is usually caused by drivers that have used improper addresses.

If we take a look at the call stack:

Code: 
STACK_TEXT:  
fffff800`00ba2338 fffff800`03689169 : 00000000`0000000a fffff980`6b50cfe0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba2340 fffff800`03687de0 : fffffa80`0980b3c0 fffff800`03b17b92 fffff980`6e7005d0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba2480 fffff880`066736f0 : fffff880`06674770 00000000`00000000 fffff980`04be0e70 fffff980`334e2fb8 : nt!KiPageFault+0x260
fffff800`00ba2610 fffff880`06674770 : 00000000`00000000 fffff980`04be0e70 fffff980`334e2fb8 fffff980`6e6fef40 : [COLOR=#ff0000][I][B]monblanking+0x16f0[/B][/I][/COLOR]
fffff800`00ba2618 00000000`00000000 : fffff980`04be0e70 fffff980`334e2fb8 fffff980`6e6fef40 fffff800`03b32d26 : [COLOR=#ff0000][I][B]monblanking+0x2770[/B][/I][/COLOR]

FAILURE_BUCKET_ID: X64_0xD1_VRFK_monblanking+16f0

To my knowledge, monblanking.sys is a part of GoToMyPC. The reason for monblanking.sys causing the crash is here - PROCESS_NAME: N360.exe. GoToMyPC's latest version(s) install a system driver as part of the new screen blanking feature. This new screen blanking driver is capable of blanking out multiple monitors. This can cause many conflicts, and it's conflicting with your Norton 360.

Rather than uninstalling the entire software itself, just in case you use it and like it (unless you want to, of course), we can remove the screen blanking and keep the rest of the software intact:

1. Click Start
2. Click Run or click in the start search box
3. Type appwiz.cpl and press Enter
4. The driver will be listed as: Windows Driver Package - Citrix Systems monblanking Citrix Driver
5. Select the driver and click Change/Remove or Uninstall/Change
Click to expand...

Regards,

Patrick
 
(If Patrick's solution shouldn't work)
This guy is using windows 6.1.7601.17640 (win7sp1_gdr.110622-1506) with Intel Core i5-2500K Sandybridge @ 3.30GHz and has got your same error.
It may be worthwhile to carefully check this thread: 0x000000f4 help...

:wave:
 
I removed Windows Driver Package - Citrix Systems monblanking Citrix Driver from the system and turned driver verify back on, let's see what happens
 
Just looked at it, mine is in AHCI mode and I had no problems installing the update as I remember. Also it is plugged into the Mobo correctly.

Thanks
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top