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: BSODs Started three days ago after starting FireFox


23 Jul 2012   #1

Windows 7 Home Premium 64 bit
 
 
BSODs Started three days ago after starting FireFox

Computer: Windows 7 Home premium Desktop

About three days ago I started getting BSODs whenever I would open up FireFox, I would click the quicklink and boom BSOD. So after run a virus scan (malwarebytes) and deleting the Trojan and web hacker everything was running smoothly, but the next day whenever i would turn on the PC after abut 5 minutes it would crash again. I would restart and boom it happens again, now I can't run anything in normal mode at all, just being idle it will crash to BSOD so I am posting this in Safe mode with networking and everything that isn't restricted is working just fine with no problems.

I've looked at the dates of all the minidumps and its just showing the ones that happened today, there were several the past few days, the months prior I have no clue about probably wasn't me using the computer and I wasn't told about them.

this is what most recently popped up

BCCode: a
BCP1: 00000000000000DC
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80003510405
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

I have one time gotten a different code dump but this is the one that pops up every time and I didn't take a picture of it sorry.

Any help will be appreciated and I'm willing to add what ever you need
Thanks in advance!

My System SpecsSystem Spec
.

23 Jul 2012   #2

Windows 7 Home Premium 64 bit
 
 

Update:
I downloaded "bluescreen View" to view the dmp files in safe mode and its pointing to "ntoskrnl.exe" any ideas?
My System SpecsSystem Spec
23 Jul 2012   #3
Microsoft MVP

 

Run a full scan with Malwarebytes.

Then run SFC -SCANNOW Command.

With unfixable System files you may need a Repair Install.

Here are additional Troubleshooting Steps for Windows 7 - Windows 7 Forums.

If Windows 7 wont' stay booted to do the steps then use these steps for Troubleshooting Windows 7 Failure to Boot - Windows 7 Forums
My System SpecsSystem Spec
.


23 Jul 2012   #4

Windows 7 Home Premium 64 bit
 
 

Quote   Quote: Originally Posted by gregrocker View Post
Run a full scan with Malwarebytes.

Then run SFC -SCANNOW Command.

With unfixable System files you may need a Repair Install.

Here are additional Troubleshooting Steps for Windows 7 - Windows 7 Forums.

If Windows 7 wont' stay booted to do the steps then use these steps for Troubleshooting Windows 7 Failure to Boot - Windows 7 Forums
Thank you for the reply, a few days back when it would stay on in normal mode i ran Malwarebytes and cleaned it up, after scanning again today it did not find anything.

So it seems that i will need to burn that repair disc, from reading on the link you provided it says it will not delete my data, should i back that up before anyways?

Is there anything that I should have handy while I do this?

Sorry for spamming questions thanks again
My System SpecsSystem Spec
23 Jul 2012   #5
Microsoft MVP

 

We should always have our data backed up. I sync mine to the cloud using MS Skydrive 7gb free storage with each Windows Live ID: Sync Any Folder to Your SkyDrive Account | PCWorld

What did SFC find?

Establish a clean boot, check the logs for problem at time of crash and repeat errors, utilize System Resources to check for problems as given in Troubleshooting Steps for Windows 7.
My System SpecsSystem Spec
24 Jul 2012   #6

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

I agree with Greg, anytime you get a virus, trojan, you should consider re-installing the OS. It's actually the fastest way to get your system up and running with no chance of the trojan returning.

After following Greg's advice, if you are still having crashes, try the suggestions below.

Your crashes are:

Code:
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003714100
GetUlongFromAddress: unable to read from fffff800037141c0
 00000000000000ec Nonpaged pool
FAILURE_BUCKET_ID:  X64_0xA_nt!KeStackAttachProcess+115
----------------------------------------------------------------------------------------------------------------------------------------------

STOP 0x000000C5: DRIVER_CORRUPTED_EXPOOL 
Usual causes:  Device driver, ?Memory
The kernel attempted to access pageable memory (or perhaps completely invalid memory) when the IRQL was too high. The ultimate cause of this problem is almost certainly a driver that has corrupted the system pool.
PROCESS_NAME:  wmpnscfg.exe
IMAGE_NAME:  Pool_Corruption
FAILURE_BUCKET_ID:  X64_0xC5_2_nt!ExDeferredFreePool+249
--------------------------------------------------------------------------------------------------------------------------------------------

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED 
Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a very common bug check.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
PROCESS_NAME:  wmpnetwk.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!ObpCreateHandle+29a
----------------------------------------------------------------------------------------------------------------------------------------------
IRQL_NOT_LESS_OR_EQUAL (a)
ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys - Nvidia driver
MODULE_NAME: nvlddmkm
FAILURE_BUCKET_ID:  X64_0xA_nvlddmkm+17ea00
----------------------------------------------------------------------------------------------------------------------------
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL  
Usual causes:  Device driver
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036c8100
GetUlongFromAddress: unable to read from fffff800036c81c0
 0000000000000030 Nonpaged pool
