New
#11
Nope. Blue screens still back and blue screening as ever.
Edit: Re-uploaded. Made a mistake with making this zip file.
Last edited by Gio Takahashi; 19 Dec 2010 at 01:18.
Nope. Blue screens still back and blue screening as ever.
Edit: Re-uploaded. Made a mistake with making this zip file.
Last edited by Gio Takahashi; 19 Dec 2010 at 01:18.
I don't think anyone's noticed this thread yet.
So, I'm still having issues and getting frequent BSOD, but again, not as much anymore. like maybe, once a day, at best.
Anyway, Info:
The operating system is Windows 7, Ultimate Edition x64, and it is a full retail version. The system is custom built, the current build is less than a year old. This operating system has been installed on 9/22/2010, after getting my first SSD drive.
Anyway, here's the latest stuff:
Hi -
9 mini kernel dump files in the zip attachment for BSODs occuring over a 4 day period - 15 Dec to 19 Dec 2010.
WERCON shows 71 BSODs dating back to late October 2010 -
Code:SCROLL TO RIGHT 12/19/2010 5:17 AM WERCON Fault bucket X64_0x1E_0_nt!KyRetireDpcList+5, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
� 12/18/2010 8:03 AM WERCON Fault bucket X64_0xA_nt!KiInsertTimerTable+10e, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
&# 12/18/2010 4:11 AM WERCON Fault bucket X64_IP_MISALIGNED, type 0
Event Name: BlueScreen
Response: Microsoft Windows Error Reporting Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5 12/18/2010 6:40 PM WERCON Fault bucket X64_0xA_nt!KiSecondaryClockInterrupt+125, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: &#x 12/17/2010 7:29 AM WERCON Fault bucket X64_IP_MISALIGNED, type 0
Event Name: BlueScreen
Response: Microsoft Windows Error Reporting Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5 12/17/2010 7:10 AM WERCON Fault bucket X64_0xA_nt!MiDeleteVirtualAddresses+507, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: � 12/17/2010 6:47 PM WERCON Fault bucket X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: & 12/15/2010 5:34 PM WERCON Fault bucket X64_0x1a_5003_nt!MiAllocateWsle+2fbde, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: � 12/15/2010 11:08 PM WERCON Fault bucket X64_0x3B_nt!zzz_AsmCodeRange_End+3b, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
 12/14/2010 10:03 AM WERCON Fault bucket X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 12/14/2010 9:28 AM WERCON Fault bucket X64_0x50_nt!KiSystemServiceExit+44, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
& 12/14/2010 9:28 AM WERCON Fault bucket X64_0xA_nt!KyRetireDpcList+5, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
 12/14/2010 9:28 AM WERCON Fault bucket X64_0xA_nt!PoIdle+53a, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: & 12/14/2010 9:28 AM WERCON Fault bucket X64_0x1E_0_nt!KyRetireDpcList+5, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
� 12/14/2010 9:28 AM WERCON Fault bucket X64_0x3B_nt!ObpLookupObjectName+5fc, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
 12/14/2010 9:27 AM WERCON Fault bucket X64_0xA_nt!KyRetireDpcList+5, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
 12/14/2010 9:27 AM WERCON Fault bucket X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
&# 12/14/2010 9:27 AM WERCON Fault bucket X64_0xA_dxgmms1!VidSchDdiNotifyDpcWorker+1c0, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 12/14/2010 9:27 AM WERCON Fault bucket X64_0x7E_BAD_IP_nt!PoIdle+53a, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
� 12/14/2010 9:27 AM WERCON Fault bucket X64_IP_MISALIGNED, type 0
Event Name: BlueScreen
Response: Microsoft Windows Error Reporting Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5 12/14/2010 9:27 AM WERCON Fault bucket X64_0xA_nt!MiDeleteVirtualAddresses+507, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: � 12/14/2010 9:27 AM WERCON Fault bucket X64_IP_MISALIGNED, type 0
Event Name: BlueScreen
Response: Microsoft Windows Error Reporting Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5 12/14/2010 9:20 AM WERCON Fault bucket X64_IP_MISALIGNED, type 0
Event Name: BlueScreen
Response: Microsoft Windows Error Reporting Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5 12/14/2010 9:27 AM WERCON Fault bucket X64_IP_MISALIGNED, type 0
Event Name: BlueScreen
Response: Microsoft Windows Error Reporting Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5 12/14/2010 9:02 AM WERCON Fault bucket X64_IP_MISALIGNED, type 0
Event Name: BlueScreen
Response: Microsoft Windows Error Reporting Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5 12/14/2010 7:38 AM WERCON Fault bucket X64_0x3B_nt!ObpLookupObjectName+157, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
 12/14/2010 6:06 AM WERCON Fault bucket X64_0xA_nt!PoIdle+53a, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: & 12/14/2010 9:27 AM WERCON Fault bucket X64_0xD1_NETIO!NsiEnumerateObjectsAllParametersEx+6df, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
