Sign in with
Sign up | Sign in
Your question


Last response: in Systems
January 31, 2013 12:47:46 AM

Hello all,

Built a new, very low budget ($350) system for my parents back in July 2012. Worked fine until a few months ago. Currently it just crashes constantly into the BSOD, in fact the system doesn't even finish loading all the start-up applications now and crashes into the BSOD.

I ran it in diagnostic mode, found that Skype and Avast (free edition) were taking up a lot of resources at start-up and turned Skype off from auto-booting in Windows start. Also uninstalled Avast and installed Ad-aware antivirus instead, which takes up less than a half of Avast resources. The system booted fine after that. Today it started crashing again.

Are the system specs too low for some moderate internet browsing? The CPU usage graph constantly jumps above 50% every time an internet browser window is opened or a new program is started. All my parents do is browse and watch videos online. Appreciate any recommendations on fixing or upgrading the system. Below is a quick summary of the build.

2.00 GB Dual-Channel DDR3 @ 532MHz (7-7-7-20)

Intel Celeron G530 Sandy Bridge 2.4GHz LGA 1155 65W Dual-Core Desktop Processor Intel HD Graphics BX80623G530

SeaSonic SS-300ES Bronze 300W ATX12V V2.3 80 PLUS BRONZE Certified Active PFC Power Supply - OEM

GIGABYTE GA-B75M-D3V LGA 1155 Intel B75 SATA 6Gb/s USB 3.0 Micro ATX Intel Motherboard

More about : bsod

a c 136 B Homebuilt system
January 31, 2013 1:43:15 AM

Avast is a very lightweight antivirus and it wont have been the problem

Try booting to safemode and see if it is stable
February 4, 2013 9:16:31 PM

Still not sure what is causing this. I replaced the two 1GB memory sticks with one of my 8GB G-skill Ares sticks to rule out memory. The interesting part is that the system BSOD's a little while after desktop is loaded (something obviously is still loading) if the network cable is hooked up. It doesn't crash when the system is started with the network cable out. Also, if loaded with the cable out and connected afterwards, the system doesn't seem to crash (I am currently on it).

The below from Windows Debugger, I am searching the internet for interpretation of this problem, but so far to no avail. Will appreciate any useful shred of information. I am considering upgrading the CPU and memory (to 4GB), but don't want to waste my money if the underlying problem will persist afterwards.

Thank in advance.

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is: srv*
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.120821-1629
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Jan 29 07:25:34.703 2013 (UTC - 5:00)
System Uptime: 0 days 0:01:34.364
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* *
* Bugcheck Analysis *
* *

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, 89ad1458, 89ad15cc, 805d22aa}

unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
Probably caused by : winsrv.dll ( winsrv!UserHardError+0 )

Followup: MachineOwner

1: kd> !analyze -v
* *
* Bugcheck Analysis *
* *

A process or thread crucial to system operation has unexpectedly exited or been
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arg1: 00000003, Process
Arg2: 89ad1458, Terminating object
Arg3: 89ad15cc, Process image file name
Arg4: 805d22aa, Explanatory message (ascii)

Debugging Details:

unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase


IMAGE_NAME: winsrv.dll


FAULTING_MODULE: 4a680000 csrss

PROCESS_NAME: csrss.exe

EXCEPTION_RECORD: a867c9d8 -- (.exr 0xffffffffa867c9d8)
ExceptionAddress: 75b7b421 (winsrv!UserHardError)
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000008
Parameter[1]: 75b7b421
Parameter[2]: c000000e
Inpage operation failed at 75b7b421, due to I/O error c000000e

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The required data was not placed into memory because of an I/O error status of "0x%08lx".


ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The required data was not placed into memory because of an I/O error status of "0x%08lx".




IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

EXCEPTION_STR: 0xc0000006_c000000e

75b7b421 ?? ???


75b7b421 ?? ???

SYMBOL_NAME: winsrv!UserHardError+0




FAILURE_BUCKET_ID: 0xF4_IOERR_C000000E_winsrv!UserHardError+0

BUCKET_ID: 0xF4_IOERR_C000000E_winsrv!UserHardError+0

Followup: MachineOwner