PROCESS_NAME:  TeaTimer.exe
IMAGE_NAME:  afd.sys - Windows Ancillary Function Driver for WinSock
FAILURE_BUCKET_ID:  X64_0xD1_afd!AfdTLConnectComplete+24
-----------------------------------------------------------------------------------------------------------------------------

IRQL_NOT_LESS_OR_EQUAL (a)
Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+115 )
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000370f100
GetUlongFromAddress: unable to read from fffff8000370f1c0
 00000000000000dc Nonpaged pool
FAILURE_BUCKET_ID:  X64_0xA_nt!KeStackAttachProcess+115
-----------------------------------------------------------------------------------------------------------------------------
System Event Logs:
Code:
Event[216]:
  Log Name: System
  Source: Microsoft-Windows-SharedAccess_NAT
  Date: 2012-02-18T12:37:27.000
  Event ID: 34005
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Alex-PC
  Description: 
The ICS_IPV6 was unable to allocate  bytes of memory. This may indicate that the system is low on virtual memory, or that the memory manager has encountered an internal error.

Event[287]:
  Log Name: System
  Source: Microsoft-Windows-DistributedCOM
  Date: 2012-02-18T15:40:16.000
  Event ID: 10000
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Alex-PC
  Description: 
Unable to start a DCOM Server: {DC0C2640-1415-4644-875C-6F4D769839BA}. The error:
"740"
Happened while starting this command:
"C:\Program Files (x86)\iTunes\iTunes.exe" -Embedding

Event[528]:
  Log Name: System
  Source: Microsoft-Windows-SharedAccess_NAT
  Date: 2012-02-19T12:38:11.000
  Event ID: 34005
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Alex-PC
  Description: 
The ICS_IPV6 was unable to allocate  bytes of memory. This may indicate that the system is low on virtual memory, or that the memory manager has encountered an internal error.
App Event LOgs:

Code:
Event[45]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2011-09-27T09:51:33.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Alex-PC
  Description: 
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

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

Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20101219-2140.dmp
C:\Windows\Temp\WER-41506624-0.sysdata.xml
C:\Windows\Temp\WERAFFA.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0ae9b038

Analysis symbol: 
Rechecking for solution: 0
Report Id: b7cb9440-0bfb-11e0-9dbc-8397591cef01
Report Status: 0

Event[46]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2011-09-27T09:51:33.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Alex-PC
  Description: 
Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

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

Attached files:
C:\Windows\Minidump\030510-18985-01.dmp
C:\Users\Alex\AppData\Local\Temp\WER-35349-0.sysdata.xml
C:\Users\Alex\AppData\Local\Temp\WERFC93.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0af4fc96

Analysis symbol: 
Rechecking for solution: 0
Report Id: 030510-18985-01
Report Status: 0

Event[47]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2011-09-27T09:51:33.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Alex-PC
  Description: 
Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

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

Attached files:
C:\Windows\Minidump\021210-21824-01.dmp
C:\Users\Alex\AppData\Local\Temp\WER-34055-0.sysdata.xml
C:\Users\Alex\AppData\Local\Temp\WERB46B.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0b44b46f

Analysis symbol: 
Rechecking for solution: 0
Report Id: 021210-21824-01
Report Status: 0

Event[48]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2011-09-27T09:51:33.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Alex-PC
  Description: 
Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

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

Attached files:
C:\Windows\Minidump\011810-17082-01.dmp
C:\Users\Alex\AppData\Local\Temp\WER-34055-0.sysdata.xml
C:\Users\Alex\AppData\Local\Temp\WERB49B.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0b44b49e

Analysis symbol: 
Rechecking for solution: 0
Report Id: 011810-17082-01
Report Status: 0

Event[49]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2011-09-27T09:51:33.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Alex-PC
  Description: 
Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

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

Attached files:
C:\Windows\Minidump\011210-17706-01.dmp
C:\Users\Alex\AppData\Local\Temp\WER-34055-0.sysdata.xml
C:\Users\Alex\AppData\Local\Temp\WERB4CA.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0b44b4bd

