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.

Photo

Brand new laptop - BSODs every day


  • Please log in to reply
19 replies to this topic

#1 JayBuys

JayBuys

  • Members
  • 5 posts
  • OFFLINE
  •  

Posted 22 January 2016 - 01:19 PM

I bought a new laptop about a month ago and have had many problems with it.  I get Windows "blue screen of death" errors just about every day.  I've installed BlueScreenView to look at the crash dumps and it looks like it’s always either DRIVER_IRQL_NOT_LESS_OR_EQUAL or BAD_POOL_HEADER.  Both are triggered by iaStorA.sy which is the driver for Intel Rapid Storage Technology.  I've tried updating this driver but that didn't fix the issue.  I've contacted Dell already and they're trying to help troubleshoot but this forum appears in tons of Google posts so I thought I'd try my luck here as well.

 

Perfmon and SysnativeFileCollectionApp zips are attached.

 

Relevant laptop specs...

Dell Mobile Precision7510 XCTO BASE

Intel® Core™ i7-6820HQ (Quad Core 2.70GHz, 3.60GHz Turbo, 8MB 45W, w/Intel HD Graphics 530)

64GB, DDR4-2133MHz SDRAM, 4 DIMMS, Non-ECC

Nvidia® Quadro® M2000M w/4GB GDDR5

512GB M.2 PCIe NVMe High Performance Solid State Drive

Windows 10 Pro 64-Bit (OEM installed)

Age of system / OS install: Approximately 30 days

 

Any help at all would be very much appreciated.

Thanks

Attached Files



BC AdBot (Login to Remove)

 


#2 jburd1800

jburd1800

  • Members
  • 565 posts
  • OFFLINE
  •  
  • Local time:11:16 AM

Posted 22 January 2016 - 01:27 PM

I know nothing about BSOD, but I wouldn't bother messing with it but just send it back


“May the sun bring you new energy by day, may the moon softly restore you by night, may the rain wash away your worries, may the breeze blow new strength into your being, may you walk gently thorugh the world and know it's beauty all the days of your life.”


#3 JayBuys

JayBuys
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  

Posted 22 January 2016 - 01:31 PM

I know nothing about BSOD, but I wouldn't bother messing with it but just send it back

 

Sending it back, getting a new one, and then re-installing / configuring everything on it will result in many days of lost productivity which, as a small business owner, is very difficult.  It may definitely come to that but I at least wanted to exhaust all possible options first to see if I could find a fix.



#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:16 AM

Posted 23 January 2016 - 07:15 AM

There are ways around sending the system back and preserving your settings (such as making an image of the hard drive).
BUT, this won't help if the problem is in the software - only if it's a hardware problem.

 

So, let's have a look at the reports that you've submitted and we'll see what's going on there............

 

Only 4 Windows Update hotfixes installed.  Most build 10586 (TH2/1511) systems have more than this.  Please visit Windows Update and get ALL available Windows Updates.

Interesting to note - on a month old laptop you have 360 gB of files on the hard drive.  Newer systems usually have less than 100 gB (and quite often less than 30 or 40)

Have you checked your disk space with a program such as WinDirStat (free from here:  https://windirstat.info/download.html )?

 

The WER section of the MSINFO32 report tends to blame the stdcfltn.sys driver

There are also things that blame the iaStorA.sys driver and some STOP 0x117 errors that blame your Intel graphics

You've already taken the necessary steps to fix the iaStorA.sys driver - and the STOP 0x117 error never shows a BSOD (if it does, it's a STOP 0x116 error).

FYI - STOP 0x117 errors are the one's that popup in the System Tray (Notification Area) and say that the display driver stopped responding and was recovered.  The STOP 0x116 error is when the display driver stops responding and doesn't recover.

 

As such, we're left with troubleshooting the stdcfltn.sys driver.

This driver is related to the ST Microelectronics Accelerometer (which helps to protect your hard drive from bumps/impacts).

I'd suggest uninstalling this program temporarily (from Control Panel...Programs and Features) and see if that helps

Once we're finished troubleshooting, please reinstall the latest version available from the Dell support site.

 

I notice that you've been using Driver Verifier.  Please turn it off as it's done it's job for now.

To do this, open up verifier.exe and select "Delete existing settings", then click on "Finish" and reboot for the changes to take effect.

 

My suspicion here is that the stdcfltn.sys driver is infringing on the memory space used by the iaStorA.sys driver.

If this is the case, then it makes sense that the BSOD's tend to blame iaStorA.sys rather than stdcfltn.sys

The test is to remove the stdcfltn.sys driver (by uninstalling it's program - NOT by deleting it) and see if that stops the BSOD's or changes the character/appearance of the errors.

Another concern is a hardware problem (as at least one of the memory dumps blames hardware) - but I think that is unlikely at this point.  The errors are too regular and focused - whereas hardware errors are usually confusing and random.

 

Finally, another hunch is that there's issues with the PC Doctor service (and it's an older driver from 2011, so it may be an incompatibilty - which could spit out a hardware problem.)

The PC Doctor service is a part of the Dell Support Center - so you may have to uninstall that if the other things don't stop the BSOD's

This hunch is because many of the memory dumps were created when the system crashed while in the pcdrsysinfosto process.  This isn't usually significant, but when it occurs repeatedly (as it does in your case) you have to wonder about it.

 

Just FYI - when a BSOD shows hardware problems, there's actually several different possibilities:

- hardware issues

- compatibility issues

- low-level driver issues

 

So, in short:

- get ALL available Windows Updates

- uninstall Accelerometer and test

- if BSOD's continue, uninstall PC Doctor and Dell Support Center and test

- if BSOD's continue, run hardware diagnostics (both the Dell one's and these:  http://www.carrona.org/hwdiag.html )

The duplicate tests will help to assure us that hardware is/is not involved.

 

 

Analysis:
The following is for informational purposes only.

