- Thread Author
- #1
New system I built and get bsod when computer sits for a while with no use then I come back and it usually happens while surfing the internet with internet explorer.
I would really appreciate any help!
Thank you
I apologize for uploading files separate. zip file would not upload and a few files from the folder also would not upload. don't know why?
Hopefully the files that did upload is enough info someone can help.
I would really appreciate any help!
Thank you
I apologize for uploading files separate. zip file would not upload and a few files from the folder also would not upload. don't know why?
Hopefully the files that did upload is enough info someone can help.
Attachments
-
052313-10530-01.dmp282.1 KB · Views: 333
-
052413-11263-01.dmp287.6 KB · Views: 316
-
052513-10966-01.dmp287.6 KB · Views: 306
-
052713-10358-01.dmp287.5 KB · Views: 313
-
052813-10888-01.dmp281.7 KB · Views: 311
-
053113-10296-01.dmp287.6 KB · Views: 316
-
060513-10405-01.dmp280.8 KB · Views: 306
-
060813-10498-01.dmp287.6 KB · Views: 315
-
060813-10982-01.dmp286.8 KB · Views: 302
-
060813-10998-01.dmp281.3 KB · Views: 312
-
061013-10233-01.dmp287.1 KB · Views: 308
-
061113-10826-01.dmp283.3 KB · Views: 301
-
061313-10030-01.dmp285 KB · Views: 287
-
061513-7753-01.dmp287.5 KB · Views: 306
-
061513-7940-01.dmp282.1 KB · Views: 316
-
dxdiag.txt42.6 KB · Views: 287
-
DriverList.txt19.4 KB · Views: 261
-
Hosts.txt824 bytes · Views: 264
-
SystemInfo.txt7.9 KB · Views: 284
- Joined
- Mar 22, 2010
- Messages
- 3,052
Still need the MSINFO32.nfo file. If it won't upload here, upload it to a free file hosting site and post a link to it here.
Only 136 Windows Updates installed. Most systems have 160 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).
There is some older driver running out of your Temp folders. The latest one is tmpDB8F.tmp and is running out of C:\Users\muscle34\AppData\Local\Temp\tmpDB8F.tmp See if you can locate it, right click on it, and see what info it gives you.
Broadcom NetXtreme II and Western Digital software drivers both date from 2008 - but do not have the same date/timestamp as the .tmp drivers. Still, I'd suggest un-installing both the Broadcom software and the Western Digital software (as it's known to cause BSOD's).
Remove the Elby program that uses the ElbyCDIO Filter Driver (ElbyCDFL.sys). It dates from 2006. This is most likely an older program from Elaborate Bytes.
AnyDVD was seen in the raw stack text. While this isn't definitive, it'd be worthwhile uninstalling it to see if it helps stop the BSOD's.
Analysis:
The following is for informational purposes only.
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Link Removed
tmpDB8F.tmp - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
BrUsbSIb.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
BrSerIb.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
tmp56B6.tmp - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
tmp5E26.tmp - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
tmpB5F5.tmp - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
tmpAE09.tmp - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
tmp6F07.tmp - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
tmp2EBD.tmp - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
tmp87D4.tmp - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
tmp621C.tmp - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Only 136 Windows Updates installed. Most systems have 160 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).
There is some older driver running out of your Temp folders. The latest one is tmpDB8F.tmp and is running out of C:\Users\muscle34\AppData\Local\Temp\tmpDB8F.tmp See if you can locate it, right click on it, and see what info it gives you.
Broadcom NetXtreme II and Western Digital software drivers both date from 2008 - but do not have the same date/timestamp as the .tmp drivers. Still, I'd suggest un-installing both the Broadcom software and the Western Digital software (as it's known to cause BSOD's).
Remove the Elby program that uses the ElbyCDIO Filter Driver (ElbyCDFL.sys). It dates from 2006. This is most likely an older program from Elaborate Bytes.
AnyDVD was seen in the raw stack text. While this isn't definitive, it'd be worthwhile uninstalling it to see if it helps stop the BSOD's.
Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Sat Jun 15 13:56:10.846 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061513-7940-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 6:00:17.689[/B]
Probably caused by :[B]Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/B]
BugCheck [B]101, {11, 0, fffff88003257180, 9}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000011, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003257180, The PRCB address of the hung processor.
Arg4: 0000000000000009, 0.
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_c_PROC
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_CLOCK_WATCHDOG_TIMEOUT_c_PROC_ANALYSIS_INCONCLUSIVE[/B]
CPUID: "Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz"
MaxSpeed: 3200
CurrentSpeed: [B]3201[/B]
BIOS Version 4005
BIOS Release Date 04/18/2013
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jun 15 00:03:21.700 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061513-7753-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 2:04:43.932[/B]
Probably caused by :[B]Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/B]
BugCheck [B]101, {11, 0, fffff88003257180, 9}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000011, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003257180, The PRCB address of the hung processor.
Arg4: 0000000000000009, 0.
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_c_PROC
PROCESS_NAME: WmiPrvSE.exe
FAILURE_BUCKET_ID: [B]X64_CLOCK_WATCHDOG_TIMEOUT_c_PROC_ANALYSIS_INCONCLUSIVE[/B]
CPUID: "Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz"
MaxSpeed: 3200
CurrentSpeed: [B]3201[/B]
BIOS Version 4005
BIOS Release Date 04/18/2013
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jun 13 22:05:53.970 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061313-10030-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 1:49:59.217[/B]
Probably caused by :[B]Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/B]
BugCheck [B]101, {11, 0, fffff88003257180, 9}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000011, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003257180, The PRCB address of the hung processor.
Arg4: 0000000000000009, 0.
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_c_PROC
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_CLOCK_WATCHDOG_TIMEOUT_c_PROC_ANALYSIS_INCONCLUSIVE[/B]
CPUID: "Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz"
MaxSpeed: 3200
CurrentSpeed: [B]3201[/B]
BIOS Version 4005
BIOS Release Date 04/18/2013
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jun 11 22:07:33.698 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061113-10826-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:53:29.945[/B]
Probably caused by :[B]Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/B]
BugCheck [B]101, {11, 0, fffff88003257180, 9}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000011, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003257180, The PRCB address of the hung processor.
Arg4: 0000000000000009, 0.
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_c_PROC
PROCESS_NAME: svchost.exe
FAILURE_BUCKET_ID: [B]X64_CLOCK_WATCHDOG_TIMEOUT_c_PROC_ANALYSIS_INCONCLUSIVE[/B]
CPUID: "Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz"
MaxSpeed: 3200
CurrentSpeed: [B]3201[/B]
BIOS Version 4005
BIOS Release Date 04/18/2013
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jun 10 19:51:17.876 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061013-10233-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 3:10:08.123[/B]
Probably caused by :[B]Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/B]
BugCheck [B]101, {11, 0, fffff880032c9180, a}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000011, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880032c9180, The PRCB address of the hung processor.
Arg4: 000000000000000a, 0.
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_c_PROC
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_CLOCK_WATCHDOG_TIMEOUT_c_PROC_ANALYSIS_INCONCLUSIVE[/B]
CPUID: "Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz"
MaxSpeed: 3200
CurrentSpeed: [B]3201[/B]
BIOS Version 4005
BIOS Release Date 04/18/2013
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jun 8 22:11:26.487 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\060813-10982-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:57:00.331[/B]
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by :[B]Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/B]
BugCheck [B]101, {11, 0, fffff880009c0180, 8}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000011, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009c0180, The PRCB address of the hung processor.
Arg4: 0000000000000008, 0.
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_c_PROC
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_CLOCK_WATCHDOG_TIMEOUT_c_PROC_ANALYSIS_INCONCLUSIVE[/B]
CPUID: "Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz"
MaxSpeed: 3200
CurrentSpeed: [B]3201[/B]
BIOS Version 4005
BIOS Release Date 04/18/2013
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jun 8 19:01:13.257 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\060813-10998-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 5:58:57.504[/B]
Probably caused by :[B]Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/B]
BugCheck [B]101, {11, 0, fffff88003257180, 9}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000011, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003257180, The PRCB address of the hung processor.
Arg4: 0000000000000009, 0.
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_c_PROC
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_CLOCK_WATCHDOG_TIMEOUT_c_PROC_ANALYSIS_INCONCLUSIVE[/B]
CPUID: "Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz"
MaxSpeed: 3200
CurrentSpeed: [B]3201[/B]
BIOS Version 4005
BIOS Release Date 04/18/2013
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jun 8 13:01:08.444 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\060813-10498-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 6:06:38.691[/B]
Probably caused by :[B]Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/B]
BugCheck [B]101, {11, 0, fffff880009c0180, 8}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000011, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009c0180, The PRCB address of the hung processor.
Arg4: 0000000000000008, 0.
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_c_PROC
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_CLOCK_WATCHDOG_TIMEOUT_c_PROC_ANALYSIS_INCONCLUSIVE[/B]
CPUID: "Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz"
MaxSpeed: 3200
CurrentSpeed: [B]3201[/B]
BIOS Version 4005
BIOS Release Date 04/18/2013
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jun 5 17:08:09.175 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\060513-10405-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:06:36.422[/B]
Probably caused by :[B]Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/B]
BugCheck [B]101, {11, 0, fffff880009c0180, 8}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000011, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009c0180, The PRCB address of the hung processor.
Arg4: 0000000000000008, 0.
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_c_PROC
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_CLOCK_WATCHDOG_TIMEOUT_c_PROC_ANALYSIS_INCONCLUSIVE[/B]
CPUID: "Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz"
MaxSpeed: 3200
CurrentSpeed: [B]3201[/B]
BIOS Version 4005
BIOS Release Date 04/18/2013
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code:
[font=lucida console]**************************Sat Jun 15 13:56:10.846 2013 (UTC - 4:00)**************************
[COLOR=RED][B]ElbyCDFL.sys Thu Dec 14 16:22:27 2006 (4581C093)[/B][/COLOR]
[COLOR=RED][B]tmpDB8F.tmp Sat Jul 26 09:29:37 2008 (488B26C1)[/B][/COLOR]
intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
BrUsbSIb.sys Mon Nov 2 22:06:35 2009 (4AEF9E3B)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
btath_bus.sys Thu Jun 24 02:17:43 2010 (4C22F887)
AsUpIO.sys Mon Aug 2 22:47:59 2010 (4C57835F)
nx6000.sys Thu Dec 2 17:23:39 2010 (4CF81C6B)
CLBStor.sys Mon Jul 11 04:49:51 2011 (4E1AB92F)
asmtxhci.sys Wed Nov 2 23:00:22 2011 (4EB203C6)
asmthub3.sys Wed Nov 2 23:00:32 2011 (4EB203D0)
asahci64.sys Thu Jan 5 00:08:19 2012 (4F053043)
BrSerIb.sys Tue Jul 31 07:54:47 2012 (5017C787)
e1c62x64.sys Fri Aug 10 18:44:15 2012 (50258EBF)
AsIO.sys Wed Aug 22 05:54:47 2012 (5034AC67)
HECIx64.sys Mon Dec 17 14:32:21 2012 (50CF7345)
avgntflt.sys Fri Feb 22 04:33:47 2013 (51273B7B)
avkmgr.sys Fri Feb 22 04:33:49 2013 (51273B7D)
avipbb.sys Fri Feb 22 04:33:53 2013 (51273B81)
nvhda64v.sys Mon Feb 25 00:27:35 2013 (512AF647)
ElbyCDIO.sys Mon Mar 4 04:21:51 2013 (513467AF)
eudskacs.sys Sat Mar 16 00:32:13 2013 (5143F5CD)
eubakup.sys Sat Mar 16 00:32:18 2013 (5143F5D2)
EUBKMON.sys Sat Mar 16 00:32:37 2013 (5143F5E5)
EuFdDisk.sys Sat Mar 16 00:32:42 2013 (5143F5EA)
nvlddmkm.sys Sun May 12 15:09:45 2013 (518FE8F9)
AnyDVD.sys Sun May 19 07:04:47 2013 (5198B1CF)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jun 15 00:03:21.700 2013 (UTC - 4:00)**************************
[COLOR=RED][B]tmp56B6.tmp Sat Jul 26 09:29:37 2008 (488B26C1)[/B][/COLOR]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jun 13 22:05:53.970 2013 (UTC - 4:00)**************************
[COLOR=RED][B]tmp5E26.tmp Sat Jul 26 09:29:37 2008 (488B26C1)[/B][/COLOR]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jun 11 22:07:33.698 2013 (UTC - 4:00)**************************
[COLOR=RED][B]tmpB5F5.tmp Sat Jul 26 09:29:37 2008 (488B26C1)[/B][/COLOR]
btath_rcp.sys Thu Jun 24 02:17:21 2010 (4C22F871)
btath_flt.sys Thu Jun 24 02:17:38 2010 (4C22F882)
btath_hcrp.sys Tue Jun 29 05:30:43 2010 (4C29BD43)
btath_lwflt.sys Mon Sep 13 04:26:54 2010 (4C8DE04E)
btath_a2dp.sys Mon Feb 14 20:47:47 2011 (4D59DB43)
btfilter.sys Tue Mar 8 01:15:22 2011 (4D75C97A)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jun 10 19:51:17.876 2013 (UTC - 4:00)**************************
[COLOR=RED][B]tmpAE09.tmp Sat Jul 26 09:29:37 2008 (488B26C1)[/B][/COLOR]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jun 8 22:11:26.487 2013 (UTC - 4:00)**************************
[COLOR=RED][B]tmp6F07.tmp Sat Jul 26 09:29:37 2008 (488B26C1)[/B][/COLOR]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jun 8 19:01:13.257 2013 (UTC - 4:00)**************************
[COLOR=RED][B]tmp2EBD.tmp Sat Jul 26 09:29:37 2008 (488B26C1)[/B][/COLOR]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jun 8 13:01:08.444 2013 (UTC - 4:00)**************************
[COLOR=RED][B]tmp87D4.tmp Sat Jul 26 09:29:37 2008 (488B26C1)[/B][/COLOR]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jun 5 17:08:09.175 2013 (UTC - 4:00)**************************
[COLOR=RED][B]tmp621C.tmp Sat Jul 26 09:29:37 2008 (488B26C1)[/B][/COLOR]
rikvm_38F51D56.sys Mon May 14 03:49:40 2012 (4FB0B914)
[/font]
tmpDB8F.tmp - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
BrUsbSIb.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
BrSerIb.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
tmp56B6.tmp - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
tmp5E26.tmp - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
tmpB5F5.tmp - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
tmpAE09.tmp - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
tmp6F07.tmp - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
tmp2EBD.tmp - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
tmp87D4.tmp - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
tmp621C.tmp - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
- Thread Author
- #3
Ok, First off thank you!
this file was not in the location. "There is some older driver running out of your Temp folders. The latest one is tmpDB8F.tmp and is running out of C:\Users\muscle34\AppData\Local\Temp\tmpDB8F.tmp See if you can locate it, right click on it, and see what info it gives you".
I have removed "the Elby program that uses the ElbyCDIO Filter Driver (ElbyCDFL.sys). It dates from 2006. This is most likely an older program from Elaborate Bytes".
"AnyDVD was seen in the raw stack text. While this isn't definitive, it'd be worthwhile uninstalling it to see if it helps stop the BSOD's".
I can't find anything on my system to these. "Broadcom NetXtreme II and Western Digital software drivers both date from 2008"
I was able to zip and upload the msinfo file.
"Still need the MSINFO32.nfo file".
ok and when I go to windows update it says my windows is up to date?
"Only 136 Windows Updates installed. Most systems have 160 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all)".
sorry never used forum's before so if I do something wrong just let me know please. I'v been building computers since 1990 and never had a problem I could not figure out till now.
![frown :frown: :frown:](/images/smilies/frown.png)
this file was not in the location. "There is some older driver running out of your Temp folders. The latest one is tmpDB8F.tmp and is running out of C:\Users\muscle34\AppData\Local\Temp\tmpDB8F.tmp See if you can locate it, right click on it, and see what info it gives you".
I have removed "the Elby program that uses the ElbyCDIO Filter Driver (ElbyCDFL.sys). It dates from 2006. This is most likely an older program from Elaborate Bytes".
"AnyDVD was seen in the raw stack text. While this isn't definitive, it'd be worthwhile uninstalling it to see if it helps stop the BSOD's".
I can't find anything on my system to these. "Broadcom NetXtreme II and Western Digital software drivers both date from 2008"
I was able to zip and upload the msinfo file.
"Still need the MSINFO32.nfo file".
ok and when I go to windows update it says my windows is up to date?
"Only 136 Windows Updates installed. Most systems have 160 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all)".
sorry never used forum's before so if I do something wrong just let me know please. I'v been building computers since 1990 and never had a problem I could not figure out till now.
![frown :frown: :frown:](/images/smilies/frown.png)
- Thread Author
- #4
Here are the other 3 files that did not upload initially I was able to zip them and upload.
Hope it helps you.. to help me![Smile :) :)](https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png)
Hope it helps you.. to help me
![Smile :) :)](https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png)
- Joined
- Mar 22, 2010
- Messages
- 3,052
SSD's were temperamental when they first came out, but their reliability has improved greatly over the last year or two. There are 2 things that MUST be checked on systems with BSOD's and SSD's:
Your Bluetooth is disabled. Is this deliberate? If so, why?
Please enable the Bluetooth, update it's drivers, then disable it again (if that's how you want it).
There are a lot of Live Kernel Events in the Event Viewer logs. This is Windows saying that it doesn't know why the system restarted. Often this is a hardware issue, so I'd suggest these 2 things:
1) monitor your temps with this free utility: HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools
2) run these free hardware diagnostics: Link Removed
Let us know the results of the temp monitoring and the hardware diagnostics and we'll move on from there.
1) That the SSD firmware is the latest available for the SSD
2) That the storage controller drivers on the motherboard are the most recent. They must date from late 2012 or later. This is ALL controllers, not just the one that the SSD is attached to.
Your Bluetooth is disabled. Is this deliberate? If so, why?
Please enable the Bluetooth, update it's drivers, then disable it again (if that's how you want it).
There are a lot of Live Kernel Events in the Event Viewer logs. This is Windows saying that it doesn't know why the system restarted. Often this is a hardware issue, so I'd suggest these 2 things:
1) monitor your temps with this free utility: HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools
2) run these free hardware diagnostics: Link Removed
Let us know the results of the temp monitoring and the hardware diagnostics and we'll move on from there.
- Thread Author
- #6
Similar threads
- Replies
- 0
- Views
- 739
- Replies
- 1
- Views
- 844
- Replies
- 0
- Views
- 113
- Replies
- 5
- Views
- 780
- Article
- Replies
- 3
- Views
- 606