Windows 7: Multiple BSODs during start up and general use

sammyd1995 · 27 Jul 2012

I recently (Thursday) I have been getting many BSODs like memory management or page fault in non page area. After some research, one of the most common faults seem to be with ntoskrnl.exe which indicates possible faulty RAM. I have yet to run Memtest 86 simply because I haven't had time, but I will in about 24 hours. I do know there is a small possibility this is due to undated or corrupt drivers. I have included all the information needed such as the mini dump and the 7 other types of info using the Seven Forum BSOD tool. Please let me know if there is something other wrong with my system than possibly a faulty RAM stick or bad graphics card. Thank you.

Jonathan_King · 27 Jul 2012

Hello,

I'd pretty much agree with your self-diagnosis, hardware (specifically RAM) is probably at fault. I still encourage you to run Memtest86, but if you want a quicker test, try Prime95: Hardware - Stress Test With Prime95

Memtest86 is a good test to run overnight, while Prime95 takes maybe 45 minutes to give trustworthy results.

...Summary of the dumps:

Code:


Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jul 27 02:38:32.732 2012 (UTC - 4:00)
System Uptime: 0 days 2:31:28.606
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+425 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+425
BiosReleaseDate = 07/22/2011
SystemProductName = Dell System XPS L702X
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jul 27 12:23:21.569 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:24.443
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53
BiosReleaseDate = 07/22/2011
SystemProductName = Dell System XPS L702X
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jul 27 12:12:06.451 2012 (UTC - 4:00)
System Uptime: 0 days 0:04:29.325
Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+468 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!MiDeleteAddressesInWorkingSet+468
BiosReleaseDate = 07/22/2011
SystemProductName = Dell System XPS L702X
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jul 27 14:28:17.965 2012 (UTC - 4:00)
System Uptime: 0 days 1:44:00.839
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption ( nt!MiCaptureAndResetWorkingSetAccessBits+d9 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_nt!MiCaptureAndResetWorkingSetAccessBits+d9
BiosReleaseDate = 07/22/2011
SystemProductName = Dell System XPS L702X
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jul 27 21:27:58.277 2012 (UTC - 4:00)
System Uptime: 0 days 3:15:32.152
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29dba )
BUGCHECK_STR:  0x1a_5002
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x1a_5002_nt!_??_::FNODOBFM::_string_+29dba
BiosReleaseDate = 07/22/2011
SystemProductName = Dell System XPS L702X
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jul 27 14:30:24.381 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:09.255
Probably caused by : memory_corruption ( nt!MiUpdateWsle+2b9 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  BSecAMX.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!MiUpdateWsle+2b9
BiosReleaseDate = 07/22/2011
SystemProductName = Dell System XPS L702X
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jul 27 14:53:38.484 2012 (UTC - 4:00)
System Uptime: 0 days 0:22:08.359
*** WARNING: Unable to verify timestamp for cng.sys
*** ERROR: Module load completed but symbols could not be loaded for cng.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for pci.sys
*** ERROR: Module load completed but symbols could not be loaded for pci.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : pci.sys
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_nvlddmkm_IMAGE_pci.sys
BiosReleaseDate = 07/22/2011
SystemProductName = Dell System XPS L702X
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jul 27 18:10:27.957 2012 (UTC - 4:00)
System Uptime: 0 days 3:15:51.831
Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+10c )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  FacebookMessen
FAILURE_BUCKET_ID:  X64_0x3B_nt!ObReferenceObjectByHandleWithTag+10c
BiosReleaseDate = 07/22/2011
SystemProductName = Dell System XPS L702X
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jul 27 21:32:50.502 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:18.376
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Rotate+2d0 )
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x1a_41284_dxgmms1!VIDMM_PROCESS_HEAP::Rotate+2d0
BiosReleaseDate = 07/22/2011
SystemProductName = Dell System XPS L702X
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jul 27 21:59:05.097 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:24.971
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+355e4 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  GoogleUpdate.e
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+355e4
BiosReleaseDate = 07/22/2011
SystemProductName = Dell System XPS L702X
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jul 27 21:30:22.846 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:33.720
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by : ntkrnlmp.exe ( nt!ObFastReferenceObject+10 )
BUGCHECK_STR:  0x1e_c0000005
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  avguard.exe
FAILURE_BUCKET_ID:  X64_0x1e_c0000005_nt!ObFastReferenceObject+10
BiosReleaseDate = 07/22/2011
SystemProductName = Dell System XPS L702X
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

sammyd1995 · 28 Jul 2012

That is what I thought. Thank you. I do, however, some extra information. My screen seems to go dark for about half a second every 2 seconds especially right before a BSOD or when I take my charger off. Does this have anything to do with BSOD or is this a purely battery power options issue?

Jonathan_King · 28 Jul 2012

The battery issue sounds like it could be a BIOS issue. You might try giving a BIOS flash a shot: Drivers and Downloads | Dell [United States]

sammyd1995 · 28 Jul 2012

Yea it was defnitely ram. Two minutes into the test I started getting that. Thank you for your help.

Jonathan_King · 29 Jul 2012

Good luck with the RAM replacement...glad Memtest86 showed results!

sammyd1995 · 01 Aug 2012

This is a little embrassing but it doesn't seem like I can go into my bios to change timings to the manufacturers setting because my computer seems to be misreading the SPD. I was told to press F2 to access the bios but I get a menu for Phoenix SecureCore Tiano Setup which looks very bios li
ke but I don't see anywhere that lets me change timengs or voltages for anything so this probably not the actual bios. You wouldn't happen to know eaxtly how to acces bios on my system would you? Thank you.

Jonathan_King · 03 Aug 2012

Unfortunately, OEMs lock down their BIOS setup programs to prevent users from messing around with stuff like RAM timings. Are you having any problems with your RAM now? You might be able to run it right like it is, if it's not causing any errors.

sammyd1995 · 06 Aug 2012

It's running well enough as it is but its not using my ram efficiently enough. I don't even want to overclock just get it to manufacturer's standards but guess I can't. Thanks for your help anyways.

Windows 7: Multiple BSODs during start up and general use

Multiple BSODs during start up and general use problems?