I have a newly-built PC, which worked great for about 8 days. I have only installed about 4-5 programs on it.

Last night (05/28), I connected some external hard drives and did some file transfers. I was unable to get two of them to stop (because apparently some program was still accessing them.) Eventually I gave up and shut down.

A while later I restarted. Startup failed and a System Repair utility attempted to fix things, but this was less than successful. Restarted and was given a recommended option to run the System Repair, so I did. No errors (apparently).

Could not start Windows Media Player. Message that it was installed incorrectly.
Could not start AVG. I can't remember the message for that one, but I think it was some kind of missing/invalid file.

This morning I started up. Started OK but same problems with software.
I tried two different System Restore points.
1. Yesterday at 8pm (Automatic Restore Point): Would not work.
2. A Windows Update the night before: Catastrophic Failure (0x08000FFFF).

Again I tried System Restore to yesterday 8pm. Everything came back, WMP worked, AVG started.

Firefox started crashing a lot, and couldn't restore my tabs upon restarting. I decided to uninstall and reinstall. At one point I got a very brief blue screen with something about "MEMORY_MANAGEMENT".

Reinstalling firefox was interrupted with the following message:

C:\Users\Sam\AppData\Local\Temp\7z546BF.tmp\nonloc alized\js3250.dll
File could not be scanned probably due to an invalid file structure (address a0077bf9a1)
Detected on open.

I then got an AVG warning box for the following three files:
c:\Program Files (x86)\Mozilla Firefox\js3250.dll
c:\Program Files (x86)\Mozilla Firefox\xpcom.dll
C:\Users\Sam\AppData\Local\Temp\7z546BF.tmp\nonloc alized\js3250.dll

"The file could not be scanned probably due to an invalid file structure (address a007bf9a1).";"Object is white-listed (critical/system file that should not be removed)"

Uninstalled firefox again.

Performed full AVG scan:

"C:\Windows\winsxs\amd64_microsoft-windows-ieframe_31bf3856ad364e35_8.0.7600.20651_none_dbf7b 4b157dae956\ieframe.dll";"The file could not be scanned probably due to an invalid file structure (address a007bf9a1).";"Object is white-listed (critical/system file that should not be removed)"
"C:\Windows\System32\wininet.dll";"The file could not be scanned probably due to an invalid file structure (address a007bf9a1).";"Object is white-listed (critical/system file that should not be removed)"
"C:\Users\Sam\AppData\Local\Temp\AVGDownloadManage r\packages\u9ichjw4qt.bin";"The file could not be scanned probably due to an invalid file structure (address a007bf9a1).";"Object is white-listed (critical/system file that should not be removed)"
"C:\Program Files (x86)\VIA\VIAudioi\VDeck\SoundEffectComponent.dll" ;"The file could not be scanned probably due to an invalid file structure (address a007bf9a1).";"Object is white-listed (critical/system file that should not be removed)"

After each of these were found, I got an alert:
AVG Scanning Core Module - Server Part has stopped working.

Decided to write to D-A-L. While browsing, IE stopped working briefly.
Message:
C:\Users\Sam\AppData\Local\Microsoft\Windows\Tempo rary Internet Files\Low\Content.IE5\08QP60GK\nav_red[1].gif
File could not be scanned probably due to an invalid file structure (address a0077bf9a1)
Detected on open.

While visiting Spybot S&D download page, got another quick blue screen, this time about SYSTEM_SERVICE_EXCEPTION
Restarted successfully.

Tried to run MBAM full scan, and it kept stopping.
Halfway through a quick scan I got a blue screen: BAD_POOL_HANDLER
Tried quick scan again: nothing malicious found.

Ran HJT. It told me to get hosts via the Run command.

Rebooted and ran another AVG scan. Nothing found.
MBAM still can't run a full scan.

Just now I brought the PC out of sleep and got a blue screen. Restarted and Windows Explorer would not start (or kept "stopping"). I shut down, started again and did a new HJT log.

I am completely baffled. I have done almost nothing on this PC, and there is not much on it besides a few programs, but it's quickly becoming a disaster. Any advice is greatly appreciated.

