BSOD occurs randomly once or twice a day

[bebopkid]

Thanks for any help you can offer.

 

[Arc]

Hi bebopkid.

Download and install Display Drivers for Intel® Core™ Processors on 64-bit Windows 7 ; it works for your Embedded Intel® Core™ i5 Processors.

Let us know the results.

 

[bebopkid]

Hi, thanks for the response. I downloaded and installed the driver last night.

I just had another BSOD.

I reran the SF diagnostic tool and attached the results.

 

[Arc]

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 memtest comes free from errors, 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. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[bebopkid]

Thanks for the response. I let the memory test run for 12 hours. I stopped it in the 10th pass. There were no errors. I'm going to turn DV on now. I'll update with the results.

 

[bebopkid]

Here is the diagnostic tool zip file of the crash with the driver verifier running.

Thanks for looking at this.

 

[Arc]

Get Intel® PROSet/Wireless Software and Drivers for Windows 7.

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff9803556aec2, 2, 1, fffff88005642627}

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

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

1: 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: fffff9803556aec2, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88005642627, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c2100
GetUlongFromAddress: unable to read from fffff800030c21c0
 fffff9803556aec2 

CURRENT_IRQL:  2

FAULTING_IP: 
NETw5s64+3c627
fffff880`05642627 6689b8a2000000  mov     word ptr [rax+0A2h],di

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF88002F22FB0

TRAP_FRAME:  fffff88002f222a0 -- (.trap 0xfffff88002f222a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff9803556ae20 rbx=0000000000000000 rcx=fffffa80097dc000
rdx=fffffa80085b7000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005642627 rsp=fffff88002f22430 rbp=0000000000000000
 r8=0000000000000316  r9=fffff88001559d94 r10=fffff88002f22770
r11=fffff88002f22350 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
NETw5s64+0x3c627:
fffff880`05642627 6689b8a2000000  mov     word ptr [rax+0A2h],di ds:fffff980`3556aec2=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e8a169 to fffff80002e8abc0

STACK_TEXT:  
fffff880`02f22158 fffff800`02e8a169 : 00000000`0000000a fffff980`3556aec2 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f22160 fffff800`02e88de0 : fffffa80`097dc000 fffff800`0332413c fffffa80`05b7df80 fffff980`03f76df0 : nt!KiBugCheckDispatch+0x69
fffff880`02f222a0 fffff880`05642627 : fffff980`03f76df0 00000000`00000000 fffff880`033bdc84 fffff800`00000003 : nt!KiPageFault+0x260
fffff880`02f22430 fffff980`03f76df0 : 00000000`00000000 fffff880`033bdc84 fffff800`00000003 00000000`00000005 : NETw5s64+0x3c627
fffff880`02f22438 00000000`00000000 : fffff880`033bdc84 fffff800`00000003 00000000`00000005 fffff800`02f4e5cb : 0xfffff980`03f76df0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETw5s64+3c627
fffff880`05642627 6689b8a2000000  mov     word ptr [rax+0A2h],di

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  NETw5s64+3c627

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETw5s64

IMAGE_NAME:  NETw5s64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b4df6b9

FAILURE_BUCKET_ID:  X64_0xD1_VRF_NETw5s64+3c627

BUCKET_ID:  X64_0xD1_VRF_NETw5s64+3c627

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

1: 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: fffff9803556aec2, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88005642627, address which referenced memory

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


WRITE_ADDRESS:  fffff9803556aec2 

CURRENT_IRQL:  2