&# 12/14/2010 9:27 AM WERCON Fault bucket X64_0xD1_CODE_AV_NULL_IP_nt!PoIdle+53a, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: � 12/14/2010 9:27 AM WERCON Fault bucket X64_0x1E_0_nt!KyRetireDpcList+5, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
� 12/14/2010 9:27 AM WERCON Fault bucket X64_0x7f_8_volmgr!VmDeviceControl+106, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: � 12/14/2010 9:27 AM WERCON Fault bucket X64_0xA_nt!PoIdle+53a, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: & 12/14/2010 9:27 AM WERCON Fault bucket X64_0x3B_ndis!ndisQuerySetMiniportEx+1a9, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: &#x 12/14/2010 9:27 AM WERCON Fault bucket X64_0x3B_nt!KiSystemServiceHandler+7c, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: � 12/14/2010 9:27 AM WERCON Fault bucket X64_IP_MISALIGNED, type 0
Event Name: BlueScreen
Response: Microsoft Windows Error Reporting Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5 12/14/2010 9:27 AM WERCON Fault bucket X64_0x7f_10, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 
&#x 12/14/2010 9:26 AM WERCON Fault bucket X64_IP_MISALIGNED, type 0
Event Name: BlueScreen
Response: Microsoft Windows Error Reporting Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5 12/14/2010 9:24 AM WERCON Fault bucket X64_IP_MISALIGNED, type 0
Event Name: BlueScreen
Response: Microsoft Windows Error Reporting Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5 12/14/2010 9:27 AM WERCON Fault bucket X64_IP_MISALIGNED, type 0
Event Name: BlueScreen
Response: Microsoft Windows Error Reporting Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5 12/14/2010 9:27 AM WERCON Fault bucket X64_0x50_nt!KiSystemServiceExit+44, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
& 12/14/2010 9:27 AM WERCON Fault bucket X64_0xA_nt!KiInsertTimerTable+110, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
&# 12/14/2010 9:27 AM WERCON Fault bucket X64_0x3B_nt!ObpLookupObjectName+157, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
 12/12/2010 5:18 PM WERCON Fault bucket X64_0x7f_8_volmgr!VmDeviceControl+106, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: � 12/11/2010 6:40 AM WERCON Fault bucket X64_IP_MISALIGNED, type 0
Event Name: BlueScreen
Response: Microsoft Windows Error Reporting Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5 12/10/2010 8:29 AM WERCON Fault bucket X64_0x7f_10, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 
&#x 12/05/2010 6:21 AM WERCON Fault bucket X64_0x50_nt!KiSystemServiceExit+44, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
& 12/01/2010 8:50 PM WERCON Fault bucket X64_0xD1_CODE_AV_NULL_IP_nt!PoIdle+53a, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: � 11/30/2010 8:45 AM WERCON Fault bucket X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
&# 11/30/2010 12:28 AM WERCON Fault bucket X64_0xA_nt!KyRetireDpcList+5, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
 11/30/2010 12:44 AM WERCON Fault bucket X64_0xA_nt!KiInsertTimerTable+110, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
&# 11/30/2010 4:15 AM WERCON Fault bucket X64_0xD1_NETIO!NsiEnumerateObjectsAllParametersEx+6df, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
&# 11/29/2010 9:44 PM WERCON Fault bucket X64_IP_MISALIGNED, type 0
Event Name: BlueScreen
Response: Microsoft Windows Error Reporting Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5 11/21/2010 4:26 AM WERCON Fault bucket X64_0x50_nt!KiSystemServiceExit+44, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
& 11/21/2010 7:50 AM WERCON Fault bucket X64_0x3B_ndis!ndisQuerySetMiniportEx+1a9, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: &#x 11/21/2010 3:13 AM WERCON Fault bucket X64_0x3B_nt!KiSystemServiceHandler+7c, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: � 11/21/2010 7:38 AM WERCON Fault bucket X64_0x1E_0_nt!KyRetireDpcList+5, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
� 11/21/2010 3:13 AM WERCON Fault bucket X64_0x3B_nt!KiSystemServiceHandler+7c, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: � 11/21/2010 3:13 AM WERCON Fault bucket X64_0x3B_nt!KiSystemServiceHandler+7c, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: � 11/21/2010 3:13 AM WERCON Fault bucket X64_0x3B_nt!KiSystemServiceHandler+7c, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: � 11/20/2010 8:18 AM WERCON Fault bucket X64_0xA_dxgmms1!VidSchDdiNotifyDpcWorker+1c0, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 11/20/2010 10:34 PM WERCON Fault bucket X64_0x7E_BAD_IP_nt!PoIdle+53a, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
� 11/20/2010 8:19 AM WERCON Fault bucket X64_0xA_dxgmms1!VidSchDdiNotifyDpcWorker+1c0, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 11/20/2010 8:19 AM WERCON Fault bucket X64_0xA_nt!PoIdle+53a, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: & 11/20/2010 8:20 AM WERCON Fault bucket X64_0xA_nt!MiDeleteVirtualAddresses+507, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: � 11/20/2010 12:52 AM WERCON Fault bucket X64_0xA_nt!PoIdle+53a, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: & 11/20/2010 6:17 AM WERCON Fault bucket X64_0xA_nt!KyRetireDpcList+5, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
 11/19/2010 1:33 AM WERCON Fault bucket X64_0xA_nt!MiDeleteVirtualAddresses+507, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: � 11/17/2010 5:22 AM WERCON Fault bucket X64_0x3B_nt!ObpLookupObjectName+5fc, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
 10/29/2010 4:08 PM WERCON Fault bucket X64_IP_MISALIGNED, type 0
