Blue screen needs fixing!! Please Help!

Can anyone help me with this blue screen error,



It has been happening randomly every day for a few months, (Usually when Browsing the net) and its really starting to P*ss me off now.

I copied the error report

problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.256.6
Locale ID: 2057

Additional information about the problem:
BCCode: 19
BCP1: 00000022
BCP2: 10000000
BCP3: 00000000
BCP4: 00000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini052611-01.dmp
C:\Users\OWNER\AppData\Local\Temp\WER-75722-0.sysdata.xml
C:\Users\OWNER\AppData\Local\Temp\WERA459.tmp.version.txt

Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

-----------------------------------------------------------------------

Would be much appreciated if anyone can help me solve this, I know a little about PC's but not great amounts.

Thanks.

 

Thank you Plod,
Will install this and post results.

 

Have installed it, and to be honest I really dont what I am looking for. Could not save or copy a log so I have used Snipping Tool.

Would be great if somebody who knows more can help!!

 

Thank you Plod, think its the same all the time.


hal.dll hal.dll+7700 0x82e19000 0x82e4c000 0x00033000 0x49e018d9 11/04/2009 5:13:13 Microsoft® Windows® Operating System Hardware Abstraction Layer DLL 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\hal.dll



ntkrnlpa.exe ntkrnlpa.exe+b5c7c 0x82e4c000 0x83206000 0x003ba000 0x4cb710d6 14/10/2010 3:16:54 Microsoft® Windows® Operating System NT Kernel & System 6.0.6002.18327 (vistasp2_gdr.101014-0432) Microsoft Corporation C:\Windows\system32\ntkrnlpa.exe


Its these two that are highlighted,

Shall I delete the files?

 

Thanks Plod, yes Vista

Just downloading and making a Vista recovery disc as I can not boot into that Ststem Recovery Options.

Will be in touch soon.

 

Have just booted into the system Recovery Options, ran the Startup Repair, Found Nothing,

I then ran the Windows Memory Diagnostics Tool, and also found nothing,

Not looking too good is it?

Maybe time for a new PC I rekon.

 

Recovery for Vista

Often Having the blue screen thing.

Any help much appreciated.

Thanks

 

Re: Recovery for Vista

First you need to rule out any potential hardware problems.

If you can upload the minidump files, I'll try to analyse them. Open C:\Windows\Minidump\, copy the *.dmp files to your Desktop, zip (right-click > Send to > compressed folder) and attach the zip file to your post.

 

Hi Satrow, Thanks for the fast repy, Its just happened again, and its soo annoying!!

I have the 2 files on my desktop but having a little trouble uploading them to the site as I will have to uninstall Winrar.

Will post when done.

Thanks

 

Here are the both files.

 

have you checked for memory errors? 0x50 is usually memory, or lately, if you have viruses. mbr is infected.

 

Used Windows Memory Diagnostics Tool earlier, and found nothing. However, It may well be a memory problem as it does seem to shutdown when I click on a link or something.

Also think I'm virus free, have ran several AV programs. :confused

 

I haven't debugged it yet, just looked at the drivers listed in date order; first thought - uninstall Avast!, it looks like it was the most recent installation.

On to the debugging:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {95c4da38, 0, 8c5c5d29, 0}


Could not read faulting driver name
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b6d29 )

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

0: 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: 95c4da38, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 8c5c5d29, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from 82f70868
Unable to read MiSystemVaType memory at 82f50420
 95c4da38 

