BSOD Help please

[AJZ]

Hi wonderful forum helpers,

I could use some help. I've gotten two bosd in the last week and am not sure why. I'm assuming it's a driver issue but could use some help.

There error I'm getting is as follows:

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3

Extra information about the problem
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Bucket ID: X64_0x1E_c000001d_BAD_IP_nt!KiProcessExpiredTimerList+4a
Server information: 09786397-cb3e-4896-a418-1d900e9fd0d3

Attached dmp

Thanks for any help in advice.


My system information is as follows:
Os: Windows 7 64 bit home
CPU: i5 2500k oc'd to 4.8ghz
Cooler: Antec Khuler
Mobo: Asus p8z68-v/gen 3
Ram: 4x4 (16) Kingston Hyperx blu
PSU: Thermatek Black Widow 850watt
Video card: nvidia evga 560 GTX TI

Any other info needed?

Started doing this when I added the video card, I think.

 

[writhziden]

Loading Dump File [D:\Kingston\BSODDmpFiles\AJZ\040312-10545-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.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0324a000 PsLoadedModuleList = 0xfffff800`0348e650
Debug session time: Tue Apr  3 16:12:52.666 2012 (UTC - 6:00)
System Uptime: 0 days 2:27:39.509
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+6634393064363435
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000b9c268 -- (.exr 0xfffff80000b9c268)
ExceptionAddress: fffff800032d188a (nt!KiProcessExpiredTimerList+0x000000000000004a)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff80000b9c310 -- (.trap 0xfffff80000b9c310)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa80127eb650
rdx=fffffa8010b40e60 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032d188a rsp=fffff80000b9c4a0 rbp=000000000008aa69
 r8=fffffa800d13db50  r9=000000000000006a r10=fffff8000343be80
r11=fffffa800d13daf0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KiProcessExpiredTimerList+0x4a:
fffff800`032d188a f00fba2b07      lock bts dword ptr [rbx],7 ds:0088:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032be6fe to fffff800032c6d10

STACK_TEXT:  
fffff800`00b9b348 fffff800`032be6fe : 00000000`00000000 00000000`00000000 fffff800`00b9bac0 fffff800`032f1da0 : nt!KeBugCheck
fffff800`00b9b350 fffff800`032f1a6d : fffff800`034cf71c fffff800`0340c078 fffff800`0324a000 fffff800`00b9c268 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b380 fffff800`032f0845 : fffff800`0340ffac fffff800`00b9b3f8 fffff800`00b9c268 fffff800`0324a000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b3b0 fffff800`033017c1 : fffff800`00b9c268 fffff800`00b9bac0 fffff800`00000000 fffff800`00b9c4e0 : nt!RtlDispatchException+0x415
fffff800`00b9ba90 fffff800`032c63c2 : fffff800`00b9c268 fffffa80`1121cc20 fffff800`00b9c310 00000000`00000003 : nt!KiDispatchException+0x135
fffff800`00b9c130 fffff800`032c451f : fffff800`00b9c310 fffffa80`10c94902 fffffa80`42554800 fffffa80`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c310 fffff800`032d188a : fffffa80`0d13db30 fffffa80`1121cc68 fffffa80`1121cc68 00000000`00000000 : nt!KiInvalidOpcodeFault+0x11f
fffff800`00b9c4a0 fffff800`032d17ee : 00000014`a0ade3ac fffff800`00b9cb18 00000000`0008aa69 fffff800`0343efa8 : nt!KiProcessExpiredTimerList+0x4a
fffff800`00b9caf0 fffff800`032d15d7 : 00000006`a5f795c2 00000006`0008aa69 00000006`a5f7953f 00000000`00000069 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`032bea6a : fffff800`0343be80 fffff800`03449cc0 00000000`00000000 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`032be6fe 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

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

It is difficult to analyze one .dmp file and find patterns, especially when the .dmp file is inconclusive as yours is. Possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...


Start with the following tests to see if we can narrow down the cause more:

• If you are overclocking any hardware, please stop.
  
  
• Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
  
  
• 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 205837
  • 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.

Also, please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to provide us with more information regarding your crashes so we can give more specific troubleshooting steps.

 

[AJZ]

Mate,

I truly apologize for not following the steps during my first posts. I have since followed everything you said in your post and each guide you linked to. Attached are the files you asked for.

Along with the bsod's, Also I'm getting purple/pink screens during video playback now and my computer is not responding, this just started happening today. I added a logitech G510...

Please help if possible bit upset about the status of my pc.

Windows is completely up to date.

Mem test comes back with all negative 10hrs in.

I also did driver sweeper and deleted and reinstalled all the drivers that I could.


Attached youll also find a picture of the pink screen while watching a streaming music video.

iI'd like to also note, I dont think its a virus, I dont surf porn sites or download programs from random sites. I thinks its a huge driver problem. Or windows erroring.

Specs are:

The computer is only 3 months old, all is OEM, I built it myself. Im great with hardware just not with software.

CoolerMaster HAF 912 (8x120mm fans)
Thermaltake Black Widow 850W
Intel I5 2500k
Antec h20 620 Cooler (Double pull config)
Asus P8Z68-V
16gb (4x4) Kingston Hyper X
SSD 120gb OCZ Agility Sata III
HDD 500 gb Hatichi Sata II (7200rpm)
EVGA GTX 560 TI FBP

 

[writhziden]

That appears to be a graphics card problem. I also note you have an SSD. Is the SSD firmware up to date? What about the BIOS? Chipset Drivers? SATA controller drivers?


I would recommend checking the graphics card hardware.

• 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). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. 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.

