terrybobo Posted March 13, 2008 Posted March 13, 2008 I use the Imgburn and Microsoft Vista Business .. Everytime I use the Imgburn to burn the images ISO / MDS file to DVD, my vista display Blue screen and reboot my PC... I am using Pioneer DVR 212 SATA internal writer... the imgburn version are 2.3.2.0 and 2.4.0 both have the similar problem. the attachment is my Vista dump file. Please advise. Terry Mini031308_01.dmp
Cynthia Posted March 13, 2008 Posted March 13, 2008 Hi and welcome to the forum, terrybobo! If you change this setting; Vista Control panel -> Advanced system settings -> System -> the tab 'Start and Recovery' -> Settings -> uncheck the option to restart automatic That would allow you to see what driver that is causing the blue screen (you should see the driver name on the blue text). Another thing: Not sure If you have JMicron SATA on the mother board. I know those connections don't like to have burners attached to them. The power supply is strong enough?
LIGHTNING UK! Posted March 13, 2008 Posted March 13, 2008 RegKill.sys is causing it and it's actually wmplayer.exe that's initiating it. ******************************************************************************* * * * 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: 0012e705, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: 88be03f5, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 81d275a0 Unable to read MiSystemVaType memory at 81d086a0 0012e705 CURRENT_IRQL: 2 FAULTING_IP: RegKill+3f5 88be03f5 ?? ??? CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: wmplayer.exe TRAP_FRAME: 87403d9c -- (.trap 0xffffffff87403d9c) ErrCode = 00000000 eax=0012e700 ebx=854bf4b0 ecx=83d0fe88 edx=0861000a esi=83a57788 edi=83a578af eip=88be03f5 esp=87403e10 ebp=87403e4c iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 RegKill+0x3f5: 88be03f5 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from 88be03f5 to 81c493d4 STACK_TEXT: 87403d9c 88be03f5 badb0d00 0861000a c026928c nt!KiTrap0E+0x2ac WARNING: Stack unwind information not available. Following frames may be wrong. 87403e0c 88be0493 854bf4b0 0012e700 81c34ae0 RegKill+0x3f5 87403e4c 877980fb 83a57788 87403e6c 87798148 RegKill+0x493 87403e58 87798148 83a57788 00000000 83c67a68 ataport!IdeCompleteIoctl+0x17 87403e6c 8779c76f 83a57788 84229970 83cbd1eb ataport!ASyncScsiPassThroughCompletion+0x12 87403e8c 8779c806 83a57788 83c67a68 83cbd178 ataport!PortpCompleteRequestIrp+0x57 87403ea0 81c34ae0 00000000 83cbd178 83c67a68 ataport!PortpAsyncCompletion+0x1e 87403ed4 877952c9 83d0fe30 83a3b2e8 87403f04 nt!IopfCompleteRequest+0x12d 87403ee4 87795cac 84229970 83cbd178 83d0fe30 ataport!IdeCompleteScsiIrp+0x31 87403f04 87792fdc 84229970 00000000 87403f34 ataport!IdeCommonCrbCompletion+0x44 87403f14 87797e39 841e20e0 83a3b2e8 83a3b2e8 ataport!IdeTranslateCompletedRequest+0x3e 87403f34 8779806f 841e20e0 83a3b2e8 81cec820 ataport!IdeProcessCompletedRequests+0x121 87403f88 81c6b07e 841e209c 841e2028 00000000 ataport!IdePortCompletionDpc+0xab 87403ff4 81c3751d a04c145c 00000000 00000000 nt!KiRetireDpcList+0x147 87403ff8 a04c145c 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x3d 81c3751d 00000000 0000001a 00c1850f bb830000 0xa04c145c STACK_COMMAND: kb FOLLOWUP_IP: RegKill+3f5 88be03f5 ?? ??? SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: RegKill+3f5 FOLLOWUP_NAME: MachineOwner MODULE_NAME: RegKill IMAGE_NAME: RegKill.sys DEBUG_FLR_IMAGE_TIMESTAMP: 3c8ad50e FAILURE_BUCKET_ID: 0xD1_RegKill+3f5 BUCKET_ID: OLD_IMAGE_RegKill.sys Followup: MachineOwner ---------
terrybobo Posted March 20, 2008 Author Posted March 20, 2008 I've unload the Regkill and the Imgburn works fine now, Thank you very much for your great help. RegKill.sys is causing it and it's actually wmplayer.exe that's initiating it. ******************************************************************************* * * * 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: 0012e705, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: 88be03f5, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 81d275a0 Unable to read MiSystemVaType memory at 81d086a0 0012e705 CURRENT_IRQL: 2 FAULTING_IP: RegKill+3f5 88be03f5 ?? ??? CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: wmplayer.exe TRAP_FRAME: 87403d9c -- (.trap 0xffffffff87403d9c) ErrCode = 00000000 eax=0012e700 ebx=854bf4b0 ecx=83d0fe88 edx=0861000a esi=83a57788 edi=83a578af eip=88be03f5 esp=87403e10 ebp=87403e4c iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 RegKill+0x3f5: 88be03f5 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from 88be03f5 to 81c493d4 STACK_TEXT: 87403d9c 88be03f5 badb0d00 0861000a c026928c nt!KiTrap0E+0x2ac WARNING: Stack unwind information not available. Following frames may be wrong. 87403e0c 88be0493 854bf4b0 0012e700 81c34ae0 RegKill+0x3f5 87403e4c 877980fb 83a57788 87403e6c 87798148 RegKill+0x493 87403e58 87798148 83a57788 00000000 83c67a68 ataport!IdeCompleteIoctl+0x17 87403e6c 8779c76f 83a57788 84229970 83cbd1eb ataport!ASyncScsiPassThroughCompletion+0x12 87403e8c 8779c806 83a57788 83c67a68 83cbd178 ataport!PortpCompleteRequestIrp+0x57 87403ea0 81c34ae0 00000000 83cbd178 83c67a68 ataport!PortpAsyncCompletion+0x1e 87403ed4 877952c9 83d0fe30 83a3b2e8 87403f04 nt!IopfCompleteRequest+0x12d 87403ee4 87795cac 84229970 83cbd178 83d0fe30 ataport!IdeCompleteScsiIrp+0x31 87403f04 87792fdc 84229970 00000000 87403f34 ataport!IdeCommonCrbCompletion+0x44 87403f14 87797e39 841e20e0 83a3b2e8 83a3b2e8 ataport!IdeTranslateCompletedRequest+0x3e 87403f34 8779806f 841e20e0 83a3b2e8 81cec820 ataport!IdeProcessCompletedRequests+0x121 87403f88 81c6b07e 841e209c 841e2028 00000000 ataport!IdePortCompletionDpc+0xab 87403ff4 81c3751d a04c145c 00000000 00000000 nt!KiRetireDpcList+0x147 87403ff8 a04c145c 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x3d 81c3751d 00000000 0000001a 00c1850f bb830000 0xa04c145c STACK_COMMAND: kb FOLLOWUP_IP: RegKill+3f5 88be03f5 ?? ??? SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: RegKill+3f5 FOLLOWUP_NAME: MachineOwner MODULE_NAME: RegKill IMAGE_NAME: RegKill.sys DEBUG_FLR_IMAGE_TIMESTAMP: 3c8ad50e FAILURE_BUCKET_ID: 0xD1_RegKill+3f5 BUCKET_ID: OLD_IMAGE_RegKill.sys Followup: MachineOwner ---------
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now