FAULTING_IP: 
nvlddmkm+1b6d29
8c5c5d29 8b4020          mov     eax,dword ptr [eax+20h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  iexplore.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8c5c4b02 to 8c5c5d29

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
80cd0988 8c5c4b02 95c4da18 80cd0a84 87c25430 nvlddmkm+0x1b6d29
80cd09b4 8c570f48 80cd0a84 00000000 80cd0a84 nvlddmkm+0x1b5b02
80cd0a40 8c4f7363 87c25430 8595e008 80cd0a84 nvlddmkm+0x161f48
80cd0a5c 8c4f8962 80cd0a84 8595e008 8595e008 nvlddmkm+0xe8363
80cd0a74 8c46d62c 80cd0a84 854d3528 c1d00fb0 nvlddmkm+0xe9962
80cd0b1c 8c46f693 caf00030 00000000 8570a7d0 nvlddmkm+0x5e62c
80cd0b3c 8c4456fa 854d3528 00000000 00000000 nvlddmkm+0x60693
80cd0b90 8ca0c9d4 80cd0c18 8806c008 80cd0c18 nvlddmkm+0x366fa
80cd0bb0 8ce75da7 8595e008 80cd0c18 b16035b8 nvlddmkm+0x5fd9d4
80cd0bcc 8ce75a3d 8595e008 80cd0c18 00000000 dxgkrnl!DXGADAPTER::DdiCloseAllocation+0x35
80cd0c38 8ce7615f 00000000 00000000 abf4d180 dxgkrnl!DXGDEVICE::DestroyAllocations+0x1d6
80cd0c94 8ce7673b 80cd0cf0 00000001 0c2b0f46 dxgkrnl!DXGDEVICE::DestroyAllocation+0x28a
80cd0d58 82e83c7a 19bafce0 19bafcf0 77045ca4 dxgkrnl!DxgkDestroyAllocation+0x538
80cd0d58 77045ca4 19bafce0 19bafcf0 77045ca4 nt!KiFastCallEntry+0x12a
19bafcf0 00000000 00000000 00000000 00000000 0x77045ca4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+1b6d29
8c5c5d29 8b4020          mov     eax,dword ptr [eax+20h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+1b6d29

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9e7e9b

FAILURE_BUCKET_ID:  0x50_nvlddmkm+1b6d29

BUCKET_ID:  0x50_nvlddmkm+1b6d29

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

This one, the most recent, suggests that the nVidia driver's at fault. "Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS" are the commonest causes for this BSOD.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 19, {22, 10000000, 0, 0}

GetPointerFromAddress: unable to read from 82f83868
Unable to read MiSystemVaType memory at 82f63420
Probably caused by : ntkrpamp.exe ( nt!ExpFindAndRemoveTagBigPages+1d5 )

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

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000022, 
Arg2: 10000000
Arg3: 00000000
Arg4: 00000000

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

GetPointerFromAddress: unable to read from 82f83868
Unable to read MiSystemVaType memory at 82f63420

BUGCHECK_STR:  0x19_22

POOL_ADDRESS: GetPointerFromAddress: unable to read from 82f83868
Unable to read MiSystemVaType memory at 82f63420
 10000000 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82f01c7c to 82f19b3f

STACK_TEXT:  
b5020a7c 82f01c7c 00000019 00000022 10000000 nt!KeBugCheckEx+0x1e
b5020ab8 82f3914a 10000000 b5020b04 b5020ae8 nt!ExpFindAndRemoveTagBigPages+0x1d5
b5020b2c 82f07eea 10000000 00000000 00000000 nt!ExFreePoolWithTag+0x145
b5020b50 88e20c10 85dd1528 b5020bb4 b5020b84 nt!ExDeleteResourceLite+0x51
b5020b60 88eaae19 85dd1528 00000000 869363d0 Ntfs!NtfsFreeEresource+0x6b
b5020b84 88e20af0 857f1ee8 b5020bb4 b5020bbe Ntfs!NtfsDeleteFcb+0xce
b5020bd8 88ea49d9 857f1ee8 86936270 afee2b48 Ntfs!NtfsTeardownFromLcb+0x250
b5020c28 88e1d186 857f1ee8 afee2c38 01000000 Ntfs!NtfsTeardownStructures+0xed
b5020c50 88e96e14 857f1ee8 afee2c38 00000000 Ntfs!NtfsDecrementCloseCounts+0xad
b5020cb0 88eaaa4b 857f1ee8 afee2c38 afee2b48 Ntfs!NtfsCommonClose+0x4da
b5020d44 82ef1e22 00000000 00000000 9e3d11f8 Ntfs!NtfsFspClose+0x117
b5020d7c 83021f7a 00000000 8c00a48f 00000000 nt!ExpWorkerThread+0xfd
b5020dc0 82e8aefe 82ef1d25 80000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExpFindAndRemoveTagBigPages+1d5
82f01c7c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExpFindAndRemoveTagBigPages+1d5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4cb710d6

FAILURE_BUCKET_ID:  0x19_22_nt!ExpFindAndRemoveTagBigPages+1d5

BUCKET_ID:  0x19_22_nt!ExpFindAndRemoveTagBigPages+1d5

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

"Usual causes: Device driver".



So, one thing at a time to try to get your PC stable; update or change the version of the nVidia graphics drivers, uninstall Avast! test the RAM with Memtest86+.

Avast! or the nVidia drivers should be the easiest to do - but any hardware error will trump drivers/software.

 

Thats very helpful, Thank you Satrow for taking the time to look into this for me,

Going to uninstall avast now,

Not sure about Nvidia as I only updated to the latest driver yestaday and have had my normal daily dose of the blue screen today. :yum

Will come back after to share the results.

bye for now.

 

Right,

Heres the steps I took.

1.Uninstalled Avast.
2.Unistalled all Nividia software/Drivers
3.Took cover off Computer & removed the Nvidia Graphics card
4.Updated the Intel graphics software
5.Cleaned up the registry using CCleaner

All seems to be running good, even better than before in fact.

I think it was something to do with the Nivida drivers, as when I bought the PC from new I put the Graphics card straight in and ever since have been having the Blue Screen thing.

Thank you all for the replys and time taken to help, If it happens once more, Its new PC time. :drool

All the best.
Carl :wave

 

Don't forget to re install some decent A/V and security software, I'd suggest the following as a minimum: MSE or Avira (or reinstall AVAST!), plus Malwarebytes for manual scanning and Secunia PSI to ensure your main programs/Java/Flash etc. are kept updated. Also consider installing a software firewall for some extra control.