Analysis symbol: 
Rechecking for solution: 0
Report Id: 011210-17706-01
Report Status: 0

Event[50]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2011-09-27T09:51:33.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Alex-PC
  Description: 
Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

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

Attached files:
C:\Windows\Minidump\010410-18298-01.dmp
C:\Users\Alex\AppData\Local\Temp\WER-34055-0.sysdata.xml
C:\Users\Alex\AppData\Local\Temp\WERB4EB.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0b44b4dd

Analysis symbol: 
Rechecking for solution: 0
Report Id: 010410-18298-01
Report Status: 0

Event[51]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2011-09-27T09:51:33.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Alex-PC
  Description: 
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

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

Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20100909-1627.dmp
C:\Windows\Temp\WER-538156-0.sysdata.xml
C:\Windows\Temp\WER5031.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0db85031

Analysis symbol: 
Rechecking for solution: 0
Report Id: d8e44a00-bc69-11df-900c-d5ccb3e2ce0c
Report Status: 0

Event[52]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2011-09-27T09:51:33.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Alex-PC
  Description: 
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

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

Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20100910-2025.dmp
C:\Windows\Temp\WER-46593411-0.sysdata.xml
C:\Windows\Temp\WERF91B.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0dbef91b

Analysis symbol: 
Rechecking for solution: 0
Report Id: 4c2c2bf0-bd54-11df-b213-9c7a70ad1806
Report Status: 0

Event[53]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2011-09-27T09:51:33.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Alex-PC
  Description: 
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

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

Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20100904-1015.dmp
C:\Windows\Temp\WER-1064145-0.sysdata.xml
C:\Windows\Temp\WER5E07.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0ed85e16

Analysis symbol: 
Rechecking for solution: 0
Report Id: 012890a0-b848-11df-aa7c-d95696c7ac0a
Report Status: 0

Event[54]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2011-09-27T09:51:33.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Alex-PC
  Description: 
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

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

Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20100926-2148.dmp
C:\Windows\Temp\WER-40530151-0.sysdata.xml
C:\Windows\Temp\WER8B69.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_10fa8b79

Analysis symbol: 
Rechecking for solution: 0
Report Id: 752c0520-c9f2-11df-9e84-a2ca5b42110f
Report Status: 0

Event[55]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2011-09-27T09:51:33.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Alex-PC
  Description: 
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

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

Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20101219-1931.dmp
C:\Windows\Temp\WER-33741175-0.sysdata.xml
C:\Windows\Temp\WERFB97.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_1186fbb6

Analysis symbol: 
Rechecking for solution: 0
Report Id: a33b60d0-0be9-11e0-9dbc-8397591cef01
Report Status: 0

Event[56]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2011-09-27T09:51:33.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Alex-PC
  Description: 
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

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

Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20100815-1713.dmp
C:\Windows\Temp\WER-7352077-0.sysdata.xml
C:\Windows\Temp\WER51B9.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_133051c9

Analysis symbol: 
Rechecking for solution: 0
Report Id: 1ed8eaa0-a8cb-11df-8c77-90e6ba4980ad
Report Status: 0

Event[57]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2011-09-27T09:51:33.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Alex-PC
  Description: 
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

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

Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20100818-1847.dmp
C:\Windows\Temp\WER-31283114-0.sysdata.xml
C:\Windows\Temp\WER79DA.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_138179e9

Analysis symbol: 
Rechecking for solution: 0
Report Id: ca510f60-ab33-11df-b544-90e6ba4980ad
Report Status: 0

Event[58]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2011-09-27T09:51:33.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Alex-PC
  Description: 
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

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

Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20100826-2220.dmp
C:\Windows\Temp\WER-46416412-0.sysdata.xml
C:\Windows\Temp\WER4E8B.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_169c4eaa

Analysis symbol: 
Rechecking for solution: 0
Report Id: e11194f0-b19a-11df-9bf7-b50d7985b702
Report Status: 0

Event[59]:
  Log Name: Application
  Source: gupdate
  Date: 2011-09-27T10:14:00.000
  Event ID: 0
  Task: None
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Alex-PC
  Description: 
N/A

Event[60]:
  Log Name: Application
  Source: gupdate
  Date: 2011-09-27T10:14:00.000
  Event ID: 0
  Task: None
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Alex-PC
  Description: 
N/A

