Solved BSOD randomly, more frequent when starting up/logging on

[MSB117]

Help! My Alienware M17xR3 started to BSOD a couple of days ago. It now happens almost every time I start up/log on and sometimes randomly.

System Specs:
Windows 7 Home Premium x64
Intel Core i7 2720-QM @ 2.20ghz
16GB
nVidia GTX560m
750GB SATA (7200RPM)

Attached the SF file, thanks!

 

[Arc]

Hello mate, I guess it is within warranty?

I checked a 3 latest dumps only, and got a lot of crashers there. Have a look.

Norton:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff82350cd4370, 0, fffff8000340a9bc, 5}

[COLOR=Red]*** WARNING: Unable to verify timestamp for SRTSP64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS
*** WARNING: Unable to verify timestamp for EX64.SYS
*** ERROR: Module load completed but symbols could not be loaded for EX64.SYS[/COLOR]

Could not read faulting driver name
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )

Followup: Pool_corruption
---------

Uninstall Norton and all Symentec products using Norton Removal tool.
Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download and install and update those, and then run full system scans with both of them, one by one. Also scan the system for possible virus infection.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

nVidia display driver:

Irp is active with 4 stacks 3 is current (= 0xfffffa801592fd60)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [ 16, 0]   0  0 fffffa800e037a10 00000000 fffff8800f9e54a4-fffffa8010b08bf0    
           \Driver\pci    nvlddmkm
            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa8011629480 00000000 00000000-00000000    pending
           \Driver\nvlddmkm
            Args: 00000000 00000001 00000001 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa8012c04740    

            Args: 00000000 00000000 00000000 00000000

• Download and install Driver Fusion.
• Reboot the computer in Advanced Boot Options, safe mode. Search Driver Fusion in your start menu, and remove all components of your nVidia display driver.
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Drivers > Beta and Legacy; search there with your cards particulars for GeForce 306.23 Driver, dated 13.9.2012 and install it.

Intel HD Graphics:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {39, 2, 1, fffff880055e5f41}

[COLOR=Red]*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys[/COLOR]
Probably caused by : hardware ( [COLOR=Red]igdkmd64[/COLOR]+344f41 )

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

Update it from Intel Download Center.

Intel Rapid Storage Driver.

fffff800`00b9c868  fffff880`01251507Unable to load image \SystemRoot\system32\DRIVERS\iaStor.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
 iaStor+0x2d507[/COLOR]

Get rid of intel rapid storage.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "Disc Drives" by clicking on the triangle in front of it.
5. Select one item under it, right click, uninstall.
6. Continue the process for all items under "Disc Drives"
7. Now restart the computer. At restart, windows will auto configure the appropriate system driver, msahci.sys.

Also, Broadcom 802.11g Network Adapter - Dell Wireless 1390 WLAN Mini-Card

fffff800`00b9ca38  fffff880`05e770f4Unable to load image \SystemRoot\system32\DRIVERS\bcmwl664.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for bcmwl664.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmwl664.sys
 bcmwl664+0x130f4[/COLOR]

And ST MicroElectronics Accelerometer

fffff800`00b9c4e0  fffff880`058024c8*** WARNING: Unable to verify timestamp for Accelern.sys
[COLOR=Red]*** ERROR: Module load completed but symbols could not be loaded for Accelern.sys
 Accelern+0x24c8[/COLOR]

Both of them are OEM. Check for updates in Alienware's site.

Free up the startup.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept the restart.

Let us know the results.

 

[MSB117]

Hey! Thanks for the reply, unfortunately the warranty ran out back in August, hence why I'm here!


Will do the above and let you know!

 

[Arc]

Hey! Thanks for the reply, unfortunately the warranty ran out back in August, hence why I'm here!


Will do the above and let you know!

In such a situation, and depending on the condition of your computer, I may make your work easy. Uninstall Norton and see if the crashes stopped or not. If not, do the http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html. It is needed there.

 

[MSB117]

Yeah I uninstalled Norton using the method above and am still experiencing crashes, so will reinstall Windows over the weekend.

My friend who knows a little bit about computers was suggesting that it may be a problem with the Hard Drive. Is there anyway to check if it is okay? Don't want to clean install only to find out its a problem with the HDD.

 

