I've installed Windows 7 x64 three times now trying to rid myself of this problem to no avail. The BSOD occurs randomly and not linked to anything that I can gather. Run memtest, OCCT, prime95 to check for errors and force anything, but no. Sought out the latest drivers and not so latest from the hardware makers sites and again the BDOS returns. Hopefully someone can help me.
Last edited by anpan879; 22 Apr 2012 at 00:01.
Another BSOD today while playing Minecraft. Minidump attached.
Another BSOD after changing my wireless adapter driver to the one suggested by Windows Update.
Possible cause of blue screen crashes:AiChargerPlus.sysCode:AiChargerPlus fffff880`00e93000 fffff880`00e94e00 Sun Nov 07 23:48:26 2010 (4cd79d3a) 00005a96 AiChargerPlus.sys
Crashes are all the same, and all are fairly inconclusive. Possible causes of the crashes include Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...Code:Loading Dump File [D:\Kingston\BSODDmpFiles\anpan879\Windows_NT6_BSOD_jcgriff2\042312-9344-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505 Machine Name: Kernel base = 0xfffff800`0201e000 PsLoadedModuleList = 0xfffff800`02262650 Debug session time: Mon Apr 23 10:48:29.831 2012 (UTC - 6:00) System Uptime: 0 days 12:49:34.347 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 --------- 2: 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: +3030636264323833 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: d EXCEPTION_RECORD: fffff88002286848 -- (.exr 0xfffff88002286848) ExceptionAddress: fffff800020a6249 (nt!KeUpdateRunTime+0x0000000000000049) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff880022868f0 -- (.trap 0xfffff880022868f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff78000000320 rbx=0000000000000000 rcx=fffff88002286ab0 rdx=0000270900000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800020a6249 rsp=fffff88002286a80 rbp=0000000000000000 r8=fffff880022690c0 r9=0000000000000000 r10=000000000000c2d1 r11=fffffa8011072110 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!KeUpdateRunTime+0x49: fffff800`020a6249 f683dc21000008 test byte ptr [rbx+21DCh],8 ds:0190:00000000`000021dc=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000209267e to fffff8000209ac50 STACK_TEXT: fffff880`02285928 fffff800`0209267e : fffffa80`0d6dbd18 fffffa80`1153c080 fffff880`022860a0 fffff800`020c5c80 : nt!KeBugCheck fffff880`02285930 fffff800`020c594d : fffff800`022a377c fffff800`021e4038 fffff800`0201e000 fffff880`02286848 : nt!KiKernelCalloutExceptionHandler+0xe fffff880`02285960 fffff800`020c4725 : fffff800`021e3fac fffff880`022859d8 fffff880`02286848 fffff800`0201e000 : nt!RtlpExecuteHandlerForException+0xd fffff880`02285990 fffff800`020d56a1 : fffff880`02286848 fffff880`022860a0 fffff880`00000000 00000000`002d2a03 : nt!RtlDispatchException+0x415 fffff880`02286070 fffff800`0209a302 : fffff880`02286848 fffff880`0225e180 fffff880`022868f0 00000000`00000000 : nt!KiDispatchException+0x135 fffff880`02286710 fffff800`02098c0a : fffffa80`0c7275f0 00000000`00000000 fffffa80`0c7275f0 00000000`00000000 : nt!KiExceptionDispatch+0xc2 fffff880`022868f0 fffff800`020a6249 : fffff800`02236cd0 fffff800`0209f346 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a fffff880`02286a80 fffff800`020a6041 : fffff880`0225e180 fffff880`02286b30 fffff880`022690c0 fffffa80`110db740 : nt!KeUpdateRunTime+0x49 fffff880`02286ab0 fffff800`02092962 : fffff880`0225e180 fffff880`00000000 00000000`00000000 fffff800`00000000 : nt!KiSecondaryClockInterrupt+0x131 fffff880`02286c40 00000000`00000000 : fffff880`02287000 fffff880`02281000 fffff880`02286c00 00000000`00000000 : nt!KiIdleLoop+0x32 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiKernelCalloutExceptionHandler+e fffff800`0209267e 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: 4f558b55 FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e Followup: MachineOwner ---------
See if removing the AI Charger software helps. If not, proceed with steps to check for underlying driver conflicts.
- 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 filesThe 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.
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
Attachment 208658- 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 System Restore 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.
When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:verifier /reset-> Restart your computer.
Quote