Oh okay...perfect thanks!!!
I have copied all 3 partitions to an external HD. Now my next step is to restore to factory settings correct?
Also...did this back up all of my files, or do I need to manually back up pictures...home movies...music etc?
The next step would be to make sure your files are safe, then you can do the factory restore. You can check your files by going into Macrium, selecting the restore tab, and then selecting Browse an image or backup file in Windows Explorer. See How to browse an Image or 'File and Folder' Backup in Windows Explorer for all methods to preview the image.
You should also make sure you can access the image with the boot CD you made.
I am able to access the files by browsing. I am about to recover to factory settings and test from there.
Alright, good luck!
I restored my computer to "Out of Box" settings and when I attempted to burn an mp4 file using convertXtoDVD I got a BSOD
Do you have this problem just burning DVD videos, or does it happen with data discs, as well?
Attempting a data dvd now (I haven't copied over much but one home vid (mp4)) but hopefully that will be enough to check.
Also, attached is an updated crash report from the crash after the fresh install
Blames a driver but is not able to determine which one. Same as before.Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Mike\Downloads\jo15765\Windows_NT6_BSOD_jcgriff2\013012-23899-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available 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 Personal Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Machine Name: Kernel base = 0xfffff800`02c5e000 PsLoadedModuleList = 0xfffff800`02ea3650 Debug session time: Mon Jan 30 19:10:17.364 2012 (GMT-7) System Uptime: 0 days 0:40:55.592 Loading Kernel Symbols ............................................................... ................................................................ ........................................ Loading User Symbols Loading unloaded module list ............... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {0, 2, 8, 0} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) 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: 0000000000000000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000008, value 0 = read operation, 1 = write operation Arg4: 0000000000000000, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0d100 0000000000000000 CURRENT_IRQL: 2 FAULTING_IP: +0 00000000`00000000 ?? ??? PROCESS_NAME: System CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 TRAP_FRAME: fffff800041ef740 -- (.trap 0xfffff800041ef740) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff800041ef801 rbx=0000000000000000 rcx=fffffa800608b618 rdx=fffff800041ef8d8 rsi=0000000000000000 rdi=0000000000000000 rip=0000000000000000 rsp=fffff800041ef8d0 rbp=0000000000000000 r8=fffff800041ef8d0 r9=0000000000000000 r10=0000000000000000 r11=000000005e040600 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc 00000000`00000000 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002cdd2a9 to fffff80002cddd00 FAILED_INSTRUCTION_ADDRESS: +0 00000000`00000000 ?? ??? STACK_TEXT: fffff800`041ef5f8 fffff800`02cdd2a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx fffff800`041ef600 fffff800`02cdbf20 : fffff880`03165180 fffffa80`07a3bb60 00000000`40f30088 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff800`041ef740 00000000`00000000 : 00000000`00000200 00000000`5e040600 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiPageFault+260 fffff800`02cdbf20 440f20c0 mov rax,cr8 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiPageFault+260 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260 BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260 Followup: MachineOwner ---------
Is there any way to definitively find out which driver is causing the problem?
I can burn a data dvd fine. To me the (from all the times I have unsuccesfully burned) the problem is in switching from Reading the CD (or converting the movie) from where it swaps over to actually burning the DVD.
For example, the Data DVD I just burned, was a straight BURN no need to swap over from read/write....maybe I am crazy here, but it may help :)
Do you burn 4.35 GB discs or 8.5 GB?
Quote