Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD troubles, again.

11 Sep 2010   #1

Windows 7
BSOD troubles, again.

Now my tales of BSOD is a long one stretching back to January.

Link to original thread

Now, I sent back the hard drive and the ram which were reported as faulty. I get the system all back together and working...fantastic...for 2 weeks. Now it's blue screened twice, Bad Pool header. The only thing I've been changing is opening ports on the router and changing upnp settings, not something I'd imagine would force bluescreens.

The ram has seemed fine, no lockups like before.

Voltage seemed fine for the ram when installing, can't remember what I set it as but I just set it to the voltage shown on the box.

My System SpecsSystem Spec
11 Sep 2010   #2

Win 8 Release candidate 8400

Quote   Quote: Originally Posted by Gingermadman View Post
Now my tales of BSOD is a long one stretching back to January.

Link to original thread

Now, I sent back the hard drive and the ram which were reported as faulty. I get the system all back together and working...fantastic...for 2 weeks. Now it's blue screened twice, Bad Pool header. The only thing I've been changing is opening ports on the router and changing upnp settings, not something I'd imagine would force bluescreens.

The ram has seemed fine, no lockups like before.

Voltage seemed fine for the ram when installing, can't remember what I set it as but I just set it to the voltage shown on the box.


Bugcheck 19 is a bad pool header. Can be caused by a driver or bad RAM. There isnt enough info to say which at the moment. I think I do notice is that there is no timestamp on almost all of your drivers and wonder where did you download the image from.? I went back to your previous thread and there were dates then, so I am confused.

