• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 867
  • Last Modified:

New computer keeps crashing with BSOD

I am getting random BSOD on a new desktop i've put together. Bellow is the latest memory dump.
The Event viewer just  reports same NTFS error for both C and D drives.

The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume D:.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


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

And this is the Dumpchk

Loading Dump File [C:\WINDOWS\Minidump\Mini021809-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.080814-1236
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Feb 18 03:10:02.312 2009 (GMT-5)
System Uptime: 0 days 0:03:12.037
Loading Kernel Symbols
.....................................................................................................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {e334d008, 0, 8054b0ba, 1}


Could not read faulting driver name
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+b4 )

Followup: Pool_corruption
---------

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: e334d008, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 8054b0ba, If non-zero, the instruction address which referenced the bad memory
      address.
Arg4: 00000001, (reserved)

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


Could not read faulting driver name

READ_ADDRESS:  e334d008

FAULTING_IP:
nt!ExDeferredFreePool+b4
8054b0ba 8b10            mov     edx,dword ptr [eax]

MM_INTERNAL_CODE:  1

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  lsass.exe

LAST_CONTROL_TRANSFER:  from 8054b75f to 8054b0ba

STACK_TEXT:  
ba14dc54 8054b75f 00000001 00000000 e335c9c0 nt!ExDeferredFreePool+0xb4
ba14dc94 805c106b e335c9b0 e56b6f54 8a8e40e8 nt!ExFreePoolWithTag+0x47f
ba14dcb4 805bb47a 00000000 e335c9c0 e335c9d8 nt!ObpFreeObject+0x18d
ba14dccc 805266da e335c9d8 00000000 00000294 nt!ObpRemoveObjectRoutine+0xe8
ba14dce4 805bc347 88d5c360 e1ab6438 89e496f0 nt!ObfDereferenceObject+0x4c
ba14dcfc 805bc3dd e1ab6438 e335c9d8 00000294 nt!ObpCloseHandleTableEntry+0x155
ba14dd44 805bc515 00000294 00000001 00000000 nt!ObpCloseHandle+0x87
ba14dd58 8054162c 00000294 00b9f854 7c90e4f4 nt!NtClose+0x1d
ba14dd58 7c90e4f4 00000294 00b9f854 7c90e4f4 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00b9f854 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!ExDeferredFreePool+b4
8054b0ba 8b10            mov     edx,dword ptr [eax]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExDeferredFreePool+b4

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  0x50_nt!ExDeferredFreePool+b4

BUCKET_ID:  0x50_nt!ExDeferredFreePool+b4

Followup: Pool_corruption
---------

0
PChelpKit
Asked:
PChelpKit
1 Solution
 
Dirtpatch-JenkinsCommented:
IS it a Windows Server 2003 system?

if so check out

http://support.microsoft.com/kb/832336
0
 
PChelpKitAuthor Commented:
No this is Windows XP
0
 
jamietonerCommented:
If it came with an xp cd boot to it and enter the recovery console and run chkdsk /r from the command prompt. If you continue to get the bsod run a diagnostic on the hard drive.
0
How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

 
PChelpKitAuthor Commented:
I've ran Chkdsk but the error keep coming back, and it happens on both drives. i am attaching all dump files.
0
 
nobusCommented:
i would start by testing ram and disks, to be sure about the basics
download ubcd, and run memetest86+ and the disk diag you need :
 http://www.tacktech.com/display.cfm?ttid=287
0
 
PChelpKitAuthor Commented:
Cheked all dirves, and memory, fund no errors, still BSOD... help
0
 
nobusCommented:
"lsass.exe" is the Local Security Authentication Server. It verifies the validity of user logons to your PC/Server. It generates the process responsible for authenticating users for the Winlogon service. This process is performed by using authentication packages such as the default Msgina.dll. If authentication is successful, Lsass generates the user's access token, which is used to launch the initial shell. Other processes that the user initiates inherit this token. More info

Note: The lsass.exe file is located in the folder C:\Windows\System32. In other cases, lsass.exe is a virus, spyware, trojan or worm! Check this with Security Task Manager.

from : http://www.neuber.com/taskmanager/process/lsass.exe.html
0
 
asmodeusnzCommented:
Re-install the OS, your wasting your time trying to fix it and chances of fixing it anyway are very slim.

You can try running Windows Repair if you havent done that already, but its likely that wont work either.

Do a full format (not a quick format) of your HDD to make sure its ok and re-install the OS.

This will get it running again and eliminate and virus/malware you probably got that caused this in the first place
0
 
nobusCommented:
>>  Do a full format (not a quick format)   <<    why ?  they are the same, the full just does a complete surface scan extra (why it takes so long)
0
 
PChelpKitAuthor Commented:
I seam like it was hardware related, i swapped the motherboard and ram and it looks good now.
0
 
nobusCommented:
yep - new boards DOA - happens far too oftne...
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now