RAM was defective... but BSOD's still happen!

P

Pablo

Well-known member
Joined
May 9, 2014
Posts
73
Location
Argentina
Hello friends, this case is special because it's an old computer whose only purpose is to control an specialized spectrometer.... It runs WinXP! and there seems to be no software updates for that piece of equipment so we have to stick to this unsopported OS....
Random BSOD's began to occur and Memtest showed errors... so RAM was replaced... Now a full overnight memtest (10+ passes) shows a clean RAM... but BSOD's keep happening! can someone shed some light on this please?

Here are the minidumps:
View attachment Minidump LAB ACERIA.rar

I know this is not the procedure to post BSOD's, but I don't have physical access to the computer currently.

Thanks in advance!
 
Pablo said:
Here are the minidumps:
View attachment 37977

I know this is not the procedure to post BSOD's, but I don't have physical access to the computer currently.
Click to expand...

I understand that you don't have physical access to the system, but you still should be able to run the jcgriff2/Sysnative app found in the BSOD Posting Instructions (step 1) - Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 + Vista

After all, you were able to gather the mini kernel memory dumps; upload them and attach the RAR file to your opening post.

So, please run the app and upload/attach the resulting ZIP file to your next post.

One reason for doing this is that I need some information from the ~25 system/software files that the app generates because a reply to your October 2017 BSOD thread questioned the authenticity of your Windows installation -

axe0 said:
It appears that the OS is counterfeit, an OEM key with a retail motherboard.

We do not provide support whilst there is piracy present on your system.
Please perform a clean install with a genuine copy before looking for further help.
Click to expand...

I ran (processed) 21 of the 81 dumps (all had a July 2018 timestamp on them) and see definite indicators in the dumps of a non-genuine Windows OS (possibly counterfeit) in the form of symbol errors on Microsoft Windows OS files, including the Windows kernel.

File symbol errors occur when the file(s) in your system cannot be identified (compared to successfully) the Microsoft Windows OS related files at the Microsoft MSDL symbol server site (MSDN). Every Microsoft Windows XP OS-related file should be able to be identified/ find a match for at the Microsoft MSDL symbol server site. Many Microsoft Windows files in your system cannot be identified/ cannot find a match for it at the MSDL symbol server site.

There should not be any Microsoft Windows OS-related file symbol errors on a Windows XP system as there have not been any new Microsoft Windows XP files issued in well over 10 years.

