Random - BSOD Need Help!

[aleks82]

Hello I am new at Sevenforums, and I am seeking for help, my PC gets BSODs at random times even though its new (not even 2 weeks old)
everything is every piece of hardware, I do not really know what could cause the BSODs, I need experts help, here is the info I can provide

I am running : Win 7 Pro x64
Motherboard: ASUS P7P55D-E
CPU: Intel Core i5-760
Video: nVIDIA GeForce GTS 450

I also should mention that I am getting constant crashes of applications random applications browers, my av (Kaspersky Internet Security) got ruined and so on
I did use Bluescreenview to analyze the dump maybe it can be useful (screenshot attached)

Here are also the requested information regarding the BSOD Instructions Post attached


Would really appreciate your help

 

[zigzag3143]

Hello I am new at Sevenforums, and I am seeking for help, my PC gets BSODs at random times even though its new (not even 2 weeks old)
everything is every piece of hardware, I do not really know what could cause the BSODs, I need experts help, here is the info I can provide

I am running : Win 7 Pro x64
Motherboard: ASUS P7P55D-E
CPU: Intel Core i5-760
Video: nVIDIA GeForce GTS 450

I also should mention that I am getting constant crashes of applications random applications browers, my av (Kaspersky Internet Security) got ruined and so on
I did use Bluescreenview to analyze the dump maybe it can be useful (screenshot attached)

Here are also the requested information regarding the BSOD Instructions Post attached


Would really appreciate your help

I would start by removing Kaspersky, and updating these drivers

lv302a64.sys    7/26/2008 11:06:31 AM        fffff880`02971000    fffff880`02973380    0x00002380    0x488b3d77                        
LVUSBS64.sys    7/26/2008 11:06:36 AM        fffff880`053f5000    fffff880`053ff980    0x0000a980    0x488b3d7c                        
lvrs64.sys    7/26/2008 11:09:02 AM        fffff880`02600000    fffff880`026bf580    0x000bf580    0x488b3e0e                        
LV302V64.SYS    7/26/2008 11:09:08 AM        fffff880`026f1000    fffff880`02970180    0x0027f180    0x488b3e14

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Removing Kaspersky and replacing it with Microsoft Security essentials

http://support.kaspersky.com/downloads/utils/kavremover10.zip

Virus, Spyware & Malware Protection | Microsoft Security Essentials

 

[aleks82]

Thank your very much for your reply,

I did follow your instructions and did uninstall Kaspersky, the PC runs now much more smother and is more responsive, no crashes or BSODs till now, now I am updating the specified drivers, if anything else happens will infor you, thank you very much

 

[zigzag3143]

Thank your very much for your reply,

I did follow your instructions and did uninstall Kaspersky, the PC runs now much more smother and is more responsive, no crashes or BSODs till now, now I am updating the specified drivers, if anything else happens will infor you, thank you very much

My pleasure and let us know if you need further assistance.

 

[aleks82]

Hello, sadly news, today just got another BSOD totally random I think while the PC was sleeping, here are as usual the BSOD info attached, waiting for your reply

 

[aleks82]

anything new, today I did got another BSOD, please I need help

 

[aleks82]

4 BSODs till now, totally random

NTFS_FILE_SYSTEM 0x24
MEMORY_MANAGEMENT 0x1a
MEMORY_MANAGEMENT 0x1a
PAGE_FAULT_IN_NONPAGED_AREA 0x50

I need help!

 

[zigzag3143]

4 BSODs till now, totally random

NTFS_FILE_SYSTEM 0x24
MEMORY_MANAGEMENT 0x1a
MEMORY_MANAGEMENT 0x1a
PAGE_FAULT_IN_NONPAGED_AREA 0x50

I need help!

Most recent crash was blamed on Diectx. I would start by re-installing y our video driver and directX. If that doesnt fix it we may need to start looking at the video card, temps, and power.

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper


Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\061311-15600-01.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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02c1f000 PsLoadedModuleList = 0xfffff800`02e64650
Debug session time: Mon Jun 13 14:38:23.342 2011 (GMT-4)
System Uptime: 0 days 0:07:11.684
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8200158ebd0, 0, fffff88004237953, 5}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_LINEAR_POOL::Free+f )

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

3: 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: fffff8200158ebd0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88004237953, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ece100
 fffff8200158ebd0 

FAULTING_IP: 
dxgmms1!VIDMM_LINEAR_POOL::Free+f
fffff880`04237953 833a04          cmp     dword ptr [rdx],4

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800849f030 -- (.trap 0xfffff8800849f030)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8005e95500
rdx=fffff8200158ebd0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004237953 rsp=fffff8800849f1c0 rbp=fffff8a00223b6c0
 r8=0000000000000004  r9=fffff88002fd3180 r10=0000000000000000
