[Kshksh]

OS -Windows 7
· x86 (32-bit)
· What was original installed OS on system? Windows 7 32bit.
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Retail.
· Age of system (hardware) Around 6 years. 3 year old hard drive.
· Age of OS installation - have you re-installed the OS? - A couple of minutes

· CPU - Pentium Dual-Core 2GHz
· Video Card - Integrated GMA 4500
·
·

· System Manufacturer - Asus
· Exact model number (if laptop, check label on bottom) - F52Q

Hello again, I'm writing about my old laptop again. We've been together through a lot so he's kinda like a friend to me and I'd like to give him a few more years at least.
I've been experiencing numerous BSODs and today I've decided to reinstall the system and set up everything from scratch to eliminate all possible causes of problems. I've reinstalled Win 7 Ultimate but right after it first launched into desktop I was greeted with a BSOD. During my setting up basic windows setting to my liking, I got another 2 BSODs.
Please help me save my friend again. I'm suspecting ram this time because BSODs happened with many Bug Check Strings before. I'm going to run MEMTest before sleep tonight and post result tomorrow.

 

[jcgriff2]

Hi. . .

Sorry to ask, but is this copy of Windows 7 Ultimate genuine (legit)? I am getting symbol errors in Windbg, which means that Microsoft (the MSDL symbol server site) cannot identify some of the Windows drivers, likely due to patching, including the primary NT kernel driver itself.

The dumps really were of no help to us due to the symbol errors.

You only have 19 Windows Updates installed. There should be about 400, including Windows 7 Service Pack 1. Windows Update installation is a must. You have to get ALL of these updates installed. The current build number is 7600; will change to 7601 once SP1 is installed.

In the event that we are dealing with hardware failure here, I would start with RAM diagnostics.

Run memtest86+ - run 1 stick at a time; alternate the slots - https://www.sysnative.com/forums/hardware-tutorials/3909-test-ram-memtest86.html

Then run HDD diags. Run SeaTools for DOS, LONG test - https://www.sysnative.com/forums/hardware-tutorials/4072-hard-drive-hdd-diagnostics.html

Regards. . .

jcgriff2

`

[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\031916-25521-01.dmp]
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.17795.x86fre.win7_gdr.150318-1623
Debug session time: Sat Mar 19 14:06:51.742 2016 (UTC - 4:00)
System Uptime: 0 days 0:06:37.584
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.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!550A2C44411000 )
BUGCHECK_STR:  550A2C44
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_7600.17795.x86fre.win7_gdr.150318-1623_TIMESTAMP_150319-015412
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_7600.17795.x86fre.win7_gdr.150318-1623_TIMESTAMP_150319-015412_550A2C44_nt_wrong_symbols!550A2C44411000
Bugcheck code 0000000A
Arguments 00000000 00000002 00000001 828688ef
BiosVersion = 206    
BiosReleaseDate = 05/19/2009
SystemManufacturer = ASUSTeK Computer Inc.        
SystemProductName = F52Q                
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\031916-26894-01.dmp]
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.17795.x86fre.win7_gdr.150318-1623
Debug session time: Sat Mar 19 14:09:54.098 2016 (UTC - 4:00)
System Uptime: 0 days 0:02:31.939
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!550A2C44411000 )
BUGCHECK_STR:  550A2C44
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_7600.17795.x86fre.win7_gdr.150318-1623_TIMESTAMP_150319-015412
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_7600.17795.x86fre.win7_gdr.150318-1623_TIMESTAMP_150319-015412_550A2C44_nt_wrong_symbols!550A2C44411000
Bugcheck code 0000000A
Arguments 839fffec 00000002 00000001 828e77fe
BiosVersion = 206    
BiosReleaseDate = 05/19/2009
SystemManufacturer = ASUSTeK Computer Inc.        
SystemProductName = F52Q                
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\031916-19141-01.dmp]
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat Mar 19 13:16:29.016 2016 (UTC - 4:00)
System Uptime: 0 days 0:00:59.857
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!4A5BC007410000 )
BUGCHECK_STR:  4A5BC007
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X86_7600.16385.x86fre.win7_rtm.090713-1255_TIMESTAMP_090713-231519
FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X86_7600.16385.x86fre.win7_rtm.090713-1255_TIMESTAMP_090713-231519_4A5BC007_nt_wrong_symbols!4A5BC007410000
Bugcheck code 0000000A
Arguments eeb7ad5a 00000002 00000000 82836d64
BiosVersion = 206    
BiosReleaseDate = 05/19/2009
SystemManufacturer = ASUSTeK Computer Inc.        
SystemProductName = F52Q                
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]

 

[jcgriff2]

Seeing that you have a retail version of Windows 7 and therefore have a valid Windows keycode, download the Windows 7 ISO from Microsoft - https://www.microsoft.com/en-us/software-download/windows7

You can then enter your Windows 7 Ultimate x86 retail keycode during the re-installation of Windows.

Perhaps the symbol errors that I came upon were caused by a corrupted DVD/USB ISO copy of Windows 7.

Regards. . .

jcgriff2

`

 

[Kshksh]

Hello again,
I've run Memtest for 12 passes and ended up with no errors, SeaTools Dos also turned up nothing.
May the symbol errors you encountered be caused by my installation not being activated at the time, I skipped it during installation.
I've run updates and the file collection app from your site one more time. However after installing Windows Update Agent 7.6.7600.2320 I've run into problems with updates being stuck in a loop looking for new updates. I'm gonna run Windows Update Diagnostic later.

 

[jcgriff2]

However after installing Windows Update Agent 7.6.7600.2320...

What is "Windows Update Agent"?

Whatever it is, it has a Windows 7 SP0 version number on it - 7600

Windows 7 SP1 = 7601