Event Name: BlueScreen
Response: Microsoft Windows Error Reporting Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5 10/27/2010 1:27 AM WERCON Fault bucket X64_0x1E_0_nt!KyRetireDpcList+5, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
� 10/25/2010 7:21 AM WERCON Fault bucket X64_IP_MISALIGNED, type 0
Event Name: BlueScreen
Response: Microsoft Windows Error Reporting Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5
The bucgecks are spread all over indicating problems with RAM, CPU, HDD, drivers, OS corruption, etc...
The only driver of interest I found appears to be related to ATI Tray tools. It was written before Windows 7 x64 and may be causing problems -
OS corruption is present in some dumps. I'm not sure if it is the SSD drive, bad RAM or other unknown hardware failure affecting RAMs ability to properly hold kernel code.Code:DRIVER_BIN64 Tue Jul 31 22:05:51 2007 (46AFEA7F)
I would suggest that you run memtest86+ one stick at a time; alternate slots --> Memtest86+ - Advanced Memory Diagnostic Tool
Use ImgBurn to burn memtest86+ ISO to CD --> The Official ImgBurn Website
The SSD needs to be looked at closer. System files show -
Intel SSD Toolbox - http://downloadcenter.intel.com/Deta...&DwnldID=18455Code:INTEL SSDSA2M080G2GC ATA Device
Additional info - Intel SSDs - Intelо Solid-State Drive Toolbox with Intelо SSD Optimizer Enables Users to Maximize SSD Performance over Time
I would also suggest running the Driver Verifier if the SSD and RAM check OK.
Driver Verifier -- Driver Verifier - sysnative.com
Windbg Logs
--> http://sysnative.com/BSOD_2010/jcgri..._jcgriff2_.txt
--> http://sysnative.com/BSOD_2010/jcgri...riff2_.txt.zip
Regards. . .
jcgriff2
`
BSOD BUGCHECK SUMMARY
Code:Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sun Dec 19 00:15:20.675 2010 (GMT-5) System Uptime: 0 days 10:36:53.939 Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1E PROCESS_NAME: firefox.exe Bugcheck code 0000001E Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sat Dec 18 07:49:46.272 2010 (GMT-5) System Uptime: 0 days 4:47:31.537 Probably caused by : ntkrnlmp.exe ( nt!KiSecondaryClockInterrupt+125 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System Bugcheck code 0000000A Arguments ffffffff`ffffffaa 00000000`00000002 00000000`00000000 fffff800`02cd9395 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sat Dec 18 03:01:40.212 2010 (GMT-5) System Uptime: 0 days 3:51:44.477 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+10e ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA Bugcheck code 0000000A Arguments 00000000`000004e1 00000000`00000002 00000000`00000000 fffff800`02cdb11e ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Dec 17 23:08:31.547 2010 (GMT-5) System Uptime: 0 days 9:25:13.812 Probably caused by : hardware ( nt!KiDeferredReadyThread+4e1 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: pol.exe Bugcheck code 0000000A Arguments 00000000`00000001 00000000`00000002 00000000`00000000 fffff800`02c753c1 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Dec 17 07:09:34.574 2010 (GMT-5) System Uptime: 0 days 4:43:47.838 BugCheck D1, {2, c, 8, 2} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) PROCESS_NAME: svchost.exe DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 Bugcheck code 000000D1 Arguments 00000000`00000002 00000000`0000000c 00000000`00000008 00000000`00000002 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Dec 17 02:24:38.814 2010 (GMT-5) System Uptime: 0 days 0:16:55.078 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Probably caused by : hardware ( nt!KiSystemServiceExit+49 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B Bugcheck code 0000003B Arguments 00000000`c0000005 fffff800`02c879e4 fffff880`0baf6250 00000000`00000000 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Dec 17 02:06:53.949 2010 (GMT-5) System Uptime: 1 days 8:01:22.214 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+507 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA Bugcheck code 0000000A Arguments ffffffff`ffffff89 00000000`00000000 00000000`00000001 fffff800`02cb7480 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Wed Dec 15 16:37:05.031 2010 (GMT-5) System Uptime: 0 days 2:27:09.935 Probably caused by : ntkrnlmp.exe ( nt!KiSecondaryClockInterrupt+2cc ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: vpc.exe Bugcheck code 0000003B Arguments 00000000`c000001d fffff800`02c9b53c fffff880`0270fda0 00000000`00000000 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Wed Dec 15 06:19:01.833 2010 (GMT-5) System Uptime: 0 days 15:12:36.737 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b46 ) BUGCHECK_STR: 0x1a_5003 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: firefox.exe Bugcheck code 0000001A Arguments 00000000`00005003 fffff700`01080000 00000000`0001f1f7 0001d84d`0003e3e6 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` by jcgriff2 J. C. Griffith, Microsoft MVP https://mvp.support.microsoft.com/profile/Griffith www.sysnative.com www.jcgriff2.com ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
EDIT: Didn't see you there John!
Hi,
Miscellaneous bugchecks - no clear software cause so it is now time to look at the hardware side of things.
Hardware tests to run:
RAM - Test with Memtest86+
https://www.sevenforums.com/tutorials...t-prime95.html (run the Blend test as well as the Small FFT test)
That SSD could definitely be a possible cause too, but we will look at that on in depth after the other tests pass.
Regards,
Reventon
BUGCHECK SUMMARY
Code:Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sun Dec 19 18:15:20.675 2010 (GMT+13) System Uptime: 0 days 10:36:53.939 Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1E PROCESS_NAME: firefox.exe Bugcheck code 0000001E Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sun Dec 19 01:49:46.272 2010 (GMT+13) System Uptime: 0 days 4:47:31.537 Probably caused by : ntkrnlmp.exe ( nt!KiSecondaryClockInterrupt+125 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System Bugcheck code 0000000A Arguments ffffffff`ffffffaa 00000000`00000002 00000000`00000000 fffff800`02cd9395 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sat Dec 18 21:01:40.212 2010 (GMT+13) System Uptime: 0 days 3:51:44.477 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+10e ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA Bugcheck code 0000000A Arguments 00000000`000004e1 00000000`00000002 00000000`00000000 fffff800`02cdb11e ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sat Dec 18 17:08:31.547 2010 (GMT+13) System Uptime: 0 days 9:25:13.812 Probably caused by : hardware ( nt!KiDeferredReadyThread+4e1 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: pol.exe Bugcheck code 0000000A Arguments 00000000`00000001 00000000`00000002 00000000`00000000 fffff800`02c753c1 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sat Dec 18 01:09:34.574 2010 (GMT+13) System Uptime: 0 days 4:43:47.838 BugCheck D1, {2, c, 8, 2} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) PROCESS_NAME: svchost.exe DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 Bugcheck code 000000D1 Arguments 00000000`00000002 00000000`0000000c 00000000`00000008 00000000`00000002 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Dec 17 20:24:38.814 2010 (GMT+13) System Uptime: 0 days 0:16:55.078 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Probably caused by : hardware ( nt!KiSystemServiceExit+49 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B Bugcheck code 0000003B Arguments 00000000`c0000005 fffff800`02c879e4 fffff880`0baf6250 00000000`00000000 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Dec 17 20:06:53.949 2010 (GMT+13) System Uptime: 1 days 8:01:22.214 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+507 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA Bugcheck code 0000000A Arguments ffffffff`ffffff89 00000000`00000000 00000000`00000001 fffff800`02cb7480 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Thu Dec 16 10:37:05.031 2010 (GMT+13) System Uptime: 0 days 2:27:09.935 Probably caused by : ntkrnlmp.exe ( nt!KiSecondaryClockInterrupt+2cc ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: vpc.exe Bugcheck code 0000003B Arguments 00000000`c000001d fffff800`02c9b53c fffff880`0270fda0 00000000`00000000 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Thu Dec 16 00:19:01.833 2010 (GMT+13) System Uptime: 0 days 15:12:36.737 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b46 ) BUGCHECK_STR: 0x1a_5003 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: firefox.exe Bugcheck code 0000001A Arguments 00000000`00005003 fffff700`01080000 00000000`0001f1f7 0001d84d`0003e3e6 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Okay. I will do all those tests, and get back to you when I find anything.