I have the following problem: I'm using a Sony Vaio VGN-FZ31S and since I updated to Windows 7 64 (clean install) I experience the following issues: - when I scroll PDF files the system sometimes hangs completely - when I watch movies with Itunes (but not with windows media player) the system also hangs after a while sometimes I have done a complete memory check and I consulted other forums (sent in minidumps etc) but nobody was able to tell me what the problem is. Could there be a compatibility issue with my video driver? Any advice is appreciated.

check eventlogs "eventvwr.msc" check application and system logs check for errors and run the windows memory dagnostic.I want to be a MVP! | Computer Technician

- Memory diagnostics dedetcted no errors - eventvwr has the following events: A fatal hardware error has occurred. Reported by component: Processor Core Error Source: Machine Check Exception Error Type: Bus/Interconnect Error Processor ID: 1 The details view of this entry contains further information. Minidump file: http://dickreuter.com/md.dmp

Can you scroll PDF files in Safe Mode without issue?

I will have to test that. The problem is, it can sometimes take a long time for the error to occur. If it would work in safe mode, would that mean that there is a problem with the driver?

If it works in Safe mode then the problem would more likely be with a driver rather than the actual hardware.

It looks like this is the case. So what can I do? Am I right in thinking that a 2-year old Sony vaio is just not compatible with Windows 7 64? Looks like a switch to Apple is the only right step here...

You tried it in Safe Mode and it worked OK?

I have tried safe mode and I was unable to replicate the error. But this is hardly surprising as the safe mode is really using only the skeleton of Windows 7. I'm quite certain that there must be an issue with the video driver. How can I pinpoint the issue? Nobody appears to be able to read and interpret dumpfiles - I wonder what they're good for!

This is what the minidump says: But it is very unlikely that the hardware error started to occur since I installed Windows 7.... I can't believe that there is a hardware error. Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\md.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 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`03251000 PsLoadedModuleList = 0xfffff800`0348ee50 Debug session time: Fri Feb 12 21:05:29.181 2010 (GMT+0) System Uptime: 0 days 0:00:15.210 Loading Kernel Symbols ...................................................... Loading User Symbols Mini Kernel Dump does not contain unloaded driver list ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa8005067038, 0, 0} Probably caused by : hardware Followup: MachineOwner --------- 1: 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: 0000000000000000, Machine Check Exception Arg2: fffffa8005067038, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_GenuineIntel DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`02fee6f0 fffff800`0350ba89 : fffffa80`05067010 fffffa80`03cfe680 00000000`00000002 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c fffff880`02feec10 fffff800`033ed547 : fffffa80`05067010 fffff800`034665f8 fffffa80`03cfe680 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49 fffff880`02feec40 fffff800`03355b95 : fffff800`034c8360 fffffa80`050400e8 fffffa80`050400e0 fffffa80`03cfe680 : nt!WheapProcessWorkQueueItem+0x57 fffff880`02feec80 fffff800`032d0161 : fffff880`010d6e00 fffff800`03355b70 fffffa80`03cfe680 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25 fffff880`02feecb0 fffff800`03566166 : 086894fc`a0ec5cef fffffa80`03cfe680 00000000`00000080 fffffa80`03ceb890 : nt!ExpWorkerThread+0x111 fffff880`02feed40 fffff800`032a1486 : fffff880`009e7180 fffffa80`03cfe680 fffff880`009f1f40 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x5a fffff880`02feed80 00000000`00000000 : fffff880`02fef000 fffff880`02fe9000 fffff880`02fee220 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV Followup: MachineOwner ---------

Your problem is you're overclocking the CPU which causes it to be unstable, reset the CPU to factory default settings and run it again. THe bugcheck is referring to a CPU problem.MCSE, MCSA, MCDST [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]

Can you open the Device Manager and expand Display adapters then double-click the display adapter > Driver What is the Driver date and Driver version?

NVidia GeForce 8600M GS Date: 23/08/2007 Version: 7.15.11.5655

I believe it would highly benefit to try to update the display driver as the driver now installed pre-dates Windows 7.As Sony does not appear to have specific Windows 7 drivers for your laptop and NVIDIA restricts Sony Vaio users from installing their reference drivers consider using drivers with a modified .inf file to install.You could try here for drivers with a modified inf:http://www.laptopvideo2go.com/driversRead the "Quickstart Guide" first.