Your attachments contain the perfmon report, but not the jcgriff .zip file.

 

[AJZ]

The ”here” attachement should have had the jf one.

Ran video heating tests and checked the fan. I will run mem test tonight. ill also try to reatach my my jf file'

As for the ssd firmware I havent updated it since installing it. One thing though, here OCZ Technology it says it cant be updated on an ssd that has the windows os on it and is primary, any work arounds? Or can I boot the driver off of a flash driver directly.

 

[AJZ]

Fixed the pink/purple screen of death now am getting bsod with different errors, attached the file again, please have a look at it and give me your expertise.

Should be attached this time.

 

[writhziden]

The latest crashes did not generate any new .dmp files, unfortunately.

We should check your SSD firmware and whether it needs to be updated. If it does, you will have to update it by installing Windows on another drive, updating the firmware, and then moving back to the SSD. I know it is a pain to do, but that is one of the prices of new technology.

You can check the SSD firmware version in the BIOS or device manager. Intel® High Performance Solid State Drive — How to find the SSD Firmware Version shows how to find it in device manager (you have to scroll down past the first two steps to where it says "To find SSD Firmware version in Windows*:").

http://www.ocztechnology.com/files/ssd_tools/OCZ SSD v1.7 Firmware Update Guide.pdf may also be useful.

 

[AJZ]

The latest crashes did not generate any new .dmp files, unfortunately.

We should check your SSD firmware and whether it needs to be updated. If it does, you will have to update it by installing Windows on another drive, updating the firmware, and then moving back to the SSD. I know it is a pain to do, but that is one of the prices of new technology.

You can check the SSD firmware version in the BIOS or device manager. Intel® High Performance Solid State Drive — How to find the SSD Firmware Version shows how to find it in device manager (you have to scroll down past the first two steps to where it says "To find SSD Firmware version in Windows*:").

http://www.ocztechnology.com/files/ssd_tools/OCZ SSD v1.7 Firmware Update Guide.pdf may also be useful.

Did it, version was 2.15 current. All is good with the ssd.

So what's the next Step? I really want they bsod to stupid they're ruining gaming and work.

 

[writhziden]

Recommend updating your BIOS. It appears the most recent version is supposed to provide more system stability.

P8Z68-V LX BIOS 3703
1.Improve system stability.
2.Improve memory compatibility.
3.Support new CPUs. Please refer to our website at: ASUSTeK Computer Inc. -Support- CPU Support
* Enable support for Intel Next Gen 22nm Processor E1 stepping MP version CPU.

Do not shut down or reset the system to prevent system boot up failure while BIOS is updating.

ASUS - Motherboards- ASUS P8Z68-V LX

 

[AJZ]

Recommend updating your BIOS. It appears the most recent version is supposed to provide more system stability.

P8Z68-V LX BIOS 3703
1.Improve system stability.
2.Improve memory compatibility.
3.Support new CPUs. Please refer to our website at: ASUSTeK Computer Inc. -Support- CPU Support
* Enable support for Intel Next Gen 22nm Processor E1 stepping MP version CPU.

