Random BSOD while browsing

[emwashere]

I've been having a variety of BSODs lately with different error messages while browsing the web and playing flash games on facebook. I've tried updating all the drivers to the latest versions, and tried doing system repair from the windows 7 installation disk, but BSODs still occur.

I've tried running chkdsk overnight, but I would wake up to a black screen. Tried the startup repair option from the installation disk but received a "Startrep.exe application error" message. image I've not had any problems since I replaced my hdd a few months back until this few weeks. Had another BSOD this morning with the 'System Service Exception' error. I am unsure if it was something I installed or something I did, as I've been working the past weeks and have just used the computer to browse facebook.

Would greatly appreciate any help as this BSOD problem has been escalating since the day before.

Thanks!

 

[Arc]

Hi emwashere.

Update the driver to DW1501 Wireless-N WLAN Half-Mini Card. Get it from Dell's site using your service tag.
Support | Dell US

Let us know the situation after updating the driver.

 

[emwashere]

Thanks for the reply! I've updated the driver, and so far, everything seems to be working fine.

 

[emwashere]

I just had another BSOD --

Memory_Management ; Stop: 0x0000001A. attached are the files from the SF Diagnostic tool. I don't know what is the issue this time since I've already updated the dw1501 driver.

 

[Arc]

This time the crash dump is not providing adequate information about the BSOD. So we have to try to debug it based on the bugcheck code, that is BugCheck 1A. It is technically called MEMORY_MANAGEMENT (1a). Typically caused by malfunctioning memory. Either the RAM is failing or any driver is passing some bad info to the memory. Sometimes corrupt/not updated kernel data also causes it.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
___________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {3452, 542a000, fffff7000108bbb8, ee600000265bf866}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35163 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000003452, The subtype of the bugcheck.
Arg2: 000000000542a000
Arg3: fffff7000108bbb8
Arg4: ee600000265bf866

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


BUGCHECK_STR:  0x1a_3452

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80003149e33 to fffff800030d8bc0

STACK_TEXT:  
fffff880`08a6fee8 fffff800`03149e33 : 00000000`0000001a 00000000`00003452 00000000`0542a000 fffff700`0108bbb8 : nt!KeBugCheckEx
fffff880`08a6fef0 fffff800`030a9892 : fffffa80`07786b30 fffffa80`00000000 fffff880`00000b35 fffff800`00000000 : nt! ?? ::FNODOBFM::`string'+0x35163
fffff880`08a707a0 fffff800`033ae05a : fffff8a0`0bbdea10 fffff880`08a70ae0 00000000`00000000 fffffa80`073bcb50 : nt!MmCleanProcessAddressSpace+0x96
fffff880`08a707f0 fffff800`03392b7d : 00000000`c0000005 00000000`c0000001 00000000`fff91000 fffffa80`07790060 : nt!PspExitThread+0x56a
fffff880`08a708f0 fffff800`030cb6fa : 00000000`00000100 fffffa80`073bcc10 00000000`00000001 fffff800`030ce7fd : nt!PsExitSpecialApc+0x1d
fffff880`08a70920 fffff800`030cba40 : 00000000`00000246 fffff880`08a709a0 fffff800`03392af0 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`08a709a0 fffff800`030d7ef7 : fffffa80`073bcb50 00000000`000001e0 00000000`00000000 fffffa80`075afb70 : nt!KiInitiateUserApc+0x70
fffff880`08a70ae0 00000000`74aa2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`0342e9f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74aa2e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+35163
fffff800`03149e33 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+35163

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb

IMAGE_VERSION:  6.1.7601.18409

FAILURE_BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+35163

BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+35163

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x1a_3452_nt!_??_::fnodobfm::_string_+35163

FAILURE_ID_HASH:  {b68bb6d6-c4e1-ed4f-abca-56d9004b82c0}

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

 

[emwashere]

I have been testing the RAM sticks over the past few days, each in their respective slots do not generate an error. However, when I initially ran Memtest with all four sticks, error messages appeared. Not too sure what is going on but I'll test the sticks in other slots.

 

[Arc]

I see. So there is a chance of corrupt RAM.
Let us know the results of your quest.