Windows 7: BSOD randomly, more frequent when starting up/logging on

Arc · 23 Jan 2013

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

Code:

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

Use !analyze -v to get detailed debugging information.

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


Could not read faulting driver name
Probably caused by : memory_corruption ( 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 · 24 Jan 2013

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 · 24 Jan 2013

Quote: Originally Posted by 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?

How to Test and Diagnose RAM Issues with Memtest86+

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

Quote:

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 · 25 Jan 2013

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 · 25 Jan 2013

Quote: Originally Posted by 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.

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 · 13 Feb 2013

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 · 13 Feb 2013

MSB117, it is caused by the Intel graphics driver.

Code:

*******************************************************************************
*                                                                             *
*                        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.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus and the touchpad driver, SynTPEnh.
Apply > OK
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 · 13 Feb 2013

Thanks! Will keep you posted

MSB117 · 19 Feb 2013

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 · 19 Feb 2013

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

Code:

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

Use !analyze -v to get detailed debugging information.

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

Probably caused by : volsnap.sys ( volsnap!VolSnapPnp+0 )

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

The event log clarifies it....

Code:

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: 
The following boot-start or system-start driver(s) failed to load: 
stdcfltn

Description here: Driver Reference Table - stdcfltn.sys

Better you uninstall this stuff.

Windows 7: BSOD randomly, more frequent when starting up/logging on

BSOD randomly, more frequent when starting up/logging on problems?