Hardware Ids
Value
After some searching, I believe it may be a gameport. At least I'm seeing quite a few people having the same unknown device, then disabling gameport in BIOS and it disappearing. According to this post on a different website, Windows dropped support as of XP-64. I can't see any drivers for it on the CD or website either.Code:ACPI\PNPB02F *PNPB02F
Are you able to disable it in the BIOS? Does that provide any more stability, or do you still experience crashes/freezes?
There's no option to disable it in BIOS. It's not caused a problem before though - it was there before the BSOD/freezes started.
Caused by your graphics card; hardware related. Other possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...Code:Loading Dump File [G:\Kingston\BSODDmpFiles\Kewne\Windows_NT6_BSOD_jcgriff2\020212-30765-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 UP Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`0260e000 PsLoadedModuleList = 0xfffff800`0284be70 Debug session time: Wed Feb 1 20:07:26.164 2012 (GMT-7) System Uptime: 0 days 1:15:31.414 Loading Kernel Symbols ............................................................... ................................................................ .................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc000001d, fffff8800f2b3509, a, fffffa8002a32000} 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 : hardware ( nvlddmkm+25e509 ) Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffffc000001d, The exception code that was not handled Arg2: fffff8800f2b3509, The address that the exception occurred at Arg3: 000000000000000a, Parameter 0 of the exception Arg4: fffffa8002a32000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction. FAULTING_IP: nvlddmkm+25e509 fffff880`0f2b3509 c7 ??? EXCEPTION_PARAMETER1: 000000000000000a EXCEPTION_PARAMETER2: fffffa8002a32000 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1E PROCESS_NAME: System CURRENT_IRQL: a EXCEPTION_RECORD: fffff80000b9c4f8 -- (.exr 0xfffff80000b9c4f8) ExceptionAddress: fffff8800f2b3509 (nvlddmkm+0x000000000025e509) ExceptionCode: c000001d (Illegal instruction) ExceptionFlags: 00000000 NumberParameters: 0 TRAP_FRAME: fffff80000b9c5a0 -- (.trap 0xfffff80000b9c5a0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000009 rbx=0000000000000000 rcx=fffffa800324f000 rdx=000000000000000c rsi=0000000000000000 rdi=0000000000000000 rip=fffff8800f2b3509 rsp=fffff80000b9c730 rbp=fffffa800324f000 r8=0000000000000000 r9=0000000000000000 r10=fffffa8002a32000 r11=fffff80000b9c8c0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nvlddmkm+0x25e509: fffff880`0f2b3509 c7 ??? Resetting default scope MISALIGNED_IP: nvlddmkm+25e509 fffff880`0f2b3509 c7 ??? LAST_CONTROL_TRANSFER: from fffff800026b8919 to fffff8000267e5c0 FAILED_INSTRUCTION_ADDRESS: nvlddmkm+25e509 fffff880`0f2b3509 c7 ??? STACK_TEXT: fffff800`00b9bd28 fffff800`026b8919 : 00000000`0000001e ffffffff`c000001d fffff880`0f2b3509 00000000`0000000a : nt!KeBugCheckEx fffff800`00b9bd30 fffff800`0267dc02 : fffff800`00b9c4f8 fffffa80`0324f000 fffff800`00b9c5a0 00000000`0000000c : nt!KiDispatchException+0x1b9 fffff800`00b9c3c0 fffff800`0267bd5f : fffff800`00b9c5a0 ffffeb1e`039f8f0a fffff800`027f8e00 00000000`00000000 : nt!KiExceptionDispatch+0xc2 fffff800`00b9c5a0 fffff880`0f2b3509 : fffffa80`02bec040 fffff880`0f230a57 00000000`00000000 00000000`00000000 : nt!KiInvalidOpcodeFault+0x11f fffff800`00b9c730 fffffa80`02bec040 : fffff880`0f230a57 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x25e509 fffff800`00b9c738 fffff880`0f230a57 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`02bec040 fffff800`00b9c740 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`01e90c80 : nvlddmkm+0x1dba57 STACK_COMMAND: kb FOLLOWUP_IP: nvlddmkm+25e509 fffff880`0f2b3509 c7 ??? SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: nvlddmkm+25e509 FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_IP_MISALIGNED_nvlddmkm.sys BUCKET_ID: X64_IP_MISALIGNED_nvlddmkm.sys Followup: MachineOwner ---------
Thanks to JMH for helping with my understanding of this crash.
We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.
- If you are overclocking any hardware, please stop.
- Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
- Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
- Download and install the appropriate version of HWINFO: HWiNFO32 for 32-bit Windows 7 or HWiNFO64 for 64-bit Windows 7 to check hardware temperatures by running in sensor-only mode.
- Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory.
- Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
- Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
[*]If you are overclocking any hardware, please stop.
I'm not overclocking.
[*]Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
I've done this and it showed no errors. Where can I find the report?
Edit
Code:CHKDSK is verifying files (stage 1 of 5)... 75008 file records processed. File verification completed. 84 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 106356 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)... 75008 file SDs/SIDs processed. Cleaning up 150 unused index entries from index $SII of file 0x9. Cleaning up 150 unused index entries from index $SDH of file 0x9. Cleaning up 150 unused security descriptors. Security descriptor verification completed. 15675 data files processed. CHKDSK is verifying Usn Journal... 35456288 USN bytes processed. Usn Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... 74992 files processed. File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... 21786119 free clusters processed. Free space verification is complete. Windows has checked the file system and found no problems. 102399999 KB total disk space. 15031368 KB in 58933 files. 45164 KB in 15676 indexes. 0 KB in bad sectors. 178987 KB in use by the system. 65536 KB occupied by the log file. 87144480 KB available on disk. 4096 bytes in each allocation unit. 25599999 total allocation units on disk. 21786120 allocation units available on disk. Internal Info: 00 25 01 00 7c 23 01 00 17 53 02 00 00 00 00 00 .%..|#...S...... 2d 00 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 -...,........... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Windows has finished checking your disk. Please wait while your computer restarts.
[*]Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
Proceeding to do this now - I've just installed Win7 on a completely different hard drive and had the same error before finishing setting up though, so this seems unlikely.
UPDATE: No integrity errors.
Download and install the appropriate version of HWINFO: HWiNFO32 for 32-bit Windows 7 or HWiNFO64 for 64-bit Windows 7 to check hardware temperatures by running in sensor-only mode.
EDIT: See attachment.
Last edited by Kewne; 02 Feb 2012 at 19:50.
Good, one instability cause down. :)
Check Disk (chkdsk) - Read Event Viewer Log
It is unlikely, but I have seen it happen once or twice. Usually it only happens when people are using automated optimization programs.
Alright, let us know the temperatures at idle and during stress.
Attached images of results when idle and stressed (running Burn In test - 100% processor, 1.4/2GB RAM used according to Performance in Ctrl+Alt+Del).
Currently waiting for the computer to reset on me as I couldn't run the sensor program in Safe Mode so trying to be quick by using an image.
Burn in test seems to be running okay, apart from a rising temp.
Let us know what the temperature maxes out at or what it is at when the computer resets, whichever comes first. Temperatures look good in the post, by the way. Nothing too high.
|MG| Video Memory Stress Test passed - all okay, with a couple of not compatibles.
Will see what temp the burn out test maxes out at now.
EDIT: It seems to level out at 73 degree Celsius max. It didn't reset while doing that for 15 minutes.
Regarding Prime95 - is it okay if I use safe mode? It's almost certain to freeze or reset before three hours are up if not.
Quote