Event[61]:
  Log Name: Application
  Source: SideBySide
  Date: 2011-09-27T10:16:34.000
  Event ID: 59
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Alex-PC
  Description: 
Activation context generation failed for "c:\program files (x86)\microsoft\search enhancement pack\search helper\searchhelper.dll".Error in manifest or policy file "c:\program files (x86)\microsoft\search enhancement pack\search helper\searchhelper.dll" on line 2. Invalid Xml syntax.


Go to your HP site and check for an updates for your drivers.
Install all with a more recent date than yours are now.

Run memtest86+ for a minimum on 7 full passes with all RAM cards installed, best to run overnight.
Stop the test if you get any errors.
RAM - Test with Memtest86+

What Nvidia driver are you using?
You need to check for an update, if you are using the latest then try a previous driver.

D/L and run Western Digital Lifeguard – Quick Test and Extended Test

Un-install itunes for testing purposes.

Check if there is a BIOS update.
Yours:
Quote:
BIOS Date: 09/08/09 15:16:20 Ver: 5.18
My System SpecsSystem Spec
24 Jul 2012   #7

Windows 7 Home Premium 64 bit
 
 

Quote   Quote: Originally Posted by gregrocker View Post
We should always have our data backed up. I sync mine to the cloud using MS Skydrive 7gb free storage with each Windows Live ID: Sync Any Folder to Your SkyDrive Account | PCWorld

What did SFC find?

Establish a clean boot, check the logs for problem at time of crash and repeat errors, utilize System Resources to check for problems as given in Troubleshooting Steps for Windows 7.
Will SFC run correctly in safe mode? The main proble I have is normal mode will only work for maybe 5 minutes before blue screening, and another potential problem is best buy did not give me the windows 7 install disc when I bought the pc, does this mean I'm stuck, I will have access to the computer tomorrow to attempt to try the fixes you guys have provided I have a 500gb hard drive to back everything up on too

Thanks for the help
My System SpecsSystem Spec
24 Jul 2012   #8
Microsoft MVP

 

Work through Dave's suggestions first as he is working from your crash report and is our top hardware expert.

Earlier I linked the steps for Troubleshooting Windows 7 Failure to Boot which include how to run all of the tests and repairs from boot disks, rescue files, test hardware - everything that possibly can be done to save the install.

We may have added steps based on what you report back.
My System SpecsSystem Spec
24 Jul 2012   #9

Windows 7 Home Premium 64 bit
 
 

Quote   Quote: Originally Posted by gregrocker View Post
Work through Dave's suggestions first as he is working from your crash report and is our top hardware expert.

Earlier I linked how the steps for Troubleshooting Windows 7 Failure to Boot which include how to run all of the tests and repairs from boot disks, rescue files, test hardware - everything that possibly can be done to save the install.

We may have added steps based on what you report back.

Okay sorta good news i wasn't going to be able to get on the computer till tomorrow because I'm outta town, but my mother turned it on today and it's currently running in normal thus allowing me to VNC in. I ran the sfc scan and and it did not find anything wrong. I am about to run the WD Lifeguard and check the nvidia drivers, and then report back, then run Memtest86+. I have uninstalled itunes

Thanks guys I feel like i can make some progress with it currently working **crosses fingers**
My System SpecsSystem Spec
25 Jul 2012   #10

Windows 7 Home Premium 64 bit
 
 

Quote   Quote: Originally Posted by Dave76 View Post

Check if there is a BIOS update.
Yours:
Quote:
BIOS Date: 09/08/09 15:16:20 Ver: 5.18
After going to HP.com and using their HP product search tool I have found and update for the BIOS, version 5.22 Date: 2010-7-21, the WD scan did not find anything either it said the quick and extended scan both passed should i update the bios now?

I'm scard to do it right now because of the pc currently running in normal mode right now and updating the BIOS will surely need a restart.... what do you guys think? is there anything I should do before the update?
My System SpecsSystem Spec
Reply

 BSODs Started three days ago after starting FireFox




Thread Tools



Similar help and support threads for2: BSODs Started three days ago after starting FireFox
Thread Forum
Started having BSOD's in the last couple of days BSOD Help and Support
Laptop was working ok, few days later it started beeping on start up Hardware & Devices
BSOD - frequent, started just few days ago BSOD Help and Support
Solved BSOD Started 5 days ago. BSOD Help and Support
System_Service_Exception occurs once in 2 days while starting BSOD Help and Support
7MC Randomly started crashing two days ago... 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 07:39 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33