Tech Support Forum banner
Status
Not open for further replies.
1 - 10 of 10 Posts

· Registered
Joined
·
4 Posts
Discussion Starter · #1 ·
Hi so this is my brothers computer and it seems to crash at least twice a day. It is running windows 7 32 bit it was custom build by a friend and came with windows xp it is an os version of 7.

The computer is about 3 years old i re-installed windows 7 about a month ago but the bsods were happening before i installed windows 7 just not as much.

the cpu is an amd athlon 64 x2 dual core processor 6000+ 3.01 GHz. The video card is an evga geforce 9800 gt not sure about the psu or mobo but i know the psu is at least 750w.

Thanks
 

Attachments

· TSF Team Emeritus, Microsoft MVP
Joined
·
7,498 Posts
No memory dump files in the attachment - but MSINFO32 shows a bunch of crashes.
Please do the following:
Upload Dump Files:
Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.
Left click on the first minidump file.
Hold down the "Shift" key and left click on the last minidump file.
Right click on the blue highlighted area and select "Send to"
Select "Compressed (zipped) folder" and note where the folder is saved.
Upload that .zip file with your next post.

If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.

If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service . I recommend Windows Live SkyDrive - http://skydrive.live.com or another free, file-hosting service. Then post the link to it in your topic so that we can download it.

Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): http://www.carrona.org/setmini.html
I'm suspecting an incompatible device/software - but can't be sure. Please check for compatibility here: http://www.microsoft.com/windows/compatibility/windows-7/en-us/default.aspx

Memory dumps from MSINFO32:
01/07/2010 12:32 AM Windows Error Reporting Fault bucket 0x124_AuthenticAMD_PROCESSOR_CACHE, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\063010-11671-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-29656-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WERA623.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0b58da33

Analysis symbol: 0x124_AuthenticAMD_PROCESSOR_CACHE
Rechecking for solution: 0
Report Id: 063010-11671-01
Report Status: 0

29/06/2010 3:39 AM Windows Error Reporting Fault bucket 0x50_nt!ObReferenceObjectByHandleWithTag+1e, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\062810-12281-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-44531-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WERD06F.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0bc8f0c8

Analysis symbol: 0x50_nt!ObReferenceObjectByHandleWithTag+1e
Rechecking for solution: 0
Report Id: 062810-12281-01
Report Status: 0

30/06/2010 7:00 AM Windows Error Reporting Fault bucket 0x50_nt!ObReferenceObjectByHandleWithTag+1e, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\062910-16843-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-42046-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WERE04D.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0af1874b

Analysis symbol:
0x50_nt!ObReferenceObjectByHandleWithTag+1e
Rechecking for solution: 0
Report Id: 062910-16843-01
Report Status: 0

08/06/2010 6:48 PM Windows Error Reporting Fault bucket 0x7f_d_win32k!NtUserGetMessage+82, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\060810-10812-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-27000-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WERACDA.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0aecfeb3

Analysis symbol: 0x7f_d_win32k!NtUserGetMessage+82
Rechecking for solution: 0
Report Id: 060810-10812-01
Report Status: 0

04/07/2010 1:42 AM Windows Error Reporting Fault bucket 0x8E_STACKPTR_ERROR, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\070310-12468-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-26250-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WER7196.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0bc08aee

Analysis symbol: 0x8E_STACKPTR_ERROR
Rechecking for solution: 0
Report Id: 070310-12468-01
Report Status: 0

03/07/2010 7:07 AM Windows Error Reporting Fault bucket 0xA_dxgmms1!VidSchiProcessCompletedQueuePacketInternal+43a, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\070310-11343-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-24250-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WER9AC9.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0a50c13c

Analysis symbol: 0xA_dxgmms1!VidSchiProcessCompletedQueuePacketInternal+43a
Rechecking for solution: 0
Report Id:

070310-11343-01
Report Status: 0
27/06/2010 5:39 AM Windows Error Reporting Fault bucket 0xA_nt!KiCommitThreadWait+11c, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\062610-10734-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-21437-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WER5D23.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0a97b9b5