*****

I have serious doubts, if this is any infection, but...

Download BlueScreenView (in Zip file)
No installation required.
Unzip downloaded file and double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

================================================== =========

Please download VEW and save it to your Desktop: http://images.malwareremoval.com/vino/VEW.exe

Double-click VEW.exe then under Select log to query, select:
Application
System

Under Select type to list, select:
Critical (Vista only)
Error

Click the radio button for Number of events
Type 20 in the 1 to 20 box
Then click the Run button.
Notepad will open with the output log.

In Notepad, click Edit > Select all then Edit > Copy
Reply to this post, click in the reply window and press Ctrl+V on your keyboard to paste the log.

Thanks again, broni.

I ran both, but for some reason I had to search for the VEW log file.

*****

BSOD file
==================================================
Dump File : 052910-19156-01.dmp
Crash Time : 5/29/2010 8:04:49 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`02cd028c
Parameter 3 : fffff880`031b69c8
Parameter 4 : fffff880`031b6230
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+2c928c
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\052910-19156-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 052910-24804-01.dmp
Crash Time : 5/29/2010 6:53:07 PM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`039612e0
Parameter 3 : fffffa80`039610e0
Parameter 4 : fffffa80`039612e0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\052910-24804-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 052910-19125-01.dmp
Crash Time : 5/29/2010 6:46:04 PM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`03961320
Parameter 3 : fffffa80`03961120
Parameter 4 : fffffa80`03961320
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\052910-19125-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 052910-21418-01.dmp
Crash Time : 5/29/2010 6:28:55 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`02d77665
Parameter 3 : fffff880`0769c070
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\052910-21418-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 052910-20014-01.dmp
Crash Time : 5/29/2010 5:10:26 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00005003
Parameter 2 : fffff781`c0000000
Parameter 3 : 00000000`00002bb7
Parameter 4 : 00002bbf`0000556e
Caused By Driver : fileinfo.sys
Caused By Address : fileinfo.sys+7cba
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\052910-20014-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

VEW file
Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 29/05/2010 10:35:28 PM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 30/05/2010 12:06:33 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: explorer.exe, version: 6.1.7600.16450, time stamp: 0x4aebab8d Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b Exception code: 0xc0000005 Fault offset: 0x000000000004d400 Faulting process id: 0x690 Faulting application start time: 0x01caff8be98b1d73 Faulting application path: C:\Windows\explorer.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 345fe374-6b7f-11df-9ab4-e0cb4ebac608

Log: 'Application' Date/Time: 30/05/2010 12:06:06 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: explorer.exe, version: 6.1.7600.16450, time stamp: 0x4aebab8d Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b Exception code: 0xc0000005 Fault offset: 0x000000000004d400 Faulting process id: 0x58c Faulting application start time: 0x01caff8be0d4b414 Faulting application path: C:\Windows\explorer.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 2404cef6-6b7f-11df-9ab4-e0cb4ebac608

Log: 'Application' Date/Time: 30/05/2010 12:05:42 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: Explorer.EXE, version: 6.1.7600.16450, time stamp: 0x4aebab8d Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b Exception code: 0xc0000005 Fault offset: 0x000000000004d400 Faulting process id: 0xb04 Faulting application start time: 0x01caff8bd50801db Faulting application path: C:\Windows\Explorer.EXE Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 15d1f9b7-6b7f-11df-9ab4-e0cb4ebac608

Log: 'Application' Date/Time: 30/05/2010 12:05:29 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: Explorer.EXE, version: 6.1.7600.16450, time stamp: 0x4aebab8d Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b Exception code: 0xc0000005 Fault offset: 0x000000000004d400 Faulting process id: 0x6ec Faulting application start time: 0x01caff8bc4f2fee5 Faulting application path: C:\Windows\Explorer.EXE Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 0ddc5fce-6b7f-11df-9ab4-e0cb4ebac608

