BSOD downloading from internet

Asus G53SW Notebook running Windows 7 64 Bit

Just had a HDD crash and had to do a reinstall. The HDD was replaced with a Crucial M4 SSD.

Received a BSOD which I think read PAGE_POOL_HEADER.

I have managed to open the .dmp file and post the contents here:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Code:

Loading Dump File [E:\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c58000 PsLoadedModuleList = 0xfffff800`02e9d670
Debug session time: Thu Jan 12 00:02:59.888 2012 (UTC + 11:00)
System Uptime: 0 days 0:07:14.840
Loading Kernel Symbols
...............................................................

Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd9018).  Type ".hh dbgerr001" for details
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffffffffffff5, 0, fffff80002fa1e6e, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1de )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffffffffffff5, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002fa1e6e, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------

READ_ADDRESS:  fffffffffffffff5 
FAULTING_IP: 
nt!CmpKcbCacheLookup+1de
fffff800`02fa1e6e 418b45f4        mov     eax,dword ptr [r13-0Ch]
MM_INTERNAL_CODE:  0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
CURRENT_IRQL:  0
TRAP_FRAME:  fffff8800746d990 -- (.trap 0xfffff8800746d990)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000000044a
rdx=000000000470ed4e rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002fa1e6e rsp=fffff8800746db20 rbp=fffff8a000024010
 r8=000000000000000a  r9=0000000000000000 r10=0000000000000002
r11=fffff8800746dca0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!CmpKcbCacheLookup+0x1de:
fffff800`02fa1e6e 418b45f4        mov     eax,dword ptr [r13-0Ch] ds:0005:fff4=????????
Resetting default scope
LOCK_ADDRESS:  fffff80002ed39e0 -- (!locks fffff80002ed39e0)
Resource @ nt!PnpRegistryDeviceResource (0xfffff80002ed39e0)    Exclusively owned
    Contention Count = 99
     Threads: fffffa800d168b60-01<*> 
1 total locks, 1 locks currently held
PNP_TRIAGE: 
 Lock address  : 0xfffff80002ed39e0
 Thread Count  : 1
 Thread address: 0xfffffa800d168b60
 Thread wait   : 0x6ce2
LAST_CONTROL_TRANSFER:  from fffff80002c809fc to fffff80002cd4c40
STACK_TEXT:  
fffff880`0746d828 fffff800`02c809fc : 00000000`00000050 ffffffff`fffffff5 00000000`00000000 fffff880`0746d990 : nt!KeBugCheckEx
fffff880`0746d830 fffff800`02cd2d6e : 00000000`00000000 ffffffff`fffffff5 fffff880`0746dd00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`0746d990 fffff800`02fa1e6e : fffff880`0746dfd0 fffff880`0746df78 fffff880`0746df98 fffff880`0746dfca : nt!KiPageFault+0x16e
fffff880`0746db20 fffff800`02fa2b75 : fffff880`0746dca0 fffff880`00000001 fffff880`0746e0b8 fffff880`0746e0b0 : nt!CmpKcbCacheLookup+0x1de
fffff880`0746dc10 fffff800`02f9f224 : fffff8a0`02ef9790 fffff880`0746e0b0 fffff880`0746e100 fffff880`0746e0e0 : nt!CmpBuildHashStackAndLookupCache+0x335
fffff880`0746dff0 fffff800`02fcf838 : fffffa80`0d1471c8 fffffa80`00000000 fffffa80`0d147010 fffff800`00000000 : nt!CmpParseKey+0x294
fffff880`0746e2f0 fffff800`02fd0a56 : ffffffff`800006a0 fffffa80`0d147010 fffff8a0`00000000 fffffa80`0cdaa510 : nt!ObpLookupObjectName+0x588
fffff880`0746e3e0 fffff800`02fa42bc : 00000000`0000002a 00000000`00000000 00000000`00000000 00000000`00000200 : nt!ObOpenObjectByName+0x306
fffff880`0746e4b0 fffff800`02faf392 : fffff880`0746e8b0 00000000`00020019 fffff880`0746e800 fffff880`00000000 : nt!CmOpenKey+0x28a
fffff880`0746e600 fffff800`02cd3ed3 : fffffa80`00000000 fffff8a0`07423830 fffff880`00000200 fffff880`0746e884 : nt!NtOpenKey+0x12
fffff880`0746e640 fffff800`02cd0470 : fffff800`02f43e58 00000000`0000000e 00000000`00000200 00000000`0000002a : nt!KiSystemServiceCopyEnd+0x13
fffff880`0746e7d8 fffff800`02f43e58 : 00000000`0000000e 00000000`00000200 00000000`0000002a fffff8a0`07423830 : nt!KiServiceLinkage
fffff880`0746e7e0 fffff800`02f40b0a : 00000000`00000000 fffff880`0746e9e0 fffff8a0`02f10700 00000000`00000000 : nt!IopOpenRegistryKeyEx+0x38
fffff880`0746e840 fffff800`02f412a1 : 00000000`00000002 00000000`00000000 fffff880`00000000 00000000`00000001 : nt!IopGetDeviceInterfaces+0x37e
fffff880`0746e9b0 fffff800`02f4056d : 00000000`00000002 00000000`00000000 00000000`00000000 fffff8a0`02f10780 : nt!PiGetInterfaceDeviceList+0x41
fffff880`0746ea10 fffff800`02f996dc : fffff8a0`02f10780 fffff800`00008000 fffff880`0746eb01 fffff800`0319fda0 : nt!PiControlGetInterfaceDeviceList+0x111
fffff880`0746ea90 fffff800`02cd3ed3 : fffffa80`0d168b60 00000000`0048ebd0 fffff880`0746eb60 00000000`0048ec58 : nt!NtPlugPlayControl+0x100
fffff880`0746eae0 00000000`778e236a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0048eb98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778e236a

STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!CmpKcbCacheLookup+1de
fffff800`02fa1e6e 418b45f4        mov     eax,dword ptr [r13-0Ch]
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  nt!CmpKcbCacheLookup+1de
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
FAILURE_BUCKET_ID:  X64_0x50_nt!CmpKcbCacheLookup+1de
BUCKET_ID:  X64_0x50_nt!CmpKcbCacheLookup+1de
Followup: MachineOwner
--------------------------------------------------------------
 
I also ran the windows troubleshoot utility and post the results here:
 
Devices and Printers Publisher details 
Issues found 
Bluetooth Module is not working properlyBluetooth Module is not working properly
Windows has detected a problem with Bluetooth Module. Detected  
View device details Completed 
 
Problem with PnP devicesProblem with PnP devices
There are problems with some PnP devices. Windows will take additional steps to further troubleshoot these devices. Detected  
Issues found Detection details 
6 Bluetooth Module is not working properly Detected  
 
Windows has detected a problem with Bluetooth Module. 
Device information 
Name: Bluetooth Module 
ID: USB\VID_13D3&PID_3304\6&1CA26F5B&0&1 
Error code: 43 
 
View device details Completed 
 
View details about Bluetooth Module and check if there is a solution available. 
 
 Problem with PnP devices Detected  
 
There are problems with some PnP devices. Windows will take additional steps to further troubleshoot these devices. 
 
Detection details  
Collection information 
Computer Name:  VP2011 
Windows Version: 6.1 
Architecture: amd64 
Time: Thursday, January 12, 2012 4:57:04 PM 
Publisher details  
Devices and Printers 
Troubleshoot problems with devices and printers. 
Package Version: 2.0 
Publisher: Microsoft Corporation 
Devices and Printers 
Troubleshoot problems with devices and printers. 
Package Version: 2.0 
Publisher: Microsoft Corporation 
Hardware and Devices 
Use hardware and access devices connected to your computer. 
Package Version: 1.1 
Publisher: Microsoft Windows 
Windows Network Diagnostics 
Detects problems with network connectivity. 
Package Version: 1.0 
Publisher: Microsoft Windows 
Printer 
Troubleshoot problems preventing printing from completing. 
Package Version: 1.0 
Publisher: Microsoft Windows 
USB 
Troubleshoot problems with a USB device 
Package Version: 1.0 
Publisher: Microsoft Corporation 
----------------------------------------------

Any assistance would be greatly appreicated.

fredbv

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Hi ZIGZAG3143.

Thanks for your reply.

As advised, I have located and zipped the minidump folder. The file was too large so you may download from rapidshare:

https://rapidshare.com/files/1651765865/Minidump.zip

I look forward to your response. Thanks for you support.

fredbv

fredbv said:

Hi ZIGZAG3143.

Thanks for your reply.

As advised, I have located and zipped the minidump folder. The file was too large so you may download from rapidshare:

https://rapidshare.com/files/1651765865/Minidump.zip

I look forward to your response. Thanks for you support.

fredbv

Fred

You missed the part of configuring your control panel for the 256K DMP file. WIll take me abt 30 mins to DL from rapidshare.



Invalid system memory referenced. Usually a driver. Please run these.






If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



2-Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Driver Verifier - Enable and Disable


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users

Thanks for the advice.

Sorry about the dmp file... I made the change to 256k DMP file after the system crash... it has not crashed since.

I will follow all of your advice and post results once I have them.

I really appreciated your help with this.

Cheers

Fred

fredbv said:

Thanks for the advice.

Sorry about the dmp file... I made the change to 256k DMP file after the system crash... it has not crashed since.

I will follow all of your advice and post results once I have them.

I really appreciated your help with this.

Cheers

Fred

No worries abt the dmp size, just want you to fix it before the next dmp.

Let me know if you need help and good luck.

Yes, I have made the change to Dump file size. Also, I forgot to mention that I am not overclocking... wouldn't know how to.

I have run memtest... 8 passes... no errors.

I am now running verifier... I have no data on the computer, but I have created a restore point and rescue disc as advised.

I shall be in touch... thx.

fredbv said:

Yes, I have made the change to Dump file size. Also, I forgot to mention that I am not overclocking... wouldn't know how to.

I have run memtest... 8 passes... no errors.

I am now running verifier... I have no data on the computer, but I have created a restore point and rescue disc as advised.

I shall be in touch... thx.

Good news on memtest, and good luck

Hi ZizZag

BSOD is back.... Unfortunately I had turned off the driver verifier, thinking all was well since I had not had a BSOD we last spoke.

I have the .dmp file and have attached it here. I have also attached the Windows error report that displayed after I rebooted.

Hope you can help. Thanks, Fred