1: kd> !process ffffffff89ad1458 3
PROCESS 89ad1458 SessionId: 0 Cid: 02a8 Peb: 7ffd5000 ParentCid: 025c
DirBase: 78980060 ObjectTable: e1021a88 HandleCount: 496.
Image: csrss.exe
VadRoot 899dcad8 Vads 120 Clone 0 Private 314. Modified 2878. Locked 0.
DeviceMap e10092c0
Token e1892c58
ElapsedTime 00:01:11.937
UserTime 00:00:00.312
KernelTime 00:00:01.265
QuotaPoolUsage[PagedPool] 76244
QuotaPoolUsage[NonPagedPool] 6712
Working Set Sizes (now,min,max) (988, 50, 345) (3952KB, 200KB, 1380KB)
PeakWorkingSetSize 1556
VirtualSize 24 Mb
PeakVirtualSize 46 Mb
PageFaultCount 4409
MemoryPriority BACKGROUND
BasePriority 13
CommitCharge 373

THREAD 899e9840 Cid 02a8.02b0 Teb: 7ffde000 Win32Thread: e299f870 WAIT: (WrLpcReply) UserMode Non-Alertable
899e9a34 Semaphore Limit 0x1

THREAD 89a00600 Cid 02a8.02b4 Teb: 7ffdd000 Win32Thread: e2589420 WAIT: (UserRequest) UserMode Alertable
89c5e360 SynchronizationEvent
89c7b3e0 SynchronizationEvent
89c64928 SynchronizationEvent

THREAD 89af6cb0 Cid 02a8.02b8 Teb: 7ffdc000 Win32Thread: e1d0feb0 RUNNING on processor 1
THREAD 89af9020 Cid 02a8.02bc Teb: 7ffdb000 Win32Thread: 00000000 WAIT: (WrLpcReceive) UserMode Non-Alertable
89c5cae8 Semaphore Limit 0x7fffffff

THREAD 89aaf440 Cid 02a8.02c8 Teb: 7ffda000 Win32Thread: e1cefeb0 WAIT: (WrLpcReceive) UserMode Non-Alertable
89c5c368 Semaphore Limit 0x7fffffff

THREAD 89ad6610 Cid 02a8.02cc Teb: 7ffd9000 Win32Thread: e1db28c0 WAIT: (WrUserRequest) KernelMode Alertable
89ad8c68 SynchronizationEvent
89c7a4d8 SynchronizationEvent
89c5ced8 NotificationTimer
89d73350 SynchronizationEvent
80563720 NotificationEvent
89c79618 SynchronizationEvent
89ae2100 SynchronizationTimer

THREAD 89a18da0 Cid 02a8.02d0 Teb: 7ffd8000 Win32Thread: e1cdc6f0 WAIT: (WrUserRequest) UserMode Non-Alertable
89c81478 SynchronizationEvent
899fbbc0 SynchronizationEvent
89b36d10 SynchronizationEvent

THREAD 89710970 Cid 02a8.0300 Teb: 7ffd7000 Win32Thread: e1d745d8 WAIT: (WrUserRequest) UserMode Non-Alertable
8966f108 SynchronizationEvent
89c0d668 SynchronizationEvent

THREAD 89a6c7d0 Cid 02a8.0330 Teb: 7ffd6000 Win32Thread: e2410c20 WAIT: (WrLpcReceive) UserMode Non-Alertable
89c5c368 Semaphore Limit 0x7fffffff

THREAD 88f97bc0 Cid 02a8.05b0 Teb: 7ffd4000 Win32Thread: e2b712c0 WAIT: (WrLpcReceive) UserMode Non-Alertable
89c5c368 Semaphore Limit 0x7fffffff

THREAD 8900d2a0 Cid 02a8.0bb8 Teb: 7ffaf000 Win32Thread: 00000000 WAIT: (UserRequest) UserMode Non-Alertable
88f202ac NotificationEvent

Related resources
February 9, 2013 8:12:09 PM

Can anyone suggest steps to diagnose if this is a software or hardware issue, and if so what specifically? I took out the CMOS battery and popped it back in today, it seemed to have helped. The next few times I started the system with the network cable plugged it, I had no issues. So I told my parents to test it out, and 30 minutes later the system crashed while using Gmail.

Are there any good diagnostic software packages I could buy perhaps? This whole experience is going to teach me not to build myself. Never have this many problems with a ready-build system...
February 15, 2013 11:00:40 PM

Resolved: bad hard drive. 2 weeks later PC stopped recognizing.