Log: 'Application' Date/Time: 30/05/2010 12:05:05 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: Explorer.EXE, version: 6.1.7600.16450, time stamp: 0x4aebab8d Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b Exception code: 0xc0000005 Fault offset: 0x000000000004d400 Faulting process id: 0xac8 Faulting application start time: 0x01caff8bc12b387f Faulting application path: C:\Windows\Explorer.EXE Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: ff832673-6b7e-11df-9ab4-e0cb4ebac608

Log: 'Application' Date/Time: 30/05/2010 12:05:04 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541 Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b Exception code: 0xc0000005 Fault offset: 0x0000000000051e02 Faulting process id: 0x874 Faulting application start time: 0x01caff8bb9e5c46a Faulting application path: C:\Windows\system32\Dwm.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: fefb7804-6b7e-11df-9ab4-e0cb4ebac608

Log: 'Application' Date/Time: 30/05/2010 12:04:57 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: svchost.exe_SENS, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1 Faulting module name: sens.dll, version: 6.1.7600.16385, time stamp: 0x4a5be06a Exception code: 0xc0000005 Fault offset: 0x0000000000001ad7 Faulting process id: 0x464 Faulting application start time: 0x01caff8bb559c385 Faulting application path: C:\Windows\system32\svchost.exe Faulting module path: c:\windows\system32\sens.dll Report Id: fafc0f5f-6b7e-11df-9ab4-e0cb4ebac608

Log: 'Application' Date/Time: 30/05/2010 12:04:57 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: Explorer.EXE, version: 6.1.7600.16450, time stamp: 0x4aebab8d Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b Exception code: 0xc0000005 Fault offset: 0x000000000004d400 Faulting process id: 0x8c0 Faulting application start time: 0x01caff8bba1ee571 Faulting application path: C:\Windows\Explorer.EXE Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: fafbe84f-6b7e-11df-9ab4-e0cb4ebac608

Log: 'Application' Date/Time: 29/05/2010 11:44:19 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: iexplore.exe, version: 8.0.7600.16385, time stamp: 0x4a5bc69e Faulting module name: DUser.dll, version: 6.1.7600.16385, time stamp: 0x4a5bda06 Exception code: 0xc0000005 Fault offset: 0x000108db Faulting process id: 0xdac Faulting application start time: 0x01caff88a5b55a83 Faulting application path: C:\Program Files (x86)\Internet Explorer\iexplore.exe Faulting module path: C:\Windows\system32\DUser.dll Report Id: 1902fc2a-6b7c-11df-bcc6-e0cb4ebac608

Log: 'Application' Date/Time: 29/05/2010 11:42:08 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: mbam.exe, version: 1.46.0.1, time stamp: 0x4bd9ed9b Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdb3b Exception code: 0xc0000005 Fault offset: 0x00032f15 Faulting process id: 0x2b8 Faulting application start time: 0x01caff8886265c28 Faulting application path: C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbam.exe Faulting module path: C:\Windows\SysWOW64\ntdll.dll Report Id: cada7756-6b7b-11df-bcc6-e0cb4ebac608

Log: 'Application' Date/Time: 29/05/2010 11:42:07 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: WerFault.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc2d9 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000001 Faulting process id: 0xaa4 Faulting application start time: 0x01caff888b7f1365 Faulting application path: C:\Windows\SysWOW64\WerFault.exe Faulting module path: unknown Report Id: ca8e4b4d-6b7b-11df-bcc6-e0cb4ebac608

Log: 'Application' Date/Time: 29/05/2010 11:42:05 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: mbam.exe, version: 1.46.0.1, time stamp: 0x4bd9ed9b Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdb3b Exception code: 0xc0000005 Fault offset: 0x00032f15 Faulting process id: 0x2b8 Faulting application start time: 0x01caff8886265c28 Faulting application path: C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbam.exe Faulting module path: C:\Windows\SysWOW64\ntdll.dll Report Id: c95ffc8b-6b7b-11df-bcc6-e0cb4ebac608