drivers without dates
ACPI.sys        fffff880`00e58000    fffff880`00eaf000    0x00057000    0x00000000                            
amdxata.sys        fffff880`00fec000    fffff880`00ff7000    0x0000b000    0x00000000                            
atapi.sys        fffff880`00fb9000    fffff880`00fc2000    0x00009000    0x00000000                            
ataport.SYS        fffff880`00fc2000    fffff880`00fec000    0x0002a000    0x00000000                            
CI.dll        fffff880`00c90000    fffff880`00d50000    0x000c0000    0x00000000                            
CLASSPNP.SYS        fffff880`01000000    fffff880`01030000    0x00030000    0x00000000                            
CLFS.SYS        fffff880`00c32000    fffff880`00c90000    0x0005e000    0x00000000                            
cng.sys        fffff880`0130d000    fffff880`01380000    0x00073000    0x00000000                            
disk.sys        fffff880`0127d000    fffff880`01293000    0x00016000    0x00000000                            
fileinfo.sys        fffff880`01044000    fffff880`01058000    0x00014000    0x00000000                            
fltmgr.sys        fffff880`00e00000    fffff880`00e4c000    0x0004c000    0x00000000                            
Fs_Rec.sys        fffff880`01391000    fffff880`0139b000    0x0000a000    0x00000000                            
fvevol.sys        fffff880`01243000    fffff880`0127d000    0x0003a000    0x00000000                            
fwpkclnt.sys        fffff880`0148b000    fffff880`014d5000    0x0004a000    0x00000000                            
hal.dll        fffff800`02818000    fffff800`02861000    0x00049000    0x4a5bdf08    7/13/2009 21:27:36                        
hwpolicy.sys        fffff880`0123a000    fffff880`01243000    0x00009000    0x00000000                            
kdcom.dll        fffff800`00b99000    fffff800`00ba3000    0x0000a000    0x4a5bdfdb    7/13/2009 21:31:07                        
ksecdd.sys        fffff880`012f3000    fffff880`0130d000    0x0001a000    0x00000000                            
ksecpkg.sys        fffff880`01460000    fffff880`0148b000    0x0002b000    0x00000000                            
mcupdate.dll        fffff880`00c11000    fffff880`00c1e000    0x0000d000    0x00000000                            
mountmgr.sys        fffff880`00f9f000    fffff880`00fb9000    0x0001a000    0x00000000                            
msisadrv.sys        fffff880`00eb8000    fffff880`00ec2000    0x0000a000    0x00000000                            
msrpc.sys        fffff880`01295000    fffff880`012f3000    0x0005e000    0x00000000                            
mup.sys        fffff880`015ea000    fffff880`015fc000    0x00012000    0x00000000                            
ndis.sys        fffff880`014f8000    fffff880`015ea000    0x000f2000    0x00000000                            
NETIO.SYS        fffff880`01400000    fffff880`01460000    0x00060000    0x00000000                            
Ntfs.sys        fffff880`01058000    fffff880`011fb000    0x001a3000    0x00000000                            
ntoskrnl.exe    ntoskrnl.exe+7e24a    fffff800`02861000    fffff800`02e3d000    0x005dc000    0x4c1c44a9    6/19/2010 00:16:41                        
partmgr.sys        fffff880`00f02000    fffff880`00f17000    0x00015000    0x00000000                            
pci.sys        fffff880`00ec2000    fffff880`00ef5000    0x00033000    0x00000000                            
pciide.sys        fffff880`00f88000    fffff880`00f8f000    0x00007000    0x00000000                            
PCIIDEX.SYS        fffff880`00f8f000    fffff880`00f9f000    0x00010000    0x00000000                            
pcw.sys        fffff880`01380000    fffff880`01391000    0x00011000    0x00000000                            
PSHED.dll        fffff880`00c1e000    fffff880`00c32000    0x00014000    0x00000000                            
rdyboost.sys        fffff880`01200000    fffff880`0123a000    0x0003a000    0x00000000                            
speedfan.sys        fffff880`014ed000    fffff880`014f4000    0x00007000    0x00000000                            
spldr.sys        fffff880`014e5000    fffff880`014ed000    0x00008000    0x00000000                            
tcpip.sys        fffff880`01602000    fffff880`017ff000    0x001fd000    0x00000000                            
Unknown_Module_00000000`0471de10        00000000`0471de10    00000000`fc490720    0xf7d72910    0x00000000                            
vdrvroot.sys        fffff880`00ef5000    fffff880`00f02000    0x0000d000    0x00000000                            
vmstorfl.sys        fffff880`014d5000    fffff880`014e5000    0x00010000    0x00000000                            
volmgr.sys        fffff880`00f17000    fffff880`00f2c000    0x00015000    0x00000000                            
volmgrx.sys        fffff880`00f2c000    fffff880`00f88000    0x0005c000    0x00000000                            
volsnap.sys        fffff880`0139b000    fffff880`013e7000    0x0004c000    0x00000000                            
Wdf01000.sys        fffff880`00d50000    fffff880`00df4000    0x000a4000    0x00000000                            
WDFLDR.SYS        fffff880`00c00000    fffff880`00c0f000    0x0000f000    0x00000000                            
WMILIB.SYS        fffff880`00eaf000    fffff880`00eb8000    0x00009000    0x00000000
In order to identify the driver I would run driver verifier to identify it

Beyond that, please run Verifier with these settings:
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.

So, I'd suggest that you first backup your stuff 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).

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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
Let us know if you need assistance

My System SpecsSystem Spec
11 Sep 2010   #3

Windows 7

crashes before I can get into windows, won't load up windows either which way

Here are the two dumps of the day...

edit. blue screened as I was writing this, more one dump

how strange I can go from having a perfectly fine machine to one that blue screens constantly after changing nothing
My System SpecsSystem Spec

11 Sep 2010   #4

Windows 7

Sorry for the early bump, but I'll be unlikely to see this thread over the course of the rest of the weekend and I'll be busy on Monday and Tuesday.
My System SpecsSystem Spec
11 Sep 2010   #5

Windows 7 Ultimate 32 bit

I looked at the three dumps and all have different error codes. Add to this the fact that your latest crash occurred during booting points to hardware or driver issues.

Error code 7E , SYSTEM_THREAD_EXCEPTION_NOT_HANDLED - Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

Error code 19, BAD_POOL_HEADER - Usual causes: Device driver

Error code A, IRQL_NOT_LESS_OR_EQUAL - Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

Notice in the usual causes in all three error codes, device driver is listed.

This may well be your main problem:

ASACPI.sys Sun Mar 27 22:30:36 2005

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.

Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).
Reboot and run your system.

I find another out of date driver on your system. Win 7 generally does not like out of date third party drivers. The can and do cause conflicts and memory corruption. Two of your dumps indicated memory corruption.

Rt64win7.sys Thu Feb 26 04:04:13 2009 - Realtek 8101E/8168/8169 NDIS 6.20 64-bit Driver. Realtek. Update this driver.

Let's see if there is any improvement in your system.. Post back and let us know.
My System SpecsSystem Spec
11 Sep 2010   #6

Windows 7

only doing a quick pit stop home so I can reply here so I can't check, but I left a memory checker running and it had done 8 tests and found 0 errors.
My System SpecsSystem Spec
12 Sep 2010   #7

Windows 7

blue screened instantly as I went into windows, wouldn't load web pages to upload any dumps, now back to the computer in an infinite cycle of trying to start up and failing to get into the BIOS. Web pages work in explorer apparantly, very strange.


Edit. after switching it on and off at the back it decided to turn itself on and get into windows.

Greeted by "This copy of windows is not geniune"

Chances of a windows update borking everything was high in XP, not sure about w7

another edit. Trying to run repair install, says cannot install 64 bit onto a 32bit installation


cannot install 32 bit onto a 64 bit installation

My System SpecsSystem Spec
12 Sep 2010   #8

Windows 7 Ultimate 32 bit

Windows updates have cause problems for me twice, but not to the extent of borking my system. One update rendered URL's in emails (Outlook) useless and another messed up other parts of of MS Office. Have you tried booting in the safe mode? Can you use a restore point or a system image to take your system back before this problem started? If not, it is time to reformat your drive and do a clean install.

If you reformat and do a clean install, immediately create a restore point or, preferably, image your system. Do this before you install any software other than Microsoft Security Essentials. Then start gradually adding your software, one at a time. Reboot after installing each software and run your system. If it runs smoothly, create another restore point of system image. If you get a BSOD, upload it using this tutorial so that we can take a full look at your system:

One of the four dumps was corrupted. The three good dumps did not point to anything specific; but all three indicated memory problems or memory corruption. Here are the error codes:

Error code A (2 instances), IRQL_NOT_LESS_OR_EQUAL - BSOD Index

Error code 4E (corrupted dump), PFN LIST CORRUPT - BSOD Index

My System SpecsSystem Spec
12 Sep 2010   #9

Windows 7

One more dump. This SHOULD be the IO something something verified dump, if not that means it's obviously not dumping the verified dumps properly.

and do I need to repeat the bsod posting thing for every bsod? as I have it included up top in my second post.
My System SpecsSystem Spec
12 Sep 2010   #10

Windows 7 Ultimate 32 bit

It is a Driver Verifier enabled dump. Unfortunately, it points to a Windows system core driver which is very unlikely to be the cause. The dump does reference memory. You can turn off Driver Verifier.


Kernel base = 0xfffff800`02817000 PsLoadedModuleList = 0xfffff800`02a54e50
Debug session time: Sun Sep 12 11:54:51.212 2010 (GMT-4)
System Uptime: 0 days 0:00:15.054
Loading Kernel Symbols
Loading User Symbols
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck A, {6, 2, 0, fffff800028a72b3}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

Followup: MachineOwner

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

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.
Arg1: 0000000000000006, 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: fffff800028a72b3, address which referenced memory

Debugging Details:

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002abf0e0


fffff800`028a72b3 488b09          mov     rcx,qword ptr [rcx]





