Windows 7: BSOD after taking in PC to repair shop

Ferny84 · 19 Sep 2011

Hi everyone, I have been having problems with BSOD on my 1.5 year old PC.

It BSOD mainly whenever i'm playing a video game (World of Warcraft/League of Legends) but sometimes happens when i'm browsing the internet.

I have replaced the Hard Drive, Video Card, Memory and Power Supply but the BSOD still happens after that.

I have also removed all USB devices from my PC, just my Mouse and Keyboard are plugged in and it is still having the problem.

After a few weeks of not being able to fix the problem I took my PC to a PC repair shop (best in the city...and quite expensive). They took a look at my PC, checked power supply, hard drive, memory and video card and everything was fine. They even ran 3dMark on it for 24 hours and Youtube videos for another 24 hours and they could not find a problem! No BSOD or crashes!

The people at the PC repair shop said it could be something external connected to my PC like a mouse or keyboard but I have different types!

I even brought my PC to a friends house and it still crashed using his mouse and keyboard.

One thing I was thinking is that maybe it could be caused by the LCD monitor that I am using. It is a Asus VE208 LCD monitor.

Well here I am coming to you experts for help!

Please help me!

PC specs:
Windows 7 Professional 64BIT (OEM, got this from my school website MSDN, I formatted my PC just a week ago before taking my PC in and reinstalled Windows)
AMD Phenom II X2 550 Black Edition Dual Core Processor
OCZ ModXStream Pro 500W
ASUS M4A78T-E ATX
Western Digital Caviar Black 640GB 7200RPM
LG 16X DVD-ROM Optical Drive
Mushkin Enhanced Silverline Stiletto 8GB 2X4GB PC3-10666
XFX 5770 1gb video card

Ferny84 · 20 Sep 2011

Cans someone please help?

gregrocker · 21 Sep 2011

While you wait for a BSOD expert, install and run WhoCrashed, automatic crash dump analyzer.

Post back results if you need further help analyzing them.

Ferny84 · 24 Sep 2011

Here is the report:

System Information (local)
computer name: RICARDO-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X2 550 Processor AMD586, level: 16
2 logical processors, active mask: 3
RAM: 8588025856 total
VM: 2147352576, free: 1985974272

Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 24/09/2011 6:16:57 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF91, 0x1, 0xFFFFF80002F789F9, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown PAGE_FAULT_IN_NONPAGED_AREA

On Sun 18/09/2011 7:04:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091811-14773-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF88002A3A7F2)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown KMODE_EXCEPTION_NOT_HANDLED

On Sun 18/09/2011 5:47:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091811-18236-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x777C6)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002A8C7C6, 0xFFFFF88005EA15D8, 0xFFFFF88005EA0E40)
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 Sun 18/09/2011 5:20:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091811-21294-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800743C3C8, 0xFFFFF8800743BC30, 0xFFFFF80002AEB486)
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 Sun 11/09/2011 5:06:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091311-18517-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF880038297F2)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown KMODE_EXCEPTION_NOT_HANDLED

On Sat 10/09/2011 3:29:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090911-17206-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\091811-13369-01.dmp

Conclusion
On your computer a total of 7 crash dumps have been found. Only 6 could be analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

unknown

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

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.

gregrocker · 24 Sep 2011

Not very helpful, was it? While you wait for analysis of your crash dump file run Disk Check

Ferny84 · 27 Sep 2011

I tried Disk Check and it says the hard drive is fine.

So far I have tried a different monitor, mouse and keyboard and am still having BSOD.

Someone please help

Dave76 · 27 Sep 2011

Welcome to Seven Forums.

Please fill in your 'System Specs' in the lower left corner in any of your posts, this will help anyone that is looking at your case. It will also keep us from searching the thread for information.

Disconnect all peripherals that are not absolutely needed, 3 1/2" floppy drive, CD/DVD drive, any hubs, any external device, pretty much everything except what is needed for the computer to run.
This is for testing purposes, they can all be re-connected after the problem has been found.

D/L and run Western Digital Lifeguard – Quick Test and Extended Test
Be sure to run both tests, the extended test will take a while.

STOP 0x00000024: NTFS_FILE_SYSTEM
Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

Cause:
One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.

Another possible cause is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.

Try disabling any virus scanners, backup programs, or disk defragmenter tools that continually monitor the system. You should also run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer. Run Chkdsk /f /r to detect and resolve any file system structural corruption. You must restart the system before the disk scan begins on a system partition.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff8800743c3c8
Arg3: fffff8800743bc30
Arg4: fffff80002aeb486

Debugging Details:
------------------


EXCEPTION_RECORD:  fffff8800743c3c8 -- (.exr 0xfffff8800743c3c8)
ExceptionAddress: fffff80002aeb486 (nt!IoSetShareAccessEx+0x0000000000000016)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800743bc30 -- (.cxr 0xfffff8800743bc30)
rax=0000000000000000 rbx=0000000000000001 rcx=00000000000e0080
rdx=0000000000000007 rsi=fffffa80092b9368 rdi=fffff88007139400
rip=fffff80002aeb486 rsp=fffff8800743c608 rbp=0000000000000000
 r8=fffdfa8008f799d0  r9=fffff8a001635c40 r10=fffff8a000212000