Log: 'Application' Date/Time: 29/05/2010 11:15:41 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: mbam.exe, version: 1.46.0.1, time stamp: 0x4bd9ed9b Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdb3b Exception code: 0xc0000005 Fault offset: 0x0002e29b Faulting process id: 0x4c0 Faulting application start time: 0x01caff84407b7709 Faulting application path: C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbam.exe Faulting module path: C:\Windows\SysWOW64\ntdll.dll Report Id: 1913707d-6b78-11df-b469-e0cb4ebac608

Log: 'Application' Date/Time: 29/05/2010 10:55:31 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: svchost.exe_ProfSvc, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1 Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b Exception code: 0xc0000005 Fault offset: 0x0000000000024bfa Faulting process id: 0x470 Faulting application start time: 0x01caff81b580f77f Faulting application path: C:\Windows\system32\svchost.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 47d934cc-6b75-11df-b469-e0cb4ebac608

Log: 'Application' Date/Time: 29/05/2010 10:43:56 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: mbam.exe, version: 1.46.0.1, time stamp: 0x4bd9ed9b Faulting module name: shell32.dll, version: 6.1.7600.16532, time stamp: 0x4b7cec9c Exception code: 0xc0000005 Fault offset: 0x00027049 Faulting process id: 0x6e4 Faulting application start time: 0x01caff806959b589 Faulting application path: C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbam.exe Faulting module path: C:\Windows\syswow64\shell32.dll Report Id: a98b5553-6b73-11df-8989-e0cb4ebac608

Log: 'Application' Date/Time: 29/05/2010 10:43:28 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: mbam.exe, version: 1.46.0.1, time stamp: 0x4bd9ed9b Faulting module name: shell32.dll, version: 6.1.7600.16532, time stamp: 0x4b7cec9c Exception code: 0xc0000005 Fault offset: 0x00027049 Faulting process id: 0xd30 Faulting application start time: 0x01caff80438482f3 Faulting application path: C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbam.exe Faulting module path: C:\Windows\syswow64\shell32.dll Report Id: 98d19666-6b73-11df-8989-e0cb4ebac608

Log: 'Application' Date/Time: 29/05/2010 10:41:58 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: iexplore.exe, version: 8.0.7600.16385, time stamp: 0x4a5bc69e Faulting module name: SHELL32.dll, version: 6.1.7600.16532, time stamp: 0x4b7cec9c Exception code: 0xc0000005 Fault offset: 0x00027049 Faulting process id: 0xe6c Faulting application start time: 0x01caff80207b8065 Faulting application path: C:\Program Files (x86)\Internet Explorer\iexplore.exe Faulting module path: C:\Windows\syswow64\SHELL32.dll Report Id: 62f829b7-6b73-11df-8989-e0cb4ebac608

Log: 'Application' Date/Time: 29/05/2010 10:41:44 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: iexplore.exe, version: 8.0.7600.16385, time stamp: 0x4a5bc69e Faulting module name: SHELL32.dll, version: 6.1.7600.16532, time stamp: 0x4b7cec9c Exception code: 0xc0000005 Fault offset: 0x00027049 Faulting process id: 0xc5c Faulting application start time: 0x01caff8001348783 Faulting application path: C:\Program Files (x86)\Internet Explorer\iexplore.exe Faulting module path: C:\Windows\syswow64\SHELL32.dll Report Id: 5ad17d43-6b73-11df-8989-e0cb4ebac608

Log: 'Application' Date/Time: 29/05/2010 10:40:54 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: iexplore.exe, version: 8.0.7600.16385, time stamp: 0x4a5bc69e Faulting module name: SHELL32.dll, version: 6.1.7600.16532, time stamp: 0x4b7cec9c Exception code: 0xc0000005 Fault offset: 0x00027049 Faulting process id: 0x914 Faulting application start time: 0x01caff7ff46d4888 Faulting application path: C:\Program Files (x86)\Internet Explorer\iexplore.exe Faulting module path: C:\Windows\syswow64\SHELL32.dll Report Id: 3d2d7692-6b73-11df-8989-e0cb4ebac608

