BSOD with no specific situations/conditions observed

[raymond1688]

My computer has been experiencing BSOD, and it seems to happen randomly. I can't pinpoint a specific thing that initiated it because it just seems to happen at any time, opening word documents, browsing the web, etc. Because I can't find a specific pattern, I don't know how to replicate the problem, it seem to happen on its own.

This is after a fresh install. It happened previously, and I figured I just need to reformat and do a fresh install.

OS: Windows 7 Professional x64 Service Pack 1

Processor: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Installed memory (RAM): 4.00 GB
Display adapter type: Intel(R) G33/G31 Express Chipset Family
Total available graphics memory: 256 MB

Hard Drive:
Primary (OS): Intel SSDSA2CW080G3 80.0 GB
Storage: Seagate Barracuda ST31000528AS 1000.2 GB
Western Digital Caviar Blue WDC WD5000AAKS-00V1A0 500.1 GB

Unfortunately, I'm not very familiar with troubleshooting computers, so I'll try to post as much as information as I can.

I used a app called BlueScreenView, and here's the information I got:
Caused by Driver: ntoskrnl.exe (3 times already), fltmgr.sys (1 time)

edit:
I tried crystaldiskinfo and it seems that all of my hard drives are fine

 

[raymond1688]

Sorry, bump for help, I really have no clue what's going on and would really appreciate anyone who can read and interpret what's going on with my computer.

 

[raymond1688]

Is there any other information that I can post that'll help solve what the problem is with my computer?

 

[raymond1688]

I would really appreciate it if someone can help me out, or if there's something missing or I haven't done that's stopping or preventing others from helping me.

Thank you

edit: I've just received a note telling me to read the thread about posting. I re-read it again, made sure I followed the instructions and uploaded the zip file. Is there something I'm missing or doing wrong?

 

[Arc]

Hello raymond1688.

Make sure that your intel SSD is running with the up-to-date firmware.
https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=18363

Update D-Link DWA-552 XtremeN Desktop Adapter driver.
D-Link | Building Networks for People

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. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
____________________________________________________________________________________

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

[COLOR=Red]BAD_POOL_HEADER (19)[/COLOR]
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then [COLOR=Red]special pool applied to the suspect tags or the driver
verifier to a suspect driver.[/COLOR]
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa8006201b50, The pool entry we were looking for within the page.
Arg3: fffffa8006201ca0, The next pool entry.
Arg4: 0000000004150004, (reserved)

 

[raymond1688]

Thank you so much! I'll get DV up and running.

 

[raymond1688]

Attached is the memory dump that I've got after running the DV.

What happened was, I followed the instructions in the link posted above, and enabled DV. I ran it for 30+ hours and nothing happened, I opened multiple browsers hoping it would trigger it, still no luck.

So I decided to delete the settings and try it again. What probably happened was I clicked display settings instead of delete settings, and after I that, I couldn't boot back into Windows and ran into BSOD every single time. I booted into safe mode and it turns out I probably didn't select the right choice.

I grabbed a copy of the memory dump, hopefully this will be able to help solve what is wrong with my computer.

Thanks!

 

[Arc]

The DV enavled BSODs are also not giving any hint of a failing driver. So it may not be a driver, but somehow memory is the problem.

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.

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80002898a55}

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

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002898a55, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002abb100
GetUlongFromAddress: unable to read from fffff80002abb1c0
 0000000000000000 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!IopCompleteRequest+ae5
fffff800`02898a55 488b09          mov     rcx,qword ptr [rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

IRP_ADDRESS:  ffffffffffffff89

TRAP_FRAME:  fffff880031c2a50 -- (.trap 0xfffff880031c2a50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880031c3e10 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002898a55 rsp=fffff880031c2be0 rbp=fffff880031c2d30
 r8=fffff880031c2ce8  r9=fffff880031c2ce0 r10=0000000000000002
r11=fffff80002897f70 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po cy
nt!IopCompleteRequest+0xae5:
fffff800`02898a55 488b09          mov     rcx,qword ptr [rcx] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800028831a9 to fffff80002883c00

