BSOD Win7 help

V

vannet10

Member
Joined
Feb 13, 2015
Posts
9
Hello,

I got got a BSOD and hope someone here could help me out. Thanks to Tom982 for refering me here. I have followed the instruction and here are my answer.

1. Window 7
2. x64
3. Original installed OS is Window 8
4. OS is OEM version
5. a little less than 2 years old hardware
6. Just installed this new OS 2 weeks ago
7. i7-4770 @ 3.40GHz
8. GeForce GTX670
9. Where to check Motherboard model?
10. where to check power supply wattage and brand?
11. Dell system
12. Alienware x51 R2

Hope the above info is enough.

Thanks
Leng
 

Attachments

Code: 
6: kd> .bugcheck
Bugcheck code 00000019
Arguments 00000000`00000020 fffff8a0`169016e0 fffff8a0`16901940 00000000`0526031c

[COLOR="#800080"]//The pool entry we were looking for on the linked list[/COLOR]

6: kd> !pool fffff8a0169016e0
Pool page fffff8a0169016e0 region is Paged pool
 fffff8a016901000 size:  4d0 previous size:    0  (Allocated)  Ntff
 fffff8a0169014d0 size:   20 previous size:  4d0  (Free)       o.u.
 fffff8a0169014f0 size:   30 previous size:   20  (Allocated)  Ntf0
 fffff8a016901520 size:  1c0 previous size:   30  (Allocated)  NtFs
*fffff8a0169016e0 size:  260 previous size:  1c0  (Free ) *DxgK
		Pooltag DxgK : Vista display driver support, Binary : dxgkrnl.sys

fffff8a016901940 doesn't look like a valid small pool allocation, checking to see
if the entire page is actually part of a large page allocation...

GetUlongFromAddress: unable to read from fffff80003264a38
Unable to get pool big page table. Check for valid symbols.
fffff8a016901940 is not valid pool. Checking for freed (or corrupt) pool
Bad allocation size @fffff8a016901940, zero is invalid

***
*** An error (or corruption) in the pool was detected;
*** Attempting to diagnose the problem.
***
*** Use !poolval fffff8a016901000 for more details.


Pool page [ fffff8a016901000 ] is __inVALID.

Analyzing linked list...
[ fffff8a0169016e0 --> fffff8a016901bf0 (size = 0x510 bytes)]: Corrupt region


Scanning for single bit errors...

None found

[COLOR="#800080"]//The next pool entry on the linked list[/COLOR]

6: kd> dc fffff8a016901940
fffff8a0`16901940  00000000 00000000 00000000 00000000  ................
fffff8a0`16901950  00000000 00000000 00000000 00000000  ................
fffff8a0`16901960  00000000 00000000 00000000 00000000  ................
fffff8a0`16901970  00000000 00000000 ffffffff 00000000  ................
fffff8a0`16901980  80061085 00100810 00000016 0dead000  ................
fffff8a0`16901990  0dead000 00000016 0dead000 ffffffff  ................
fffff8a0`169019a0  00000000 00000000 00000000 00000000  ................
fffff8a0`169019b0  00000000 00000000 00000000 00000000  ................

6: kd> k
Child-SP          RetAddr           Call Site
fffff880`09722678 fffff800`031f1cae nt!KeBugCheckEx
fffff880`09722680 fffff880`10129523 nt!ExDeferredFreePool+0x12da
fffff880`09722730 fffff960`0019a016 dxgkrnl!DxgkEscape+0xc3f
fffff880`09722ab0 fffff800`030bf113 win32k!NtGdiDdDDIEscape+0x12
fffff880`09722ae0 00000000`7569148a nt!KiSystemServiceCopyEnd+0x13
00000000`0009dc28 00000000`00000000 0x7569148a

6: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f4b4000 fffff880`10101000   nvlddmkm   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sun Feb 16 05:47:22 2014 (530050EA)
    CheckSum:         00C1C97D
    ImageSize:        00C4D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The Nvidia driver has caused pool header corruption, thus linked list corruption for this pool. I'm not really surprised, it's over a year old... I recommend you update it.
 
tom982 said:
Jared I'm hopeless at BSOD analysis but I wanted to post this in case it's of any use to you:

https://www.sysnative.com/forums/wi...712-on-kb3006121-and-kb2852386.html#post95154

It listed the IRST driver on the BSOD, I'm guessing that's also outdated? (I don't have WinDbg on my Desktop so I can't check atm, sorry!).
Click to expand...

Thank you, that dump was never saved, it appears the crash hasn't worked correctly either.
It's an unknown bugcheck, it appears to be only the top bits of the crash error code. From the looks of it, iastorA.sys attempted to write to read-only memory.
Most likely a bad pointer was passed, bad programming code.
It's not surprising that this occurred, IRST is really buggy and unreliable anyway, I suggest you remove it.
Updating it doesn't usually resolve the issue, unless you're using a RAID setup there's no point keeping it.
Remove the storage driver(s) from the device manager.

Code: 
6: kd> lmvm iastora
start             end                 module name
fffff880`01287000 fffff880`01551000   iaStorA    (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\iaStorA.sys
    Image name: iaStorA.sys
    Timestamp:        Fri Jul 25 23:09:44 2014 (53D2D5A8)
    CheckSum:         000ADD39
    ImageSize:        002CA000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

It's less than a year old, nevertheless, it's still very problematic.
 
Last edited:
Hi Jared,

Sorry for the late reply. haven't really got time to sit down and fix it. I have updated the Nvidia driver (GTX 670) downloaded from Nvidia website and I'm not sure the problem has been resolved. I don't see the blue screen error anymore ( I haven't really use this problematic computer much of late tho). what test should I do to confirm that I have fixed the BSOD?

Also, you mention to remove IRST. What is this IRST? Where do I remove it? If it's of no use I would rather remove it. (Thanks Tom for giving further detail on this)

Leng
 
Just use your computer normally, it's difficult to test drivers unless you use Driver Verifier. I wouldn't recommend enabling it though, it could throw false positives when in actual fact, the driver wouldn't fail in a real life situation.

  1. To remove IRST you need to remove it on the Programs and Features
  2. Then go to Device Manager
  3. Expand IDE ATA/ATAPI controllers
  4. Then click uninstall on each one.
  5. Once removed reboot and it should have been removed
 
Hi Jared,

I got the blue screen again. However, this one is not related to the previous blue screen that you were solving because I actually reformat and reinstall the OS again since the last time we talked. So this is a different issue of blue screen I think. I attached the 2 files here for your analysis. Hope to get your help again. Thanks.

Leng
 

Attachments

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top