r11=fffffa8005eb0580 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
dxgmms1!VIDMM_LINEAR_POOL::Free+0xf:
fffff880`04237953 833a04          cmp     dword ptr [rdx],4 ds:0404:fffff820`0158ebd0=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c493cf to fffff80002c9ed00

STACK_TEXT:  
fffff880`0849eec8 fffff800`02c493cf : 00000000`00000050 fffff820`0158ebd0 00000000`00000000 fffff880`0849f030 : nt!KeBugCheckEx
fffff880`0849eed0 fffff800`02c9ce2e : 00000000`00000000 fffff820`0158ebd0 00000000`00000000 fffff8a0`028f5ec0 : nt! ?? ::FNODOBFM::`string'+0x44891
fffff880`0849f030 fffff880`04237953 : 00000000`00000001 fffff880`04205ee3 00000000`00000000 fffffa80`03c09d90 : nt!KiPageFault+0x16e
fffff880`0849f1c0 fffff880`042355eb : fffffa80`05721000 00000000`02a67000 00000000`00040000 fffff8a0`028f5ec0 : dxgmms1!VIDMM_LINEAR_POOL::Free+0xf
fffff880`0849f210 fffff880`0423554a : fffff8a0`036fc788 fffffa80`05d53300 fffffa80`05d61140 fffff880`0f07acf1 : dxgmms1!VIDMM_PROCESS_HEAP::FreeSmallAllocation+0x8b
fffff880`0849f240 fffff880`04220b5a : fffff880`0849f450 fffff8a0`013e7490 00000000`00000001 fffffa80`04dc7000 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0x13a
fffff880`0849f270 fffff880`0421b523 : fffffa80`05b11280 00000000`00000001 fffff8a0`0223b6c0 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x112
fffff880`0849f320 fffff880`04201ecc : fffff8a0`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`0849f3f0 fffff880`0fd1fccc : 00000000`00000000 fffff8a0`01687000 fffff8a0`01687000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`0849f420 fffff880`0fd1f65f : fffff8a0`01687000 fffff8a0`01688300 fffff8a0`00000000 00000000`00000799 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`0849f510 fffff880`0fd4d74f : 00000000`00000000 fffff8a0`013e9f40 fffff8a0`012b61b0 fffff880`0849f930 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3
fffff880`0849f560 fffff880`0fd4ce7b : fffff8a0`00000799 fffff8a0`012b61b0 fffff880`0849f8c0 fffff880`0849f8f0 : dxgkrnl!DXGCONTEXT::Present+0x2cb
fffff880`0849f880 fffff960`001de12c : fffffa80`05eb0580 00000000`00000000 fffff8a0`021e7430 fffff8a0`00000010 : dxgkrnl!DxgkPresent+0x543
fffff880`0849fbf0 fffff800`02c9df93 : fffffa80`05eb0580 00000000`0237fa80 000007fe`f89dc610 fffffa80`00000000 : win32k!NtGdiDdDDIPresent+0x18
fffff880`0849fc20 000007fe`fe85145a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0237eb98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fe85145a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_LINEAR_POOL::Free+f
fffff880`04237953 833a04          cmp     dword ptr [rdx],4

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_LINEAR_POOL::Free+f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_LINEAR_POOL::Free+f

BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_LINEAR_POOL::Free+f

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

 

[aleks82]

Hello, thanks for your reply

I did uninstall the Video Drivers also used the sweeper and installed the driver which came with the video card (not the latest) hope it will be the end of all this mess.
Anyhow I also should tell a little more regarding the BSODs, I first received 2 BSODs while I was installing the OS, could that have been the video card no idea but what about the other BSODs before the latest,

I researched a lot on the internet regarding these which pointed me to do some tests like the Windows Memory Diagnostic Test (which turned no errors) and chkdsk which found some errors and fixed them here is also the log

Checking file system on C:
The type of the file system is NTFS.


A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 3)...
The bytes available, 0x480, in the file record segment header for
file 0x3e8d is incorrect.  The expected value is 0x400.
Deleting corrupt file record segment 16013.
  157440 file records processed.                                          File verification completed.
  46 large file records processed.                                      0 bad file records processed.                                        2 EA records processed.                                              60 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 3)...
The file reference 0x1000000003e8c of index entry ksc.nlp of index $I30
with parent 0x2e9 is not the same as 0x17000000003e8c.
Deleting index entry ksc.nlp in index $I30 of file 745.
The file reference 0x1000000003e8c of index entry ksc.nlp of index $I30
with parent 0x7ff is not the same as 0x17000000003e8c.
Deleting index entry ksc.nlp in index $I30 of file 2047.
The file reference 0x1000000003e8c of index entry ksc.nlp of index $I30
with parent 0x22c6 is not the same as 0x17000000003e8c.
Deleting index entry ksc.nlp in index $I30 of file 8902.
Unable to locate the file name attribute of index entry normidna.nlp
of index $I30 with parent 0x22c6 in file 0x3e8f.
Deleting index entry normidna.nlp in index $I30 of file 8902.
Index entry mscorlib.dll of index $I30 in file 0x3496 points to unused file 0x3e8d.
Deleting index entry mscorlib.dll in index $I30 of file 13462.
The file reference 0x4000000003e8c of index entry B06A97~1.CUS of index $I30
with parent 0x5524 is not the same as 0x17000000003e8c.
Deleting index entry B06A97~1.CUS in index $I30 of file 21796.
The file reference 0x5000000003e8c of index entry B06A97~2.CUS of index $I30
with parent 0x5524 is not the same as 0x17000000003e8c.
Deleting index entry B06A97~2.CUS in index $I30 of file 21796.
The file reference 0x6000000003e8c of index entry B06A97~3.CUS of index $I30
with parent 0x5524 is not the same as 0x17000000003e8c.
Deleting index entry B06A97~3.CUS in index $I30 of file 21796.
The file reference 0x7000000003e8c of index entry B06A97~4.CUS of index $I30
with parent 0x5524 is not the same as 0x17000000003e8c.
Deleting index entry B06A97~4.CUS in index $I30 of file 21796.
The file reference 0x8000000003e8c of index entry B0B2C8~1.CUS of index $I30
with parent 0x5524 is not the same as 0x17000000003e8c.
Deleting index entry B0B2C8~1.CUS in index $I30 of file 21796.
The file reference 0x9000000003e8c of index entry B0B2C8~2.CUS of index $I30
with parent 0x5524 is not the same as 0x17000000003e8c.
Deleting index entry B0B2C8~2.CUS in index $I30 of file 21796.
The file reference 0xa000000003e8c of index entry B0B2C8~3.CUS of index $I30
with parent 0x5524 is not the same as 0x17000000003e8c.
Deleting index entry B0B2C8~3.CUS in index $I30 of file 21796.
The file reference 0xb000000003e8c of index entry B0B2C8~4.CUS of index $I30
with parent 0x5524 is not the same as 0x17000000003e8c.
Deleting index entry B0B2C8~4.CUS in index $I30 of file 21796.
The file reference 0xc000000003e8c of index entry B0B2C8~5.CUS of index $I30
with parent 0x5524 is not the same as 0x17000000003e8c.
Deleting index entry B0B2C8~5.CUS in index $I30 of file 21796.
The file reference 0xd000000003e8c of index entry B0B2C8~6.CUS of index $I30
with parent 0x5524 is not the same as 0x17000000003e8c.
Deleting index entry B0B2C8~6.CUS in index $I30 of file 21796.
The file reference 0xf000000003e8c of index entry B0B2C8~7.CUS of index $I30
with parent 0x5524 is not the same as 0x17000000003e8c.
Deleting index entry B0B2C8~7.CUS in index $I30 of file 21796.
The file reference 0x10000000003e8c of index entry B0B2C8~8.CUS of index $I30
with parent 0x5524 is not the same as 0x17000000003e8c.
Deleting index entry B0B2C8~8.CUS in index $I30 of file 21796.
The file reference 0x11000000003e8c of index entry B0B2C8~9.CUS of index $I30
with parent 0x5524 is not the same as 0x17000000003e8c.
Deleting index entry B0B2C8~9.CUS in index $I30 of file 21796.
The file reference 0x12000000003e8c of index entry B0B2C~10.CUS of index $I30
with parent 0x5524 is not the same as 0x17000000003e8c.
Deleting index entry B0B2C~10.CUS in index $I30 of file 21796.
The file reference 0x14000000003e8c of index entry B0B2C~11.CUS of index $I30
with parent 0x5524 is not the same as 0x17000000003e8c.
Deleting index entry B0B2C~11.CUS in index $I30 of file 21796.
The file reference 0x15000000003e8c of index entry B0B2C~12.CUS of index $I30
with parent 0x5524 is not the same as 0x17000000003e8c.
Deleting index entry B0B2C~12.CUS in index $I30 of file 21796.
The file reference 0x2000000003e8c of index entry DEFRAG~1.PF of index $I30
with parent 0xe641 is not the same as 0x17000000003e8c.
Deleting index entry DEFRAG~1.PF in index $I30 of file 58945.
The file reference 0x3000000003e8c of index entry SVCHOS~4.PF of index $I30
with parent 0xe641 is not the same as 0x17000000003e8c.
Deleting index entry SVCHOS~4.PF in index $I30 of file 58945.
The file reference 0x1000000003e8c of index entry ksc.nlp of index $I30
with parent 0x10947 is not the same as 0x17000000003e8c.
Deleting index entry ksc.nlp in index $I30 of file 67911.
The file reference 0x1000000003e8c of index entry ksc.nlp of index $I30
with parent 0x10948 is not the same as 0x17000000003e8c.
Deleting index entry ksc.nlp in index $I30 of file 67912.
  189490 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 3)...
  157440 file SDs/SIDs processed.                                         Cleaning up 276 unused index entries from index $SII of file 0x9.
Cleaning up 276 unused index entries from index $SDH of file 0x9.
Cleaning up 276 unused security descriptors.
Security descriptor verification completed.
  16026 data files processed.                                            CHKDSK is verifying Usn Journal...
  34973128 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

 204697599 KB total disk space.
  30282172 KB in 57058 files.
     40960 KB in 16027 indexes.
         0 KB in bad sectors.
    264167 KB in use by the system.
     65536 KB occupied by the log file.
 174110300 KB available on disk.

      4096 bytes in each allocation unit.
  51174399 total allocation units on disk.
  43527575 allocation units available on disk.

Internal Info:
00 67 02 00 88 1d 01 00 2f 2c 02 00 00 00 00 00  .g....../,......
10 01 00 00 3c 00 00 00 00 00 00 00 00 00 00 00  ....<...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Waiting for further advice or instructions...

 

[aleks82]

Nothing got better, here the new minidump of the new BSOD

MEMORY_MANAGEMENT 0x1a

What could cause this maybe my RAM memory?

 

[zigzag3143]

Nothing got better, here the new minidump of the new BSOD

MEMORY_MANAGEMENT 0x1a

What could cause this maybe my RAM memory?

Memory management probably caused by a driver i would


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



Driver verifier

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[aleks82]

Just started the Memtest, did complete first test phase (1 pass), in the second test phase it reported 22 Errors, will let it continue a little more and see if more errors come out, could the memory have been the issue all the time, all those BSODs

 

[zigzag3143]

Just started the Memtest, did complete first test phase (1 pass), in the second test phase it reported 22 Errors, will let it continue a little more and see if more errors come out, could the memory have been the issue all the time, all those BSODs

Easily. You need to run memtest for 6-8 passes.

 

[aleks82]

Ok finally the problem is solved, the problem was one bad RAM stick (which I found out using Memtest), will change it immediately, thank you very much for spending your time helping me, without your help it would have been a nightmare for me, I truly appreciate it

 

[zigzag3143]

Ok finally the problem is solved, the problem was one bad RAM stick (which I found out using Memtest), will change it immediately, thank you very much for spending your time helping me, without your help it would have been a nightmare for me, I truly appreciate it

\


My pleasure glad it worked out

Ken