BSOD on startup (Login screen, desktop)

kenshin16 · 01 Jan 2013

My computer tends to auto restart during most startup. I have reinstalled windows 7 but the problem still exists. Attached are the files required for debugging. Please help because I have no idea what is causing the computer to crash so frequently at startups. Thanks a lot! (:

Regards,
Kenshin16

Arc · 01 Jan 2013

Hello kenshin16.

update the network driver. It is very old, and you are getting huge network blockage.
First, download the network card driver from manufactuer's website, Realtek
Then reinstall the driver as follows:

Click the Start Button, type "devmgmt.msc" (without quotation marks) in the Start Menu Search box and press Enter.
Double click to expand "Network adaptors".
Right click your network card and click Uninstall.
Check "Delete driver software for this device" check box, click OK.
Restart the computer
If windows does not auto configure the appropriate drivers at startup, install the downloaded one manually.

Apparently you dont have an antivirus installed?
Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download and install those, and then run full system scans with both of them, one by one.
Scan the system for possible virus infection with the following tools, too.

The dumps says it it is memory corruption.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff880016bb601, 0, ffffffffffffffff}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880016bb601, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf7100
GetUlongFromAddress: unable to read from fffff80002cf71c0
 0000000000000000 Nonpaged pool

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

FAULTING_IP: 
tcpip!UdpBeginDelivery+111
fffff880`016bb601 c3              ret

BUGCHECK_STR:  0x1E_c0000005_R

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002b12a88 to fffff80002ac7fc0

STACK_TEXT:  
fffff880`0338e138 fffff800`02b12a88 : 00000000`0000001e ffffffff`c0000005 fffff880`016bb601 00000000`00000000 : nt!KeBugCheckEx
fffff880`0338e140 fffff800`02ac7642 : fffff880`0338e918 fffffa80`0556d080 fffff880`0338e9c0 fffffa80`045dbd00 : nt! ?? ::FNODOBFM::`string'+0x487ad
fffff880`0338e7e0 fffff800`02ac5f4a : fffffa80`04fcb080 fffff880`016c16ba fffffa80`04fcb080 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0338e9c0 fffff880`016bb601 : 80fffff8`80016bb6 50fffffa`800556d0 00fffffa`80045dbc 11fffffa`80045dbd : nt!KiGeneralProtectionFault+0x10a
fffff880`0338eb59 80fffff8`80016bb6 : 50fffffa`800556d0 00fffffa`80045dbc 11fffffa`80045dbd 88000000`00000000 : tcpip!UdpBeginDelivery+0x111
fffff880`0338eb61 50fffffa`800556d0 : 00fffffa`80045dbc 11fffffa`80045dbd 88000000`00000000 a0fffff8`800338ec : 0x80fffff8`80016bb6
fffff880`0338eb69 00fffffa`80045dbc : 11fffffa`80045dbd 88000000`00000000 a0fffff8`800338ec 00fffff8`800338eb : 0x50fffffa`800556d0
fffff880`0338eb71 11fffffa`80045dbd : 88000000`00000000 a0fffff8`800338ec 00fffff8`800338eb 80fffff8`800338ec : 0x00fffffa`80045dbc
fffff880`0338eb79 88000000`00000000 : a0fffff8`800338ec 00fffff8`800338eb 80fffff8`800338ec 00fffffa`8004b801 : 0x11fffffa`80045dbd
fffff880`0338eb81 a0fffff8`800338ec : 00fffff8`800338eb 80fffff8`800338ec 00fffffa`8004b801 f0000000`00000000 : 0x88000000`00000000
fffff880`0338eb89 00fffff8`800338eb : 80fffff8`800338ec 00fffffa`8004b801 f0000000`00000000 00fffffa`80045eea : 0xa0fffff8`800338ec
fffff880`0338eb91 80fffff8`800338ec : 00fffffa`8004b801 f0000000`00000000 00fffffa`80045eea 01000000`00000000 : 0x00fffff8`800338eb
fffff880`0338eb99 00fffffa`8004b801 : f0000000`00000000 00fffffa`80045eea 01000000`00000000 00000000`00000000 : 0x80fffff8`800338ec
fffff880`0338eba1 f0000000`00000000 : 00fffffa`80045eea 01000000`00000000 00000000`00000000 ec000000`00000000 : 0x00fffffa`8004b801
fffff880`0338eba9 00fffffa`80045eea : 01000000`00000000 00000000`00000000 ec000000`00000000 01fffff8`80016434 : 0xf0000000`00000000
fffff880`0338ebb1 01000000`00000000 : 00000000`00000000 ec000000`00000000 01fffff8`80016434 00fffff8`800338ec : 0x00fffffa`80045eea
fffff880`0338ebb9 00000000`00000000 : ec000000`00000000 01fffff8`80016434 00fffff8`800338ec 00fffffa`80000000 : 0x01000000`00000000


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !tcpip
    fffff880016bb600 - tcpip!UdpBeginDelivery+110
    [ 78:79 ]
1 error : !tcpip (fffff880016bb600)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

Without taking a risk, test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

Finally, if possible, plan for a BIOS update.

Code:

BiosVendor = Award Software International, Inc.
BiosVersion = F7
BiosReleaseDate = 08/31/2009
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = EP45-UD3L

The BIOS is kinda old, for sure.

Let us know the results.

kenshin16 · 02 Jan 2013

Thank you Arc for taking time to help me out. Greatly appreciate it (:

I have done everything you have suggested. I have updated my network card driver and the BIOS as well.

I have used TDSSKiller, Windows Defender offline, free MBAM and my recently installed ESET to scan the whole computer, one at a time. All were optimised to perform the highest degree of scanning.

In addition, I let Memtest86+ run overnight to test the integrity of my memory/RAM. In the morning, when I saw the Memtest86+ screen, it showed 10 passes. However, the Memtest86+ hung at the 11th test at 82% passing mark; no buttons could be pressed, I had to force restart my computer.

After doing these, my computer still restarts and hangs itself at various places, although not all of the time: Start-up, login screen, and even the moment when I press the shut down button.

Attached are the updated details of my computer.

Thanks again for helping out Arc!

Arc · 03 Jan 2013

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff683f3000000, 0, fffff80002abf99b, 2}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 )

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

According to Carrona.org, STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

I may suggest you ....

► Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

► Run SFC /SCANNOW Command - System File Checker

► Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

► Do some Disc Checks.

Update your SSD's Firmware (Skip it, if it is not a SSD)
Re-seat the sata and power.
Run chkdsk /f/r, following the option two of the tutorial Disk Check
Seatool for dos: SeaTools | Seagate download
Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

The other two causes ....

BIOS, I guess you updated it recently.

Device Driver .... it will be our next search, if all those fails to detect anything.