Do not shut down or reset the system to prevent system boot up failure while BIOS is updating.

ASUS - Motherboards- ASUS P8Z68-V LX

I have the latest one updated. Did that a month ago. Any other ideas?

 

[writhziden]

How did you update to the latest a month ago when the latest is less than a month old?

BIOS Version/Date	American Megatrends Inc. 3201, 2/15/2012

Indicates you have the version a month prior to the newest.

 

[AJZ]

How did you update to the latest a month ago when the latest is less than a month old?

BIOS Version/Date    American Megatrends Inc. 3201, 2/15/2012

Indicates you have the version a month prior to the newest.

That's the newest version available for my board located on the manufactors website here: ASUS - Motherboards- ASUS P8Z68-V/GEN3

P.s. I dont have the LX it's the V/gen three

 

[writhziden]

Ah, sorry about that. Google was not finding the right board earlier. Now when I do a search, your board is the first one it finds... Strange. Earlier it took me to the completely wrong one which I originally posted, then it took me to the one you saw. I think it was having issues with the gen3 part of the name.

Make sure your Chipset and SATA controller drivers are up to date. There is a 2012.01.20 update for your Chipset, a 2011.07.20 update for the Intel Rapid Storage Technology Controller driver, and a 2011.06.09 update for the JMicron controller driver. If you have not already installed these, now would be a good time to do so.


Let me know when you've done that. I will try to take a closer look at your crash reports and see if I can come up with anything new later tonight. Could you give details as to what you did to fix the purple/pink screen problem?

 

[AJZ]

Ah, sorry about that. Google was not finding the right board earlier. Now when I do a search, your board is the first one it finds... Strange. Earlier it took me to the completely wrong one which I originally posted, then it took me to the one you saw. I think it was having issues with the gen3 part of the name.

Make sure your Chipset and SATA controller drivers are up to date. There is a 2012.01.20 update for your Chipset, a 2011.07.20 update for the Intel Rapid Storage Technology Controller driver, and a 2011.06.09 update for the JMicron controller driver. If you have not already installed these, now would be a good time to do so.


Let me know when you've done that. I will try to take a closer look at your crash reports and see if I can come up with anything new later tonight. Could you give details as to what you did to fix the purple/pink screen problem?

All of the drivers through Asus and intel are up to date. That includes the jmicron one as well. Ive cleared all old drivers as well.

For the pink screen I had uninstall evga ocscanner and updated to scanner x and then.i went to nvidia beta drivers. I think the current issue was cauing the issue.

Yes please see what you can find out through the crash logs. I appreciate.all of you help on this. Its just difficult to know I have a.great computer that I cant relay on due to bsods.

 

[Dwarf]

What version of Flash have you got installed? If it is 11.1.102.63 (or older), then update it. The current version is 11.2.202.228

 

[AJZ]

What version of Flash have you got installed? If it is 11.1.102.63 (or older), then update it. The current version is 11.2.202.228

Have the newest one. Still bsod.

 

[writhziden]

The following Asus Charger driver can be problematic:

AiChargerPlus	fffff880`00e63000	fffff880`00e64e00	Sun Nov 07 23:48:26 2010 (4cd79d3a)	00005a96		AiChargerPlus.sys

Please remove the Asus Charger software at least to test. I have seen the removal of this help, and considering your crashes increased in frequency with the addition of a USB device, I suspect you may be in this category.

 

[AJZ]

The following Asus Charger driver can be problematic:

AiChargerPlus    fffff880`00e63000    fffff880`00e64e00    Sun Nov 07 23:48:26 2010 (4cd79d3a)    00005a96        AiChargerPlus.sys

Please remove the Asus Charger software at least to test. I have seen the removal of this help, and considering your crashes increased in frequency with the addition of a USB device, I suspect you may be in this category.

This solution sounds extremely promising, do you have any method you would recommend for removing this driver? Either a step by step processor or program?

Thanks much, also, did anything else stick out in your research as potentially problematic?

 

[writhziden]

You should be able to remove it through Start Menu -> Control Panel -> Uninstall a program -> ASUS AI Charger -> Uninstall

 

[AJZ]

You should be able to remove it through Start Menu -> Control Panel -> Uninstall a program -> ASUS AI Charger -> Uninstall

Nope not there, the only asus app that's there is Ai Suite which is an application not a driver.