Analysis symbol: 0xA_nt!KiCommitThreadWait+11c
Rechecking for solution: 0
Report Id: 062610-10734-01
Report Status: 0

28/06/2010 2:29 AM Windows Error Reporting Fault bucket 0xA_nt!KiCommitThreadWait+11c, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\062710-11718-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-23984-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WER7956.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0ab8b1ac

Analysis symbol: 0xA_nt!KiCommitThreadWait+11c
Rechecking for solution: 0
Report Id: 062710-11718-01
Report Status: 0

28/06/2010 6:28 PM Windows Error Reporting Fault bucket 0xA_nt!KiCommitThreadWait+11c, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\062810-12828-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-2644187-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WER636A.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_07706f9f

Analysis symbol: 0xA_nt!KiCommitThreadWait+11c
Rechecking for solution: 0
Report Id: 062810-12828-01
Report Status: 0

27/06/2010 2:58 AM Windows Error Reporting Fault bucket 0xA_nt!KiExecuteAllDpcs+1a, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\062610-9734-02.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-27531-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WER90C6.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0b08ae12

Analysis symbol: 0xA_nt!KiExecuteAllDpcs+1a
Rechecking for solution: 0
Report Id: 062610-9734-02
Report Status: 0

04/07/2010 2:41 AM Windows Error Reporting Fault bucket 0xA_nt!KiExecuteAllDpcs+1a, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\070310-13921-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-42937-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WER6A9C.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0bd79fea

Analysis symbol: 0xA_nt!KiExecuteAllDpcs+1a
Rechecking for solution: 0
Report Id: 070310-13921-01
Report Status: 0

04/07/2010 2:32 AM Windows Error Reporting Fault bucket 0xA_nt!KiExecuteAllDpcs+1a, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\070310-25500-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-39421-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WERAB63.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0b64ce5c

Analysis symbol: 0xA_nt!KiExecuteAllDpcs+1a
Rechecking for solution: 0
Report Id: 070310-25500-01
Report Status: 0

08/06/2010 2:26 AM Windows Error Reporting Fault bucket 0xA_nt!KiInsertTimerTable+128, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\060710-17343-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-179890-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WERF591.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0fa31f02

Analysis symbol: 0xA_nt!KiInsertTimerTable+128
Rechecking for solution: 0
Report Id: 060710-17343-01
Report Status: 0

25/06/2010 1:42 AM Windows Error Reporting Fault bucket 0xA_nt!KiInsertTimerTable+128, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\062410-10562-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-36796-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WERB054.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0bacc071

Analysis symbol: 0xA_nt!KiInsertTimerTable+128
Rechecking for solution: 0
Report Id: 062410-10562-01
Report Status: 0

02/07/2010 4:14 AM Windows Error Reporting Fault bucket 0xA_nt!KiInsertTimerTable+128, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\070110-12031-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-21968-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WER692.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0aa22253

Analysis symbol: 0xA_nt!KiInsertTimerTable+128
Rechecking for solution: 0
Report Id: 070110-12031-01
Report Status: 0

02/07/2010 3:52 AM Windows Error Reporting Fault bucket 0xA_nvlddmkm!GpuWatchdogCallback+13, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\070110-12531-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-24578-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WER6CF2.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0b6ca160

Analysis symbol: 0xA_nvlddmkm!GpuWatchdogCallback+13
Rechecking for solution: 0
Report Id: 070110-12531-01
Report Status: 0

23/06/2010 10:53 PM Windows Error Reporting Fault bucket 0xB8_nt!KiIdleLoop+ce, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\062310-9578-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-83484-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WER78D4.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0c2984bb

Analysis symbol: 0xB8_nt!KiIdleLoop+ce
Rechecking for solution: 0
Report Id: 062310-9578-01
Report Status: 0

01/07/2010 12:49 AM Windows Error Reporting Fault bucket 0xB8_nt!KiIdleLoop+ce, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\063010-13593-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-27171-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WER830A.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0b08a1fc