[Arc]

My friend who knows a little bit about computers was suggesting that it may be a problem with the Hard Drive. Is there anyway to check if it is okay? Don't want to clean install only to find out its a problem with the HDD.

Though I haven't got any solid reason to claim that the HDD is problematic, but your friends words must not be nullified. Do the following Disc checks.

1. Update your SSD's Firmware (Skip it, if it is not a SSD)
2. Re-seat the sata and power.
   
   
3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
4. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
5. Post a screenshot of the HDD/HDDs using CrystalDiskInfo - Software - Crystal Dew World

 

[MSB117]

Did the tests. The chkdsk test seemed to go through with no problems but towards the end of the Long Test using Sea Tools for DOS the screen locked up and the computer made a loud beep noise.

Attached is the screenshot.

 

[Arc]

It seems to be good. Dont worry about the Discs.

Either you may upload the further crash dumps those you experienced, or you may go with your plan to have a clean install, which is always a good option.

Whatever you do, let us informed

 

[MSB117]

Ill probably go ahead with the clean install over the weekend/beginning of next week! Thanks for all your help!

 

[MSB117]

Hi Archie,

So I reinstalled windows over today and everything was all well and good for a few hours until I had my first BSOD. I thought that this may just be happening due to the outdated drivers on the Dell support site/Resource DVD so I attempted to download new drivers from the respective manufacturers websites.

However now every time I try to access these sites (Intel, Microsoft etc.) Internet Explorer crashes, and happens only for these sites (Hotmail, Youtube etc. load fine) and I can't access any websites at all through Chrome.

It almost feels as though the computer is infected with a Virus even after all the malware scans and reinstall.

Your help would be greatly appreciated, thanks!

(Attached are the latest SF Files)

 

[Arc]

As it shows a memory corruption (it may be caused something other than the RAM too), let us start with the RAM tests.

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa824b00d6b8, 0, fffff80002aaf7ca, 5}


Could not read faulting driver name
[COLOR=Red][B]Probably caused by : memory_corruption[/B][/COLOR] ( nt!MiRemoveWorkingSetPages+3b2 )

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

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.

Let us know the results.

 

[MSB117]

Hi Archie,

Just to keep you updated I ran memtest last night, came back with 940,000 errors on the first pass!

So I reran the test overnight with only one RAM stick in the laptop after 10 passes it came back with 0 errors. Going to run the test with second stick in the next MOBO slot tonight. Should this be on its own or with the first stick still in the laptop?

 

[Arc]

Hi Archie,

Just to keep you updated I ran memtest last night, came back with 940,000 errors on the first pass!

So I reran the test overnight with only one RAM stick in the laptop after 10 passes it came back with 0 errors. Going to run the test with second stick in the next MOBO slot tonight. Should this be on its own or with the first stick still in the laptop?

How to Test and Diagnose RAM Issues with Memtest86+

Follow the Part 3: If You Have Errors: Do exactly what is stated there.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.​

 

[MSB117]

Completed the tests and this is what I got:

RAM Stick #1 and #2 in Motherboard Slot #1 and #2 = Errors
RAM Stick #1 in Motherboard Slot #1 = No Errors
RAM Stick #2 in Motherboard Slot #2 = Errors
RAM Stick #1 in Motherboard Slot #2 = No Errors

So I guess its pretty safe to say that RAM Stick #2 is faulty! I bought these sticks from Crucial just last month so can probably get a replacement.

 

[Arc]

Completed the tests and this is what I got:

RAM Stick #1 and #2 in Motherboard Slot #1 and #2 = Errors
RAM Stick #1 in Motherboard Slot #1 = No Errors
RAM Stick #2 in Motherboard Slot #2 = Errors
RAM Stick #1 in Motherboard Slot #2 = No Errors

So I guess its pretty safe to say that RAM Stick #2 is faulty! I bought these sticks from Crucial just last month so can probably get a replacement.

Extremely well done with the memtest. Let us know the situation after getting the replacement RAM, and in between, use the stick #1 only.

 

[MSB117]

Hi Archie,

I received my replacement RAM last week and ran a couple of passes with memtest after installing it. Everything checked out fine, but I just had my first BSOD since reinstalling Windows today.