STACK_TEXT:  
fffff880`031c2908 fffff800`028831a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`031c2910 fffff800`02881e20 : 00000000`0000001c fffff800`02c6e747 fffffa80`04604040 fffff980`0174eee0 : nt!KiBugCheckDispatch+0x69
fffff880`031c2a50 fffff800`02898a55 : fffffa80`039e9040 fffff880`00cc4739 fffff880`031c2c80 00000000`00000001 : nt!KiPageFault+0x260
fffff880`031c2be0 fffff800`02876617 : 00000000`00000001 fffff800`02886af2 fffff880`031c2d00 fffff800`00000000 : nt!IopCompleteRequest+0xae5
fffff880`031c2cb0 fffff800`028768c7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7
fffff880`031c2d30 fffff800`029462a6 : 00000000`0002fd90 00000000`00000000 fffff880`031c2fe0 00000000`002dacb4 : nt!KiApcInterrupt+0xd7
fffff880`031c2ec0 fffff800`02946733 : fffffa80`0414d898 fffff880`00000011 00000000`00000000 fffff800`00000004 : nt!RtlpWalkFrameChain+0x1226
fffff880`031c3560 fffff800`029475bb : 00000000`00000003 fffffa80`0414d898 00000000`00000000 00000000`00000000 : nt!RtlWalkFrameChain+0x63
fffff880`031c3590 fffff800`02d1e13c : fffffa80`0414d880 00000000`00000040 00000000`00000003 fffff800`02973911 : nt!RtlCaptureStackBackTrace+0x4b
fffff880`031c35c0 fffff800`02d201aa : fffff880`031bf000 fffff880`031c5000 00000000`00000040 00000000`00000000 : nt!IovpLogStackCallout+0x1c
fffff880`031c35f0 fffff800`02d22a4a : fffff8a0`00743180 00000000`00000004 00000000`00000001 00000000`00000003 : nt!ViPoolLogStackTrace+0x8a
fffff880`031c3620 fffff800`029b6c57 : fffff8a0`00743170 00000000`00000040 00000000`00000003 00000000`00000001 : nt!VfFreePoolNotification+0x4a
fffff880`031c3650 fffff800`02c2f756 : fffff8a0`002a0a30 fffff8a0`00043800 00000000`69634d43 00000000`00000000 : nt!ExDeferredFreePool+0x1283
fffff880`031c3700 fffff800`02bba96a : fffff880`0000001b fffff880`031c3800 fffff8a0`00747500 40000000`0000001b : nt!CmpCallCallBacks+0x4f6
fffff880`031c37d0 fffff800`02ae8cb4 : fffff880`031c3ba8 fffff880`031c3db0 fffff8a0`00022010 fffff880`031c3cc0 : nt! ?? ::NNGAKEGL::`string'+0x120db
fffff880`031c3850 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x2cab9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+1283
fffff800`029b6c57 90              nop

SYMBOL_STACK_INDEX:  c

SYMBOL_NAME:  nt!ExDeferredFreePool+1283

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!ExDeferredFreePool+1283

BUCKET_ID:  X64_0xA_VRF_nt!ExDeferredFreePool+1283

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

 

[raymond1688]

Arc, thanks for your response.

I actually ran Memtest86+ a couple of days ago, just because I didn't know what I could do. I got errors within 15 mins of running it the first time. But after that I wasn't able to reproduce the errors anymore. I tried running each stick individually and no errors came up. I ran all 4 sticks together for 30 hours (15 passes I think) and not a single error came up.

Is there any thing else I can provide or try that will help solve this?

Once again, really appreciate the help you've provided.

edit: I haven't updated my SSD or wireless adapter firmware yet, so I'll update that and try running DV again and post back.