Lastly, you have experienced BSODs in just about every month since May 2017 -
Code: 
Mini052917-01.dmp                            	 90112	5/29/2017	7:07:20 AM	A
Mini061317-01.dmp                            	 90112	6/13/2017	9:56:08 AM	A
Mini061917-01.dmp                            	 90112	6/19/2017	6:06:28 AM	A
Mini061917-02.dmp                            	 90112	6/19/2017	2:01:30 PM	A
Mini062117-01.dmp                            	 90112	6/21/2017	6:08:48 AM	A
Mini062117-02.dmp                            	 90112	6/21/2017	12:45:10 PM	A
Mini071717-01.dmp                            	 90112	7/17/2017	7:49:00 AM	A
Mini071817-01.dmp                            	 90112	7/18/2017	5:51:02 AM	A
Mini071917-02.dmp                            	 90112	7/19/2017	5:38:48 AM	A
Mini071917-01.dmp                            	 90112	7/19/2017	5:51:04 AM	A
Mini072017-01.dmp                            	 90112	7/20/2017	5:48:06 AM	A
Mini072117-01.dmp                            	 90112	7/21/2017	5:00:30 AM	A
Mini072117-02.dmp                            	 90112	7/21/2017	9:20:18 AM	A
Mini072617-01.dmp                            	 90112	7/26/2017	5:38:46 AM	A
Mini080117-01.dmp                            	 90112	8/1/2017	5:38:28 AM	A
Mini080317-01.dmp                            	 90112	8/3/2017	5:50:22 AM	A
Mini080317-02.dmp                            	 90112	8/3/2017	8:37:24 AM	A
Mini080917-01.dmp                            	 90112	8/9/2017	6:45:34 AM	A
Mini081317-01.dmp                            	 90112	8/13/2017	3:43:20 AM	A
Mini081417-01.dmp                            	 90112	8/14/2017	6:53:34 AM	A
Mini081517-01.dmp                            	 90112	8/15/2017	5:53:08 AM	A
Mini081517-02.dmp                            	 90112	8/15/2017	7:40:36 AM	A
Mini081617-01.dmp                            	 90112	8/16/2017	2:38:14 PM	A
Mini081817-01.dmp                            	 90112	8/18/2017	8:26:24 AM	A
Mini082217-01.dmp                            	 90112	8/22/2017	2:11:46 PM	A
Mini083017-01.dmp                            	 90112	8/30/2017	7:58:22 AM	A
Mini091717-01.dmp                            	 90112	9/17/2017	3:58:30 AM	A
Mini102217-01.dmp                            	 90112	10/22/2017	6:48:28 AM	A
Mini011818-01.dmp                            	 90112	1/18/2018	11:38:32 AM	A
Mini012318-01.dmp                            	 90112	1/23/2018	6:07:08 AM	A
Mini012418-01.dmp                            	 90112	1/24/2018	4:06:46 AM	A
Mini020918-01.dmp                            	 90112	2/9/2018	12:41:40 PM	A
Mini032218-01.dmp                            	 90112	3/22/2018	7:17:24 PM	A
Mini040418-01.dmp                            	 90112	4/4/2018	10:39:44 AM	A
Mini040618-01.dmp                            	 90112	4/6/2018	6:58:22 PM	A
Mini050318-01.dmp                            	 90112	5/3/2018	5:10:10 AM	A
Mini051418-01.dmp                            	 90112	5/14/2018	7:04:52 AM	A
Mini051618-01.dmp                            	 90112	5/16/2018	3:21:56 AM	A
Mini052218-01.dmp                            	 90112	5/22/2018	8:18:22 PM	A
Mini052318-01.dmp                            	 90112	5/23/2018	9:16:48 AM	A
Mini053118-01.dmp                            	 90112	5/31/2018	7:41:52 AM	A
Mini060118-01.dmp                            	 90112	6/1/2018	10:16:42 PM	A
Mini060618-01.dmp                            	 90112	6/5/2018	11:55:50 PM	A
Mini060618-02.dmp                            	 90112	6/6/2018	5:00:24 AM	A
Mini060618-03.dmp                            	 90112	6/6/2018	10:50:48 AM	A
Mini060618-04.dmp                            	 90112	6/6/2018	10:52:34 AM	A
Mini060718-01.dmp                            	 90112	6/7/2018	10:49:18 AM	A
Mini060918-01.dmp                            	 90112	6/9/2018	1:52:08 PM	A
Mini061418-01.dmp                            	 90112	6/14/2018	9:12:26 AM	A
Mini061718-01.dmp                            	 90112	6/17/2018	12:18:50 PM	A
Mini061818-01.dmp                            	 90112	6/18/2018	9:12:28 PM	A
Mini061818-02.dmp                            	 90112	6/18/2018	9:13:00 PM	A
Mini062018-01.dmp                            	 90112	6/20/2018	3:14:32 AM	A
Mini062218-01.dmp                            	 90112	6/22/2018	8:37:20 PM	A
Mini062418-01.dmp                            	 90112	6/23/2018	11:36:02 PM	A
Mini062618-01.dmp                            	 90112	6/25/2018	11:33:54 PM	A
Mini062618-02.dmp                            	 90112	6/26/2018	6:56:50 PM	A
Mini062818-01.dmp                            	 90112	6/28/2018	9:40:28 AM	A
Mini062818-02.dmp                            	 90112	6/28/2018	1:36:46 PM	A
Mini062918-01.dmp                            	 90112	6/29/2018	12:03:00 AM	A
Mini070318-01.dmp                            	 90112	7/3/2018	5:16:06 AM	A
Mini070618-01.dmp                            	 90112	7/6/2018	10:48:22 AM	A
Mini071118-01.dmp                            	 90112	7/11/2018	8:57:06 AM	A
Mini071118-02.dmp                            	 90112	7/11/2018	8:20:12 PM	A
Mini071218-01.dmp                            	 90112	7/12/2018	10:48:52 AM	A
Mini071218-02.dmp                            	 90112	7/12/2018	12:28:38 PM	A
Mini071418-01.dmp                            	 90112	7/14/2018	9:14:54 AM	A
Mini071718-01.dmp                            	 90112	7/17/2018	12:40:14 PM	A
Mini071818-01.dmp                            	 90112	7/18/2018	8:55:02 AM	A
Mini071818-02.dmp                            	 90112	7/18/2018	3:15:34 PM	A
Mini071918-01.dmp                            	 90112	7/19/2018	10:21:32 AM	A
Mini072118-01.dmp                            	 90112	7/21/2018	5:09:50 AM	A
Mini072318-01.dmp                            	 90112	7/23/2018	6:53:40 AM	A
Mini072418-01.dmp                            	 90112	7/24/2018	5:30:36 AM	A
Mini072418-02.dmp                            	 90112	7/24/2018	12:31:42 PM	A
Mini072518-01.dmp                            	 90112	7/25/2018	4:05:48 AM	A
Mini072618-01.dmp                            	 90112	7/26/2018	5:52:22 PM	A
Mini072718-01.dmp                            	 90112	7/27/2018	6:29:46 AM	A
Mini072718-02.dmp                            	 90112	7/27/2018	10:31:12 AM	A
Mini073018-01.dmp                            	 90112	7/30/2018	7:00:16 AM	A
Mini073018-02.dmp                            	 90112	7/30/2018	7:05:34 AM	A