FAULTING_IP: 
NETw5s64+3c627
fffff880`05642627 6689b8a2000000  mov     word ptr [rax+0A2h],di

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF88002F22FB0

TRAP_FRAME:  fffff88002f222a0 -- (.trap 0xfffff88002f222a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff9803556ae20 rbx=0000000000000000 rcx=fffffa80097dc000
rdx=fffffa80085b7000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005642627 rsp=fffff88002f22430 rbp=0000000000000000
 r8=0000000000000316  r9=fffff88001559d94 r10=fffff88002f22770
r11=fffff88002f22350 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
NETw5s64+0x3c627:
fffff880`05642627 6689b8a2000000  mov     word ptr [rax+0A2h],di ds:fffff980`3556aec2=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e8a169 to fffff80002e8abc0

STACK_TEXT:  
fffff880`02f22158 fffff800`02e8a169 : 00000000`0000000a fffff980`3556aec2 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f22160 fffff800`02e88de0 : fffffa80`097dc000 fffff800`0332413c fffffa80`05b7df80 fffff980`03f76df0 : nt!KiBugCheckDispatch+0x69
fffff880`02f222a0 fffff880`05642627 : fffff980`03f76df0 00000000`00000000 fffff880`033bdc84 fffff800`00000003 : nt!KiPageFault+0x260
fffff880`02f22430 fffff980`03f76df0 : 00000000`00000000 fffff880`033bdc84 fffff800`00000003 00000000`00000005 : NETw5s64+0x3c627
fffff880`02f22438 00000000`00000000 : fffff880`033bdc84 fffff800`00000003 00000000`00000005 fffff800`02f4e5cb : 0xfffff980`03f76df0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETw5s64+3c627
fffff880`05642627 6689b8a2000000  mov     word ptr [rax+0A2h],di

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  NETw5s64+3c627

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETw5s64

IMAGE_NAME:  NETw5s64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b4df6b9

FAILURE_BUCKET_ID:  X64_0xD1_VRF_NETw5s64+3c627

BUCKET_ID:  X64_0xD1_VRF_NETw5s64+3c627

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

1: kd> lmvm NETw5s64
start             end                 module name
fffff880`05606000 fffff880`05d65000   NETw5s64 T (no symbols)           
    Loaded symbol image file: NETw5s64.sys
    Image path: \SystemRoot\system32\DRIVERS\NETw5s64.sys
[COLOR=Red]    Image name: NETw5s64.sys
    Timestamp:        Wed Jan 13 22:07:13 2010[/COLOR] (4B4DF6B9)
    CheckSum:         0075EBFF
    ImageSize:        0075F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[bebopkid]

Hi,

I updated the driver mentioned in the previous response.

I just got another blue screen. Here is the diagnostic files.

Thanks.

 

[Arc]

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to 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.

 

[bebopkid]

Thanks for the response. I let the driver verifier run for 24 hours with no crash. I have turned it off. If I crash again, I'll turn it back on and send in the diagnostic files.

Thanks.

 

[bebopkid]

Well it's been 6 days since it crashed. Here's the diagnostic files from my crash today. Thanks for looking it.

 

[Arc]

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

Use !analyze -v to get detailed debugging information.

[URL="http://carrona.org/bsodindx.html#0x00000019"]BugCheck 19[/URL], {3, fffff8a002638080, fffff8a002638080, fffff8a0026380c9}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c96 )

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

BSOD Index

If DV is not crashing the system, that means no driver is failing.
If memtest shows no error, that means no Memory error is there.

Usually there is no any other cause of a stop 0x19.

I am taking my final chance here:

fffff880`0a4426c8 fffff800`02fa96ea nt!KeBugCheckEx
fffff880`0a4426d0 fffff800`02faa4f1 nt!ExDeferredFreePool+0xc96
fffff880`0a442760 fffff880`02c4a771 nt!ExFreePoolWithTag+0x411
fffff880`0a442810 fffff880`02c4a8e1 [COLOR=Red]dxgkrnl!DXGDEVICE::ProcessTerminationList[/COLOR]+0x1b5
fffff880`0a442860 fffff880`02c4e739 [COLOR=Red]dxgkrnl!DXGDEVICE::TerminateAllocations[/COLOR]+0xb9
fffff880`0a4428b0 fffff880`02c51285 [COLOR=Red]dxgkrnl!DXGDEVICE::DestroyAllocation[/COLOR]+0x99
fffff880`0a442940 fffff960`0019144a [COLOR=Red]dxgkrnl!DxgkDestroyAllocation[/COLOR]+0xa9d
fffff880`0a442bf0 fffff800`02e75e53 win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`0a442c20 00000000`72c9141a nt!KiSystemServiceCopyEnd+0x13
00000000`0008e2f8 00000000`00000000 0x72c9141a

It appears to be some issue with the DirectX Graphics device. And the device is onboard, Intel(R) HD Graphics .... a motherboard component.

You try to update the display driver ... Intel® HD graphics Driver for Windows 7.

Let us know the results.