**************************Fri Jan 22 12:18:10.356 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\012216-12218-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.63.amd64fre.th2_release.160104-1513
System Uptime: 0 days 0:12:31.356
*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
Probably caused by : iaStorA.sys ( iaStorA+c90a7 )
BugCheck D1, {ffffd00025af1000, 2, 1, fffff800675790a7}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments:
Arg1: ffffd00025af1000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff800675790a7, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  pcdrsysinfosto
FAILURE_BUCKET_ID:  AV_VRFK_iaStorA!Unknown_Function
CPUID:        "Intel® Core™ i7-6820HQ CPU @ 2.70GHz"
MaxSpeed:     2700
CurrentSpeed: 2712
  BIOS Version                  1.2.0
  BIOS Release Date             11/16/2015
  Manufacturer                  Dell Inc.
  Product Name                  Precision 7510
  Baseboard Product             0RJHDG
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jan 22 00:49:00.358 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\012116-12718-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.63.amd64fre.th2_release.160104-1513
System Uptime: 0 days 0:02:06.356
*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
Probably caused by : hardware ( iaStorA+c945f )
BugCheck D1, {ffffd00027d81000, 2, 1, fffff80013b0945f}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments:
Arg1: ffffd00027d81000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff80013b0945f, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
FAILURE_BUCKET_ID:  IP_MISALIGNED_iaStorA.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jan 22 00:40:45.851 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\012116-13031-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.63.amd64fre.th2_release.160104-1513
System Uptime: 0 days 0:03:19.849
*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
Probably caused by : iaStorA.sys ( iaStorA+c945f )
BugCheck D1, {ffffd0002b01e000, 2, 1, fffff8003f91945f}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments:
Arg1: ffffd0002b01e000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8003f91945f, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  pcdrsysinfosto
FAILURE_BUCKET_ID:  AV_VRFK_iaStorA!Unknown_Function
CPUID:        "Intel® Core™ i7-6820HQ CPU @ 2.70GHz"
MaxSpeed:     2700
CurrentSpeed: 2712
  BIOS Version                  1.2.0
  BIOS Release Date             11/16/2015
  Manufacturer                  Dell Inc.
  Product Name                  Precision 7510
  Baseboard Product             0RJHDG
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jan 22 00:32:11.389 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\012116-12859-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.63.amd64fre.th2_release.160104-1513
System Uptime: 0 days 0:03:47.387
*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
Probably caused by : iaStorA.sys ( iaStorA+c945f )
BugCheck D1, {ffffd001c3a71000, 2, 1, fffff8015e91945f}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments:
Arg1: ffffd001c3a71000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8015e91945f, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  pcdrsysinfosto
FAILURE_BUCKET_ID:  AV_VRFK_iaStorA!Unknown_Function
CPUID:        "Intel® Core™ i7-6820HQ CPU @ 2.70GHz"
MaxSpeed:     2700
CurrentSpeed: 2712
  BIOS Version                  1.2.0
  BIOS Release Date             11/16/2015
  Manufacturer                  Dell Inc.
  Product Name                  Precision 7510
  Baseboard Product             0RJHDG
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 21 19:39:07.007 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\012116-12390-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.63.amd64fre.th2_release.160104-1513
System Uptime: 0 days 19:27:12.840
*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
Probably caused by : iaStorA.sys ( iaStorA+c945f )
BugCheck D1, {ffffd000230a0000, 2, 1, fffff8019ca7945f}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments:
Arg1: ffffd000230a0000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8019ca7945f, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  pcdrsysinfosto
FAILURE_BUCKET_ID:  AV_VRFK_iaStorA!Unknown_Function
CPUID:        "Intel® Core™ i7-6820HQ CPU @ 2.70GHz"
MaxSpeed:     2700
CurrentSpeed: 2712
  BIOS Version                  1.2.0
  BIOS Release Date             11/16/2015
  Manufacturer                  Dell Inc.
  Product Name                  Precision 7510
  Baseboard Product             0RJHDG
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jan 20 20:36:35.362 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\012016-23593-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.63.amd64fre.th2_release.160104-1513
System Uptime: 1 days 9:57:13.214
*** WARNING: Unable to verify timestamp for stdcfltn.sys
*** ERROR: Module load completed but symbols could not be loaded for stdcfltn.sys
Probably caused by : stdcfltn.sys ( stdcfltn+1d18 )
BugCheck 19, {20, ffffe0012346c280, ffffe0012346c340, c0c0011}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: ffffe0012346c280, The pool entry we were looking for within the page.
Arg3: ffffe0012346c340, The next pool entry.
Arg4: 000000000c0c0011, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  pcdrsysinfosto
FAILURE_BUCKET_ID:  0x19_20_stdcfltn!Unknown_Function
CPUID:        "Intel® Core™ i7-6820HQ CPU @ 2.70GHz"
MaxSpeed:     2700
CurrentSpeed: 2712
  BIOS Version                  1.2.0
  BIOS Release Date             11/16/2015
  Manufacturer                  Dell Inc.
  Product Name                  Precision 7510
  Baseboard Product             0RJHDG
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 14 19:18:33.666 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\011416-22734-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.63.amd64fre.th2_release.160104-1513
System Uptime: 1 days 4:19:30.520
*** WARNING: Unable to verify timestamp for stdcfltn.sys
*** ERROR: Module load completed but symbols could not be loaded for stdcfltn.sys
Probably caused by : stdcfltn.sys ( stdcfltn+1d18 )
BugCheck 19, {20, ffffe00086d93d40, ffffe00086d93e00, c0c0001}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: ffffe00086d93d40, The pool entry we were looking for within the page.
Arg3: ffffe00086d93e00, The next pool entry.
Arg4: 000000000c0c0001, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  pcdrsysinfosto
FAILURE_BUCKET_ID:  0x19_20_stdcfltn!Unknown_Function
CPUID:        "Intel® Core™ i7-6820HQ CPU @ 2.70GHz"
MaxSpeed:     2700
CurrentSpeed: 2712
  BIOS Version                  1.2.0
  BIOS Release Date             11/16/2015
  Manufacturer                  Dell Inc.
  Product Name                  Precision 7510
  Baseboard Product             0RJHDG
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jan 12 10:59:26.645 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\011216-24187-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.17.amd64fre.th2_release.151121-2308
System Uptime: 4 days 0:29:36.563
*** WARNING: Unable to verify timestamp for stdcfltn.sys
*** ERROR: Module load completed but symbols could not be loaded for stdcfltn.sys
Probably caused by : stdcfltn.sys ( stdcfltn+1d18 )
BugCheck 19, {20, ffffe000e2b58000, ffffe000e2b580c0, c0c0000}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: ffffe000e2b58000, The pool entry we were looking for within the page.
Arg3: ffffe000e2b580c0, The next pool entry.
Arg4: 000000000c0c0000, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  pcdrsysinfosto
FAILURE_BUCKET_ID:  0x19_20_stdcfltn!Unknown_Function
CPUID:        "Intel® Core™ i7-6820HQ CPU @ 2.70GHz"
MaxSpeed:     2700
CurrentSpeed: 2712
  BIOS Version                  1.2.0
  BIOS Release Date             11/16/2015
  Manufacturer                  Dell Inc.
  Product Name                  Precision 7510
  Baseboard Product             0RJHDG
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan  7 20:23:35.261 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\010716-22328-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.17.amd64fre.th2_release.151121-2308
System Uptime: 0 days 22:04:13.120
*** WARNING: Unable to verify timestamp for stdcfltn.sys
*** ERROR: Module load completed but symbols could not be loaded for stdcfltn.sys
Probably caused by : stdcfltn.sys ( stdcfltn+1d18 )
BugCheck 19, {20, ffffe000996fb000, ffffe000996fb0c0, c0c0000}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: ffffe000996fb000, The pool entry we were looking for within the page.
Arg3: ffffe000996fb0c0, The next pool entry.
Arg4: 000000000c0c0000, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  pcdrsysinfosto
FAILURE_BUCKET_ID:  0x19_20_stdcfltn!Unknown_Function
CPUID:        "Intel® Core™ i7-6820HQ CPU @ 2.70GHz"
MaxSpeed:     2700
CurrentSpeed: 2712
  BIOS Version                  1.2.0
  BIOS Release Date             11/16/2015
  Manufacturer                  Dell Inc.
  Product Name                  Precision 7510
  Baseboard Product             0RJHDG
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jan  6 22:17:03.794 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\010616-22578-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.17.amd64fre.th2_release.151121-2308
System Uptime: 2 days 9:19:10.654
*** WARNING: Unable to verify timestamp for stdcfltn.sys
*** ERROR: Module load completed but symbols could not be loaded for stdcfltn.sys
Probably caused by : stdcfltn.sys ( stdcfltn+1d18 )
BugCheck 19, {20, ffffe0015f1ff1c0, ffffe0015f1ff280, c0c0005}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: ffffe0015f1ff1c0, The pool entry we were looking for within the page.
Arg3: ffffe0015f1ff280, The next pool entry.
Arg4: 000000000c0c0005, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  pcdrsysinfosto
FAILURE_BUCKET_ID:  0x19_20_stdcfltn!Unknown_Function
CPUID:        "Intel® Core™ i7-6820HQ CPU @ 2.70GHz"
MaxSpeed:     2700
CurrentSpeed: 2712
  BIOS Version                  1.2.0
  BIOS Release Date             11/16/2015
  Manufacturer                  Dell Inc.
  Product Name                  Precision 7510
  Baseboard Product             0RJHDG
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan  4 12:56:41.094 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\010416-24015-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.17.amd64fre.th2_release.151121-2308
System Uptime: 0 days 15:34:27.952
*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
Probably caused by : iaStorA.sys ( iaStorA+c90cc )
BugCheck D1, {ffffd00025462000, 2, 1, fffff800602190cc}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments:
Arg1: ffffd00025462000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff800602190cc, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  pcdrsysinfosto
FAILURE_BUCKET_ID:  AV_iaStorA!Unknown_Function
CPUID:        "Intel® Core™ i7-6820HQ CPU @ 2.70GHz"
MaxSpeed:     2700
CurrentSpeed: 2712
  BIOS Version                  1.2.0
  BIOS Release Date             11/16/2015
  Manufacturer                  Dell Inc.
  Product Name                  Precision 7510
  Baseboard Product             0RJHDG
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jan  3 20:52:15.226 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\010316-9984-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.17.amd64fre.th2_release.151121-2308
System Uptime: 1 days 8:07:13.088
Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+134 )
BugCheck 19, {20, ffffe00097c43380, ffffe00097c43440, c0c0001}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: ffffe00097c43380, The pool entry we were looking for within the page.
Arg3: ffffe00097c43440, The next pool entry.
Arg4: 000000000c0c0001, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  pcdrsysinfosto
FAILURE_BUCKET_ID:  0x19_20_nt!KiDeliverApc
CPUID:        "Intel® Core™ i7-6820HQ CPU @ 2.70GHz"
MaxSpeed:     2700
CurrentSpeed: 2712
  BIOS Version                  1.2.0
  BIOS Release Date             11/16/2015
  Manufacturer                  Dell Inc.
  Product Name                  Precision 7510
  Baseboard Product             0RJHDG
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jan  2 12:43:38.784 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\010216-10468-01.dmp]
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Built by: 10586.17.amd64fre.th2_release.151121-2308
System Uptime: 0 days 15:04:18.728
*** WARNING: Unable to verify timestamp for stdcfltn.sys
*** ERROR: Module load completed but symbols could not be loaded for stdcfltn.sys
Probably caused by : stdcfltn.sys ( stdcfltn+1d18 )
BugCheck 19, {20, ffffe0014b89acc0, ffffe0014b89ad80, c0c0001}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: ffffe0014b89acc0, The pool entry we were looking for within the page.
Arg3: ffffe0014b89ad80, The next pool entry.
Arg4: 000000000c0c0001, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  pcdrsysinfosto
FAILURE_BUCKET_ID:  0x19_20_stdcfltn!Unknown_Function
CPUID:        "Intel® Core™ i7-6820HQ CPU @ 2.70GHz"
MaxSpeed:     2700
CurrentSpeed: 2712
  BIOS Version                  1.2.0
  BIOS Release Date             11/16/2015
  Manufacturer                  Dell Inc.
  Product Name                  Precision 7510
  Baseboard Product             0RJHDG
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``