Please could you have a look at the attached SF file, thanks!

 

[Arc]

MSB117, it is caused by the Intel graphics driver.

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ffffffffffffffc8, 2, 0, fffff88004d91438}

*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+346438 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffffffffffffc8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88004d91438, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f16100
GetUlongFromAddress: unable to read from fffff80002f161c0
 ffffffffffffffc8 

CURRENT_IRQL:  2

FAULTING_IP: 
igdkmd64+346438
fffff880`04d91438 488b4dc8        mov     rcx,qword ptr [rbp-38h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

TRAP_FRAME:  fffff80000b9c290 -- (.trap 0xfffff80000b9c290)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffff880017e4c14
rdx=fffffa800d0ba970 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004d91438 rsp=fffff80000b9c428 rbp=0000000000000000
 r8=00000000f19d6bec  r9=0000000001ce09fc r10=0000000000000054
r11=fffffa800d0ba980 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po nc
igdkmd64+0x346438:
fffff880`04d91438 488b4dc8        mov     rcx,qword ptr [rbp-38h] ss:0018:ffffffff`ffffffc8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ce6569 to fffff80002ce6fc0

STACK_TEXT:  
fffff800`00b9c148 fffff800`02ce6569 : 00000000`0000000a ffffffff`ffffffc8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c150 fffff800`02ce51e0 : fffff880`03374180 fffff880`03376300 fffff800`00b90004 fffff800`00b9c4c0 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c290 fffff880`04d91438 : fffff800`02cf1c3c 00000000`00000000 fffffa80`00000000 00000000`40551288 : nt!KiPageFault+0x260
fffff800`00b9c428 fffff800`02cf1c3c : 00000000`00000000 fffffa80`00000000 00000000`40551288 fffff800`00b9c630 : igdkmd64+0x346438
fffff800`00b9c430 fffff800`02cf1ad6 : fffffa80`0d0ba9c0 00000000`00066154 00000000`00000000 00000000`ffffffff : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`02cf19be : 0000000f`2ff519b2 fffff800`00b9cb18 00000000`00066154 fffff800`02e5cd08 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`02cf17a7 : 00000003`408295c1 00000003`00066154 00000003`40829556 00000000`00000054 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`02cdecca : fffff800`02e59e80 fffff800`02e67cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
igdkmd64+346438
fffff880`04d91438 488b4dc8        mov     rcx,qword ptr [rbp-38h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  igdkmd64+346438

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdkmd64

IMAGE_NAME:  igdkmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50c92472

FAILURE_BUCKET_ID:  X64_0xD1_igdkmd64+346438

BUCKET_ID:  X64_0xD1_igdkmd64+346438

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

0: kd> lmvm igdkmd64
start             end                 module name
fffff880`04a4b000 fffff880`04f661a0   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Thu Dec 13 06:12:26 2012 (50C92472)
    CheckSum:         0051BB58
    ImageSize:        0051B1A0
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

First you Free up the startup so that the igfxtrey entry may be omitted.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus and the touchpad driver, SynTPEnh.
5. Apply > OK
6. Accept the restart.

If still the crashes continue to occur, uninstall the intel graphics driver, and then download an earlier version of it and install it. I have noticed a couple of times that the latest version is crashing, but not always.

 

[MSB117]

Thanks! Will keep you posted

 

[MSB117]

Had another BSOD, so installed an older version of the Intel Driver.

All was well until today where I experienced another crash. (SF Files attaced)

 

[Arc]

The crash dump says that it is something to do with the HDDs monitoring mechanism.....

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

Use !analyze -v to get detailed debugging information.

BugCheck C9, {221, fffff88001c2cbd0, fffff980bba14940, fffffa8011aad060}

[COLOR=Red]Probably caused by : volsnap.sys [/COLOR]( volsnap!VolSnapPnp+0 )

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

The event log clarifies it....

Event[14630]:
  Log Name: System
  Source: Service Control Manager
  Date: 2013-02-19T20:17:32.374
  Event ID: 7026
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Mani-Laptop
  Description: 
[COLOR=Red]The following boot-start or system-start driver(s) failed to load: 
[B]stdcfltn[/B][/COLOR]

Description here: Driver Reference Table - stdcfltn.sys

Better you uninstall this stuff.