BSOD ntoskrnl.exe 7cc40

[idiotoncomputer]

Im getting massive BSOD's every day. I can't even use this computer most hours and it'll probably BSOD in a few minuetes.

Could someone look at the txt file I included and point me in the right direction? Or if I need more info please tell me!!! Because Im going crazy with this BSOD.

 

[ePeen]

Please follow this post and reply accordingly.

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[idiotoncomputer]

please can someone help me???

 

[writhziden]

Security Software:

mbamservice.exe	c:\program files (x86)\malwarebytes' anti-malware\mbamservice.exe	3896	8	200	1380	3/27/2012 2:42 PM	Not Available	Not Available	Not Available
egui.exe	c:\program files\eset\eset nod32 antivirus\egui.exe	2864	8	200	1380	3/27/2012 2:40 PM	4.2.67.10	2.78 MB (2,919,168 bytes)	11/4/2010 5:15 PM
ekrn.exe	c:\program files\eset\eset nod32 antivirus\x86\ekrn.exe	1736	8	200	1380	3/27/2012 2:40 PM	4.2.67.10	791.16 KB (810,144 bytes)	11/4/2010 5:15 PM
sbiectrl.exe	c:\program files\sandboxie\sbiectrl.exe	2912	8	200	1380	3/27/2012 2:40 PM	3.54.0.0	583.73 KB (597,736 bytes)	3/24/2011 4:25 AM
sbiesvc.exe	c:\program files\sandboxie\sbiesvc.exe	1152	8	200	1380	3/27/2012 2:40 PM	3.54.0.0	93.73 KB (95,976 bytes)	3/24/2011 4:24 AM

Event[139]:
  Log Name: System
  Source: Ntfs
  Date: 2012-03-27T13:41:59.198
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: User10-PC
  Description: 
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume1.

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run the Western Digital Data Lifeguard Diagnostic tests to make sure the hard drive is not faulty.

 

[idiotoncomputer]

Thank you writhziden for replying:

I did what you asked and ran CHKDSK for both my drives, but I got no errors(I included both in the CHKDSK rar file). I should mention that most of my BSODs often say page fault or some some sort of "system exception". The other times I dont even get a BSOD, but instead a strange interlaced image or just a reboot.

I have a feeling it is either a video card driver issue or some sort of memory issue. Should I run memtest86 or could you analyze my logs and recommend something else?

Thanks!

 

[writhziden]

Your .dmp files were corrupted in most cases. This is usually a sign of hard disk errors, which is why I recommended those steps. The other two things that your crashes have in common are the possibility of memory problems and driver conflicts.

• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    View attachment 205003
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

 

[idiotoncomputer]

I ran memtest86 with no errors after 5 hours. I couldnt run windows memory because my system was so unstable.

However, the computer has stabilized greatly(though I got two BSOD's yesterday and today) ever since I cleaned out the CPU and Video card fan of dust and old thermal grease. I used to get BSOD's or reboot every 20-30 min. But now I can at least run it for several hours sometimes. I checked the CPU temperature in BIOS(37-40 C) and my GPU with GPU-Z shows about 31-33 C. Are these ok temperatures? Perhaps my Power is no good? Cleaning also helped me get rid of BSOD's last time a few months ago. I am using a stock AMD fan, so should I get a better one?

Also, in the past i had some sound driver issues. And today I found a new audio device from AMD, that I never had before. Am I suppoesd to have more than 1 sound device?


Included are the last two dmp files.

Thanks for your help writhziden!

 

[writhziden]

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\IdiotOnComputer\TwoDMPS\033112-17877-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e09000 PsLoadedModuleList = 0xfffff800`0304e670
Debug session time: Sat Mar 31 17:37:03.430 2012 (UTC - 6:00)
System Uptime: 0 days 4:49:01.600
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {e3, fffffa80059ba531, 5cdf384, 0}

Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c )

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

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000e3, Kernel Zw API called with user-mode address as parameter.
Arg2: fffffa80059ba531, Address inside the driver making the incorrect API call.
Arg3: 0000000005cdf384, User-mode address used as API parameter.
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc4_e3

FAULTING_IP: 
+3035313636653265
fffffa80`059ba531 85c0            test    eax,eax

FOLLOWUP_IP: 
nt!VerifierBugCheckIfAppropriate+3c
fffff800`0330f3dc cc              int     3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  ekrn.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000330f3dc to fffff80002e85c40

STACK_TEXT:  
fffff880`077f8568 fffff800`0330f3dc : 00000000`000000c4 00000000`000000e3 fffffa80`059ba531 00000000`05cdf384 : nt!KeBugCheckEx
fffff880`077f8570 fffff800`0330fec5 : fffffa80`03e25b00 fffff800`0331e09a fffff880`077f3000 fffff880`077f9000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`077f85b0 fffff800`0331139e : 00000000`00000000 00000000`00000028 fffffa80`059ba3b9 ffffe61c`0000051e : nt!ViZwCheckAddress+0x35
fffff880`077f85f0 fffff800`03311426 : fffff880`077f8738 fffff880`077f8738 00000000`00000000 00000000`00000000 : nt!ViZwCheckUnicodeString+0x2e
fffff880`077f8630 fffff800`03314d99 : fffffa80`059ba531 00000000`00000000 00000000`70616745 00000000`00000000 : nt!ViZwCheckObjectAttributes+0x26
fffff880`077f8660 fffffa80`059ba531 : 00000000`05cdf384 00000000`00000000 00000000`05cdf3b4 00000000`05cdf3fa : nt!VfZwOpenFile+0x49
fffff880`077f86a0 00000000`05cdf384 : 00000000`00000000 00000000`05cdf3b4 00000000`05cdf3fa 00000000`00000007 : 0xfffffa80`059ba531
fffff880`077f86a8 00000000`00000000 : 00000000`05cdf3b4 00000000`05cdf3fa 00000000`00000007 fffffa80`00000021 : 0x5cdf384


STACK_COMMAND:  kb

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!VerifierBugCheckIfAppropriate+3c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xc4_e3_VRF_nt!VerifierBugCheckIfAppropriate+3c

BUCKET_ID:  X64_0xc4_e3_VRF_nt!VerifierBugCheckIfAppropriate+3c

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

Verifier enabled, and blaming system files. That usually means you have hardware problems. It could still be drivers and it is just not picking them up, but based on the information you've provided, I suspect hardware.


37-40 C is a bit high for AMD on idle. Thank you for the information that cleaning helps. I would recommend you do some hardware diagnosis and temperature monitoring.

• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing a CPU stress test using IntelBurnTest