3rd Party Drivers:
The following is for information purposes only.

**************************Fri Jan 22 12:18:10.356 2016 (UTC - 5:00)**************************
pcdsrvc_x64.pkms            Mon May  9 20:20:44 2011 (4DC884DC)
DellRbtn.sys                Fri Aug  3 17:32:54 2012 (501C4386)
CLVirtualDrive.sys          Mon Nov 11 22:31:36 2013 (5281A118)
DDDriver64Dcsa.sys          Wed May 28 15:58:54 2014 (53863FFE)
VMNET.SYS                   Sun Jul 27 09:30:27 2014 (53D4FEF3)
vmnetadapter.sys            Sun Jul 27 09:30:30 2014 (53D4FEF6)
vmnetbridge.sys             Sun Jul 27 09:30:32 2014 (53D4FEF8)
vmci.sys                    Thu Sep  4 22:11:32 2014 (54091BD4)
vsock.sys                   Thu Sep  4 22:12:05 2014 (54091BF5)
stdcfltn.sys                Thu Jan  8 21:01:11 2015 (54AF3667)
ST_Accel.sys                Wed Feb 25 02:09:05 2015 (54ED7511)
usb3Hub.sys                 Mon Mar 16 05:15:44 2015 (55069F40)
DellProf.sys                Wed May 13 10:17:19 2015 (55535CEF)
POADrvr.sys                 Thu May 21 10:41:03 2015 (555DEE7F)
Apfiltr.sys                 Fri Jun  5 03:21:37 2015 (55714E01)
e1d65x64.sys                Thu Jun 18 12:37:56 2015 (5582F3E4)
DellRctl.sys                Wed Jun 24 04:23:09 2015 (558A68ED)
RtsPer.sys                  Tue Aug  4 04:53:27 2015 (55C07D87)
cvusbdrv.sys                Wed Aug  5 17:15:02 2015 (55C27CD6)
Netwtw02.sys                Sun Aug  9 07:34:30 2015 (55C73AC6)
RTDVHD64.sys                Tue Aug 11 08:33:05 2015 (55C9EB81)
iaStorA.sys                 Tue Aug 18 08:18:59 2015 (55D322B3)
TeeDriverW8x64.sys          Mon Aug 31 15:49:07 2015 (55E4AFB3)
IntcDAud.sys                Fri Sep  4 09:55:37 2015 (55E9A2D9)
igdkmd64.sys                Tue Sep 15 14:01:37 2015 (55F85D01)
dptf_acpi.sys               Fri Oct 23 15:24:17 2015 (562A8961)
dptf_cpu.sys                Fri Oct 23 15:24:21 2015 (562A8965)
esif_lf.sys                 Fri Oct 23 15:24:35 2015 (562A8973)
intelppm.sys                Thu Oct 29 22:09:51 2015 (5632D16F)
nvlddmkm.sys                Thu Nov  5 06:06:48 2015 (563B3848)
hcmon.sys                   Fri Nov  6 14:57:33 2015 (563D062D)
vmnetuserif.sys             Wed Nov 25 20:52:45 2015 (565665ED)
vmx86.sys                   Wed Nov 25 21:05:01 2015 (565668CD)
VMkbd.sys                   Wed Nov 25 21:05:02 2015 (565668CE)
VMparport.sys               Wed Nov 25 21:05:08 2015 (565668D4)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jan 22 00:40:45.851 2016 (UTC - 5:00)**************************
dptf_acpi.sys               Thu Jul 23 14:24:12 2015 (55B1314C)
dptf_cpu.sys                Thu Jul 23 14:24:14 2015 (55B1314E)
esif_lf.sys                 Thu Jul 23 14:24:27 2015 (55B1315B)
iaStorA.sys                 Wed Nov  4 05:27:49 2015 (5639DDA5)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 21 19:39:07.007 2016 (UTC - 5:00)**************************
netr28ux.sys                Thu Jun  5 22:14:29 2014 (53912405)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jan 12 10:59:26.645 2016 (UTC - 5:00)**************************
cpuz138_x64.sys             Thu Feb 26 02:04:34 2015 (54EEC582)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jan  2 12:43:38.784 2016 (UTC - 5:00)**************************
iqvw64e.sys                 Tue Oct 23 04:48:15 2012 (508659CF)
http://www.carrona.org/drivers/driver.php?id=pcdsrvc_x64.pkms
http://www.carrona.org/drivers/driver.php?id=DellRbtn.sys
http://www.carrona.org/drivers/driver.php?id=CLVirtualDrive.sys
http://www.carrona.org/drivers/driver.php?id=DDDriver64Dcsa.sys
http://www.carrona.org/drivers/driver.php?id=VMNET.SYS
http://www.carrona.org/drivers/driver.php?id=vmnetadapter.sys
http://www.carrona.org/drivers/driver.php?id=vmnetbridge.sys
http://www.carrona.org/drivers/driver.php?id=vmci.sys
http://www.carrona.org/drivers/driver.php?id=vsock.sys
http://www.carrona.org/drivers/driver.php?id=stdcfltn.sys
http://www.carrona.org/drivers/driver.php?id=ST_Accel.sys
http://www.carrona.org/drivers/driver.php?id=usb3Hub.sys
http://www.carrona.org/drivers/driver.php?id=DellProf.sys
POADrvr.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=Apfiltr.sys
e1d65x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
DellRctl.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=RtsPer.sys
http://www.carrona.org/drivers/driver.php?id=cvusbdrv.sys
Netwtw02.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=RTDVHD64.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=dptf_acpi.sys
http://www.carrona.org/drivers/driver.php?id=dptf_cpu.sys
http://www.carrona.org/drivers/driver.php?id=esif_lf.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=hcmon.sys
http://www.carrona.org/drivers/driver.php?id=vmnetuserif.sys
http://www.carrona.org/drivers/driver.php?id=vmx86.sys
http://www.carrona.org/drivers/driver.php?id=VMkbd.sys
http://www.carrona.org/drivers/driver.php?id=VMparport.sys
http://www.carrona.org/drivers/driver.php?id=dptf_acpi.sys
http://www.carrona.org/drivers/driver.php?id=dptf_cpu.sys
http://www.carrona.org/drivers/driver.php?id=esif_lf.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=netr28ux.sys
http://www.carrona.org/drivers/driver.php?id=cpuz138_x64.sys
http://www.carrona.org/drivers/driver.php?id=iqvw64e.sys
 