Analysis symbol: 0xB8_nt!KiIdleLoop+ce
Rechecking for solution: 0
Report Id: 063010-13593-01
Report Status: 0

27/06/2010 3:18 AM Windows Error Reporting Fault bucket 0xD1_afd!AfdFastConnectionReceive+d7, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\062610-11078-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-24125-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WER6532.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0a8935c0

Analysis symbol: 0xD1_afd!AfdFastConnectionReceive+d7
Rechecking for solution: 0
Report Id: 062610-11078-01
Report Status: 0

29/06/2010 4:09 AM Windows Error Reporting Fault bucket 0xD1_afd!AfdFastDatagramReceive+75, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\062810-11828-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-32750-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WER8E74.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0b24a41f

Analysis symbol: 0xD1_afd!AfdFastDatagramReceive+75
Rechecking for solution: 0
Report Id: 062810-11828-01
Report Status: 0

02/07/2010 11:02 PM Windows Error Reporting Fault bucket 0xD1_CODE_AV_BAD_IP_nt!KiTimerExpiration+25c, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\070210-13593-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-30546-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WER7FEE.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0bb24126

Analysis symbol: 0xD1_CODE_AV_BAD_IP_nt!KiTimerExpiration+25c
Rechecking for solution: 0
Report Id: 070210-13593-01
Report Status: 0

27/06/2010 1:36 AM Windows Error Reporting Fault bucket 0xF7_ONE_BIT_nt!KiDeferredReadyThread+8f2, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\062610-9750-02.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-23468-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WER7D0F.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0aa49598

Analysis symbol: 0xF7_ONE_BIT_nt!KiDeferredReadyThread+8f2
Rechecking for solution: 0
Report Id: 062610-9750-02
Report Status: 0

28/06/2010 4:10 AM Windows Error Reporting Fault bucket 0xF7_ONE_BIT_nt!KiDeferredReadyThread+8f2, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\062710-11859-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-21750-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WER761A.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0ab89c40

Analysis symbol: 0xF7_ONE_BIT_nt!KiDeferredReadyThread+8f2
Rechecking for solution: 0
Report Id: 062710-11859-01
Report Status: 0

28/06/2010 4:27 AM Windows Error Reporting Fault bucket 0xF7_ONE_BIT_nt!KiDeferredReadyThread+8f2, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\062710-11906-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-20812-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WER5B00.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0a88883b

Analysis symbol: 0xF7_ONE_BIT_nt!KiDeferredReadyThread+8f2
Rechecking for solution: 0
Report Id: 062710-11906-01
Report Status: 0

28/06/2010 7:34 PM Windows Error Reporting Fault bucket 0xF7_ONE_BIT_nt!KiDeferredReadyThread+8f2, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\062810-13281-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-21593-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WER5DB0.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0abc7f13

Analysis symbol: 0xF7_ONE_BIT_nt!KiDeferredReadyThread+8f2
Rechecking for solution: 0
Report Id: 062810-13281-01
Report Status: 0

01/07/2010 4:27 AM Windows Error Reporting Fault bucket 0xF7_ONE_BIT_nt!KiDeferredReadyThread+8f2, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\063010-12671-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-33906-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WER8B86.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0bec9d59

Analysis symbol: 0xF7_ONE_BIT_nt!KiDeferredReadyThread+8f2
Rechecking for solution: 0
Report Id: 063010-12671-01
Report Status: 0

03/07/2010 10:06 PM Windows Error Reporting Fault bucket 0xF7_ONE_BIT_nt!KiDeferredReadyThread+8f2, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\070310-11468-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-27187-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WER97FA.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0a90c7b5

Analysis symbol: 0xF7_ONE_BIT_nt!KiDeferredReadyThread+8f2
Rechecking for solution: 0
Report Id: 070310-11468-01
Report Status: 0

03/07/2010 11:13 PM Windows Error Reporting Fault bucket 0xF7_ONE_BIT_nt!KiDeferredReadyThread+8f2, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\070310-13265-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-25156-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WERC9D.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0bc17e53