Ok, unfortunately I had another crash with the new driver. The crash looked a bit differently now (I got a blue screen instead of just the system hanging and the fonts were all over the place). This is what I was able to get from debug from memory.dmp: Any suggestions are appreciated Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Summary Dump File: Only kernel address space is available Symbol search path is: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`03264000 PsLoadedModuleList = 0xfffff800`034a1e50 Debug session time: Wed Feb 17 09:15:47.812 2010 (GMT+0) System Uptime: 0 days 0:10:42.841 Loading Kernel Symbols ............................................................... ................................................................ .............................................. Loading User Symbols Loading unloaded module list ....... 1: 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: 0000000000000000, Machine Check Exception Arg2: fffffa8004e2a038, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000f2000040, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000800, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_GenuineIntel DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: f STACK_TEXT: fffff880`009ef9d8 fffff800`0322d903 : 00000000`00000124 00000000`00000000 fffffa80`04e2a038 00000000`f2000040 : nt!KeBugCheckEx fffff880`009ef9e0 fffff800`033ea513 : 00000000`00000001 fffffa80`04e2aea0 00000000`00000000 fffffa80`04e2aef0 : hal!HalBugCheckSystem+0x1e3 fffff880`009efa20 fffff800`0322d5c8 : 00000000`00000728 fffffa80`04e2aea0 fffff880`009efdb0 fffff880`009efd00 : nt!WheaReportHwError+0x263 fffff880`009efa80 fffff800`0322cf1a : fffffa80`04e2aea0 fffff880`009efdb0 fffffa80`04e2aea0 00000000`00000000 : hal!HalpMcaReportError+0x4c fffff880`009efbd0 fffff800`0322cdd5 : 00000000`00000002 00000000`00000001 fffff880`009efe30 00000000`00000000 : hal!HalpMceHandler+0x9e fffff880`009efc10 fffff800`03220e88 : fffffa80`0677f000 fffffa80`0542d910 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55 fffff880`009efc40 fffff800`032d47ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40 fffff880`009efc70 fffff800`032d4613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c fffff880`009efdb0 fffff880`0fffc22e : fffff880`10344707 fffff880`04e293b8 fffff880`10070b52 fffffa80`03d20290 : nt!KiMcheckAbort+0x153 fffff880`04e29338 fffff880`10344707 : fffff880`04e293b8 fffff880`10070b52 fffffa80`03d20290 00000000`00000000 : nvlddmkm+0x18c22e fffff880`04e29340 fffff880`104c71b6 : fffffa80`0677f000 fffffa80`03d20290 00000095`a733d988 00000000`00000000 : nvlddmkm+0x4d4707 fffff880`04e29380 fffff880`104c74cd : fffffa80`0677f000 fffffa80`055972d0 00000000`00000000 00000000`00000000 : nvlddmkm+0x6571b6 fffff880`04e29410 fffff880`1038821b : fffffa80`0677f000 fffffa80`055972d0 00000000`00000044 00000000`00000000 : nvlddmkm+0x6574cd fffff880`04e29450 fffff880`1038b3dd : fffffa80`0677f000 00000000`00000043 fffffa80`055972d0 fffffa80`00000001 : nvlddmkm+0x51821b fffff880`04e295a0 fffff880`1024deae : 00000000`0000001e fffffa80`0677f000 fffffa80`055972d0 fffffa80`0677f000 : nvlddmkm+0x51b3dd fffff880`04e296a0 fffff880`0fff6aa4 : 00000000`0000001e 00000000`0000001e 00000000`00000001 00000000`00000051 : nvlddmkm+0x3ddeae fffff880`04e29820 fffff880`0ff528fd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x186aa4 fffff880`04e298d0 fffff880`0ff5631f : 00000000`00000000 fffff880`0ff528ae fffffa80`05189dc8 00000000`00000000 : nvlddmkm+0xe28fd fffff880`04e29950 fffff880`0ff6773a : 00000000`00000000 00000000`00000000 fffffa80`05189dc8 00000000`00000000 : nvlddmkm+0xe631f fffff880`04e29980 fffff880`105a3ad9 : fffffa80`00000000 fffff8a0`0e0098d7 00000000`00000000 00000000`00000000 : nvlddmkm+0xf773a fffff880`04e299b0 fffff880`04323cf1 : fffff880`105a3a85 00000000`00000000 fffffa80`06987000 fffffa80`0490b010 : nvlddmkm+0x733ad9 fffff880`04e29a30 fffff880`0431f54a : 00000000`00000001 fffffa80`06987000 fffffa80`0697a010 fffffa80`0697a928 : dxgkrnl!DXGADAPTER::DdiResetFromTimeout+0x45 fffff880`04e29a60 fffff880`0434bca5 : fffffa80`0490b010 fffffa80`0490b010 fffffa80`0490b010 fffffa80`0697a010 : dxgkrnl!DXGADAPTER::PrepareToReset+0xea fffff880`04e29aa0 fffff880`0420ff07 : fffffa80`0490b010 00000000`00000000 fffffa80`0714a850 fffffa80`0697a010 : dxgkrnl!TdrIsRecoveryRequired+0x245 fffff880`04e29ad0 fffff880`0423dd7e : fffffa80`ffffffff 00000000`0000995e fffff880`04e29c30 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`04e29bb0 fffff880`0420b29e : fffffa80`0697a010 ffffffff`feced300 fffffa80`06750860 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196 fffff880`04e29bf0 fffff880`04237e7a : 00000000`00000000 fffffa80`06750860 00000000`00000080 fffffa80`0697a010 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2 fffff880`04e29d00 fffff800`03579166 : 00000000`030f3085 fffffa80`06711a10 fffffa80`03ceb890 fffffa80`06711a10 : dxgmms1!VidSchiWorkerThread+0xba fffff880`04e29d40 fffff800`032b4486 : fffff880`009e7180 fffffa80`06711a10 fffff880`009f1f40 fffff880`01252534 : nt!PspSystemThreadStartup+0x5a fffff880`04e29d80 00000000`00000000 : fffff880`04e2a000 fffff880`04e24000 fffff880`04e28f20 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS Followup: MachineOwner

...and another one... Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\021710-29359-01.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 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`0320c000 PsLoadedModuleList = 0xfffff800`03449e50 Debug session time: Wed Feb 17 12:43:22.332 2010 (GMT+0) System Uptime: 0 days 0:00:09.221 Loading Kernel Symbols ...................................................... Loading User Symbols Mini Kernel Dump does not contain unloaded driver list ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa8004edb8f8, 0, 0} Probably caused by : hardware Followup: MachineOwner --------- 1: 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: 0000000000000000, Machine Check Exception Arg2: fffffa8004edb8f8, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`02fd96f0 fffff800`034c6a89 : fffffa80`04edb8d0 fffffa80`03cff680 00000000`00000006 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c fffff880`02fd9c10 fffff800`033a8547 : fffffa80`04edb8d0 fffff800`034215f8 fffffa80`03cff680 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49 fffff880`02fd9c40 fffff800`03310b95 : fffff800`03483360 fffffa80`04e25b98 fffffa80`04e25b90 fffffa80`03cff680 : nt!WheapProcessWorkQueueItem+0x57 fffff880`02fd9c80 fffff800`0328b161 : fffff880`0110ce00 fffff800`03310b70 fffffa80`03cff680 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25 fffff880`02fd9cb0 fffff800`03521166 : 00000000`00000000 fffffa80`03cff680 00000000`00000080 fffffa80`03ceb890 : nt!ExpWorkerThread+0x111 fffff880`02fd9d40 fffff800`0325c486 : fffff880`009e7180 fffffa80`03cff680 fffff880`009f1f40 d3344c14`0e466112 : nt!PspSystemThreadStartup+0x5a fffff880`02fd9d80 00000000`00000000 : fffff880`02fda000 fffff880`02fd4000 fffff880`03790590 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV Followup: MachineOwner ---------

The first crash with the new driver shows a direct involvement of the nvlddmkm.sys which is the display adapter driver (NVIDIA Windows Kernel Mode Driver). The nvlddmkm.sys (nvlddmkm) shows up in the STACK_TEXT field along with other drivers such as the dxgkrn.sys (dxgkrn) which is the DirectX Graphics Kernel.That does tend to indicate that the problem is with the display adapter driver or the display adapter itself.When did these crashes occur? Was it when scrolling PDFs or watching movies with iTunes?Also, it may help to provide some more info on the computer:Start > type msinfo32 in the "Search programs and files" box and press "Enter" > File > Save > then save as an .nfo fileThen make the resulting .nfo file available as you did for the minidump file in your second post.Also, in the Device Manager can you expand "Display Adapters" then double-click the display adapter > Details, then select "Hardware Ids"What information is given?

The error occured when watching a movie with iTunes (after about 20min). I had to go back to the old driver as the new one caused crashed at random, even without watching movies. Hardware lds of the display adaptor are as follows: PCI\VEN_10DE&DEV_0425&SUBSYS_9005104D&REV_A1 PCI\VEN_10DE&DEV_0425&SUBSYS_9005104D PCI\VEN_10DE&DEV_0425&CC_030000 PCI\VEN_10DE&DEV_0425&CC_0300 Computer specs: http://www.dickreuter.com/computer.nfo thanks

The computer is now crashing much more frequently and it appears that the error persists even after the crash. Sometimes after start-up I need to cold-start the coputer (have it switched off for more than 10sec) to avoid a screen a start-up that looks faulty (wrong colors and strange lines in the middle of the screen). This is since I updated the driver and going back to the old one didn't reverse the problem.

...and another crash dump. I'm almost certain, that it's the drivers which are faulty. A hardware error is very unlikely as the problem started to occur exactly once I installed Windows 7 (clean install). Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\021710-28236-01.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 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`03218000 PsLoadedModuleList = 0xfffff800`03455e50 Debug session time: Wed Feb 17 21:49:07.746 2010 (GMT+0) System Uptime: 0 days 0:00:42.775 Loading Kernel Symbols ............................................................... ................................................................ .......................... Loading User Symbols Loading unloaded module list .... Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for dxgkrnl.sys *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa8006914010, fffff880048c6890, 0, 2} Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+a890 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa8006914010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff880048c6890, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000002, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: nvlddmkm+a890 fffff880`048c6890 4885c9 test rcx,rcx DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`029249c8 fffff880`042e5ef8 : 00000000`00000116 fffffa80`06914010 fffff880`048c6890 00000000`00000000 : nt!KeBugCheckEx fffff880`029249d0 00000000`00000116 : fffffa80`06914010 fffff880`048c6890 00000000`00000000 00000000`00000002 : dxgkrnl+0x5cef8 fffff880`029249d8 fffffa80`06914010 : fffff880`048c6890 00000000`00000000 00000000`00000002 00000000`00000000 : 0x116 fffff880`029249e0 fffff880`048c6890 : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 : 0xfffffa80`06914010 fffff880`029249e8 00000000`00000000 : 00000000`00000002 00000000`00000000 00000000`00000000 fffff880`042e5c02 : nvlddmkm+0xa890 STACK_COMMAND: kb FOLLOWUP_IP: nvlddmkm+a890 fffff880`048c6890 4885c9 test rcx,rcx SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: nvlddmkm+a890 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 46cddb34 FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys Followup: MachineOwner