Edited by usasma, 23 January 2016 - 07:16 AM.

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#5 JayBuys

JayBuys
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  

Posted 24 January 2016 - 01:07 PM

Thank you so much for the incredibly detailed response.

 

All Windows updates are installed and the hard drive is using a lot of space because I installed Dropbox and synced a ton of large Photoshop files.

I uninstalled the accelerometer program but that still didn't help.

 

One interesting thing I noticed is that if I remote and run the Dell hardware diagnostics, it gives me a message saying that there's no hard drive installed (other tests for RAM, video, etc. don't return anything out of the ordinary).  I also tried booting into Seagate's SeaTools and got a similar message.  I installed Samsung's Magician software but all that let's me do is run a very basic performance test.



#6 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:16 AM

Posted 25 January 2016 - 06:12 AM

This system should have a hardware warranty on it.  I would contact Dell and ask them what they want you to do.

If the Dell diags don't see the hard drive - then there's a problem (I have seen the problem with Seatools, but that has to do with it's support of AHCI)

This could be due to the SSD (there aren't any real diagnostics that I've found for SSD's) - but it still needs looking into.

 

As it's still giving you issues, I presume that you're still getting BSOD's?

If that's so, then please zip up the contents of the C:\Windows\Minidump directory and upload it with your next post.
If unable to zip it up there, copy it to your Desktop and zip it up there.

 

Now that you've eliminated the Accelerometer, the BSOD will have to find something else to blame.

And we'll track that one down also.  We'll keep this up until we find the final problem and fix it.


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#7 JayBuys

JayBuys
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  

Posted 26 January 2016 - 03:01 PM

Just closing the loop on this to say thank you.  I spoke with Dell and gave them some of the details in this thread.  They were very nice and after a few questions and some brief troubleshooting they concluded that it may be an issue with the hard drive itself.  They FedEx'ed me a new hard drive and I've spent the last 36 hours re-installing everything.  So far so good.  Haven't had a blue screen yet and have run several diagnostics that show the machine running okay.  Hopefully the issue is resolved for good now.

 

I sincerely appreciate the quick and robust responses.  They were super helpful in getting to a diagnosis so that I didn't have to spend 12 hours having Dell support ask me if tried restarting the system.



#8 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:16 AM

Posted 26 January 2016 - 06:00 PM

I'm glad that Dell was able to help you out and get things fixed for you.
Thanks for letting us know!


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#9 speedracergreg

speedracergreg

  • Members
  • 3 posts
  • OFFLINE
  •  

Posted 01 February 2016 - 11:00 AM

Just closing the loop on this to say thank you.  I spoke with Dell and gave them some of the details in this thread.  They were very nice and after a few questions and some brief troubleshooting they concluded that it may be an issue with the hard drive itself.  They FedEx'ed me a new hard drive and I've spent the last 36 hours re-installing everything.  So far so good.  Haven't had a blue screen yet and have run several diagnostics that show the machine running okay.  Hopefully the issue is resolved for good now.

 

I sincerely appreciate the quick and robust responses.  They were super helpful in getting to a diagnosis so that I didn't have to spend 12 hours having Dell support ask me if tried restarting the system.

 

@JayBuys - accepting that there's not much time passed since you had the new drive, how are you getting on with the new drive? I have a near-identical machine and have suffered the same recurrent BSOD (and some "hard" reboots without kernel panic) despite doing all sorts to update drivers etc.That my model is the same as yours and the symptoms identical, I'm wondering if the replacement drive is enough to deal with the issue. What size was your old drive? Mine is a 2TB - wonder if it's a bad batch given you must have received your machine about the same time as me too...



#10 JayBuys

JayBuys
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  

Posted 01 February 2016 - 11:47 AM

I have a 512GB SSD drive in mine.  The replacement drive arrived last Monday and I spent the day re-installing / configuring all my software on it so I've been using it full force for about a week no.  No issues at all.  Everything has been great since the new drive.  



#11 dtbartholomew

dtbartholomew

  • Members
  • 1 posts
  • OFFLINE
  •  

Posted 18 February 2016 - 10:12 PM

I have the same problem with nearly the same configuration. Random BSOD's about once a day. Dell was very helpful and updated a couple of drivers, repaired some corrupted system files. Crashed again the next day. The reason that the diagnostics don't see the SSD is that it is PCIe drive (according to Dell). I'm not a hardware geek at all, so I rely on my IT guys and Dell. This is my 7th Dell in 20+ years and I've never had these kinds of problems. Guess I'll be on with Dell techs tomorrow again.



#12 JanOuwehand

JanOuwehand

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Amsterdam
  • Local time:05:16 PM

Posted 17 March 2016 - 10:36 AM

I got my new laptop last week. Almost got same configuration: Dell 7510, 2x16Gb, Xeon 1335, NVMe SM951 Samsung 512Gb SSD. I get blue screens once or twice a day, consistently. 
 
Yesterday I updated my BIOS version from 1.3.10 to 1.3.12 (25-2-2016). After the BIOS update the BIOS diagnostic tool is able to read out the SMART table of the SSD. Version 1.3.10 didn't detect any hard drive. 
 
I analyzed the memory.dmp of before the BIOS-update and after the BIOS-update. It didn't solve the blue screen problem, unfortunatelly. Before it was telling that file stdcfltn.sys was probably the cause, after the update it is iaStorA.sys. I wonder what the chances are that my SSD is defected too, referring to JayBuys post. I hope that there will be a solution. The laptop wasn't cheap. Especially in Europe.
 
Any helpful comment will be appreciated.
 
 
-- The memory.dmp analysis after blue screen, before BIOS-update (version: 1.3.10)
 
 
Microsoft ® Windows Debugger Version 10.0.10586.567 AMD64
Copyright © Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Temp\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
 
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.162.amd64fre.th2_release_sec.160223-1728
Machine Name:
Kernel base = 0xfffff802`a381b000 PsLoadedModuleList = 0xfffff802`a3af9cd0
Debug session time: Mon Mar 14 16:11:59.078 2016 (UTC + 1:00)
System Uptime: 0 days 4:07:40.797
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000033`1eb17018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 19, {20, ffffe0008e2f5340, ffffe0008e2f5400, c0c0002}
 
*** ERROR: Module load completed but symbols could not be loaded for stdcfltn.sys
*** ERROR: Module load completed but symbols could not be loaded for SEDFilter.sys
Page 19315 not present in the dump file. Type ".hh dbgerr004" for details
Page 480 not present in the dump file. Type ".hh dbgerr004" for details
Page 480 not present in the dump file. Type ".hh dbgerr004" for details
Page 480 not present in the dump file. Type ".hh dbgerr004" for details
Page 480 not present in the dump file. Type ".hh dbgerr004" for details
Page 480 not present in the dump file. Type ".hh dbgerr004" for details
Page 480 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : stdcfltn.sys ( stdcfltn+1d18 )
 
Followup:     MachineOwner
---------
 
1: 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: 0000000000000020, a pool block header size is corrupt.
Arg2: ffffe0008e2f5340, The pool entry we were looking for within the page.
Arg3: ffffe0008e2f5400, The next pool entry.
Arg4: 000000000c0c0002, (reserved)
 
Debugging Details:
------------------
 
Page 19315 not present in the dump file. Type ".hh dbgerr004" for details
Page 480 not present in the dump file. Type ".hh dbgerr004" for details
Page 480 not present in the dump file. Type ".hh dbgerr004" for details
Page 480 not present in the dump file. Type ".hh dbgerr004" for details
Page 480 not present in the dump file. Type ".hh dbgerr004" for details
Page 480 not present in the dump file. Type ".hh dbgerr004" for details
Page 480 not present in the dump file. Type ".hh dbgerr004" for details
 
DUMP_CLASS: 1
 
DUMP_QUALIFIER: 401
 
BUILD_VERSION_STRING:  10586.162.amd64fre.th2_release_sec.160223-1728
 
SYSTEM_MANUFACTURER:  Dell Inc.
 
SYSTEM_PRODUCT_NAME:  Precision 7510
 
SYSTEM_SKU:  06D9
 
BIOS_VENDOR:  Dell Inc.
 
BIOS_VERSION:  1.3.10
 
BIOS_DATE:  01/24/2016
 
BASEBOARD_MANUFACTURER:  Dell Inc.
 
BASEBOARD_PRODUCT:  0692Y5
 
BASEBOARD_VERSION:  A00
 
DUMP_TYPE:  1
 
BUGCHECK_P1: 20
 
BUGCHECK_P2: ffffe0008e2f5340
 
BUGCHECK_P3: ffffe0008e2f5400
 
BUGCHECK_P4: c0c0002
 
BUGCHECK_STR:  0x19_20
 
POOL_ADDRESS:  ffffe0008e2f5340 Nonpaged pool
 
CPU_COUNT: 8
 
CPU_MHZ: b58
 
CPU_VENDOR:  GenuineIntel
 
CPU_FAMILY: 6
 
CPU_MODEL: 5e
 
CPU_STEPPING: 3
 
CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: 74'00000000 (cache) 74'00000000 (init)
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
PROCESS_NAME:  pcdrrealtime.p
 
CURRENT_IRQL:  1
 
ANALYSIS_SESSION_HOST:  DELL
 
ANALYSIS_SESSION_TIME:  03-17-2016 16:35:24.0718
 
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
 
IRP_ADDRESS: ffffe00077bf2138
 
LAST_CONTROL_TRANSFER:  from fffff802a3a4cde5 to fffff802a395d760
 
STACK_TEXT:  
ffffd000`2bc99898 fffff802`a3a4cde5 : 00000000`00000019 00000000`00000020 ffffe000`8e2f5340 ffffe000`8e2f5400 : nt!KeBugCheckEx
ffffd000`2bc998a0 fffff802`a38964d9 : ffffe000`8d049b00 ffffd001`0e67e5d8 ffffe000`7544af00 00000000`20206f49 : nt!ExFreePool+0x2c5
ffffd000`2bc99980 fffff802`a3894c64 : ffffe000`77bf21b0 ffffe000`77bf2388 00000000`00000000 fffff801`7ac42e58 : nt!IopCompleteRequest+0x79
ffffd000`2bc99a70 fffff802`a3960953 : 00000000`00000001 ffffe000`77a0c950 00000000`00000000 fffff801`7ac45302 : nt!KiDeliverApc+0x134
ffffd000`2bc99b00 fffff802`a38544d7 : fffff801`7ac43ba1 ffffd001`0e67e010 ffffd000`2bc99d19 ffffe000`77bf21b0 : nt!KiApcInterrupt+0xc3
ffffd000`2bc99c98 fffff801`7ac43ba1 : ffffd001`0e67e010 ffffd000`2bc99d19 ffffe000`77bf21b0 fffff6fb`7dbede00 : nt!KzLowerIrql+0x7
ffffd000`2bc99ca0 fffff801`7ac4346f : ffffd001`0e980000 ffffe000`8ccbd800 00000000`00000001 ffffe000`8d049b03 : storport!RaidStartIoPacket+0x3e1
ffffd000`2bc99d80 fffff801`7ac4303a : ffffe000`8d049b00 ffffe000`8e2f53e0 ffffe000`77bf2060 ffffd001`00000096 : storport!RaUnitScsiIrp+0x3ef
ffffd000`2bc99e20 fffff801`7ac99391 : 00000000`00000103 ffffe000`8d049b00 ffffe000`8ccbd780 ffffd001`00000096 : storport!RaDriverScsiIrp+0x5a
ffffd000`2bc99e60 fffff801`7ac98cc2 : ffffd000`2bc9a0f0 fffff801`7ac7cb0f 00000000`00000000 ffffe000`768ef480 : storport!PortPassThroughSendAsync+0x1b9
ffffd000`2bc99f10 fffff801`7ac96e0a : ffffe000`768ef480 00000000`00000000 00000000`0004d000 ffffe000`77a881a0 : storport!PortPassThroughExSendAsync+0x72
ffffd000`2bc99f80 fffff801`7ac58b7c : ffffe000`768ef480 00000000`0004d004 ffffe000`77a881a0 ffffd000`2b000007 : storport!RaidAdapterPassThrough+0xa2
ffffd000`2bc99fd0 fffff801`7ac444c5 : 00000000`00000000 00000000`00000000 ffffe000`768ef480 fffff801`7ac88000 : storport!RaidAdapterDeviceControlIrp+0x142e4
ffffd000`2bc9a050 fffff801`7ac97e76 : ffffe000`768ef480 00000000`0004d004 ffffe000`77a881a0 ffffe000`77bf21b0 : storport!RaDriverDeviceControlIrp+0x95
ffffd000`2bc9a090 fffff801`7ac588d1 : ffffd000`2bc9a160 fffff801`00000000 ffffe000`768ef480 ffffe000`77bf21b0 : storport!RaUnitScsiPassThroughIoctl+0xfa
ffffd000`2bc9a100 fffff801`7ac4448a : ffffe000`85004b40 00000000`00000070 ffffe000`768ef5e0 fffff801`7ac88000 : storport!RaUnitDeviceControlIrp+0x14401
ffffd000`2bc9a180 fffff801`7a181d18 : ffffe000`768ef5e0 ffffe000`768ef480 ffffe000`7797cc60 ffffd000`2bc9a268 : storport!RaDriverDeviceControlIrp+0x5a
ffffd000`2bc9a1c0 fffff801`792b4cf0 : ffffe000`85004b40 ffffd000`2bc9a268 00000000`00000000 00000000`00000000 : stdcfltn+0x1d18
ffffd000`2bc9a200 fffff801`7a1949f9 : ffffe000`7795bf90 ffffe000`85004b40 ffffe000`77978e70 ffffe000`77976c20 : Wdf01000!imp_WdfRequestSend+0x220 [d:\th\minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 2001]
ffffd000`2bc9a280 fffff801`792bad78 : ffffe000`85004b40 fffff802`a3bfaa97 ffffe000`7795bdf0 ffffe000`779d2b10 : SEDFilter+0x49f9
ffffd000`2bc9a2c0 fffff801`792baa14 : 00000000`00000200 fffff802`a38a1a49 ffffc001`a079c660 00000000`00000000 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x168 [d:\th\minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 3306]
ffffd000`2bc9a360 fffff801`792b7b2a : ffffe000`77976c20 fffff801`79965c00 00000000`00000000 ffffe000`779d2b10 : Wdf01000!FxIoQueue::DispatchEvents+0xee4 [d:\th\minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 3100]
ffffd000`2bc9a440 fffff801`792b11b1 : ffffe000`768ef400 ffffe000`768ef400 00000000`00000001 ffffe000`85004b40 : Wdf01000!FxPkgIo::DispatchStep1+0x52a [d:\th\minkernel\wdf\framework\shared\irphandlers\io\fxpkgio.cpp @ 324]
ffffd000`2bc9a500 fffff801`7a413a6d : ffffd000`2bc9a660 ffffe000`768ef480 ffffe000`768ef480 ffffc001`00000000 : Wdf01000!FxDevice::DispatchWithLock+0x111 [d:\th\minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1402]
ffffd000`2bc9a560 fffff801`7a3f16cf : 00000000`00000000 fffff802`a3a4bc33 00000000`0004d004 ffffe000`8ccb0358 : CLASSPNP!ClassDeviceControl+0x52d
ffffd000`2bc9a6d0 fffff801`7a418a73 : 00000000`00000000 00000000`c0000910 ffffe000`77aa71b0 ffffe000`77974c60 : disk!DiskDeviceControl+0x8f
ffffd000`2bc9a760 fffff801`79694925 : ffffe000`768ef480 ffffe000`77974c60 00000000`00000001 ffffe000`8ccb0080 : CLASSPNP!ClassDeviceControlDispatch+0x53
ffffd000`2bc9a790 fffff801`79682935 : ffffe000`768ef400 00000000`00000000 00000000`00000000 ffffe000`768ef480 : partmgr!PmIoctlRedirect+0x4d
ffffd000`2bc9a800 fffff802`a3c25ac2 : ffffe000`8e9ab590 ffffd000`2bc9ab80 ffffe000`8e9ab590 00000000`00000001 : partmgr!PmFilterDeviceControl+0x2a5
ffffd000`2bc9a850 fffff802`a3c24956 : e000770b`34900000 00000000`001f0003 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x1162
ffffd000`2bc9aa20 fffff802`a3967fa3 : 00000000`00000102 00000000`00000001 00000000`00000000 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
ffffd000`2bc9aa90 00007fff`589051b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000033`1efff938 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`589051b4
 
 
STACK_COMMAND:  kb
 
THREAD_SHA1_HASH_MOD_FUNC:  d823d69d6348bed2a5735a03be068391781d3bed
 
THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  da09748ff2aa8b77d3c448b3fb1f2e1428c0f469
 
THREAD_SHA1_HASH_MOD:  e2786172fdd9b049cdf0a85dcb1266dd9d6e2835
 
FOLLOWUP_IP: 
stdcfltn+1d18
fffff801`7a181d18 488b5c2440      mov     rbx,qword ptr [rsp+40h]
 
FAULT_INSTR_CODE:  245c8b48
 
SYMBOL_STACK_INDEX:  11
 
SYMBOL_NAME:  stdcfltn+1d18
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: stdcfltn
 
IMAGE_NAME:  stdcfltn.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  54af3667
 
BUCKET_ID_FUNC_OFFSET:  1d18
 
FAILURE_BUCKET_ID:  0x19_20_stdcfltn!Unknown_Function
 
BUCKET_ID:  0x19_20_stdcfltn!Unknown_Function
 
PRIMARY_PROBLEM_CLASS:  0x19_20_stdcfltn!Unknown_Function
 
TARGET_TIME:  2016-03-14T15:11:59.000Z
 
OSBUILD:  10586
 
OSSERVICEPACK:  0
 
SERVICEPACK_NUMBER: 0
 
OS_REVISION: 0
 
SUITE_MASK:  272
 
PRODUCT_TYPE:  1
 
OSPLATFORM_TYPE:  x64
 
OSNAME:  Windows 10
 
OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
 
OS_LOCALE:  
 
USER_LCID:  0
 
OSBUILD_TIMESTAMP:  2016-02-24 06:48:00
 
BUILDDATESTAMP_STR:  160223-1728
 
BUILDLAB_STR:  th2_release_sec
 
BUILDOSVER_STR:  10.0.10586.162.amd64fre.th2_release_sec.160223-1728
 
ANALYSIS_SESSION_ELAPSED_TIME: 459f
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:0x19_20_stdcfltn!unknown_function
 
FAILURE_ID_HASH:  {fa4d2e4b-7af0-32de-e281-c677dbd21785}
 
Followup:     MachineOwner
---------
 
 
 
 
 
-- The memory.dmp analysis after blue screen, after BIOS-update to 1.3.12
 
 
Microsoft ® Windows Debugger Version 10.0.10586.567 AMD64
Copyright © Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
 
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.162.amd64fre.th2_release_sec.160223-1728
Machine Name:
Kernel base = 0xfffff803`8ea09000 PsLoadedModuleList = 0xfffff803`8ece7cd0
Debug session time: Thu Mar 17 16:13:58.910 2016 (UTC + 1:00)
System Uptime: 0 days 6:55:13.715
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000087`abc99018).  Type ".hh dbgerr001" for details
Loading unloaded module list
....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck D1, {ffffd000282e6000, 2, 1, fffff80133a490cc}
 
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for stdcfltn.sys
*** ERROR: Module load completed but symbols could not be loaded for SEDFilter.sys
Page 19444 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : iaStorA.sys ( iaStorA+c90cc )
 
Followup:     MachineOwner
---------
 
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffd000282e6000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff80133a490cc, address which referenced memory
 
Debugging Details:
------------------
 
Page 19444 not present in the dump file. Type ".hh dbgerr004" for details
 
DUMP_CLASS: 1
 
DUMP_QUALIFIER: 401
 
BUILD_VERSION_STRING:  10586.162.amd64fre.th2_release_sec.160223-1728
 
SYSTEM_MANUFACTURER:  Dell Inc.
 
SYSTEM_PRODUCT_NAME:  Precision 7510
 
SYSTEM_SKU:  06D9
 
BIOS_VENDOR:  Dell Inc.
 
BIOS_VERSION:  1.3.12
 
BIOS_DATE:  02/25/2016
 
BASEBOARD_MANUFACTURER:  Dell Inc.
 
BASEBOARD_PRODUCT:  0692Y5
 
BASEBOARD_VERSION:  A00
 
DUMP_TYPE:  1
 
BUGCHECK_P1: ffffd000282e6000
 
BUGCHECK_P2: 2
 
BUGCHECK_P3: 1
 
BUGCHECK_P4: fffff80133a490cc
 
WRITE_ADDRESS:  ffffd000282e6000 
 
CURRENT_IRQL:  2
 
FAULTING_IP: 
iaStorA+c90cc
fffff801`33a490cc 48894120        mov     qword ptr [rcx+20h],rax
 
CPU_COUNT: 8
 
CPU_MHZ: b58
 
CPU_VENDOR:  GenuineIntel
 
CPU_FAMILY: 6
 
CPU_MODEL: 5e
 
CPU_STEPPING: 3
 
CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: 74'00000000 (cache) 74'00000000 (init)
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
BUGCHECK_STR:  AV
 
PROCESS_NAME:  pcdrrealtime.p
 
ANALYSIS_SESSION_HOST:  DELL
 
ANALYSIS_SESSION_TIME:  03-17-2016 16:20:48.0600
 
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
 
TRAP_FRAME:  ffffd00032169710 -- (.trap 0xffffd00032169710)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd000282e5fe0
rdx=ffffe000663cd00d rsi=0000000000000000 rdi=0000000000000000
rip=fffff80133a490cc rsp=ffffd000321698a0 rbp=0000000000000006
 r8=000000000000000d  r9=0000000000000001 r10=0000000000000040
r11=fffff80133a6a117 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
iaStorA+0xc90cc:
fffff801`33a490cc 48894120        mov     qword ptr [rcx+20h],rax ds:ffffd000`282e6000=????????????????
Resetting default scope
 
LAST_CONTROL_TRANSFER:  from fffff8038eb562e9 to fffff8038eb4b760
 
STACK_TEXT:  
ffffd000`321695c8 fffff803`8eb562e9 : 00000000`0000000a ffffd000`282e6000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffd000`321695d0 fffff803`8eb54ac7 : 00640063`00700000 00730079`00730072 006f0066`006e0069 00650072`00690064 : nt!KiBugCheckDispatch+0x69
ffffd000`32169710 fffff801`33a490cc : 00000000`00001200 72006400`63007000 69007300`79007300 64006f00`66006e00 : nt!KiPageFault+0x247
ffffd000`321698a0 fffff801`33a48ad7 : ffffe000`663cd0d0 65007300`73006500 00000900`00007300 00075d00`00030000 : iaStorA+0xc90cc
ffffd000`321698e0 fffff801`33a4344f : ffffe000`663cd0d0 ffffd000`21d5a5d8 00000000`00000001 4e005b00`00000000 : iaStorA+0xc8ad7
ffffd000`32169930 fffff801`33a40683 : ffffe000`663cd0d0 ffffd000`21d5a5d8 ffffe000`5224af00 00640063`00700000 : iaStorA+0xc344f
ffffd000`32169980 fffff801`339d17a1 : ffffe000`663cd0d0 ffffd000`21d5a5d8 ffffe000`5224af80 00000000`00000000 : iaStorA+0xc0683
ffffd000`321699b0 fffff801`339d0db5 : ffffe000`663cd0d0 ffffd000`32169a80 ffffe000`548801a0 fffff803`8ed26180 : iaStorA+0x517a1
ffffd000`321699f0 fffff801`339c378b : ffffe000`663cd0d0 ffffffff`00000000 00000000`00000000 00000000`00000000 : iaStorA+0x50db5
ffffd000`32169a20 fffff801`33f05520 : ffffe000`548801a0 00000000`004d00fd ffffe000`548801a0 ffffd000`21d5a010 : iaStorA+0x4378b
ffffd000`32169a50 fffff801`33f05302 : ffffe000`548801a0 ffffe000`54370338 ffffd000`21d5a010 ffffd000`282e5fe0 : storport!RaidAdapterPostScatterGatherExecute+0x1f0
ffffd000`32169b20 fffff803`8f1d727f : ffffe000`54370338 00000000`00000018 00000000`00000000 ffffe000`54880050 : storport!RaidpAdapterContinueScatterGather+0x42
ffffd000`32169b50 fffff801`33f04d26 : ffffe000`549ef1b0 ffffe000`54880050 ffffd000`21d5a108 ffffe000`6a51dfe0 : hal!HalBuildScatterGatherListV2+0x1ff
ffffd000`32169be0 fffff801`33f03b88 : 00000000`00000001 ffffd000`00000001 ffffd000`32169cf8 fffff6fb`7dbede00 : storport!RaUnitStartIo+0x266
ffffd000`32169ca0 fffff801`33f0346f : ffffe000`52204000 ffffe000`6a463700 00000000`00000001 ffffe000`663cd103 : storport!RaidStartIoPacket+0x3c8
ffffd000`32169d80 fffff801`33f0303a : ffffe000`663cd0d0 ffffe000`6a51dfe0 ffffe000`549ef060 fffff803`00000096 : storport!RaUnitScsiIrp+0x3ef
ffffd000`32169e20 fffff801`33f59391 : 00000000`00000103 ffffe000`663cd0d0 ffffe000`6a463680 fffff803`00000096 : storport!RaDriverScsiIrp+0x5a
ffffd000`32169e60 fffff801`33f58cc2 : ffffd000`3216a0f0 fffff801`33f3cb0f 00000000`00000000 ffffe000`6698f4b0 : storport!PortPassThroughSendAsync+0x1b9
ffffd000`32169f10 fffff801`33f56e0a : ffffe000`6698f4b0 00000000`00000000 00000000`0004d000 ffffe000`548801a0 : storport!PortPassThroughExSendAsync+0x72
ffffd000`32169f80 fffff801`33f18b7c : ffffe000`6698f4b0 00000000`0004d004 ffffe000`548801a0 ffffd000`32000007 : storport!RaidAdapterPassThrough+0xa2
ffffd000`32169fd0 fffff801`33f044c5 : 00000000`00000000 00000000`00000000 ffffe000`6698f4b0 fffff801`33f48000 : storport!RaidAdapterDeviceControlIrp+0x142e4
ffffd000`3216a050 fffff801`33f57e76 : ffffe000`6698f4b0 00000000`0004d004 ffffe000`548801a0 ffffe000`549ef1b0 : storport!RaDriverDeviceControlIrp+0x95
ffffd000`3216a090 fffff801`33f188d1 : ffffd000`3216a160 fffff801`00000000 ffffe000`6698f4b0 ffffe000`549ef1b0 : storport!RaUnitScsiPassThroughIoctl+0xfa
ffffd000`3216a100 fffff801`33f0448a : ffffe000`6a5525d0 00000000`00000070 ffffe000`6698f610 fffff801`33f48000 : storport!RaUnitDeviceControlIrp+0x14401
ffffd000`3216a180 fffff801`34751d18 : ffffe000`6698f610 ffffe000`6698f4b0 ffffe000`5477ce00 ffffd000`3216a268 : storport!RaDriverDeviceControlIrp+0x5a
ffffd000`3216a1c0 fffff801`33454cf0 : ffffe000`6a5525d0 ffffd000`3216a268 00000000`00000000 00000000`00000000 : stdcfltn+0x1d18
ffffd000`3216a200 fffff801`347649f9 : ffffe000`5475cac0 ffffe000`6a5525d0 ffffe000`5477c8c0 ffffe000`547778c0 : Wdf01000!imp_WdfRequestSend+0x220 [d:\th\minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 2001]
ffffd000`3216a280 fffff801`3345ad78 : ffffe000`6a5525d0 fffff803`8ede8a97 ffffe000`5475c920 ffffe000`549e6920 : SEDFilter+0x49f9
ffffd000`3216a2c0 fffff801`3345aa14 : 00000000`00000200 fffff803`8ea8fa49 ffffc001`0d5bd600 00000000`00000000 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x168 [d:\th\minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 3306]
ffffd000`3216a360 fffff801`33457b2a : ffffe000`547778c0 fffff801`33335c00 00000000`00000000 ffffe000`549e6920 : Wdf01000!FxIoQueue::DispatchEvents+0xee4 [d:\th\minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 3100]
ffffd000`3216a440 fffff801`334511b1 : ffffe000`6698f400 ffffe000`6698f400 00000000`00000001 ffffe000`6a5525d0 : Wdf01000!FxPkgIo::DispatchStep1+0x52a [d:\th\minkernel\wdf\framework\shared\irphandlers\io\fxpkgio.cpp @ 324]
ffffd000`3216a500 fffff801`349e3a6d : ffffd000`3216a660 ffffe000`6698f4b0 ffffe000`6698f4b0 ffffc001`00000000 : Wdf01000!FxDevice::DispatchWithLock+0x111 [d:\th\minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1402]
ffffd000`3216a560 fffff801`349c16cf : 00000000`00000000 fffff803`8ec39c33 00000000`0004d004 ffffe000`72555358 : CLASSPNP!ClassDeviceControl+0x52d
ffffd000`3216a6d0 fffff801`349e8a73 : 00000000`00000000 00000000`c0000910 ffffe000`549f11b0 ffffe000`54775c60 : disk!DiskDeviceControl+0x8f
ffffd000`3216a760 fffff801`33834925 : ffffe000`6698f4b0 ffffe000`54775c60 00000000`00000001 ffffe000`72555080 : CLASSPNP!ClassDeviceControlDispatch+0x53
ffffd000`3216a790 fffff801`33822935 : ffffe000`6698f400 00000000`00000000 00000000`00000000 ffffe000`6698f4b0 : partmgr!PmIoctlRedirect+0x4d
ffffd000`3216a800 fffff803`8ee13ac2 : ffffe000`6a5afa70 ffffd000`3216ab80 ffffe000`6a5afa70 00000000`00000001 : partmgr!PmFilterDeviceControl+0x2a5
ffffd000`3216a850 fffff803`8ee12956 : e0006ca5`3dc00000 00000000`001f0003 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x1162
ffffd000`3216aa20 fffff803`8eb55fa3 : 00000000`00000102 00000000`00000001 00000000`00000000 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
ffffd000`3216aa90 00007ffb`81d951b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000087`ac5ffa18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`81d951b4
 
 
STACK_COMMAND:  kb
 
THREAD_SHA1_HASH_MOD_FUNC:  680dec21051cbdab04c619bb80d06f007166a32d
 
THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  cd2b9a0ee3d12d93ee230fc01aeca29878b2d659
 
THREAD_SHA1_HASH_MOD:  0fa91c13655e35d50d2f827a8bd7ea7ed55116a7
 
FOLLOWUP_IP: 
iaStorA+c90cc
fffff801`33a490cc 48894120        mov     qword ptr [rcx+20h],rax
 
FAULT_INSTR_CODE:  20418948
 
SYMBOL_STACK_INDEX:  3
 
SYMBOL_NAME:  iaStorA+c90cc
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: iaStorA
 
IMAGE_NAME:  iaStorA.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  55d322b3
 
BUCKET_ID_FUNC_OFFSET:  c90cc
 
FAILURE_BUCKET_ID:  AV_iaStorA!Unknown_Function
 
BUCKET_ID:  AV_iaStorA!Unknown_Function
 
PRIMARY_PROBLEM_CLASS:  AV_iaStorA!Unknown_Function
 
TARGET_TIME:  2016-03-17T15:13:58.000Z
 
OSBUILD:  10586
 
OSSERVICEPACK:  0
 
SERVICEPACK_NUMBER: 0
 
OS_REVISION: 0
 
SUITE_MASK:  272
 
PRODUCT_TYPE:  1
 
OSPLATFORM_TYPE:  x64
 
OSNAME:  Windows 10
 
OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
 
OS_LOCALE:  
 
USER_LCID:  0
 
OSBUILD_TIMESTAMP:  2016-02-24 06:48:00
 
BUILDDATESTAMP_STR:  160223-1728
 
BUILDLAB_STR:  th2_release_sec
 
BUILDOSVER_STR:  10.0.10586.162.amd64fre.th2_release_sec.160223-1728
 
ANALYSIS_SESSION_ELAPSED_TIME: 71d3
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:av_iastora!unknown_function
 
FAILURE_ID_HASH:  {72d271bd-a196-1959-0f3f-ddb017a6f169}
 
Followup:     MachineOwner
---------
 


#13 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:16 AM

Posted 17 March 2016 - 04:40 PM

.

JanOuwehand - Please start your own topic so that your issue can get the individual attention that it deserves.

 

Nice analysis, but it doesn't have all the info that I need.

Please run this report collecting tool so that we can provide a complete analysis:  http://omgdebugging.com/bsod-inspector/
When done a Notepad document will open with the name of the file and it's location. (By default it'll be a .zip file located on your Desktop)
Simply upload the .zip file with your next post and we'll move on from there.

If it doesn't work for you, then please try this:  http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/



BUT, if it's only a week old, see about returning it - or exchanging it for another one.

If they suggest sending it out for repair, that's an unreasonable loss of use of a brand new computer - I'd suggest refusing it and contacting the manufacturer at that point.


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#14 speedracergreg

speedracergreg

  • Members
  • 3 posts
  • OFFLINE
  •  

Posted 18 March 2016 - 04:08 AM

I got my motherboard changed and the hard drive. I copied a software image from old drive to new and the problem sadly persisted. This confirmed it was not a hardware issue and must be software. Sadly, Dell are still fumbling around trying to get installation media to me that actually works (drive not detected when booting from USB) so I've had to stick with my current faulty build for now. 

 

Earlier this week I caught a break after getting a BSOD at a time when the system wasn't doing much else. I investigated and this led me to uninstall Dell SupportAssist. Since then I have had no BSOD. It's odd, since i wasn't routinely using SupportAssist (though it was installed) but so far all is good.

 

This is the thread that led me to try removing SupportAssist. You'll note that one of the Dell technicians recounts anecdotal evidence of "UAS drives being problematic". I don't think PCIe M.2 (like mine) is a UAS drive, but it certainly suggests to me that there is scope for it to do stuff even when I'm not using it: http://en.community.dell.com/dell-groups/dell_integrated_support/end-user/f/4985/t/19626325

 

For the purposes of anyone Googling, this workaround helped me resolve BSOD (Blue Screen of Death) reporting BAD_HEADER_POOL particularly in iAStor.sys with my Dell Precision 7510 running a PCIe M.2. SSD drive.

 

I suspect that the reason the hardware swap apparently worked for the OP (@JayBuys) was more to do with the software rebuild (which maybe didn't include SupportAssist). Hopefully this prevents anyone else having to go through the frankly painful Dell "Pro Support" (ha!!) process I've had to go through (And still end up resolving the issue myself).


Edited by speedracergreg, 18 March 2016 - 04:11 AM.


#15 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:16 AM

Posted 18 March 2016 - 07:18 PM

I'm glad to hear that you've fixed it.

Thanks for letting us know - it'll help others who come looking for help with similar problems.


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users