Regards. . .

jcgriff2


BSOD KERNEL DUMP PROCESSING SUMMARY
Code: 
[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\Mini073018-02.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Mon Jul 30 07:05:11.132 2018 (UTC - 4:00)
System Uptime: 0 days 0:05:02.164
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for atapi.sys
*** WARNING: Unable to verify timestamp for imapi.sys
*** ERROR: Module load completed but symbols could not be loaded for imapi.sys
*** WARNING: Unable to verify timestamp for PxHelp20.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHelp20.sys
*** WARNING: Unable to verify timestamp for CLASSPNP.SYS
*** ERROR: Module load completed but symbols could not be loaded for CLASSPNP.SYS
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!4249FA5420B000 )
BUGCHECK_STR:  4249FA54
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108_4249FA54_nt_wrong_symbols!4249FA5420B000
Bugcheck code 1000000A
Arguments 00000001 00000002 00000001 8053fa99
BiosVersion = 2.6.6 
BiosReleaseDate = 06/26/2011
SystemManufacturer = Dell Inc.                
SystemProductName = OptiPlex 745                 
MaxSpeed:     1800
CurrentSpeed: 1795
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\Mini073018-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Mon Jul 30 06:59:55.337 2018 (UTC - 4:00)
System Uptime: 2 days 20:28:48.273
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for netbt.sys
*** ERROR: Module load completed but symbols could not be loaded for netbt.sys
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!4249FA5420B000 )
BUGCHECK_STR:  4249FA54
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108_4249FA54_nt_wrong_symbols!4249FA5420B000
Bugcheck code 100000D1
Arguments a9d90000 00000002 00000008 a9d90000
BiosVersion = 2.6.6 
BiosReleaseDate = 06/26/2011
SystemManufacturer = Dell Inc.                
SystemProductName = OptiPlex 745                 
MaxSpeed:     1800
CurrentSpeed: 1795
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\Mini072718-02.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Fri Jul 27 10:30:49.839 2018 (UTC - 4:00)
System Uptime: 0 days 4:01:11.683
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : hardware ( win32k+185c66 )
DEFAULT_BUCKET_ID:  DRIVER_FAULT
BUGCHECK_STR:  0x8E
FAILURE_BUCKET_ID:  IP_MISALIGNED
Bugcheck code 1000008E
Arguments c0000005 8050513e f7690eac 00000000
BiosVersion = 2.6.6 
BiosReleaseDate = 06/26/2011
SystemManufacturer = Dell Inc.                
SystemProductName = OptiPlex 745                 
MaxSpeed:     1800
CurrentSpeed: 1795
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\Mini072718-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Fri Jul 27 06:29:23.565 2018 (UTC - 4:00)
System Uptime: 0 days 12:37:12.300
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for atapi.sys
*** WARNING: Unable to verify timestamp for CLASSPNP.SYS
*** ERROR: Module load completed but symbols could not be loaded for CLASSPNP.SYS
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!4249FA5420B000 )
BUGCHECK_STR:  4249FA54
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108_4249FA54_nt_wrong_symbols!4249FA5420B000
Bugcheck code 1000000A
Arguments 00000001 00000002 00000001 8053fa99
BiosVersion = 2.6.6 
BiosReleaseDate = 06/26/2011
SystemManufacturer = Dell Inc.                
SystemProductName = OptiPlex 745                 
MaxSpeed:     1800
CurrentSpeed: 1795
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\Mini072618-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Thu Jul 26 17:51:56.166 2018 (UTC - 4:00)
System Uptime: 0 days 7:55:28.214
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for HTTP.sys
*** ERROR: Module load completed but symbols could not be loaded for HTTP.sys
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!4249FA5420B000 )
BUGCHECK_STR:  4249FA54
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108_4249FA54_nt_wrong_symbols!4249FA5420B000
Bugcheck code 100000D1
Arguments 00000001 00000002 00000001 a90fea7f
BiosVersion = 2.6.6 
BiosReleaseDate = 06/26/2011
SystemManufacturer = Dell Inc.                
SystemProductName = OptiPlex 745                 
MaxSpeed:     1800
CurrentSpeed: 1795
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\Mini072518-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Wed Jul 25 04:05:20.794 2018 (UTC - 4:00)
System Uptime: 1 days 3:34:11.548
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!4249FA5420B000 )
BUGCHECK_STR:  4249FA54
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108_4249FA54_nt_wrong_symbols!4249FA5420B000
Bugcheck code 1000008E
Arguments c0000005 8058282b a99c4c0c 00000000
BiosVersion = 2.6.6 
BiosReleaseDate = 06/26/2011
SystemManufacturer = Dell Inc.                
SystemProductName = OptiPlex 745                 
MaxSpeed:     1800
CurrentSpeed: 1795
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\Mini072418-02.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Tue Jul 24 12:31:20.829 2018 (UTC - 4:00)
System Uptime: 0 days 7:00:49.425
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!4249FA5420B000 )
BUGCHECK_STR:  4249FA54
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108_4249FA54_nt_wrong_symbols!4249FA5420B000
Bugcheck code 1000000A
Arguments 00000002 00000002 00000001 806e4a8e
BiosVersion = 2.6.6 
BiosReleaseDate = 06/26/2011
SystemManufacturer = Dell Inc.                
SystemProductName = OptiPlex 745                 
MaxSpeed:     1800
CurrentSpeed: 1795
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\Mini072418-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Tue Jul 24 05:30:15.240 2018 (UTC - 4:00)
System Uptime: 0 days 22:36:41.175
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!4249FA5420B000 )
BUGCHECK_STR:  4249FA54
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108_4249FA54_nt_wrong_symbols!4249FA5420B000
Bugcheck code 1000000A
Arguments 000a37a8 0000001c 00000000 804fca5d
BiosVersion = 2.6.6 
BiosReleaseDate = 06/26/2011
SystemManufacturer = Dell Inc.                
SystemProductName = OptiPlex 745                 
MaxSpeed:     1800
CurrentSpeed: 1795
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\Mini072318-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Mon Jul 23 06:53:21.865 2018 (UTC - 4:00)
System Uptime: 2 days 1:43:40.195
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!4249FA5420B000 )
BUGCHECK_STR:  4249FA54
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108_4249FA54_nt_wrong_symbols!4249FA5420B000
Bugcheck code 100000D1
Arguments 00000014 00000002 00000000 f6ceffdf
BiosVersion = 2.6.6 
BiosReleaseDate = 06/26/2011
SystemManufacturer = Dell Inc.                
SystemProductName = OptiPlex 745                 
MaxSpeed:     1800
CurrentSpeed: 1795
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\Mini072118-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Sat Jul 21 05:09:24.503 2018 (UTC - 4:00)
System Uptime: 0 days 20:16:05.175
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for afd.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!4249FA5420B000 )
BUGCHECK_STR:  4249FA54
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108_4249FA54_nt_wrong_symbols!4249FA5420B000
Bugcheck code 100000D1
Arguments 2bf31738 00000002 00000001 a9d95d98
BiosVersion = 2.6.6 
BiosReleaseDate = 06/26/2011
SystemManufacturer = Dell Inc.                
SystemProductName = OptiPlex 745                 
MaxSpeed:     1800
CurrentSpeed: 1795
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\Mini071918-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Thu Jul 19 10:21:09.362 2018 (UTC - 4:00)
System Uptime: 0 days 4:00:54.901
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : hardware ( nt+2bcec )
DEFAULT_BUCKET_ID:  DRIVER_FAULT
BUGCHECK_STR:  0xA
FAILURE_BUCKET_ID:  IP_MISALIGNED
Bugcheck code 1000000A
Arguments 2d007586 0000001c 00000001 80502cec
BiosVersion = 2.6.6 
BiosReleaseDate = 06/26/2011
SystemManufacturer = Dell Inc.                
SystemProductName = OptiPlex 745                 
MaxSpeed:     1800
CurrentSpeed: 1795
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\Mini071818-02.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Wed Jul 18 15:15:11.143 2018 (UTC - 4:00)
System Uptime: 0 days 6:20:16.802
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for NDIS.sys
*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!4249FA5420B000 )
BUGCHECK_STR:  4249FA54
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108_4249FA54_nt_wrong_symbols!4249FA5420B000
Bugcheck code 100000C5
Arguments 001f3f08 00000002 00000000 8054afcb
BiosVersion = 2.6.6 
BiosReleaseDate = 06/26/2011
SystemManufacturer = Dell Inc.                
SystemProductName = OptiPlex 745                 
MaxSpeed:     1800
CurrentSpeed: 1795
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\Mini071818-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Wed Jul 18 08:54:39.020 2018 (UTC - 4:00)
System Uptime: 0 days 20:14:33.222
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!4249FA5420B000 )
BUGCHECK_STR:  4249FA54
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108_4249FA54_nt_wrong_symbols!4249FA5420B000
Bugcheck code 000000C2
Arguments 00000003 85d64650 863710c0 86371040
BiosVersion = 2.6.6 
BiosReleaseDate = 06/26/2011
SystemManufacturer = Dell Inc.                
SystemProductName = OptiPlex 745                 
MaxSpeed:     1800
CurrentSpeed: 1795
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\Mini071718-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Tue Jul 17 12:39:49.351 2018 (UTC - 4:00)
System Uptime: 0 days 0:07:22.519
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!4249FA5420B000 )
BUGCHECK_STR:  4249FA54
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108_4249FA54_nt_wrong_symbols!4249FA5420B000
Bugcheck code 10000050
Arguments ffffffb2 00000001 80540023 00000000
BiosVersion = 2.6.6 
BiosReleaseDate = 06/26/2011
SystemManufacturer = Dell Inc.                
SystemProductName = OptiPlex 745                 
MaxSpeed:     1800
CurrentSpeed: 1795
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\Mini071418-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Sat Jul 14 09:14:31.133 2018 (UTC - 4:00)
System Uptime: 0 days 1:11:20.646
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!4249FA5420B000 )
BUGCHECK_STR:  4249FA54
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108_4249FA54_nt_wrong_symbols!4249FA5420B000
Bugcheck code 1000000A
Arguments 00000000 00000002 00000001 805217f4
BiosVersion = 2.6.6 
BiosReleaseDate = 06/26/2011
SystemManufacturer = Dell Inc.                
SystemProductName = OptiPlex 745                 
MaxSpeed:     1800
CurrentSpeed: 1795
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\Mini071218-02.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Thu Jul 12 12:28:11.367 2018 (UTC - 4:00)
System Uptime: 0 days 1:39:32.796
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!4249FA5420B000 )
BUGCHECK_STR:  4249FA54
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108_4249FA54_nt_wrong_symbols!4249FA5420B000
Bugcheck code 1000008E
Arguments c0000005 bf8289d4 a9bb44ec 00000000
BiosVersion = 2.6.6 
BiosReleaseDate = 06/26/2011
SystemManufacturer = Dell Inc.                
SystemProductName = OptiPlex 745                 
MaxSpeed:     1800
CurrentSpeed: 1795
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\Mini071218-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Thu Jul 12 10:48:28.214 2018 (UTC - 4:00)
System Uptime: 0 days 4:32:49.052
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for NDIS.sys
*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys
*** WARNING: Unable to verify timestamp for psched.sys
*** ERROR: Module load completed but symbols could not be loaded for psched.sys
*** WARNING: Unable to verify timestamp for b57xp32.sys
*** ERROR: Module load completed but symbols could not be loaded for b57xp32.sys
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!4249FA5420B000 )
BUGCHECK_STR:  4249FA54
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108_4249FA54_nt_wrong_symbols!4249FA5420B000
Bugcheck code 1000000A
Arguments 10010000 00000002 00000001 806e4a2a
BiosVersion = 2.6.6 
BiosReleaseDate = 06/26/2011
SystemManufacturer = Dell Inc.                
SystemProductName = OptiPlex 745                 
MaxSpeed:     1800
CurrentSpeed: 1795
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\Mini071118-02.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Wed Jul 11 20:19:52.592 2018 (UTC - 4:00)
System Uptime: 0 days 11:22:14.183
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!4249FA5420B000 )
BUGCHECK_STR:  4249FA54
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108_4249FA54_nt_wrong_symbols!4249FA5420B000
Bugcheck code 1000000A
Arguments 80ee600c 00000002 00000000 805217ac
BiosVersion = 2.6.6 
BiosReleaseDate = 06/26/2011
SystemManufacturer = Dell Inc.                
SystemProductName = OptiPlex 745                 
MaxSpeed:     1800
CurrentSpeed: 1795
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\Mini071118-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Wed Jul 11 08:57:18.426 2018 (UTC - 4:00)
System Uptime: 0 days 2:43:45.425
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!4249FA5420B000 )
BUGCHECK_STR:  4249FA54
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108_4249FA54_nt_wrong_symbols!4249FA5420B000
Bugcheck code 1000000A
Arguments 00000008 0000001c 00000000 8050252d
BiosVersion = 2.6.6 
BiosReleaseDate = 06/26/2011
SystemManufacturer = Dell Inc.                
SystemProductName = OptiPlex 745                 
MaxSpeed:     1800
CurrentSpeed: 1795
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\Mini070618-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Fri Jul  6 10:48:31.249 2018 (UTC - 4:00)
System Uptime: 1 days 1:01:22.300
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!4249FA5420B000 )
BUGCHECK_STR:  4249FA54
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108_4249FA54_nt_wrong_symbols!4249FA5420B000
Bugcheck code 10000050
Arguments a8f7ffd4 00000001 805befb6 00000000
BiosVersion = 2.6.6 
BiosReleaseDate = 06/26/2011
SystemManufacturer = Dell Inc.                
SystemProductName = OptiPlex 745                 
MaxSpeed:     1800
CurrentSpeed: 1795
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\Mini070318-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Mon Jul  2 20:50:43.462 2018 (UTC - 4:00)
System Uptime: 0 days 13:09:48.046
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!4249FA5420B000 )
BUGCHECK_STR:  4249FA54
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_TIMESTAMP_050330-010108_4249FA54_nt_wrong_symbols!4249FA5420B000
Bugcheck code 1000000A
Arguments 0000e058 00000002 00000001 804febf8
BiosVersion = 2.6.6 
BiosReleaseDate = 06/26/2011
SystemManufacturer = Dell Inc.                
SystemProductName = OptiPlex 745                 
MaxSpeed:     1800
CurrentSpeed: 1795
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]
 
