Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Many BSODs, relating to memory and drivers

10 Jul 2012   #1
jwoglom

Windows 7 HP x64
 
 
Many BSODs, relating to memory and drivers

Most of the errors say it's "likely not a hardware problem," but they never identify a driver. I've reinstalled Windows like 3 times in the past year, and I still get constant crashes, so I think it is the hardware causing the problem. I've run Memtest86 overnight once or twice and with multiple passes and every time it says all's good..any other suggestions?

Thanks. Here is a log from using WhoCrashed, and I've also attached the response from using the program in the BSOD guidelines.
Code:
System Information (local)
--------------------------------------------------------------------------------

computer name: 
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8580947968 total
VM: 2147352576, free: 1932845056



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 7/10/2012 4:14:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071012-32276-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x5E3AA) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. 


On Tue 7/10/2012 12:35:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071012-29780-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) 
Bugcheck code: 0x109 (0xA3A039D8A236453C, 0xB3B7465EF4B31492, 0xFFFFF80002EB2F58, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Sun 7/8/2012 8:37:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070812-28158-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040) 
Bugcheck code: 0x50 (0xFFFFF6800045A4F8, 0x0, 0xFFFFF80002E88B62, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Wed 7/4/2012 3:07:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070412-38204-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040) 
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC50129EE0, 0x8770000202F40882, 0xFFFFF8A0047F8209)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Tue 7/3/2012 4:36:58 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070312-25584-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003156B50, 0xFFFFF8800BCB8B30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Sun 7/1/2012 7:58:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070112-47252-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040) 
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80036CE910, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Wed 6/27/2012 10:24:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062712-37674-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8) 
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88007536D28, 0xFFFFF88007536590, 0xFFFFF80002CB8171)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. 


On Tue 6/26/2012 8:32:57 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062612-29359-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCB4A5) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600017B4A5, 0xFFFFF88008298120, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. 


On Wed 6/20/2012 4:04:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062012-26566-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x96FC0) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002CECFC0, 0xFFFFF880093F6F48, 0xFFFFF880093F67B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Mon 6/18/2012 8:56:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061812-38828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040) 
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x14B1F, 0x15D17C09)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Mon 6/11/2012 4:23:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061112-34788-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040) 
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80037EF0C0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Wed 5/30/2012 10:38:57 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\053012-25662-01.dmp
This was probably caused by the following module: fastfat.sys (fastfat+0x1D82) 
Bugcheck code: 0x23 (0xE00E6, 0xFFFFF880031FC4D8, 0xFFFFF880031FBD40, 0xFFFFF88001096B51)
Error: FAT_FILE_SYSTEM
file path: C:\Windows\system32\drivers\fastfat.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Fast FAT File System Driver
Bug check description: This indicates that a problem occurred in the FAT file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. 