Analysis symbol: 0xF7_ONE_BIT_nt!KiDeferredReadyThread+8f2
Rechecking for solution: 0
Report Id: 070310-13265-01
Report Status: 0

04/07/2010 1:59 AM Windows Error Reporting Fault bucket 0xF7_ONE_BIT_nt!KiDeferredReadyThread+8f2, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\070310-13687-01.dmp
C:\Users\Nicholas\AppData\Local\Temp\WER-47375-0.sysdata.xml
C:\Users\Nicholas\AppData\Local\Temp\WERE6E5.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0bbdb6c8

Analysis symbol: 0xF7_ONE_BIT_nt!KiDeferredReadyThread+8f2
Rechecking for solution: 0
Report Id: 070310-13687-01
Report Status: 0
I notice that the Windows SDK is installed on your system - what are you using it for?
 

· Registered
Joined
·
4 Posts
Discussion Starter · #3 · (Edited)
Oh sorry when it was running the program i saw all the minidump files in the cmd prompt so i thought i copied them. sorry. I installed windows 7 sdk because it had the debugger tool so i thought i would be able to view the dump files for some reason but i obviously cannot.
 

Attachments

· TSF Team Emeritus
Joined
·
6,274 Posts
Hi,

50 BSODs over just a few days.

1. You have Kaspersky installed - this is known to cause BSODs. Please remove it to see whether it is the cause.

Uninstallation Instructions: http://www.jcgriff2.com/A-V_Removal_Tools/KIS_Removal.html

