I came home today to find my computer frozen, after resetting I got the BSOD.
I'm now getting it every time I start windows outside of safe mode.
I haven't changed any hardware recently.
Any help would be really appreciated
Hi and welcome
these crashes have two causes, but may in fact only be one. The first is Probably caused by : rdyboost.sys, which may really just be memory in disguise. The other is pool_corruption, or memory.
I would download memtestx86 and run it for 5 passes to test the memory. I would also not use readyboost (at least just to test) if I had 4 gigs of ram or more.
Let us know the results
Ken
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\New folder (3)\051010-23618-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c01000 PsLoadedModuleList = 0xfffff800`02e3ee50
Debug session time: Mon May 10 06:01:33.178 2010 (GMT-4)
System Uptime: 0 days 0:00:16.832
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {3, fffff80002e01920, 0, 404}
Probably caused by : Pool_Corruption ( nt!ExFreePool+536 )
Followup: Pool_corruption
---------
2: 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: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff80002e01920, the pool entry being checked.
Arg3: 0000000000000000, the read back flink freelist value (should be the same as 2).
Arg4: 0000000000000404, 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
LOCK_ADDRESS: fffff80002e75400 -- (!locks fffff80002e75400)
Resource @ nt!PiEngineLock (0xfffff80002e75400) Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
1 total locks
PNP_TRIAGE:
Lock address : 0xfffff80002e75400
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0
LAST_CONTROL_TRANSFER: from fffff80002da4d6f to fffff80002c71600
STACK_TEXT:
fffff880`031725c8 fffff800`02da4d6f : 00000000`00000019 00000000`00000003 fffff800`02e01920 00000000`00000000 : nt!KeBugCheckEx
fffff880`031725d0 fffff880`0413a208 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExFreePool+0x536
fffff880`031726c0 fffff880`0413a7cc : 00000000`00000000 fffffa80`03a43b30 fffffa80`02f25d70 fffffa80`02f60910 : mssmbios!SMBiosSMbiosProcessSMBiosData+0xe4
fffff880`03172720 fffff800`0303070e : fffffa80`02f60910 fffffa80`03a43b30 fffffa80`02f25c20 fffff880`02f63180 : mssmbios!SMBiosDriverPnp+0x154
fffff880`03172790 fffff800`02d6b09d : fffffa80`0194de30 fffffa80`03a43b30 fffff800`02d70c80 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`031727d0 fffff800`0303b456 : fffff800`02e751c0 fffffa80`0194db60 fffffa80`03a43b30 fffffa80`0194dd08 : nt!PnpStartDevice+0x11d
fffff880`03172890 fffff800`0303b6f4 : fffffa80`0194db60 fffffa80`01930012 fffffa80`019315e0 00000000`00000001 : nt!PnpStartDeviceNode+0x156
fffff880`03172920 fffff800`0305e9d6 : fffffa80`0194db60 fffffa80`019315e0 00000000`00000002 00000000`00000000 : nt!PipProcessStartPhase1+0x74
fffff880`03172950 fffff800`0305ee8c : fffff800`02e72d80 00000000`00000000 00000000`00000001 fffff800`02edf698 : nt!PipProcessDevNodeTree+0x296
fffff880`03172bc0 fffff800`02d732d2 : 00000001`00000003 fffff800`02e165f8 00000000`00000001 00000000`00000000 : nt!PiProcessStartSystemDevices+0x7c
fffff880`03172c10 fffff800`02c7e861 : fffff800`02d72fd0 fffff800`02f6e801 fffffa80`0190d000 00000000`00000000 : nt!PnpDeviceActionWorker+0x302
fffff880`03172cb0 fffff800`02f16a86 : 00000000`00000000 fffffa80`0190d040 00000000`00000080 fffffa80`019079e0 : nt!ExpWorkerThread+0x111
fffff880`03172d40 fffff800`02c4fb06 : fffff880`02f63180 fffffa80`0190d040 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03172d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExFreePool+536
fffff800`02da4d6f cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!ExFreePool+536
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
FAILURE_BUCKET_ID: X64_0x19_3_nt!ExFreePool+536
BUCKET_ID: X64_0x19_3_nt!ExFreePool+536
Followup: Pool_corruption
---------
2: 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: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff80002e01920, the pool entry being checked.
Arg3: 0000000000000000, the read back flink freelist value (should be the same as 2).
Arg4: 0000000000000404, 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
LOCK_ADDRESS: fffff80002e75400 -- (!locks fffff80002e75400)
Resource @ nt!PiEngineLock (0xfffff80002e75400) Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
1 total locks
PNP_TRIAGE:
Lock address : 0xfffff80002e75400
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0
LAST_CONTROL_TRANSFER: from fffff80002da4d6f to fffff80002c71600
STACK_TEXT:
fffff880`031725c8 fffff800`02da4d6f : 00000000`00000019 00000000`00000003 fffff800`02e01920 00000000`00000000 : nt!KeBugCheckEx
fffff880`031725d0 fffff880`0413a208 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExFreePool+0x536
fffff880`031726c0 fffff880`0413a7cc : 00000000`00000000 fffffa80`03a43b30 fffffa80`02f25d70 fffffa80`02f60910 : mssmbios!SMBiosSMbiosProcessSMBiosData+0xe4
fffff880`03172720 fffff800`0303070e : fffffa80`02f60910 fffffa80`03a43b30 fffffa80`02f25c20 fffff880`02f63180 : mssmbios!SMBiosDriverPnp+0x154
fffff880`03172790 fffff800`02d6b09d : fffffa80`0194de30 fffffa80`03a43b30 fffff800`02d70c80 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`031727d0 fffff800`0303b456 : fffff800`02e751c0 fffffa80`0194db60 fffffa80`03a43b30 fffffa80`0194dd08 : nt!PnpStartDevice+0x11d
fffff880`03172890 fffff800`0303b6f4 : fffffa80`0194db60 fffffa80`01930012 fffffa80`019315e0 00000000`00000001 : nt!PnpStartDeviceNode+0x156
fffff880`03172920 fffff800`0305e9d6 : fffffa80`0194db60 fffffa80`019315e0 00000000`00000002 00000000`00000000 : nt!PipProcessStartPhase1+0x74
fffff880`03172950 fffff800`0305ee8c : fffff800`02e72d80 00000000`00000000 00000000`00000001 fffff800`02edf698 : nt!PipProcessDevNodeTree+0x296
fffff880`03172bc0 fffff800`02d732d2 : 00000001`00000003 fffff800`02e165f8 00000000`00000001 00000000`00000000 : nt!PiProcessStartSystemDevices+0x7c
fffff880`03172c10 fffff800`02c7e861 : fffff800`02d72fd0 fffff800`02f6e801 fffffa80`0190d000 00000000`00000000 : nt!PnpDeviceActionWorker+0x302
fffff880`03172cb0 fffff800`02f16a86 : 00000000`00000000 fffffa80`0190d040 00000000`00000080 fffffa80`019079e0 : nt!ExpWorkerThread+0x111
fffff880`03172d40 fffff800`02c4fb06 : fffff880`02f63180 fffffa80`0190d040 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03172d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExFreePool+536
fffff800`02da4d6f cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!ExFreePool+536
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
FAILURE_BUCKET_ID: X64_0x19_3_nt!ExFreePool+536
BUCKET_ID: X64_0x19_3_nt!ExFreePool+536
Followup: Pool_corruption
---------
Quote