AceofproZ Posted July 15, 2007 Posted July 15, 2007 Howdy guys, Ive used imgburn for a long time, however this is the first time ive got this problem. Looked all over my PC to find out the source of the problem, but i really have no idea. It started yesterday, out of the blue. When i would burn ISOs as per normal with imgburn the computer screen would lag, music/video skips, the mouse would lag, and strangely the burning speed would be at a constant 1.0x while at max (non auto), although both my DVD writer and the discs support up to 16x. Eventually this would lead to the BSOD. I recently changed from a 7600 to a 8800 nvidia card, and am running on a 410watt psu, however im doubting this should have anything to do with the burning issue Ive tried 7 times to burn dvds using the latest imgburn, defragmented, updated all drivers, checked hardware etc to no avail. Id appreciate any help if possible, Thanks in advance.
LIGHTNING UK! Posted July 15, 2007 Posted July 15, 2007 Find the mini memory dump file - probably in c:\windows\minidump and attach it in your next post. I'll tell you which driver is causing the problem.
AceofproZ Posted July 15, 2007 Author Posted July 15, 2007 Aye, Ive got 5 seperate minidump files, and ill send the two most recent i have to you. Mini071507_04.dmp Mini071507_03.dmp
dontasciime Posted July 15, 2007 Posted July 15, 2007 Have you got a power cable going to the gfx card. A 410watt psu seems a bit low nowadays , depends on the hardware you have in but if its an amd 64 CPU say/ the gfx card you have a couple of hard drives a few fans DVD writer / DVD reader and you psu has less than 20amps on the 12v line, tbh less than 24 amp you could run into this trouble with mouse crawling etc, Especially if you have to power gfx card with extra molex from psu. I would also check all power cables and ide cables
AceofproZ Posted July 15, 2007 Author Posted July 15, 2007 Lo there DontAsciiMe and thanks for your suggestions. I've been wondering if the problem was the PSU all along, however from what im hinting from Lightning's response it could actually be a software/driver related issue. With regards to hardware, ive got the power cable connected to the graphics card, to supplement the power. Its strange still that this only happens while burning something, and not while playing games or watching movies. My system is very similar (if not the same) as the one you described, as im running an AMD 64x2 4200, 2 satas/1 ide, a benQ DVD rom on an MSI k8n neo4f. Ive double checked all the power cables and IDE cables, everything seems to be in working order.
dontasciime Posted July 15, 2007 Posted July 15, 2007 have you got mps or apic set in your bios to run 2 core cpu
LIGHTNING UK! Posted July 15, 2007 Posted July 15, 2007 Minidump 04 Microsoft (R) Windows Debugger Version 6.7.0005.1 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Documents and Settings\Administrator\Desktop\Mini071507_04.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: C:\Windows\Symbols Executable search path is: Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 6000.16386.x86fre.vista_rtm.061101-2205 Kernel base = 0x82000000 PsLoadedModuleList = 0x82111db0 Debug session time: Sun Jul 15 10:15:49.209 2007 (GMT+1) System Uptime: 0 days 0:13:01.937 Loading Kernel Symbols ................................................................................ ................................................................................ Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, 864ba440, b2000000, 70f0f} Unable to load image \SystemRoot\system32\PSHED.dll, Win32 error 0n2 *** WARNING: Unable to verify timestamp for PSHED.dll *** ERROR: Module load completed but symbols could not be loaded for PSHED.dll Probably caused by : hardware Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 00000000, MCA_ASSERT Arg2: 864ba440, Address of WHEA_ERROR_RECORD structure Arg3: b2000000, High 32 bits of MCi_STATUS MSR for the MCA bank that had the error Arg4: 00070f0f, Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error Debugging Details: ------------------ WHEA_ERROR_RECORD: !errrec ffffffff864ba440 BUGCHECK_STR: 0x124_AuthenticAMD CUSTOMER_CRASH_COUNT: 4 DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT PROCESS_NAME: ImgBurn.exe CURRENT_IRQL: 4 STACK_TEXT: 820eef84 823a6e93 00000124 00000000 864ba440 nt!KeBugCheckEx+0x1e 820eefa0 820cecb6 864ba440 864bbad8 00000001 hal!HalBugCheckSystem+0x37 820eefc0 823a6e52 864bbad8 864bbbf0 820eeff4 nt!WheaReportHwError+0x10c 820eefd0 823a6f73 00000003 864bbad8 00000000 hal!HalpReportMachineCheck+0x28 820eeff4 823a389f 80159000 00000000 00000000 hal!HalpMcaExceptionHandler+0xc3 820eeff4 00000000 80159000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x77 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: 0x124_AuthenticAMD BUCKET_ID: 0x124_AuthenticAMD Followup: MachineOwner --------- Minidump 03 Loading Dump File [C:\Documents and Settings\Administrator\Desktop\Mini071507_03.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 6000.16386.x86fre.vista_rtm.061101-2205 Kernel base = 0x82000000 PsLoadedModuleList = 0x82111db0 Debug session time: Sun Jul 15 09:04:23.067 2007 (GMT+1) System Uptime: 0 days 0:04:40.831 Loading Kernel Symbols ................................................................................ ................................................................................ Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, 8607fd18, b2000000, 70f0f} Probably caused by : hardware Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 00000000, MCA_ASSERT Arg2: 8607fd18, Address of WHEA_ERROR_RECORD structure Arg3: b2000000, High 32 bits of MCi_STATUS MSR for the MCA bank that had the error Arg4: 00070f0f, Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error Debugging Details: ------------------ WHEA_ERROR_RECORD: !errrec ffffffff8607fd18 BUGCHECK_STR: 0x124_AuthenticAMD CUSTOMER_CRASH_COUNT: 3 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: dwm.exe CURRENT_IRQL: 0 STACK_TEXT: 820eef84 823a6e93 00000124 00000000 8607fd18 nt!KeBugCheckEx+0x1e 820eefa0 820cecb6 8607fd18 864bfad8 00000001 hal!HalBugCheckSystem+0x37 820eefc0 823a6e52 864bfad8 864bfbf0 820eeff4 nt!WheaReportHwError+0x10c 820eefd0 823a6f73 00000003 864bfad8 00000000 hal!HalpReportMachineCheck+0x28 820eeff4 823a389f 80159000 00000000 00000000 hal!HalpMcaExceptionHandler+0xc3 820eeff4 00000000 80159000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x77 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: 0x124_AuthenticAMD BUCKET_ID: 0x124_AuthenticAMD Followup: MachineOwner --------- Looks like some issue with your hardware?! It keeps pointing to your chip too. Are you overclocking or anything? Done any motherboard bios updates? If not, do some!
AceofproZ Posted July 15, 2007 Author Posted July 15, 2007 (edited) Hm thats strange. Im not overclocking anything at all. All systems as per normal. Ill do a BIOS update on the mobo right now, and also would having the wrong HAL disrupt any hardware/software ? Edited July 15, 2007 by AceofproZ
LIGHTNING UK! Posted July 15, 2007 Posted July 15, 2007 Just for giggles, go back to the 7600 for a while. See if you still get the BSOD's. That might give us more of a clue about the PSU being a potential issue. I don't know why you'd have the wrong HAL. Vista's not gonna install the wrong one, so unless you've installed on a totally different machine, I very much doubt that's the issue.
dontasciime Posted July 15, 2007 Posted July 15, 2007 for dual core you would need to be using apic with mps support. so you will have wrong hal if you have these disabled in bios What is listed under device manager for computer config and how many irq's is your system using.
dontasciime Posted July 15, 2007 Posted July 15, 2007 I would def be getting a bios update for your mobo, after updating clear cmos so DMI can update f5 defaults then set up to your taste, I would then boot and see how vista responds, though i would be installing vista again. Maybe check your memory as well with memtest. Do try you older gfx card again though.
AceofproZ Posted July 15, 2007 Author Posted July 15, 2007 Aight guys, ill start working on them and let you know what i find out. Thanks for the assistance up to this point )
AceofproZ Posted July 16, 2007 Author Posted July 16, 2007 Hey guys, just an update on the situation. Ive been able to fix the problem, it was indeed the PSU. Ive upgraded to a 700w PSU for now and the problem has gone away ! Sweetness Ahhh. Thanks for the assistance both of you, this just shows how committed the guys who run imgburn are to the software. Cheers boys.
Recommended Posts