2. A lot of the dump files either blamed graphics drivers, or occured when graphics intensive applications were running. Your graphics drivers appear to be up-to-date (check for updates here anyway: http://www.nvidia.com/Download/index.aspx?lang=en-us ) so a software issue is unlikely. It is possible that your graphics card could be faulty, so run a stress test on it.
usasma said:
FurMark Setup:
Download from here: http://www.ozone3d.net/benchmarks/fur/
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit
3.

Code:
[font=lucida console]nvm62x32.sys Sat Oct 18 10:00:39 [COLOR=Red]2008[/COLOR][/font]
Your Nvidia networking driver is out of date. Find out what your motherboard chipset is (the info will be on your motherboard manufacturers site) and then download the nForce driver update from here: http://www.nvidia.com/Download/index.aspx?lang=en-us

Regards,
Reventon

BUGCHECK SUMMARY
Code:
[font=lucida console]
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Mon Jul  5 16:02:52.954 2010 (GMT+12)
System Uptime: 0 days 3:03:04.735
BugCheck D1, {815a58c3, 1a, 8, 815a58c3}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+153b7e )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Mon Jul  5 12:58:37.921 2010 (GMT+12)
System Uptime: 0 days 1:02:52.703
BUGCHECK_STR:  0xF7_ONE_BIT
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Mon Jul  5 11:20:32.456 2010 (GMT+12)
System Uptime: 0 days 1:36:30.237
BugCheck A, {7c5a0c, ff, 0, 82c832d6}
Probably caused by : ntkrpamp.exe ( nt!KiExecuteAllDpcs+1a )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Mon Jul  5 09:42:52.519 2010 (GMT+12)
System Uptime: 0 days 4:14:33.300
BugCheck A, {744b8b00, 2, 1, 83025b20}
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2cf )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Mon Jul  5 05:27:09.985 2010 (GMT+12)
System Uptime: 0 days 0:23:47.735
BUGCHECK_STR:  0xF7_ONE_BIT
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun Jul  4 19:25:57.200 2010 (GMT+12)
System Uptime: 0 days 0:18:26.855
BugCheck D1, {af3e3bd0, 2, 0, 9114c728}
Probably caused by : afd.sys ( afd!AfdFastDatagramReceive+75 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  iw4mp.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun Jul  4 19:05:35.427 2010 (GMT+12)
System Uptime: 0 days 4:28:32.193
BugCheck 100000B8, {82d70280, 87d76a48, 82d63fd0, 0}
Probably caused by : ntkrpamp.exe ( nt!KiIdleLoop+ce )
BUGCHECK_STR:  0xB8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun Jul  4 14:36:21.622 2010 (GMT+12)
System Uptime: 0 days 0:05:08.403
BugCheck A, {7c5a0c, ff, 0, 82ca92d6}
Probably caused by : ntkrpamp.exe ( nt!KiExecuteAllDpcs+1a )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun Jul  4 14:30:29.912 2010 (GMT+12)
System Uptime: 0 days 0:33:11.693
BugCheck A, {7c5a0c, ff, 0, 82cb02d6}
Probably caused by : ntkrpamp.exe ( nt!KiExecuteAllDpcs+1a )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun Jul  4 13:56:22.893 2010 (GMT+12)
System Uptime: 0 days 0:10:16.674
BUGCHECK_STR:  0xF7_ONE_BIT
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun Jul  4 13:45:22.598 2010 (GMT+12)
System Uptime: 0 days 0:38:45.379
BugCheck A, {ffffffc8, 2, 1, 82c86f80}
Probably caused by : ntkrpamp.exe ( nt!`string'+11a4 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun Jul  4 13:05:54.896 2010 (GMT+12)
System Uptime: 0 days 0:25:08.646
BugCheck 1000008E, {c0000005, 40107, 82d705d0, 0}
Probably caused by : dfsc.sys ( dfsc!g_DfscTimer+18 )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun Jul  4 11:10:41.792 2010 (GMT+12)
System Uptime: 0 days 1:04:47.574
BUGCHECK_STR:  0xF7_ONE_BIT
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun Jul  4 10:05:10.529 2010 (GMT+12)
System Uptime: 0 days 3:39:29.294
BUGCHECK_STR:  0xF7_ONE_BIT
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sat Jul  3 20:05:16.146 2010 (GMT+12)
System Uptime: 0 days 0:58:49.927
BUGCHECK_STR:  0xF7_ONE_BIT
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sat Jul  3 19:05:42.757 2010 (GMT+12)
System Uptime: 0 days 3:26:49.539
BugCheck A, {827c44ec, 2, 0, 82c6e16c}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessCompletedQueuePacketInternal+43a )
BUGCHECK_STR:  0xA
PROCESS_NAME:  iw4mp.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sat Jul  3 10:59:12.489 2010 (GMT+12)
System Uptime: 0 days 1:05:11.270
BugCheck D1, {cb4f7b, 2, 8, cb4f7b}
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2cf )
PROCESS_NAME:  System
BUGCHECK_STR:  0xD1
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sat Jul  3 09:53:19.533 2010 (GMT+12)
System Uptime: 0 days 5:00:33.298
*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
BUGCHECK_STR:  0x50
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Fri Jul  2 16:11:01.112 2010 (GMT+12)
System Uptime: 0 days 0:19:29.877
BugCheck A, {827c6600, 2, 1, 82ca492c}
Probably caused by : ntkrpamp.exe ( nt!KiInsertTimerTable+128 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  Wow.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Fri Jul  2 15:50:23.035 2010 (GMT+12)
System Uptime: 0 days 10:06:52.800
BugCheck A, {744b8b00, 2, 1, 83023b20}
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2cf )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Thu Jul  1 16:25:28.593 2010 (GMT+12)
System Uptime: 0 days 3:36:45.375
BUGCHECK_STR:  0xF7_ONE_BIT
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Thu Jul  1 12:48:00.677 2010 (GMT+12)
System Uptime: 0 days 0:16:51.458
BugCheck 100000B8, {82d84280, 8792b2b8, 82d77fd0, 0}
Probably caused by : ntkrpamp.exe ( nt!KiIdleLoop+ce )
BUGCHECK_STR:  0xB8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Thu Jul  1 12:30:24.917 2010 (GMT+12)
System Uptime: 0 days 7:37:19.683
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Wed Jun 30 18:58:05.068 2010 (GMT+12)
System Uptime: 0 days 14:13:51.849
BUGCHECK_STR:  0x50
PROCESS_NAME:  iw4mp.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 16:07:33.896 2010 (GMT+12)
System Uptime: 0 days 0:17:09.677
BugCheck D1, {ab4e3bd0, 2, 0, 90d70728}
Probably caused by : afd.sys ( afd!AfdFastDatagramReceive+75 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  iw4mp.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 15:49:16.605 2010 (GMT+12)
System Uptime: 0 days 0:10:21.386
BugCheck A, {823465ec, ff, 0, 82a832d6}
Probably caused by : ntkrpamp.exe ( nt!KiExecuteAllDpcs+1a )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 15:37:46.448 2010 (GMT+12)
System Uptime: 0 days 1:14:35.213
BUGCHECK_STR:  0x50
PROCESS_NAME:  iw4mp.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 14:22:02.565 2010 (GMT+12)
System Uptime: 0 days 0:49:04.331
BugCheck A, {7c5a0c, ff, 0, 82a772d6}
Probably caused by : ntkrpamp.exe ( nt!KiExecuteAllDpcs+1a )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 13:31:49.040 2010 (GMT+12)
System Uptime: 0 days 0:26:21.821
BUGCHECK_STR:  0xF7_ONE_BIT
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 13:04:16.863 2010 (GMT+12)
System Uptime: 0 days 0:33:36.644
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
BugCheck 1000008E, {c000001d, 821a48c4, 807e0a50, 0}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+153b7e )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 12:29:31.777 2010 (GMT+12)
System Uptime: 0 days 0:28:58.542
BUGCHECK_STR:  0xF7_ONE_BIT
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 11:59:24.245 2010 (GMT+12)
System Uptime: 0 days 0:07:11.026
BugCheck A, {827c5a3c, 2, 1, 82aa58dc}
Probably caused by : ntkrpamp.exe ( nt!KiDeferredReadyThread+625 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 11:51:27.877 2010 (GMT+12)
System Uptime: 0 days 1:17:29.659
BugCheck A, {7c5a0c, ff, 0, 82aaf2d6}
Probably caused by : ntkrpamp.exe ( nt!KiExecuteAllDpcs+1a )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 10:32:50.038 2010 (GMT+12)
System Uptime: 0 days 0:09:42.819
BugCheck A, {7c5a0c, ff, 0, 82a6b2d6}
Probably caused by : ntkrpamp.exe ( nt!KiExecuteAllDpcs+1a )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 07:32:47.330 2010 (GMT+12)
System Uptime: 0 days 0:03:45.111
BUGCHECK_STR:  0xF7_ONE_BIT
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 07:28:20.688 2010 (GMT+12)
System Uptime: 0 days 1:44:24.469
BugCheck A, {7c5a0c, ff, 0, 82a872d6}
Probably caused by : ntkrpamp.exe ( nt!KiExecuteAllDpcs+1a )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 05:40:34.010 2010 (GMT+12)
System Uptime: 0 days 0:11:46.791
BugCheck A, {2000000, 2, 1, 82a72360}
Probably caused by : ntkrpamp.exe ( nt!KiCommitThreadWait+11c )
BUGCHECK_STR:  0xA
PROCESS_NAME:  Wow.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 05:28:03.393 2010 (GMT+12)
System Uptime: 0 days 0:36:59.159
BugCheck A, {823495ec, ff, 0, 82a862d6}
Probably caused by : ntkrpamp.exe ( nt!KiExecuteAllDpcs+1a )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Mon Jun 28 16:31:35.230 2010 (GMT+12)
System Uptime: 0 days 0:04:11.011
BugCheck A, {7c5a0c, ff, 0, 82abe2d6}
Probably caused by : ntkrpamp.exe ( nt!KiExecuteAllDpcs+1a )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Mon Jun 28 16:26:43.597 2010 (GMT+12)
System Uptime: 0 days 0:07:25.378
BUGCHECK_STR:  0xF7_ONE_BIT
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Mon Jun 28 16:18:32.559 2010 (GMT+12)
System Uptime: 0 days 0:08:28.340
BugCheck A, {4b, 2, 1, 82a3af7b}
Probably caused by : hardware ( nt!KiTrap0E+2cf )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Mon Jun 28 16:09:15.225 2010 (GMT+12)
System Uptime: 0 days 0:13:42.991
BUGCHECK_STR:  0xF7_ONE_BIT
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Mon Jun 28 15:54:24.200 2010 (GMT+12)
System Uptime: 0 days 0:53:28.981
BugCheck A, {7c5a0c, ff, 0, 82aa32d6}
Probably caused by : ntkrpamp.exe ( nt!KiExecuteAllDpcs+1a )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Mon Jun 28 14:59:46.484 2010 (GMT+12)
System Uptime: 0 days 0:31:14.265
BugCheck A, {827c6858, 2, 1, 82a72abf}
Probably caused by : ntkrpamp.exe ( nt!KiInsertTimerTable+2bb )
BUGCHECK_STR:  0xA
PROCESS_NAME:  Wow.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Mon Jun 28 14:27:22.969 2010 (GMT+12)
System Uptime: 0 days 1:16:47.750
BugCheck A, {2000000, 2, 1, 82a8a360}
Probably caused by : ntkrpamp.exe ( nt!KiCommitThreadWait+11c )
BUGCHECK_STR:  0xA
PROCESS_NAME:  Wow.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun Jun 27 17:53:03.822 2010 (GMT+12)
System Uptime: 0 days 0:26:45.603
BugCheck A, {7c5a0c, ff, 0, 82aac2d6}
Probably caused by : ntkrpamp.exe ( nt!KiExecuteAllDpcs+1a )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun Jun 27 17:24:54.605 2010 (GMT+12)
System Uptime: 0 days 2:00:06.386
BugCheck A, {2000000, 2, 1, 82a74360}
Probably caused by : ntkrpamp.exe ( nt!KiCommitThreadWait+11c )
BUGCHECK_STR:  0xA
PROCESS_NAME:  Wow.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun Jun 27 15:23:39.379 2010 (GMT+12)
System Uptime: 0 days 0:06:10.161
BUGCHECK_STR:  0x50
PROCESS_NAME:  iw4mp.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun Jun 27 15:16:46.265 2010 (GMT+12)
System Uptime: 0 days 0:00:25.031
BugCheck D1, {9f9b8c, 2, 0, 90b5e320}
Probably caused by : afd.sys ( afd!AfdFastConnectionReceive+d7 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  Steam.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun Jun 27 15:13:09.833 2010 (GMT+12)
System Uptime: 0 days 0:15:09.614
BugCheck A, {2000000, 2, 1, 82a74360}
Probably caused by : ntkrpamp.exe ( nt!KiCommitThreadWait+11c )
BUGCHECK_STR:  0xA
PROCESS_NAME:  Wow.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]
 

· Registered
Joined
·
4 Posts
Discussion Starter · #8 ·
Hi I uninstalled kaspersky and I ran the test and it capped at 104 degrees celcius.
I tried to find the nforce drivers but it is nforce 430 and they dont have 400 series nforce drivers anymore on their website and i couldn'yt find them on google. i think it might be the video card though
 

· TSF Team Emeritus
Joined
·
6,274 Posts
Hi I uninstalled kaspersky and I ran the test and it capped at 104 degrees celcius.
I tried to find the nforce drivers but it is nforce 430 and they dont have 400 series nforce drivers anymore on their website and i couldn'yt find them on google. i think it might be the video card though
It is definitely a motherboard networking driver. Try your motherboard manufacturer's site. If you cannot find them then do not worry about that. Kaspersky was a greater threat to your system.
 

· TSF Team Emeritus, Microsoft MVP
Joined
·
7,498 Posts
104º C is way, way too hot!!! I would investigate cooling solutions for your video card immediately.

As for the nForce drivers, check under "Legacy" under "Product Type" at the nVidia website.
While the page doesn't let you pick Win7 drivers, if you select Vista and go to the next page you'll find that they are Win7/Vista drivers: http://www.nvidia.com/object/nforce_vista_win7_32bit_15.49.html
 
1 - 10 of 10 Posts
Status
Not open for further replies.
Top