BSOD Watching Youtube videos or just random BSOD

kenomote · 13 Mar 2012

Hello guys and i need help with this BSOD

it seems that when i watching youtube videos i get a lot of BSOD

here are my dmp files hope you guys can help me! Thanks!:)

kenomote · 15 Mar 2012

bump

writhziden · 15 Mar 2012

Antivirus Software:

Code:

avast!

Possible out of date drivers:

Code:

lv302af	8d8a9000	8d8aac00	Sat Jul 26 08:59:32 2008 (488b3bd4)	00013422		lv302af.sys
LVUSBSta	98af2000	98afa900	Sat Jul 26 08:59:36 2008 (488b3bd8)	0001726e		LVUSBSta.sys
LV302V32	8d637000	8d8a8f00	Sat Jul 26 09:05:07 2008 (488b3d23)	00275366		LV302V32.SYS
lvrs	8d8bf000	8d956a80	Sat Jul 26 09:05:18 2008 (488b3d2e)	000a0de0		lvrs.sys
mcdbus	91bab000	91bc7800	Tue Feb 24 03:42:13 2009 (49a3cf05)	0001e53c		mcdbus.sys
AtiPcie	8c011000	8c019000	Tue May 05 09:00:16 2009 (4a005480)	00012ec4		AtiPcie.sys
purendis	8d9e7000	8d9f1000	Fri Jun 05 22:32:39 2009 (4a29f167)	00013375		purendis.sys
pnarp	8d9dd000	8d9e7000	Sat Jun 06 00:07:38 2009 (4a2a07aa)	0000ce6e		pnarp.sys

lv302af.sys
LVUSBSta.sys
LV302V32.SYS
lvrs.sys
mcdbus.sys
AtiPcie.sys
purendis.sys
pnarp.sys

Code:


Loading Dump File [D:\Kingston\BSODDmpFiles\kenomote\031312-16863-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82e48000 PsLoadedModuleList = 0x82f90810
Debug session time: Tue Mar 13 09:33:13.037 2012 (UTC - 6:00)
System Uptime: 0 days 0:07:25.519
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.........
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000007, A driver has unlocked a page more times than it locked it
Arg2: 00027281, page frame number
Arg3: 00000080, current share count
Arg4: 00000000, 0

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


BUGCHECK_STR:  0x4E_7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82ebf541 to 82ed9aec

STACK_TEXT:  
ab527b5c 82ebf541 00027281 8424861c 887ef740 nt!MiPfnReferenceCountIsZero+0x24
ab527b78 82efca95 00000000 00000000 858fa7ec nt!MiRemoveLockedPageChargeAndDecRef+0x16b
ab527bd8 82e77930 88948c40 00000000 00000000 nt!MiWaitForInPageComplete+0x787
ab527bfc 82e7719c 00000000 00000000 00000000 nt!MiPfCompletePrefetchIos+0x6c
ab527c1c 82e6e27d 9a7f6758 88acfc80 88acfc80 nt!MmWaitForCacheManagerPrefetch+0x1b
ab527ca8 82ee8eff 85b826c0 9a7f66f0 855707d8 nt!CcPerformReadAhead+0x1dd
ab527d00 82eb5f2b 855707d8 00000000 88724738 nt!CcWorkerThread+0x18d
ab527d50 8305666d 80000000 9a7f6660 00000000 nt!ExpWorkerThread+0x10d
ab527d90 82f080d9 82eb5e1e 80000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiPfnReferenceCountIsZero+24
82ed9aec cc              int     3

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiPfnReferenceCountIsZero+24

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x4E_7_nt!MiPfnReferenceCountIsZero+24

BUCKET_ID:  0x4E_7_nt!MiPfnReferenceCountIsZero+24

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

Loading Dump File [D:\Kingston\BSODDmpFiles\kenomote\031312-15646-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82e00000 PsLoadedModuleList = 0x82f48810
Debug session time: Tue Mar 13 04:14:47.334 2012 (UTC - 6:00)
System Uptime: 0 days 0:20:59.817
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {40000, 2, 1, 82e68620}

Probably caused by : hardware

Followup: MachineOwner
---------
 *** Possible invalid call from 82e93b7d ( nt!MiInsertPageInFreeOrZeroedList+0x1e7 )
 *** Expected target 82e685f0 ( nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x0 )

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00040000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82e68620, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82f68718
Unable to read MiSystemVaType memory at 82f48160
 00040000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeAcquireQueuedSpinLockAtDpcLevel+20
82e68620 8908            mov     dword ptr [eax],ecx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  80786c18 -- (.trap 0xffffffff80786c18)
ErrCode = 00000002
eax=00040000 ebx=0000008c ecx=80786cac edx=854bf7dd esi=8531bf04 edi=854bf7cc
eip=82e68620 esp=80786c8c ebp=80786cb8 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
nt!KeAcquireQueuedSpinLockAtDpcLevel+0x20:
82e68620 8908            mov     dword ptr [eax],ecx  ds:0023:00040000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82e93b82 to 82e68620

POSSIBLE_INVALID_CONTROL_TRANSFER:  from 82e93b7d to 82e685f0

STACK_TEXT:  
80786c88 82e93b82 00000000 841d2f28 8531bf0c nt!KeAcquireQueuedSpinLockAtDpcLevel+0x20
80786cb8 82e63d9a 85504d10 855049a0 00000000 nt!MiInsertPageInFreeOrZeroedList+0x1ec
80786d44 82f8b483 00000000 80786d90 8300e66d nt!MmZeroPageThread+0x4c6
80786d50 8300e66d 8080a4d8 b0ec7363 00000000 nt!Phase1Initialization+0x14
80786d90 82ec00d9 82f8b46f 8080a4d8 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .trap 0xffffffff80786c18 ; kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CPU_CALL_ERROR

Followup: MachineOwner
---------
 *** Possible invalid call from 82e93b7d ( nt!MiInsertPageInFreeOrZeroedList+0x1e7 )
 *** Expected target 82e685f0 ( nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x0 )

Loading Dump File [D:\Kingston\BSODDmpFiles\kenomote\031312-14929-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82e1e000 PsLoadedModuleList = 0x82f66810
Debug session time: Mon Mar 12 22:25:52.768 2012 (UTC - 6:00)
System Uptime: 0 days 0:01:59.001
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.........
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 001904fb
Arg2: 8dd415a8
Arg3: 8dd41180
Arg4: 00000080

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


EXCEPTION_RECORD:  8dd415a8 -- (.exr 0xffffffff8dd415a8)
ExceptionAddress: 00000080
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000008
   Parameter[1]: 00000080
Attempt to execute non-executable address 00000080

CONTEXT:  8dd41180 -- (.cxr 0xffffffff8dd41180)
eax=00000080 ebx=00000000 ecx=887d89d8 edx=00000000 esi=887d8978 edi=00000000
eip=00000080 esp=8dd41670 ebp=8dd41684 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
00000080 ??              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

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:  00000008

EXCEPTION_PARAMETER2:  00000080

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82f86718
Unable to read MiSystemVaType memory at 82f66160
 00000080 

FOLLOWUP_IP: 
Ntfs!NtfsExtendedCompleteRequestInternal+107
8bc11a7b 5f              pop     edi

FAULTING_IP: 
+107
00000080 ??              ???

FAILED_INSTRUCTION_ADDRESS: 
+107
00000080 ??              ???

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from 8bb9d558 to 00000080

STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
8dd4166c 8bb9d558 887d8978 885e7e57 887d8978 0x80
8dd41684 8bb9db46 887d8978 885e7ca0 8dd416d8 fltmgr!FltpProcessIoCompletion+0x56
8dd41694 82e86b33 86415790 885e7ca0 887d8978 fltmgr!FltpPassThroughCompletion+0x98
8dd416d8 8bc11a7b 00000000 8dd41810 a0badc08 nt!IopfCompleteRequest+0x128
8dd416f0 8bc1564f 8dd41810 885e7ca0 00000000 Ntfs!NtfsExtendedCompleteRequestInternal+0x107
8dd41800 8bc1685f 8dd41810 885e7ca0 0120070a Ntfs!NtfsCommonWrite+0x2466
8dd419a4 82e5a4bc 8641c020 885e7ca0 885e7ca0 Ntfs!NtfsFsdWrite+0x2e1
8dd419bc 8bb9e20c 86415790 885e7ca0 00000000 nt!IofCallDriver+0x63
8dd419e0 8bb9e3cb 8dd41a00 86415790 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa
8dd41a18 82e5a4bc 86415790 885e7ca0 885e7ca0 fltmgr!FltpDispatch+0xc5
8dd41a30 82e52749 8dd41a70 00000000 8dd41cc4 nt!IofCallDriver+0x63
8dd41a44 82eb8aff 86416d70 86415790 8dd41b10 nt!IoSynchronousPageWrite+0x19d
8dd41b74 82eb9f3b 92dc92a0 92dc92b8 87153fc8 nt!MiFlushSectionInternal+0x828
8dd41bdc 82eada14 00429670 00003000 00000004 nt!MmFlushSection+0x78
8dd41c70 82eb6893 87429670 00000000 00000001 nt!CcFlushCache+0x329
8dd41ca8 82ebeed6 8dd41cc4 bd6c4589 85574310 nt!CcWriteBehind+0x105
8dd41d00 82e8bf2b 85574310 00000000 85584d48 nt!CcWorkerThread+0x164
8dd41d50 8302c66d 00000000 bd6c4519 00000000 nt!ExpWorkerThread+0x10d
8dd41d90 82ede0d9 82e8be1e 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  Ntfs!NtfsExtendedCompleteRequestInternal+107

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf45

STACK_COMMAND:  .cxr 0xffffffff8dd41180 ; kb

FAILURE_BUCKET_ID:  0x24_BAD_IP_Ntfs!NtfsExtendedCompleteRequestInternal+107

BUCKET_ID:  0x24_BAD_IP_Ntfs!NtfsExtendedCompleteRequestInternal+107

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

Possible causes are Memory problems... Drivers...
Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...
Possible causes are Memory problems... Corrupted hard disk file system... Drivers... corrupted SCSI or IDE Drivers...

Thanks to Dave76 for help understanding possible causes.

We will start with the common problems first (see bold possible causes). Do the following steps and test by doing your normal routine after each step to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

If you can do your normal routine for a few weeks without a crash, and your crashes are usually more frequent than that, then the problem is likely solved.

If you are overclocking any hardware, please stop.
Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
Use Bootable Hard Drive Diagnostics to determine your hard disk manufacturer and the manufacturer's hard disk diagnostic tools. If you are unable to find diagnostic tools for your manufacturer, run Seagate's SeaTools short and long tests on the drive. Otherwise, run the manufacturer's tests on the drive to determine whether the drive is faulty.
Monitor temperatures during the following tests.

Use the following programs to monitor the temperatures.
- Real Temp is a good CPU temperature monitor.
- Speccy - System Information - Free Download will monitor all hardware temperatures.
- HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
- Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
- Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

If you swap any memory components, follow these steps for ESD safety:
1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.

kenomote · 16 Mar 2012

In short i have problems with my Drivers?

writhziden · 16 Mar 2012

No, in short, it appears you have problems with your hardware. It could be an underlying driver issue, but the crashes point to hardware at this time.

kenomote · 17 Mar 2012

can it possibly be my HDD or RAM?

kenomote · 17 Mar 2012

well im not sure but since i updated my video card problems.......i think thats where it starts but its running fine......im also planning to reformat it to win7 64bit...cause of my 4gb ram

writhziden · 17 Mar 2012

kenomote said:

can it possibly be my HDD or RAM?

I gave you the steps in my first post to test the hardware to determine which hardware it is if you are still having problems.

kenomote said:

well im not sure but since i updated my video card problems.......i think thats where it starts but its running fine......im also planning to reformat it to win7 64bit...cause of my 4gb ram

You updated your video card drivers and now it is stable? Or did you replace the card itself? Your post is not clear what steps were taken...

kenomote · 17 Mar 2012

I already run test on my hardware except the Video Card everything is fine the HDD is good...i still dont know if the video card is the problem.....but the BSOD is just random.

kenomote · 17 Mar 2012

ok this two dmp happens two times in a row......and i was trying to transfer some files....before reformating it.