Basically, I tried plugging in a TV as a second monitor, but whenever I switch my TV over to HDMI input, my PC will BSOD.
I have tried about 6 different sets of drivers, all of which either didnt work properly (fuzzy screen etc), or would BSOD still. I checked most of the dumps, they have the same error
You think its a faulty card?
Also, when I used the monitors switchewd over (TV as main, pc monitor as secondary), the PC would bluescreen when the monitor was turned on, which suggests a hardware error to me..
I attatched a mini dump anyway..
I did a clean install of the drivers using driver cleaner; didnt help.
Im now running memtest through, is it OK that I have left all 4 sticks of ram in to do it; would it be better to do them 1 at a time?
If this comes up negative, im going to run spybot through, and try cleaning my PC (some of the fans are a little dusty, though I doubt this is the problem).
I have tried about 6 different sets of drivers, all of which either didnt work properly (fuzzy screen etc), or would BSOD still. I checked most of the dumps, they have the same error
Probably caused by : nv4_mini.sys ( nv4_mini!class07CStopImage+21 )
You think its a faulty card?
Also, when I used the monitors switchewd over (TV as main, pc monitor as secondary), the PC would bluescreen when the monitor was turned on, which suggests a hardware error to me..
I attatched a mini dump anyway..
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {8b476a6f, 2, 8, 8b476a6f}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** WARNING: Unable to verify timestamp for nv4_mini.sys
Probably caused by : nv4_mini.sys ( nv4_mini!class07CStopImage+21 )
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: 8b476a6f, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 8b476a6f, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 8b476a6f
CURRENT_IRQL: 2
FAULTING_IP:
+21
8b476a6f ?? ???
CUSTOMER_CRASH_COUNT: 9
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: Idle
LAST_CONTROL_TRANSFER: from 8abca005 to 8b476a6f
FAILED_INSTRUCTION_ADDRESS:
+21
8b476a6f ?? ???
SYMBOL_ON_RAW_STACK: 1
STACK_ADDR_RAW_STACK_SYMBOL: ffffffff8055128c
STACK_COMMAND: dds 8055128C-0x20 ; kb
STACK_TEXT:
8055126c b996c738 nv4_mini!_NULL_IMPORT_DESCRIPTOR <PERF> (nv4_mini+0x2e1738)
80551270 8ad9a008
80551274 00020100
80551278 00020100
8055127c 8ac89d54
80551280 8ac89d38
80551284 8ac89418
80551288 b9739981 nv4_mini!class07CStopImage+0x21
8055128c 8ad9a008
80551290 00000000
80551294 8055ade0 nt!MmSystemPtesEnd
80551298 8ad9b350
8055129c 805512bc nt!KiNMITSS+0x54
805512a0 80553680 nt!Kd_PNPMEM_Mask
805512a4 8addc4e8
805512a8 b969747e nv4_mini!ValidateModeByDevices+0x25e
805512ac 8ad9a008
805512b0 8ae8a224
805512b4 b9679070 VIDEOPRT!pVideoPortHwTimer+0x14
805512b8 8ad9b350
805512bc 805512e0 nt!KiUnexpectedEntrySize
805512c0 804f478e nt!FsRtlLookupPerStreamContextInternal+0x1c
805512c4 8ad9b038
805512c8 00000000
805512cc 804f4740 nt!CcUninitializeCacheMap+0x194
805512d0 80551308 nt!KeLargestCacheLine
805512d4 00000000
805512d8 00000005
805512dc 02000041
805512e0 805513fc nt!MmFreePageListHead+0xc
805512e4 8050220f nt!CcSetDirtyPinnedData+0x12a
805512e8 8055adc0 nt!MiSystemPteSListHeadLock
FOLLOWUP_IP:
nv4_mini!class07CStopImage+21
b9739981 ?? ???
SYMBOL_NAME: nv4_mini!class07CStopImage+21
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nv4_mini
IMAGE_NAME: nv4_mini.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 496eaf75
FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_nv4_mini!class07CStopImage+21
BUCKET_ID: 0xD1_CODE_AV_BAD_IP_nv4_mini!class07CStopImage+21
Followup: MachineOwner
I did a clean install of the drivers using driver cleaner; didnt help.
Im now running memtest through, is it OK that I have left all 4 sticks of ram in to do it; would it be better to do them 1 at a time?
If this comes up negative, im going to run spybot through, and try cleaning my PC (some of the fans are a little dusty, though I doubt this is the problem).