I have seen a lot of problems with Sony machines, enough that I would not buy one. I suggest trying the Vista drivers and see if you can graunch the situation.Vote if answered or helpful, I am running for Office (joke)! IT/Developer, Windows/Linux/Mainframe RaidMax Smilodon, 680W, Asus M2NBP-VM CSM AMD X2 4200+, 2GB DDR2-800, HD2400 Pro, more details on my site, need a new boot disk, existing one is 5 years old

Can you make available the following minidump file which corresponds to the VIDEO_TDR_FAILURE (116) error?:C:\Windows\Minidump\021710-28236-01.dmpAlso, I was unable to open the .nfo file you provided with System Information but could read portions of it with Wordpad.Can you double-check here?:Start > type msinfo32 in the "Search programs and files" box and press "Enter" > expand Components > Problem DevicesIs there anything listed in the window to the right of Problem Devices?Also, based on the Hardware Ids there appears to be drivers available for Windows 7 for the display adapter via Windows Update.You could try these drivers and see if they make any difference.First uninstall the drivers now installed using "Uninstall a program".After restarting the computer open Windows Update and select "Check for Update".The drivers should then appear for installation.As suggested by Vegan Fanatic using Vista drivers posted for the laptop at the Sony site is also a possibility.

I have now reinstalled windows 7 and put on the 32 bit version. Now everything is stable. The 64 bit drivers of nVidia are clearly faulty. They are useless. Thanks for your help anyway!