Intermittent BSOD's on boot and during use

[skyhawk]

I was hoping that you could throw some light on this problem I'm having.

My laptop intermittently suffers from BSOD's on boot and during general use. I installed Windows 7 Professional (Build 7600) yesterday, (24/12), and this has been happening from the very beginning.

The messages that the BSOD's usually show are:

PAGE_FAULT_IN_NON_PAGED_AREA
BAD_POOL_HEADER

I attach the only minidump file that I have.

 

[zigzag3143]

I was hoping that you could throw some light on this problem I'm having.

My laptop intermittently suffers from BSOD's on boot and during general use. I installed Windows 7 Professional (Build 7600) yesterday, (24/12), and this has been happening from the very beginning.

The messages that the BSOD's usually show are:

PAGE_FAULT_IN_NON_PAGED_AREA
BAD_POOL_HEADER

I attach the only minidump file that I have.

Hi and welcome


It it the readyboost.sys driver that probably caused this crash. Easy enough to verify, turn it off and see.

Also you have a bunch of old driver listed below that may also be slowing down your performance

Ken J+

sisnic.sys        0x8cdd5000    0x8cddda00    0x00008a00    0x44addc33    7/6/2006 10:59:47 PM                        
SISAGPX.sys        0x889e0000    0x889f1000    0x00011000    0x453881ba    10/20/2006 2:58:50 AM                        
lmimirr.sys        0x916b8000    0x916b8c80    0x00000c80    0x461c106b    4/10/2007 5:32:11 PM                        
ar5211.sys        0x91620000    0x916a6140    0x00086140    0x4721b162    10/26/2007 4:20:34 AM                        
AGRSM.sys        0x8cc2b000    0x8cd31000    0x00106000    0x49184ba5    11/10/2008 9:56:37 AM

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\122509-27515-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8284b000 PsLoadedModuleList = 0x82993810
Debug session time: Fri Dec 25 09:22:46.328 2009 (GMT-5)
System Uptime: 0 days 0:00:14.468
Loading Kernel Symbols
...............................................................
........................................................
Loading User Symbols
kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_HEADER (19)
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 special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000003, the pool freelist is corrupt.
Arg2: 82980a20, the pool entry being checked.
Arg3: 829c0a20, the read back flink freelist value (should be the same as 2).
Arg4: 82980a20, the read back blink freelist value (should be the same as 2).

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


BUGCHECK_STR:  0x19_3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 88749ca7 to 8296b232

STACK_TEXT:  
8078aba4 88749ca7 00000000 00000020 69576d73 nt!ExAllocatePoolWithTag+0x682
8078abb8 8874e689 00000020 69576d73 8078ac60 rdyboost!SmAlloc+0x13
82980802 00000000 00000000 00000000 00000000 rdyboost!SMKM_STORE_MGR<SMD_TRAITS>::SmPageWrite+0x135


STACK_COMMAND:  kb

FOLLOWUP_IP: 
rdyboost!SmAlloc+13
88749ca7 5d              pop     ebp

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  rdyboost!SmAlloc+13

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rdyboost

IMAGE_NAME:  rdyboost.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc19a

FAILURE_BUCKET_ID:  0x19_3_rdyboost!SmAlloc+13

BUCKET_ID:  0x19_3_rdyboost!SmAlloc+13

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

 

[skyhawk]

Hi

Thanks for your help. Unfortunately, I'm a little clueless as to how to turn off the readyboost service/driver, having done some comprehensive searching and finding no definitive answer.

Any help?

 

[zigzag3143]

Hi

Thanks for your help. Unfortunately, I'm a little clueless as to how to turn off the readyboost service/driver, having done some comprehensive searching and finding no definitive answer.

Any help?

My apologies SH I often forget to be clear. Risk of the profession I guess.

Type readyboost in search then follow the instructions.

Ken J+

 

[skyhawk]

I followed the above advice, but it comes to light that I have no removable storage devices that are actually using readyboost, so I'm afraid I'm stuck once again.

Sorry to be a bother...

 

[zigzag3143]

I followed the above advice, but it comes to light that I have no removable storage devices that are actually using readyboost, so I'm afraid I'm stuck once again.

Sorry to be a bother...

I am just having a senior moment. let me investigate brb

Ken J+


edit:the exact name of the file is rdyboost.sys. if you are not ever going to use readyboost you can simply delete that file. and of problem. If you may use it in the future simply rename rdyboost.sys to rdyboost.bak and it wont run at start up

lets hope i finally go it right <g>

 

[skyhawk]

Finally!

I've managed to disable it after changing permissions about 3 times from 'TrustedInstaller'.

Thanks very much for your help.

Mark.

 

[skyhawk]

Unfortunately, the rdyboost.sys fix didn't last very long. On startup today, following disabling it yesterday, the system wouldn't boot and went into startup repair, which then told me that the root cause file was rdyboost.sys, and it therefore 'fixed' the file (i.e from my introduced .bak extension to the standard .sys extension). Following this, a multitude of problems seem to be occurring.

The system does not get past the initial loading of the desktop without crashing, usually bringing up the following stop screen messages:

BAD_POOL_HEADER
IRQL_NOT_LESS_OR_EQUAL

and this message, just once:

PFN_LIST_ERROR

On reboot, this was followed by a black DOS screen message which said: The file is possibly corrupt. The file header checksum doesn not match the computed checksum.

This happened twice.

I would give you the minidump files, but I have been unable to boot the system.

Thanks for your help in advance.

 

[usasma]

In Startup Repair you can access the Command Prompt.
At the Command Prompt type "chkdsk /r" (without the quotes) and press Enter.

Let the test run and see what it says (about repairs and errors) and let us know.

 

[skyhawk]

Running the test "chkdsk /r" produced the following result:

The type of the file system is NTFS.

Cannot lock current drive.

Windows cannot run disk checking on this volume because it is write-protected.

 

[usasma]

Do you have the installation disk for your system? If so, boot from it, click on Install/Select Language at the first screen - then, on the second screen, click on Repair this computer in the lower left of the window.
Then you can access Command Prompt from there - and see if it'll let you run it (the volume is not supposed to be write protected).

If it offers you an option to dismount the volume, or to schedule it at reboot, let it do it.

 

[skyhawk]

After booting from the install disk, the response for chkdsk /r was the same as before, with the same error about the write-protection.

 

[usasma]

I'd have to suggest a hard drive diagnostic at this point: HD Diagnostic
If that passes, then I'd have to suggest:
- backing up your stuff
- wiping the hard drive with KillDisk or DBAN
- clean installing Windows 7