0

Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 3081

Additional information about the problem: BCCode: 4e BCP1: 0000000000000007 BCP2: 000000000043BCE3 BCP3: 0000000000000001 BCP4: 0000000000000000 OS Version: 6_1_7601 Service Pack: 1_0 Product: 768_1

Files that help describe the problem: C:\Windows\Minidump\071213-4096414-01.dmp C:\Users\swanwhisperer\AppData\Local\Temp\WER-4260558-0.sysdata.xml

Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt

Improve this question
3

1 Answer 1

Reset to default
1

ok, looks like the Intel Storage driver causes this bugcheck (BSOD):

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
Arg2: 000000000043bce3, page frame number
Arg3: 0000000000000001, current share count
Arg4: 0000000000000000, 0

Debugging Details:
------------------


BUGCHECK_STR:  0x4E_7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA0FB0

LAST_CONTROL_TRANSFER:  from fffff80002441a83 to fffff80002479c00

STACK_TEXT:  
nt!KeBugCheckEx
nt! ?? ::FNODOBFM::`string'
nt! ?? ::FNODOBFM::`string'
nt!IopfCompleteRequest
iaStor
0x0
0x0
0x0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
iaStor+293e0
fffff880`0105f3e0 ??              ???

IMAGE_NAME:  iaStor.sys

FAILURE_BUCKET_ID:  X64_0x4E_7_iaStor+293e0

BUCKET_ID:  X64_0x4E_7_iaStor+293e0

    Loaded symbol image file: iaStor.sys
    Image path: \SystemRoot\system32\drivers\iaStor.sys
    Image name: iaStor.sys
    Timestamp:        Thu Jan 13 02:50:12 2011

So use the latest driver from Intel and not the older driver which Dell offers for your XPS 17 (L702X).

Improve this answer
6
  • This has had a dramatic effect in that now I can run Windows normally without any troubles. However, my second HDD still does not appear in My Computer. Do you know why that might be?
    – user1205901 - Слава Україні
    Jul 13, 2013 at 11:11
  • 1
    IMO this answer would be greatly improved if you were to explain how you went from the dump file to the above fairly readable dump, and which tools might allow someone else to do it. As it stands, this answer doesn't really help anyone but the OP.
    – user
    Jul 13, 2013 at 11:50
  • @SwanWhisperer is the HDD detected in the BIOS/UEFI? You should create a new question about it.
    – magicandre1981
    Jul 13, 2013 at 14:25
  • 1
    @Michael Kjörling open the dump in Windbg and run analyze -v
    – magicandre1981
    Jul 13, 2013 at 14:25
  • @magicandre1981: His second HDD isn't being detected by the BIOS, and don't ask him to create a new question since he's created two already for it: 1, 2.
    – Karan
    Jul 13, 2013 at 23:58

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.