Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Please help BSOD ntoskrnl.exe+75b80

  • Please log in to reply
2 replies to this topic

#1 greyhair2014


  • Members
  • 1 posts
  • Local time:08:42 AM

Posted 14 March 2014 - 04:46 AM

New install of Windows 7 Professional. Passed memory test.


I have uploaded mini dump file results to the following link:
I'm not sure but it may be related to my Asus Motherboard P8Z68-V Pro/Gen3. BIOS version 3202.
I had this computer custom-built by a now departed tech friend; otherwise, I graduated college 38 years ago still using a slide rule.
Thank you in advance

BC AdBot (Login to Remove)


#2 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • Gender:Male
  • Location:India
  • Local time:09:12 PM

Posted 14 March 2014 - 08:11 AM

:welcome: to the Bleeping Computer forum.


There is only one crash dump can be seen in the attachment. To identify a pattern at lest 3 - 5 dumps are necessary. If there is more crash dumps available, please zip them using 7-zip and attach with next reply. Before doing that, please disconnect your hard drive from current port which is a Marvell one and plug it in to an Intel SATA port.


You will find two gray , four blue and two Navy blue ports in the MoBo. The navy blue ports are using "Marvell" SATA controller which is not so nice with "Windows 7". Make sure neither HDD nor DVD drive is connected to the Navy blue ports. I would suggest connecting both HDD and DVD to the Grey ports. Any additional drives can be connected to the normal blue ports ( 4 nos ). 




 After booting the machine, uninstall Marvell driver from "Control Panel". If the BSOD continues, make sure to publish a snapshot of your system using "Speccy" along with uploading crash dumps.



#3 Kirbyofdeath


  • Members
  • 459 posts
  • Gender:Male
  • Location:Somewhere on Earth
  • Local time:10:42 AM

Posted 21 March 2014 - 01:48 PM

Here is a debug of your minidump.


Microsoft ® Windows Debugger Version 6.3.9600.16384 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Mike&Michelle\mdmps\031314-29250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Machine Name:
Kernel base = 0xfffff800`03662000 PsLoadedModuleList = 0xfffff800`038a56d0
Debug session time: Thu Mar 13 08:56:01.515 2014 (UTC - 5:00)
System Uptime: 0 days 11:31:46.312
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, fffff8a010ddc8a0, fffff8a010ddcbb0, 5310033}
GetPointerFromAddress: unable to read from fffff8000390f100
GetUlongFromAddress: unable to read from fffff8000390f1c0
Probably caused by : ntkrnlmp.exe ( nt!RtlDeleteElementGenericTableAvl+4e )
Followup: MachineOwner
2: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
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.
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff8a010ddc8a0, The pool entry we were looking for within the page.
Arg3: fffff8a010ddcbb0, The next pool entry.
Arg4: 0000000005310033, (reserved)
Debugging Details:
BUGCHECK_STR:  0x19_20
POOL_ADDRESS:  fffff8a010ddc8a0 Paged pool
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
LAST_CONTROL_TRANSFER:  from fffff8000380acae to fffff800036d7b80
fffff880`09dfdef8 fffff800`0380acae : 00000000`00000019 00000000`00000020 fffff8a0`10ddc8a0 fffff8a0`10ddcbb0 : nt!KeBugCheckEx
fffff880`09dfdf00 fffff800`036b2a0e : fffff8a0`21707010 fffff880`09dffd50 fffffa80`7346744e fffffa80`0dcb9180 : nt!ExDeferredFreePool+0x12da
fffff880`09dfdfb0 fffff880`01aadf69 : fffff880`09dfe070 fffff880`09dffd50 fffff8a0`10ddc8b0 fffffa80`1230d760 : nt!RtlDeleteElementGenericTableAvl+0x4e
fffff880`09dfdfe0 fffff880`01a2b7a2 : fffff880`09dffd50 fffff880`09dffd00 fffff880`09dfe061 fffff8a0`21707010 : Ntfs!NtfsDeleteFcb+0x179
fffff880`09dfe040 fffff880`01ab061c : fffffa80`1230d760 fffffa80`0dcb9180 fffff8a0`21707010 fffff8a0`217073a8 : Ntfs!NtfsTeardownFromLcb+0x1e2
fffff880`09dfe0d0 fffff880`01ab6d3a : fffffa80`1230d760 fffff880`0a488390 fffffa80`1230d760 00000000`00000400 : Ntfs!NtfsTeardownStructures+0xcc
fffff880`09dfe150 fffff800`03702d8f : 00000000`00000000 fffff800`039c3dc8 fffff880`09dfff30 fffff880`09dfeac0 : Ntfs! ?? ::NNGAKEGL::`string'+0x676f
fffff880`09dfe200 fffff800`037027dd : fffff880`09dffd50 fffff880`09dffd50 00000000`00000000 fffff880`01a24000 : nt!_C_specific_handler+0x13f
fffff880`09dfe270 fffff800`03702228 : fffff880`09dffd50 fffff880`09dfe2f0 fffff880`01a3dad8 fffff880`01a24000 : nt!RtlpExecuteHandlerForUnwind+0xd
fffff880`09dfe2a0 fffff800`03702d1c : fffff880`09dfff30 fffff880`01a32412 fffff880`09dff0e0 ffffffff`c0000022 : nt!RtlUnwindEx+0x472
fffff880`09dfe940 fffff800`0370275d : fffff880`01a6f178 fffff880`09dfff30 00000000`00000000 fffff880`01a24000 : nt!_C_specific_handler+0xcc
fffff880`09dfe9b0 fffff800`03701535 : fffff880`01a6f178 fffff880`09dfea28 fffff880`09dff0e0 fffff880`01a24000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`09dfe9e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlDispatchException+0x415
fffff800`036b2a0e b001            mov     al,1
SYMBOL_NAME:  nt!RtlDeleteElementGenericTableAvl+4e
FOLLOWUP_NAME:  MachineOwner
IMAGE_NAME:  ntkrnlmp.exe
IMAGE_VERSION:  6.1.7601.18229
FAILURE_BUCKET_ID:  X64_0x19_20_nt!RtlDeleteElementGenericTableAvl+4e
BUCKET_ID:  X64_0x19_20_nt!RtlDeleteElementGenericTableAvl+4e
FAILURE_ID_HASH_STRING:  km:x64_0x19_20_nt!rtldeleteelementgenerictableavl+4e
FAILURE_ID_HASH:  {9a556563-1919-c2dd-33b6-d7f79352adff}
Followup: MachineOwner
"Seaport.exe" looks like the one causing your problem (for this minidump at least).

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users