New
#1
BSoD & Crashing with new PC
I'm getting random but infrequent BSoDs with my dad's new PC. I'm going to tell you everything i did so this may be long
*note* I have reinstalled windows 7x64 twice.
Specs:
Core i3 540
Intel DH55pj Motherboard
Corsair 2GB DDR3 1333mhz (VS2GB1333D3)
Seagate 250GB HDD
Coolermaster elite 334 with thermal master 420W PSU
*First win 7 install*
The system has Windows 7 x64 installed and was bought 1 week back.
Initially ran memtest86+ for over 3 passes which did not show an error after the first BSoD. The PC worked fine for a day or two so i thought that it was just a fluke. Then while using the PC, some programs (like firefox and the search indexer) crashed. I opened CPU-Z which caused the system to freeze for a bit and then i got another BSoD. Ran the Windows 7 memory test and it said there is a hardware problem with the memory. I went on to corsair forums and they said to change the memory timings to manually configured (seems to solve the problem for some) so i did and also put the ram into another mem slot.
Ran prime95 and CPU z for an hour or so and there was no prob with the system. I also ran memtest for over 14 passes and...once again no error.
I have updated the BIOS (did that right after the first BSoD). I've checked the timings and voltage of the RAM from Corsair's website (9-9-9-24 1.5v) and that's what i set.
Had ESET installed but removed it and installed MSE.
Checked the c drive using checkdisk /f /r and checked for bad sectors...none.
Did the SFC /scannow and got no error.
I saved the minidumps and uploaded them as 1st install.zip
*second windows install*
The first install went BSoD crazy so i reformatted the c partition on my HDD and installed win 7 x64 off a USB drive.
Reinstalling Windows 7 with drivers and some other essential programs (Office 2010, messenger, firefox) still caused the system to crash. At first it was firefox crashing, now different parts of the system crash (see below) and i got new BSoD's (page fault in non-paged area with win32.sys). Some minidumps i couldn't upload because event viewer says creating it failed . The system is really unstable at times and starting up in safe mode still causes firefox to crash. Could it be a hardware problem or a failed windows update of .net v4 causing this? or a corrupted install of win7 (though i checked the iso with win 7 iso checker)?
this repeatedly comes up at startup in the event viewer:
Session "Microsoft Security Essentials OOBE" stopped due to the following error: 0xC000000D
and these are the app crashes (most have multiple instances occuring like 4-5 times each):
Bug Check:Faulting application name: wmiprvse.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc794
Faulting module name: ole32.dll, version: 6.1.7600.16624, time stamp: 0x4c2984e3
Exception code: 0xc0000005
Fault offset: 0x000000000016f347
Faulting process id: 0x3b8
Faulting application start time: 0x01cb967301355e9f
Faulting application path: C:\Windows\system32\wbem\wmiprvse.exe
Faulting module path: C:\Windows\system32\ole32.dll
Report Id: 163905ed-0267-11e0-aa33-7071bca847ba
Faulting application name: WINWORD.EXE, version: 14.0.4734.1000, time stamp: 0x4b58fafb
Faulting module name: mso.dll, version: 14.0.4734.1000, time stamp: 0x4b59081c
Exception code: 0xc000041d
Fault offset: 0x0000000000022c81
Faulting process id: 0xf2c
Faulting application start time: 0x01cb9672c4a64a5e
Faulting application path: C:\Program Files\Microsoft Office\Office14\WINWORD.EXE
Faulting module path: C:\Program Files\Common Files\Microsoft Shared\office14\mso.dll
Report Id: 58af7417-0266-11e0-aa33-7071bca847ba
Faulting application name: svchost.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: RPCRT4.dll, version: 6.1.7600.16385, time stamp: 0x4a5be035
Exception code: 0xc0000005
Fault offset: 0x000000000004a154
Faulting process id: 0x48c
Faulting application start time: 0x01cb967078d7059c
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Windows\system32\RPCRT4.dll
Report Id: 9827f3b5-0265-11e0-aa33-7071bca847ba
Faulting application name: svchost.exe_SysMain, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: sysmain.dll, version: 6.1.7600.16385, time stamp: 0x4a5be07e
Exception code: 0xc0000005
Fault offset: 0x0000000000016d11
Faulting process id: 0x7c
Faulting application start time: 0x01cb9670780cb0a4
Faulting application path: C:\Windows\System32\svchost.exe
Faulting module path: c:\windows\system32\sysmain.dll
Report Id: 3853cded-0265-11e0-aa33-7071bca847ba
Faulting application name: msseces.exe, version: 1.0.2498.0, time stamp: 0x4c90a404
Faulting module name: gdiplus.dll, version: 6.1.7600.16385, time stamp: 0x4a5bde67
Exception code: 0xc000041d
Fault offset: 0x000000000009386b
Faulting process id: 0x9b8
Faulting application start time: 0x01cb967087964c0e
Faulting application path: C:\Program Files\Microsoft Security Essentials\msseces.exe
Faulting module path: C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7600.16385_none_2b4f45e87195f cc4\ gdiplus.dll
Report Id: ca03361a-0263-11e0-aa33-7071bca847ba
Faulting application name: lsass.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc155
Faulting module name: lsasrv.dll, version: 6.1.7600.16484, time stamp: 0x4b220e26
Exception code: 0xc000001d
Fault offset: 0x00000000000235ad
Faulting process id: 0x260
Faulting application start time: 0x01cb967027eb729b
Faulting application path: C:\Windows\system32\lsass.exe
Faulting module path: C:\Windows\system32\lsasrv.dll
Report Id: 7b0d3987-0263-11e0-aa52-7071bca847ba
Faulting application name: firefox.exe, version: 1.9.2.3951, time stamp: 0x4cc7ae16
Faulting module name: xul.dll, version: 1.9.2.3951, time stamp: 0x4cc7ad7f
Exception code: 0xc0000409
Fault offset: 0x000b99da
Faulting process id: 0x4d8
Faulting application start time: 0x01cb966bc73d2c90
Faulting application path: C:\Program Files (x86)\Mozilla Firefox\firefox.exe
Faulting module path: C:\Program Files (x86)\Mozilla Firefox\xul.dll
Report Id: 15edf4b6-025f-11e0-bd58-7071bca847ba
Faulting application name: svchost.exe_Winmgmt, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: wbemcore.dll, version: 6.1.7600.16385, time stamp: 0x4a5be088
Exception code: 0xc000001d
Fault offset: 0x00000000000108ed
Faulting process id: 0x7b8
Faulting application start time: 0x01cb96686d902d39
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Windows\system32\wbem\wbemcore.dll
Report Id: b42ea3e1-025b-11e0-bd58-7071bca847ba
Faulting application name: svchost.exe_ProfSvc, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: wbemcore.dll, version: 6.1.7600.16385, time stamp: 0x4a5be088
Exception code: 0xc000001d
Fault offset: 0x00000000000108ed
Faulting process id: 0x3ac
Faulting application start time: 0x01cb9667bfa0e074
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Windows\system32\wbem\wbemcore.dll
Report Id: 0f3f8b25-025b-11e0-bd58-7071bca847ba
Faulting application name: Explorer.EXE, version: 6.1.7600.16450, time stamp: 0x4aebab8d
Faulting module name: dwmapi.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdf27
Exception code: 0xc000041d
Fault offset: 0x000000000000282b
Faulting process id: 0x978
Faulting application start time: 0x01cb9622a4e99ba6
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: C:\Windows\system32\dwmapi.dll
Report Id: 57568c62-0216-11e0-a760-7071bca847ba
Faulting application name: TrustedInstaller.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc4b0
Faulting module name: wcp.dll, version: 6.1.7600.16385, time stamp: 0x4a5be07d
Exception code: 0x80000003
Fault offset: 0x0000000000235d17
Faulting process id: 0xb5c
Faulting application start time: 0x01cb962321adeee1
Faulting application path: C:\Windows\servicing\TrustedInstaller.exe
Faulting module path: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810b\ wcp.dll
Report Id: 603c9c7b-0216-11e0-a760-7071bca847ba
Faulting application name: mmc.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc808
Faulting module name: mscorwks.dll, version: 2.0.50727.4952, time stamp: 0x4bebe78c
Exception code: 0xc0000005
Fault offset: 0x00000000002000e9
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
Faulting application name: wmpnetwk.exe, version: 12.0.7600.16385, time stamp: 0x4a5bd03d
Faulting module name: SHELL32.dll, version: 6.1.7600.16644, time stamp: 0x4c4ef25d
Exception code: 0xc0000409
Fault offset: 0x000000000009d8e1
Faulting process id: 0x6fc
Faulting application start time: 0x01cb95c5442420d5
Faulting application path: C:\Program Files\Windows Media Player\wmpnetwk.exe
Faulting module path: C:\Windows\system32\SHELL32.dll
Report Id: ee40e951-01b9-11e0-a21b-7071bca847ba
Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: WindowsCodecs.dll, version: 6.1.7600.16385, time stamp: 0x4a5be0a5
Exception code: 0xc0000005
Fault offset: 0x000000000003256f
Faulting process id: 0x950
Faulting application start time: 0x01cb95c11aac1a61
Faulting application path: C:\Windows\system32\Dwm.exe
Faulting module path: C:\Windows\system32\WindowsCodecs.dll
Report Id: c1ea9a9e-01b4-11e0-a21b-7071bca847ba
A critical system process, C:\Windows\system32\lsass.exe, failed with status code 255. The machine must now be restarted.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffff800c00b1030, 0x0000000000000000, 0xfffff9600031ad93, 0x0000000000000005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffff800c2b180e0, 0x0000000000000000, 0xfffff96000113cd2, 0x0000000000000005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffff6837f797cf0, 0x0000000000000000, 0xfffff80002b9ea56, 0x0000000000000005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 121010-75816-01.
Multiple instances of this:
Oh and the USB drive i installed win 7 from always shows this whenever it was inserted (but i've formatted and run checkdisk on it which doesn't cause this prob anymore):Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Host Process for Windows Services because of this error.
Program: Host Process for Windows Services
File:
The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.
Additional Data
Error value: 00000000
Disk type: 0
The driver detected a controller error on \Device\Harddisk1\DR5.
Ran sfc /scannow and got errors this time. System restore didn't fix it so i'm going to reinstall win 7 again before taking the pc back to the shop. Could anyone tell me what's going on?