Thanks a lot for your time
[FONT=&quot]jcgriff2! [/FONT]​
I really appreciate you people spendind your free time to help someone you don't know (and possibly never will) having absolutely nothing as a reward. This world needs more people like you.
Gratefulness apart, the October '17 thread you mention was indeed about a PC with counterfeit software, owner was duely noted. On the other hand, this thread is about a DELL Optiplex that came with genuine Windows XP, supplied along with this spectrometer I mentioned.
I really don't know why you are getting all those symbol errors, the files involved don't seem to be the ones a crack would modify (atapi.sys? http.sys? imapi.sys?). Anyway, could it be a problem on the hard drive? SMART self diagnose finished with 100% health...
Those symbol errors make me think perhaps the images are corrupted, will try running SFC...
As soon as I can I'll run the file collection app.

Thanks a lot one more time.
 
Here I am again, been to the place and tried to run BSOD data collection app... command line program opened but refused to run because "it's not compatible with Windows versions prior to Vista"...
Figured i could run it anyway using compatiblity options, but realised that you had put that warning there for some reason....
What are your suggested steps?


Thanks in advance!
 
softwaremaniac said:
... I'll assume we're dealing with oldish hardware....
Click to expand...
Indeed, it's a DELL OptiPlex 745. As I said in the first post, RAM sticks were bad and have been replaced. Then AIDA64's burn-in test was left running for about 4hs with no issues (through Hiren's MiniXP USB boot). That makes me think hardware is ok and the BSOD's are software related.
 
ChkDsk is different kind of check, please do the following:

GSmartControl
Follow the instructions below to test your hard drive health with GSmartControl:



  • Download GSmartControl and save it on your Desktop;
  • Execute gsmartcontrol.exe; Let the install complete and launch the programme.
  • Identify your drive in the list, and double-click on it to bring up it's window (usually you'll find your drive by it's size or it's brand name);
  • Go in the Perform Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
  • Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply;
  • Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;
    info_failing.png
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top