IRP_ADDRESS:  ffffffffffffff8e

TRAP_FRAME:  fffff880031a0a70 -- (.trap 0xfffff880031a0a70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880031a0f80 rbx=0000000000000000 rcx=0000000000000006
rdx=0000000000000006 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800028a72b3 rsp=fffff880031a0c00 rbp=fffff880031a0d50
 r8=0000000000000100  r9=0000000000000000 r10=0000000000000002
r11=fffff800028a67d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
fffff800`028a72b3 488b09          mov     rcx,qword ptr [rcx] ds:00000000`00000006=????????????????
Resetting default scope

LOCK_ADDRESS:  fffff80002a8b400 -- (!locks fffff80002a8b400)

Resource @ nt!PiEngineLock (0xfffff80002a8b400)    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

    Lock address  : 0xfffff80002a8b400
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff80002886ca9 to fffff80002887740

fffff880`031a0928 fffff800`02886ca9 : 00000000`0000000a 00000000`00000006 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`031a0930 fffff800`02885920 : fffff880`031a0b30 fffff980`02e40ee0 00000001`197fe860 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`031a0a70 fffff800`028a72b3 : fffff980`02e40ee0 fffff880`031a0d50 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`031a0c00 fffff800`028640c7 : 00000000`00000006 0000007f`fffffff8 00000000`00000000 fffffa80`00000000 : nt!IopCompleteRequest+0xae3
fffff880`031a0cd0 fffff800`02864487 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`031a0d50 fffff800`02bf47a8 : fffff800`02c020c7 00000000`00000010 00000000`001700e0 fffff880`031a0f18 : nt!KiApcInterrupt+0xd7
fffff880`031a0ee8 fffff800`02c020c7 : 00000000`00000010 00000000`001700e0 fffff880`031a0f18 00000000`00000018 : nt!ChkSum+0x8
fffff880`031a0ef0 fffff800`02c60a41 : 00000000`00000000 00000000`00000000 00000000`00100000 fffff880`031a12d8 : nt!LdrVerifyMappedImageMatchesChecksum+0x67
fffff880`031a0f20 fffff800`02c60c7c : ffffffff`80000110 00000000`00100000 00000000`00170000 ffffffff`80000168 : nt!MmCheckSystemImage+0x221
fffff880`031a1050 fffff800`02c60e97 : ffffffff`80000110 00001f80`00000001 fffff880`031a1338 fffff880`031a1200 : nt!MiCreateSectionForDriver+0xcc
fffff880`031a1100 fffff800`02c6c73a : 00000000`00000000 fffff880`031a12d8 fffffa80`039feb60 00000000`00000000 : nt!MiObtainSectionForDriver+0xd7
fffff880`031a1160 fffff800`02c6f35d : fffff880`031a12d8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmLoadSystemImage+0x23a
fffff880`031a1280 fffff800`02d02c30 : 00000000`00000001 00000000`00000000 fffff880`031a1828 ffffffff`80000164 : nt!IopLoadDriver+0x44d
fffff880`031a1550 fffff800`02b41794 : fffff880`031a1860 00000000`00000000 00000000`c0000023 00000000`00000000 : nt!PipCallDriverAddDeviceQueryRoutine+0x390
fffff880`031a1650 fffff800`02b41aa2 : 00000000`00000000 00000000`00000000 fffff880`031a1860 fffff880`031a1828 : nt!RtlpCallQueryRegistryRoutine+0xf4
fffff880`031a16d0 fffff800`02c72bcc : fffffa80`047f46e0 00000000`00000000 00000000`c0000034 fffff880`031a1828 : nt!RtlQueryRegistryValues+0x17e
fffff880`031a17a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PipCallDriverAddDevice+0x45c


fffff800`02885920 440f20c0        mov     rax,cr8


SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  ntkrnlmp.exe


FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!KiPageFault+260

BUCKET_ID:  X64_0xA_VRF_nt!KiPageFault+260

Followup: MachineOwner

2: kd> lmtsmn
start             end                 module name
fffff880`00ebe000 fffff880`00f15000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`0195e000 fffff880`019e8000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`03e95000 fffff880`03eaa000   amdppm   amdppm.sys   Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`00e00000 fffff880`00e0b000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`019e8000 fffff880`019f2000   aswRdr   aswRdr.SYS   Tue Sep 07 10:47:47 2010 (4C865093)
fffff880`01016000 fffff880`01039000   aswSP    aswSP.SYS    Tue Sep 07 10:52:07 2010 (4C865197)
fffff880`0194e000 fffff880`0195e000   aswTdi   aswTdi.SYS   Tue Sep 07 10:52:27 2010 (4C8651AB)
fffff880`00ff5000 fffff880`00ffe000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00d94000 fffff880`00dbe000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`018a2000 fffff880`018a9000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`02def000 fffff880`02e00000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`0186f000 fffff880`01899000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00caa000 fffff880`00d6a000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01809000 fffff880`01839000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c4c000 fffff880`00caa000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`010f7000 fffff880`0116a000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`01839000 fffff880`01847000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`02c00000 fffff880`02c83000   csc      csc.sys      Mon Jul 13 19:24:26 2009 (4A5BC22A)
fffff880`02dd1000 fffff880`02def000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`02dc2000 fffff880`02dd1000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`01000000 fffff880`01016000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01853000 fffff880`0185c000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01847000 fffff880`01853000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0185c000 fffff880`0186f000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`14af7000 fffff880`14beb000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`13e00000 fffff880`13e46000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`01085000 fffff880`01099000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01039000 fffff880`01085000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`0122b000 fffff880`01235000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`00dbe000 fffff880`00df8000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`01589000 fffff880`015d3000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`02df3000 fffff800`02e3c000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`015f2000 fffff880`015fb000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff800`00b96000 fffff800`00ba0000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`01200000 fffff880`0121a000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`0155e000 fffff880`01589000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`00c2b000 fffff880`00c38000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`00d7a000 fffff880`00d94000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`01907000 fffff880`01912000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00f1e000 fffff880`00f28000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01099000 fffff880`010f7000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`02db7000 fffff880`02dc2000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`01235000 fffff880`01247000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`0140c000 fffff880`014fe000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`02cff000 fffff880`02d0e000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02c8b000 fffff880`02cd0000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`014fe000 fffff880`0155e000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`01912000 fffff880`01923000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`02dab000 fffff880`02db7000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02817000 fffff800`02df3000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`01255000 fffff880`013f8000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`01899000 fffff880`018a2000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`14af5000 fffff880`14af6180   nvBridge nvBridge.kmd Fri Jul 09 17:07:54 2010 (4C378FAA)
fffff880`13e63000 fffff880`14af4e00   nvlddmkm nvlddmkm.sys Fri Jul 09 17:15:58 2010 (4C37918E)
fffff880`02cd9000 fffff880`02cff000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`00f68000 fffff880`00f7d000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00f28000 fffff880`00f5b000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00fee000 fffff880`00ff5000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00d6a000 fffff880`00d7a000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`0121a000 fffff880`0122b000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00c38000 fffff880`00c4c000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`02d5a000 fffff880`02dab000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`018ec000 fffff880`018f5000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`018f5000 fffff880`018fe000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`018fe000 fffff880`01907000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`011b6000 fffff880`011f0000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`02d0e000 fffff880`02d2b000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`015eb000 fffff880`015f2000   speedfan speedfan.sys Sun Sep 24 09:26:48 2006 (45168798)
fffff880`015e3000 fffff880`015eb000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`01600000 fffff880`017fd000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`01941000 fffff880`0194e000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`01923000 fffff880`01941000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`02d46000 fffff880`02d5a000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff880`00c00000 fffff880`00c26000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`00f5b000 fffff880`00f68000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`018a9000 fffff880`018b7000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`018b7000 fffff880`018dc000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`015d3000 fffff880`015e3000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00f7d000 fffff880`00f92000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00f92000 fffff880`00fee000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`0116a000 fffff880`011b6000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`02d2b000 fffff880`02d46000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`018dc000 fffff880`018ec000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00e0b000 fffff880`00eaf000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00eaf000 fffff880`00ebe000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02cd0000 fffff880`02cd9000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`00f15000 fffff880`00f1e000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
The dump does not show us anything we do not already know.
My System SpecsSystem Spec

 BSOD troubles, again.

Thread Tools

Similar help and support threads
Thread Forum
BSOD troubles seem to be while playing games - different BsOD codes
My blue screens seem to happen when I am playing games, I have attached some logs and the zip file using the tool in the instructions. I have tried to upgrade my bios and my video card drivers without any luck. I would be grateful for any suggestions or help. thanks, Tim windows version:...
BSOD Help and Support
BSOD troubles
My Computer keeps Blue Screening. I have no Idea what the problem is and am looking for help. It usually blue screens while am playing games or watching videos (don't know if that helps or not). I noticed my performance report didn't say I have Internet security but i am running kaspersky 2011. ...
BSOD Help and Support
Same old BSOD troubles...
Well, I wished I never had to come back here, but here I am... I have the same problem as before: getting a BSOD with the error code "3B" during a game, or after I close the game, this happens Minecraft, Battlefield: Bad company 2, sometimes Starcraft 2, and Elder Scrolls: Oblivion... I'm running a...
BSOD Help and Support
BSOD troubles
Hi I'm new to the forums, but I will try to explain everything as best as I can. I have an hp pavilion dv3510nr laptop. Some of the laptop specs are: OS: windows 7 home premium Microprocessor2.00 GHz Intel Centrino 2 Processor Technology featuring Intel Core 2 Duo Processor...
BSOD Help and Support
BSOD ntoskrnl.exe troubles (I think)
Greetings to all I went from Vista Ultimate 64 to W7 Pro 64 about a week ago a since then I have been having BSOD troubles over a LOOOOONG time. (Had one during I was writing a post here a few minutes ago too, maybe my PC doesn't like me complaining :huh: ) Anyways you can get my PC specs...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 23:34.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App