Log: 'Application' Date/Time: 29/05/2010 10:30:31 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: Explorer.EXE, version: 6.1.7600.16450, time stamp: 0x4aebab8d Faulting module name: comctl32.dll, version: 6.10.7600.16385, time stamp: 0x4a5bde67 Exception code: 0xc0000409 Fault offset: 0x0000000000102200 Faulting process id: 0x79c Faulting application start time: 0x01caff7e5403c772 Faulting application path: C:\Windows\Explorer.EXE Faulting module path: C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_fa64 5303170382f6\comctl32.dll Report Id: c9c9201c-6b71-11df-8989-e0cb4ebac608

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 30/05/2010 12:04:38 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 29/05/2010 10:52:49 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 29/05/2010 10:45:59 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 29/05/2010 10:28:46 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 29/05/2010 9:10:16 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 30/05/2010 1:38:41 AM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk1\DR2.

Log: 'System' Date/Time: 30/05/2010 1:38:41 AM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk1\DR2.

Log: 'System' Date/Time: 30/05/2010 1:38:40 AM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk1\DR2.

Log: 'System' Date/Time: 30/05/2010 12:09:04 AM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk1\DR1.

Log: 'System' Date/Time: 30/05/2010 12:09:03 AM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk1\DR1.

Log: 'System' Date/Time: 30/05/2010 12:09:02 AM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk1\DR1.

Log: 'System' Date/Time: 30/05/2010 12:09:02 AM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk1\DR1.

Log: 'System' Date/Time: 30/05/2010 12:05:57 AM
Type: Error Category: 0
Event: 7032 Source: Service Control Manager
The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Shell Hardware Detection service, but this action failed with the following error: An instance of the service is already running.

Log: 'System' Date/Time: 30/05/2010 12:04:57 AM
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Windows Management Instrumentation service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.

Log: 'System' Date/Time: 30/05/2010 12:04:57 AM
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Themes service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

Log: 'System' Date/Time: 30/05/2010 12:04:57 AM
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Shell Hardware Detection service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

Log: 'System' Date/Time: 30/05/2010 12:04:57 AM
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The System Event Notification Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.

Log: 'System' Date/Time: 30/05/2010 12:04:57 AM
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Task Scheduler service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

Log: 'System' Date/Time: 30/05/2010 12:04:57 AM
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The User Profile Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.

Log: 'System' Date/Time: 30/05/2010 12:04:57 AM
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Multimedia Class Scheduler service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.

Log: 'System' Date/Time: 30/05/2010 12:04:57 AM
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Server service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

Log: 'System' Date/Time: 30/05/2010 12:04:57 AM
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The IP Helper service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.

Log: 'System' Date/Time: 30/05/2010 12:04:57 AM
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Group Policy Client service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.

Log: 'System' Date/Time: 30/05/2010 12:04:49 AM
Type: Error Category: 0
Event: 1001 Source: Microsoft-Windows-WER-SystemErrorReporting
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80002cd028c, 0xfffff880031b69c8, 0xfffff880031b6230). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052910-19156-01.

Log: 'System' Date/Time: 30/05/2010 12:04:44 AM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 8:03:37 PM on ?5/?29/?2010 was unexpected.

With those kind of errors, I'd suspect some hardware issues.
RAM would be my first suspect.
I'll remove your logs and I'll move this topic to Windows 7 forum.

A. If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-....iso.zip file.
3. Inside, you'll find memtest86+-....iso file.
4. Download, and install ImgBurn: The Official ImgBurn Website
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate memtest86+-....iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run.

The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

Hi, broni

I tried to check each stick of RAM by itself. I took one out and the PC started fine, but when I took out the second I couldn't get the first one to go back in. It just won't snap into place. I'm not sure if it's me or the sticks (they are G.Skill RipJaws) but I can't get the clips to snap closed so the sticks are just loose in there. I must be some sort of idiot because everyone says it's easy to install. The guys that assembled it had a plastic tie strip around both of the RAM slots, so maybe it's a really weird fit.

Anyway, until I can get these things back in, can we keep this thread open?

Not a problem. Nobody will close it.