r11=0000000000000007 r12=fffff88007139520 r13=fffff8a001635a80
r14=00000000000e0080 r15=fffff880071394b0
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!IoSetShareAccessEx+0x16:
fffff800`02aeb486 4588504a        mov     byte ptr [r8+4Ah],r10b ds:002b:fffdfa80`08f79a1a=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d010e0
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs!NtfsOpenAttribute+1b7
fffff880`010fca07 488b9c2410010000 mov     rbx,qword ptr [rsp+110h]

FAULTING_IP: 
nt!IoSetShareAccessEx+16
fffff800`02aeb486 4588504a        mov     byte ptr [r8+4Ah],r10b

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff880010fca07 to fffff80002aeb486

STACK_TEXT:  
fffff880`0743c608 fffff880`010fca07 : 00000000`00000000 fffff880`07139400 00000000`000001f0 fffff8a0`01635e18 : nt!IoSetShareAccessEx+0x16
fffff880`0743c610 fffff880`010eae45 : fffffa80`09281540 fffffa80`092b9368 fffffa80`07992180 fffff8a0`01635e18 : Ntfs!NtfsOpenAttribute+0x1b7
fffff880`0743c720 fffff880`010e778b : fffff880`071394b0 fffffa80`09281540 fffff8a0`01635e18 fffff8a0`00000024 : Ntfs!NtfsOpenExistingAttr+0x145
fffff880`0743c7e0 fffff880`010d0049 : fffffa80`09281540 fffffa80`092b9010 fffff8a0`01635e18 fffff8a0`00000024 : Ntfs!NtfsOpenAttributeInExistingFile+0x5ab
fffff880`0743c970 fffff880`010f3b04 : fffff880`071394b0 fffffa80`092b9010 fffffa80`09281540 00000000`00000000 : Ntfs!NtfsOpenFile+0x51d
fffff880`0743cb50 fffff880`0105cc0d : fffffa80`09281540 fffffa80`092b9010 fffff880`071394b0 fffffa80`0844ab00 : Ntfs!NtfsCommonCreate+0xc54
fffff880`0743cd30 fffff800`02ac1447 : fffff880`07139420 4a10aeec`ade75957 192f4969`c3b85174 c81f538c`63e4d84a : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`0743cd60 fffff800`02ac1401 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
fffff880`071392f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  Ntfs!NtfsOpenAttribute+1b7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

STACK_COMMAND:  .cxr 0xfffff8800743bc30 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsOpenAttribute+1b7

BUCKET_ID:  X64_0x24_Ntfs!NtfsOpenAttribute+1b7

Followup: MachineOwner
---------

After a quick look, all your drivers look ok, might need to come back to this.

This is pretty much the same as the one above.
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

This bug check indicates that a system thread generated an exception that the error handler did not catch.

Some basic troubleshooting techniques.

Make sure you have enough disk space.
If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
Try changing video adapters.
Check with your hardware vendor for any BIOS updates.
Disable BIOS memory options such as caching or shadowing.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002a8c7c6, The address that the exception occurred at
Arg3: fffff88005ea15d8, Exception Record Address
Arg4: fffff88005ea0e40, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!KiCommitThreadWait+2b6
fffff800`02a8c7c6 488901          mov     qword ptr [rcx],rax

EXCEPTION_RECORD:  fffff88005ea15d8 -- (.exr 0xfffff88005ea15d8)
ExceptionAddress: fffff80002a8c7c6 (nt!KiCommitThreadWait+0x00000000000002b6)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88005ea0e40 -- (.cxr 0xfffff88005ea0e40)
rax=fffff80002c041c8 rbx=fffff80002c041c0 rcx=fffdf80002c041c8
rdx=fffffdfffead8226 rsi=fffffa8008e34980 rdi=0000000000000001
rip=fffff80002a8c7c6 rsp=fffff88005ea1810 rbp=0000000000000000
 r8=fffff80002a15000  r9=0000000000007e00 r10=000000000000000f
r11=fffffa80073c9382 r12=0000000000000000 r13=0000000000000000
r14=fffff80002c02080 r15=00000000000000fa
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!KiCommitThreadWait+0x2b6:
fffff800`02a8c7c6 488901          mov     qword ptr [rcx],rax ds:002b:fffdf800`02c041c8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbd0e0
 ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!VidSchiWaitForSchedulerEvents+1bc
