blue screen of death

[Kuriin]

Did you try using a USB to install it instead of mounting it?

[pandergosk]

i dont have a usb big enough to hold all the files, or is that not what you meant?

[Kuriin]

That's what I meant. ><

[pandergosk]

after several days of trying to get this to load on my new lap top i still am running into the same problem.

It goes to blue screen after i mount an image and try to install the EQ files and the blue screen says system_service_exemption. I have used two diff virtual drive programs and have had the same result.

I really do not know what to do now, if any of you could help me out I would really appreciate it.

Here is a link to my mini dump file that I uploaded to megaupload, hope I did it right.

http://www.megaupload.com/?d=0925YO96

[Koota]

Have you tried using Daemon Tools Lite?

Google it.

[Mcbard]

Here's the output from your dump:

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800031790c0, fffff88006faa620, 0}

Probably caused by : ntkrnlmp.exe ( nt!PspInsertProcess+40 )

Followup: MachineOwner
---------

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800031790c0, Address of the instruction which caused the bugcheck
Arg3: fffff88006faa620, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!PspInsertProcess+40
fffff800`031790c0 49894210        mov     qword ptr [r10+10h],rax

CONTEXT:  fffff88006faa620 -- (.cxr 0xfffff88006faa620)
rax=0000000000000358 rbx=0000000000000000 rcx=0000000000000081
rdx=0000000000000000 rsi=fffffa800433db60 rdi=fffffa80041fb060
rip=fffff800031790c0 rsp=fffff88006faaff0 rbp=fffff88006fabca0
 r8=0000000002000000  r9=0000000000000000 r10=0000000000000000
r11=fffff88006faadd0 r12=0000000000000001 r13=fffffa800427b630
r14=fffff88006fab1f0 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!PspInsertProcess+0x40:
fffff800`031790c0 49894210        mov     qword ptr [r10+10h],rax ds:002b:00000000`00000010=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Install.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800031790c0

STACK_TEXT:  
fffff880`06faaff0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspInsertProcess+0x40


FOLLOWUP_IP: 
nt!PspInsertProcess+40
fffff800`031790c0 49894210        mov     qword ptr [r10+10h],rax

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!PspInsertProcess+40

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff88006faa620 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!PspInsertProcess+40

BUCKET_ID:  X64_0x3B_nt!PspInsertProcess+40

Followup: MachineOwner
---------

Judging from that I think that you are looking at a driver issue addressing invalid memory locations. It looks like the actual EverQuest install.exe that is causing this issue, so I assume you are beginning the setup and at some point during it is blue screening? If all you're doing is mounting the image and then it blue screens, try turning auto run off and see if it happens again?

[pandergosk]

it mounts fine and then it asks me what I want to do with the files install or open folder and then I click install and as soon as i do that it blue screens

[Mcbard]

Click open folder and see what happens.

[JackFlash]

Have you tried using Daemon Tools Lite?

This. I've used this on many Win7 machines without issue. Works great for me.