On Sun 5/27/2012 2:04:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052712-20607-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CDA144, 0xFFFFF8800AEDD920, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Sat 5/26/2012 9:44:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052712-19188-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040) 
Bugcheck code: 0x109 (0xA3A039D89C74D7D1, 0xB3B7465EEEF2A703, 0xFFFFF80002C1AB10, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Sat 5/26/2012 7:42:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052612-145658-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040) 
Bugcheck code: 0x109 (0xA3A039D89F4D453D, 0xB3B7465EF1CA1733, 0xFFFFF80002CD6E3A, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

15 crash dumps have been found and analyzed. 
Read the topic general suggestions for troubleshooting system crashes for more information. 

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.



My System SpecsSystem Spec
10 Jul 2012   #2
writhziden

Windows 7 Home Premium 64 Bit
 
 

Your crash reports indicate a possible problem with your Windows installation. Please follow the Windows Genuine and Activation Issue Posting Instructions. Post the results in your next post; do not start a new thread.
Quote   Quote: Originally Posted by Brink
NOTE: The MGADIAG report does not contain any sensitive or personal information, and is best posted un-edited for us to be able to help.

7. Select (highlight) all of the MGADiag report that you just pasted, and click on the code box # toolbar icon to wrap the report in a code box when posted. (see screenshot below)

Attachment 220862
My System SpecsSystem Spec
13 Jul 2012   #3
jwoglom

Windows 7 HP x64
 
 

Code:
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-XW33P-3TTD8-MD43F
Windows Product Key Hash: Zs5Mt4ElP0zUzpCqHwcqH4i85vo=
Windows Product ID: 00359-OEM-8703361-49870
Windows Product ID Type: 3
Windows License Type: OEM System Builder
Windows OS version: 6.1.7601.2.00010300.1.0.003
ID: {DFE013A7-1B48-4DFD-8D0D-7BFEA8836301}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Home Premium
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.120503-2030
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Users\James\AppData\Local\Google\Chrome\Application\chrome.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{DFE013A7-1B48-4DFD-8D0D-7BFEA8836301}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-MD43F</PKey><PID>00359-OEM-8703361-49870</PID><PIDType>3</PIDType><SID>S-1-5-21-2494609772-2123349608-3494670083</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>P55A-UD3</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F11</Version><SMBIOSVersion major="2" minor="4"/><Date>20100810000000.000000+000</Date></BIOS><HWID>66553607018400FC</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7601.17514

Name: Windows(R) 7, HomePremium edition
Description: Windows Operating System - Windows(R) 7, OEM_COA_NSLP channel
Activation ID: 586bc076-c93d-429a-afe5-a69fbc644e88
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00359-00174-033-649870-02-1033-7601.0000-1952012
Installation ID: 004694602220865533325731303641508513665130002954075753
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: MD43F
License Status: Initial grace period
Time remaining: 36000 minute(s) (25 day(s))
Remaining Windows rearm count: 3
Trusted time: 7/13/2012 6:11:58 PM

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 7:11:2012 15:12
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: RAAAAAQACAABAAIAAQACAAAAAQABAAEAln1kw/hxJ1msQk40do2AligLKGBCxpSKkjxqA4hVznDsnN6IELcG6dBUXF0=

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information: 
  ACPI Table Name	OEMID Value	OEMTableID Value
  APIC			GBT   		GBTUACPI
  FACP			GBT   		GBTUACPI
  HPET			GBT   		GBTUACPI
  MCFG			GBT   		GBTUACPI
  EUDS			GBT   		
  MATS			GBT   		
  TAMG			GBT   		GBT   B0
  SSDT			INTEL		PPM RCM
My System SpecsSystem Spec
14 Jul 2012   #4
writhziden

Windows 7 Home Premium 64 Bit
 
 

Your information changed for your WIndows installation. Did you re-install Windows 7 before changing the key, or did you enter the key on the old installation? If you did not re-install, I strongly recommend doing so: Clean Reinstall - Factory OEM Windows 7. The software you used to make your old installation work may leave your security vulnerable and prevent Windows from updating properly. Those alone may cause blue screen crashes, and they also are unsafe for both you and your system.

Please activate Windows 7. Then download the Windows Activation Technology update and run it from Description of the update for Windows Activation Technologies. You should also run Genuine Microsoft Software to make sure. After those steps are done, upload the updated MGADiag report.
My System SpecsSystem Spec
14 Jul 2012   #5
jwoglom

Windows 7 HP x64
 
 

Quote   Quote: Originally Posted by writhziden View Post
Your information changed for your WIndows installation. Did you re-install Windows 7 before changing the key, or did you enter the key on the old installation? If you did not re-install, I strongly recommend doing so: Clean Reinstall - Factory OEM Windows 7. The software you used to make your old installation work may leave your security vulnerable and prevent Windows from updating properly. Those alone may cause blue screen crashes, and they also are unsafe for both you and your system.

Please activate Windows 7. Then download the Windows Activation Technology update and run it from Description of the update for Windows Activation Technologies. You should also run Genuine Microsoft Software to make sure. After those steps are done, upload the updated MGADiag report.


I previously had some sort ofcrack on my system that wasn't needed, as I have a OEM copy of Windows 7 and a key. For whatever reason, when I wanted to activate, it hadn't completely uninstalled, which kinda screwed up my system (as you were saying). I *think* it's all removed now, and I do have a geniune install. The update you linked was already installed.

If I get any more BSODs I'll update here.
Code:
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-XW33P-3TTD8-MD43F
Windows Product Key Hash: Zs5Mt4ElP0zUzpCqHwcqH4i85vo=
Windows Product ID: 00359-OEM-8703361-49870
Windows Product ID Type: 3
Windows License Type: OEM System Builder
Windows OS version: 6.1.7601.2.00010300.1.0.003
ID: {DFE013A7-1B48-4DFD-8D0D-7BFEA8836301}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Home Premium
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.120503-2030
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Users\James\AppData\Local\Google\Chrome\Application\chrome.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{DFE013A7-1B48-4DFD-8D0D-7BFEA8836301}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-MD43F</PKey><PID>00359-OEM-8703361-49870</PID><PIDType>3</PIDType><SID>S-1-5-21-2494609772-2123349608-3494670083</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>P55A-UD3</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F11</Version><SMBIOSVersion major="2" minor="4"/><Date>20100810000000.000000+000</Date></BIOS><HWID>66553607018400FC</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7601.17514

Name: Windows(R) 7, HomePremium edition
Description: Windows Operating System - Windows(R) 7, OEM_COA_NSLP channel
Activation ID: 586bc076-c93d-429a-afe5-a69fbc644e88
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00359-00174-033-649870-02-1033-7601.0000-1952012
Installation ID: 004694602220865533325731303641508513665130002954075753
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: MD43F
License Status: Licensed
Remaining Windows rearm count: 3
Trusted time: 7/14/2012 11:41:05 AM

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 7:13:2012 23:47
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: RAAAAAQACAABAAIAAQACAAAAAQABAAEAln1kw/hxJ1msQk40do2AligLKGBCxpSKkjxqA4hVznDsnN6IELcG6dBUXF0=

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information: 
  ACPI Table Name	OEMID Value	OEMTableID Value
  APIC			GBT   		GBTUACPI
  FACP			GBT   		GBTUACPI
  HPET			GBT   		GBTUACPI
  MCFG			GBT   		GBTUACPI
  EUDS			GBT   		
  MATS			GBT   		
  TAMG			GBT   		GBT   B0
  SSDT			INTEL		PPM RCM
My System SpecsSystem Spec
Reply

 Many BSODs, relating to memory and drivers




Thread Tools



Similar help and support threads for2: Many BSODs, relating to memory and drivers
Thread Forum
BSODs from general use (memory? drivers?) BSOD Help and Support
Solved Having bsods relating to ntoskrnl.exe+75c00 BSOD Help and Support
New MoBo, CPU, RAM, Memory-related BSODs ever since BSOD Help and Support
relating os General Discussion
BSODs & Memory Issues? BSOD Help and Support
Memory Management BSODs + Minidumps BSOD Help and Support
Multiple BSODs... May need to RMA Memory BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 03:43 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App