With all those critical files displaying errors it looks to me like your OS might be corrupt BUT most of those errors pertain to memory management which could be caused by drivers/programs accessing memory incorrectly or by faulty ram. I agree with testing your ram to rule that out but you might need to eventfully reinstall windows. It could also be caused by a faulty hard drive so I recommend that you remove it from your computer and put it in another to allow you to back up your files if worst comes to worse. Don't boot into it on the other computer but use it as a secondary drive. You could also get a bootable version of Linux such as knoppix and use that to copy your files to another drive.

Edit: you made your post while I was typing mine but I'll leave it like it as is (because some of it might still apply) but I'll add that if you can't fit the ram in relativity easily then it probably isn't compatible. There shouldn't be a "really weird" fit nor should it need to be held in by tie straps. It should be completely in place with the tabs locked. If it isn't then it more than likely isn't the correct ram and if it isn't that could very easily be a possible reason for your problems. At this point we need to know more information about your computer to help you determine if you have the correct ram. Please answer the questions below as completely as possible.

townsbg:

Thanks for posting. RAM sticks went in fine once I understood how much pressure I needed to apply to get them in (I was being far too gentle. I tend to break things.). The PC started fine with each individual stick. Is that sufficient to rule out faulty RAM as the source of the problem?

As far as Windows and the hard drive go, I have absolutely no important data on this system, and very few programs installed. It's only a couple of weeks old, and I've not used it very much since I got it (a couple of hours a day since May 21). Everything worked great until Friday around 1am.

Is a Windows reinstallation difficult, and will there be any conflict with the initial installation?
Is there a way that I can test the HD?

Here's the system:
Windows 7 Home Premium Edition 64bit OEM
Processor: AMD Phenom II x4 965 Black Edition
Motherboard: Asus M4A79XTD Evo ATX AM3 790X
RAM: G.Skill F3-12800CL9D-4GBRL Ripjaws PC3-12800 4GB (2x2GB) DDR3-1600
Video: Powercolor Radeon HD 5770 850MHz 1GB 4.8GHz
Hard drive: Western Digital Caviar Black 640GB
PSU: OCZ Fatal1ty 550W ATX12V 20/24pin Active PFC ATX Modular 120MM fan

The system was built and tested by NCIX.com in Vancouver and shipped to me in Ontario. All cables are securely attached and managed. It was packed with lots of bubble wrap inside the case and outside.
I have no other OS on it. No major updates, only Security and other minor ones.

I've done my best to describe what happened in my initial post. The initial trouble occurred in the wee hours of the morning, and I was a little tired and slightly frantic so I can't be precise in every detail. Same with the restarts and blue screens the next day. I do recall that at some point (perhaps during the System Repair utility or during the System Restore), I got a warning that "WriterCall failed".

Everything from the reinstallation of firefox is just as it occurred.

To recap:

There was a failed startup, followed by an automatic System Repair attempt (failed), then an recommended System Repair (successful?). Then an inability to start WMP and AVG. Manual shutdown.

Next day, same software problems. Two unsuccessful System Repairs (including a "catastrophic failure"). Then a successful Restore to the previous evening.

Afternoon: Firefox crashes, uninstall/reinstall, blue screen about memory management. AVG found 3 unscannable dll files. Uninstalled firefox. AVG scan found 4 more unscannable files.

Evening: IE "stopped working" many times. BSOD: system service exception. MBAM will not scan fully (MBAM "stopped working"). Quick scan interrupted by BSOD: bad pool handler. Second quick scan found nothing.

Back from Sleep: BSOD. Windows Explorer "stopped working" many times. Restarted and posted logs to D-A-L. Windows Explorer and other programs operated without stopping.

The results of all the scans are posted above. Since the restart just above everything seems to be working. But I really haven't used it much beyond some internet browsing and the various scans done. I don't know if that means something worked or not.

That's all the info I can provide/remember. I hope it is helpful.

Is that sufficient to rule out faulty RAM as the source of the problem?

In some cases, re-seating RAM may help.
I assume, you have all RAM modules back right now?
Still same issues?