fffff880`03dd327c 8bd8            mov     ebx,eax

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80002a88beb to fffff80002a8c7c6

STACK_TEXT:  
fffff880`05ea1810 fffff800`02a88beb : fffffa80`08e3f000 fffffa80`08e3f000 00000000`000000fa 00000000`00000000 : nt!KiCommitThreadWait+0x2b6
fffff880`05ea18a0 fffff880`03dd327c : fffffa80`00000002 fffff880`05ea1ba8 00000000`00000001 00000000`00000000 : nt!KeWaitForMultipleObjects+0x271
fffff880`05ea1b50 fffff880`03da62c6 : ffffffff`ff676980 fffffa80`08e21410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1bc
fffff880`05ea1bf0 fffff880`03dd2e7a : 00000000`00000000 fffffa80`08ee3a80 00000000`00000080 fffffa80`08e21410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`05ea1d00 fffff800`02d256fa : 00000000`0382ce9b fffffa80`08e348c0 fffffa80`069ab9e0 fffffa80`08e348c0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`05ea1d40 fffff800`02a63b46 : fffff880`009e7180 fffffa80`08e348c0 fffff880`009f1f40 00010609`00000407 : nt!PspSystemThreadStartup+0x5a
fffff880`05ea1d80 00000000`00000000 : fffff880`05ea2000 fffff880`05e9c000 fffff880`05ea1690 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!VidSchiWaitForSchedulerEvents+1bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

STACK_COMMAND:  .cxr 0xfffff88005ea0e40 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VidSchiWaitForSchedulerEvents+1bc

BUCKET_ID:  X64_0x7E_dxgmms1!VidSchiWaitForSchedulerEvents+1bc

Followup: MachineOwner
---------

The driver mentioned, dxgmms1.sys, is a DirectX Graphics MMS driver and only available from a Windows update.

Lets take a look at your RAM.

First thing will be to run memtest86+ for a full 7 passes, this will take several hours.
Best to run overnight while you sleep.
If you get any errors you can stop the test and report here.

For the first test, run with both RAM cards installed.
We can look at the other tests in the tutorial if there are any errors.

Sometimes errors from these tests can be corrected by adjusting the settings.
RAM - Test with Memtest86+

D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

Have you been checking your temperatures?
Use Core Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.
This is important, I will need this information to help you further.

Dave76 · 28 Sep 2011

Here is some info from your event logs.

Update the anti-virus definitions from MS.
Have you been installing the Windows Updates?

Code:

Event[30]:
  Log Name: System
  Source: Microsoft Antimalware
  Date: 2011-09-19T11:39:11.000
  Event ID: 3002
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Ricardo-PC
  Description: 
Microsoft Antimalware Real-Time Protection feature has encountered an error and failed.
 	Feature: Behavior Monitoring
 	Error Code: 0x80004005
 	Error description: Unspecified error 
 	Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection.

Run the System File Checker.
Use this tutorial: SFC /SCANNOW Command - System File Checker
There are a lot of these errors.

Code:

Event[1389]:
  Log Name: System
  Source: Service Control Manager
  Date: 2011-09-18T11:56:25.379
  Event ID: 7001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Ricardo-PC
  Description: 
The Computer Browser service depends on the Server service which failed to start because of the following error: 
The dependency service or group failed to start.

This should be helped by running the System File Checker and the HDD diagnostic, WD Lifeguard.

Code:

Event[1407]:
  Log Name: System
  Source: Microsoft-Windows-DistributedCOM
  Date: 2011-09-18T11:49:24.000
  Event ID: 10005
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Ricardo-PC
  Description: 
DCOM got error "1084" attempting to start the service WSearch with arguments "" in order to run the server:
{7D096C5F-AC08-4F1F-BEB7-5C22C517CE39}

Will check these, and post something later.

Code:

Event[1416]:
  Log Name: System
  Source: Service Control Manager
  Date: 2011-09-18T11:49:10.074
  Event ID: 7026
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Ricardo-PC
  Description: 
The following boot-start or system-start driver(s) failed to load: 
discache
MpFilter
spldr
Wanarpv6

Code:

Event[3708]:
  Log Name: System
  Source: Service Control Manager
  Date: 2011-09-13T18:11:03.935
  Event ID: 7023
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Ricardo-PC
  Description: 
The Security Center service terminated with the following error: 
The authentication service is unknown.


Event[3770]:
  Log Name: System
  Source: Service Control Manager
  Date: 2011-09-13T18:09:30.986
  Event ID: 7023
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Ricardo-PC
  Description: 
The Windows Modules Installer service terminated with the following error: 
%%16405

Ferny84 · 29 Sep 2011

I disconnected my dvd drive, ethernet cable, headset, booted my PC up and got a BSOD as soon as I logged in.

I ran Western Digital Lifeguard, Quick Test was successful, when I ran the extended test, I didn't get a BSOD but my PC did crash(everything looked staticy and warped).

I updated my Motherboard BIOS last week, still getting BSOD.

I ran Memtest overnight (10+ hours) and there were no errors.

The memory/CPU voltages in BIOS are all set to auto.

Temps are fine.

Ferny84 · 29 Sep 2011

There is an unknown device that has a exclamation mark over it in Device Manager...

It says drivers are not installed for it so I just disabled it.

Running Western Digital Lifeguard again to see if system crashes.

Windows 7: BSOD after taking in PC to repair shop

BSOD after taking in PC to repair shop problems?