D drmokem Member Joined Jul 6, 2015 Posts 7 Jul 6, 2015 #1 My computer just recently started crashing, randomly it seems. I did just get a new graphics card, but it doesn't crash in games, it runs fantastically in games, so I don't see how that would be the cause. I ran furmark too, and it worked fine. I got the card on the 2nd, and crashing didn't start until the 4th, it happens every day now, seemingly random, but never in a game. Usually when browsing web, happens with both chrome, firefox, and IE. My CPU never goes above 65C, and graphics card in furmark maxed at around 85C, but it doesn't get that hot in games, nor does it even get used much when the crashes actually happen. I also have a big fan pointed inside my computer, with the AC on, so I don't think it's overheating. · OS - Windows 8.1 · x86 (32-bit) or x64 ? 64bit · What was original installed OS on system? - Windows 8 · Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Key was OEM on windows 8, upgraded to windows 8.1 · Age of system (hardware) 14 months · Age of OS installation - have you re-installed the OS? 14 months · CPU - FX-8350 @ 4.00 GHz · Video Card - MSI R9 390 8GB · MotherBoard - m5a99fx pro r2.0 · Power Supply - Thermaltake Smart Standard 650W 80 PLUS Bronze ATX12V 2.3 Power Supply · System Manufacturer - Assembled by me · Exact model number - Assembled by me · Desktop View attachment SFCFix.txtView attachment ULTRAGAMING-PC_20150706-000003.zipView attachment 14124 I'll respond when I'm finished with the other tests, thanks for any assistance you can provide
My computer just recently started crashing, randomly it seems. I did just get a new graphics card, but it doesn't crash in games, it runs fantastically in games, so I don't see how that would be the cause. I ran furmark too, and it worked fine. I got the card on the 2nd, and crashing didn't start until the 4th, it happens every day now, seemingly random, but never in a game. Usually when browsing web, happens with both chrome, firefox, and IE. My CPU never goes above 65C, and graphics card in furmark maxed at around 85C, but it doesn't get that hot in games, nor does it even get used much when the crashes actually happen. I also have a big fan pointed inside my computer, with the AC on, so I don't think it's overheating. · OS - Windows 8.1 · x86 (32-bit) or x64 ? 64bit · What was original installed OS on system? - Windows 8 · Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Key was OEM on windows 8, upgraded to windows 8.1 · Age of system (hardware) 14 months · Age of OS installation - have you re-installed the OS? 14 months · CPU - FX-8350 @ 4.00 GHz · Video Card - MSI R9 390 8GB · MotherBoard - m5a99fx pro r2.0 · Power Supply - Thermaltake Smart Standard 650W 80 PLUS Bronze ATX12V 2.3 Power Supply · System Manufacturer - Assembled by me · Exact model number - Assembled by me · Desktop View attachment SFCFix.txtView attachment ULTRAGAMING-PC_20150706-000003.zipView attachment 14124 I'll respond when I'm finished with the other tests, thanks for any assistance you can provide
D drmokem Member Joined Jul 6, 2015 Posts 7 Jul 6, 2015 #2 can't use dos version because I don't have a CD drive, used Seatools for Windows. Hard drive tests - Smart passed. Short drive self test passed. Short generic test outer, inner, Random Read passed.
can't use dos version because I don't have a CD drive, used Seatools for Windows. Hard drive tests - Smart passed. Short drive self test passed. Short generic test outer, inner, Random Read passed.
D drmokem Member Joined Jul 6, 2015 Posts 7 Jul 6, 2015 #3 Not sure exactly how to use driver verifier, but it tested two drivers. Executions synchronized 0 faults injected 0 IRQL raises 0 Pool allocations attempted 6643900 Pool allocations failed 0 pool allocations not tracked 6565625 pool allocations succeeded 6643900 pool allocations succeeded in special pool 6643900 pool allocations without tag 0 spinlocks acquired 136288 Trims 175703 atikmpag.sys non paged pool - bytes allocated 202460 non paged pool number of allocations 2045 non paged pool peak bytes allocated 204996 paged pool bytes allocated 994624 paged pool number of allocations 7692 paged pool peak bytes allocated 994624 paged pool peak number of allocations 7692 atikmdag.sys non paged pool - bytes allocated 3008619 non paged pool number of allocations 2704 non paged pool peak bytes allocated 3019907 non paged pool peak number of allocations 2739 paged pool bytes allocated 6194019 paged pool number of allocations 3256 paged pool peak bytes allocated 6228947 paged pool peak number of allocations 3275 atikmdag.sys - ATI Radeon Kernel Mode Driver atikmpag.sys - AMD Multi-vender Miniport Driver These numbers were changing as I wrote them, if they seem weird. I don't know, don't even think this information is useful.
Not sure exactly how to use driver verifier, but it tested two drivers. Executions synchronized 0 faults injected 0 IRQL raises 0 Pool allocations attempted 6643900 Pool allocations failed 0 pool allocations not tracked 6565625 pool allocations succeeded 6643900 pool allocations succeeded in special pool 6643900 pool allocations without tag 0 spinlocks acquired 136288 Trims 175703 atikmpag.sys non paged pool - bytes allocated 202460 non paged pool number of allocations 2045 non paged pool peak bytes allocated 204996 paged pool bytes allocated 994624 paged pool number of allocations 7692 paged pool peak bytes allocated 994624 paged pool peak number of allocations 7692 atikmdag.sys non paged pool - bytes allocated 3008619 non paged pool number of allocations 2704 non paged pool peak bytes allocated 3019907 non paged pool peak number of allocations 2739 paged pool bytes allocated 6194019 paged pool number of allocations 3256 paged pool peak bytes allocated 6228947 paged pool peak number of allocations 3275 atikmdag.sys - ATI Radeon Kernel Mode Driver atikmpag.sys - AMD Multi-vender Miniport Driver These numbers were changing as I wrote them, if they seem weird. I don't know, don't even think this information is useful.
D drmokem Member Joined Jul 6, 2015 Posts 7 Jul 6, 2015 #4 memtest showed 0 errors over 4 passes, I had to skip hammer test, it got to 2% before it just started slowing down massively, was stuck at 2% for 30 minutes so I skipped it.
memtest showed 0 errors over 4 passes, I had to skip hammer test, it got to 2% before it just started slowing down massively, was stuck at 2% for 30 minutes so I skipped it.
D drmokem Member Joined Jul 6, 2015 Posts 7 Jul 7, 2015 #5 Figured out how to use driver verifier, BSOD at login screen, but i think it has something to do with powerDVD, which i have had installed for over a year. Any assist would be great I've de-selected that driver, and am going to run the verifier through the night to see if anything else happens. View attachment minidump1.zip and here's full kernel dump.
Figured out how to use driver verifier, BSOD at login screen, but i think it has something to do with powerDVD, which i have had installed for over a year. Any assist would be great I've de-selected that driver, and am going to run the verifier through the night to see if anything else happens. View attachment minidump1.zip and here's full kernel dump.
P Patrick Sysnative Staff Joined Jun 7, 2012 Posts 4,618 Jul 7, 2015 #6 Code: 6: kd> .bugcheck Bugcheck code 000000C4 Arguments 00000000`000000f6 00000000`00000398 ffffe000`d1938480 fffff800`b9b5ae2f Reason for verifier throwing bug check was a user handle being referenced as kernel mode. Code: 6: kd> knL # Child-SP RetAddr Call Site 00 ffffd001`7166efa8 fffff801`6589e6b0 nt!KeBugCheckEx 01 ffffd001`7166efb0 fffff801`658a3fa0 nt!VerifierBugCheckIfAppropriate+0x3c 02 ffffd001`7166eff0 fffff801`6574b2df nt!VfCheckUserHandle+0x1b8 03 ffffd001`7166f0d0 fffff801`655b8915 nt! ?? ::NNGAKEGL::`string'+0x742f 04 ffffd001`7166f170 fffff801`6563d40f nt!ObReferenceObjectByHandle+0x25 05 ffffd001`7166f1c0 fffff801`653754b3 nt!NtQueryInformationFile+0x19f 06 ffffd001`7166f340 fffff801`6536d900 nt!KiSystemServiceCopyEnd+0x13 07 ffffd001`7166f548 fffff800`b9b5ae2f nt!KiServiceLinkage 08 ffffd001`7166f550 ffffd001`7166f658 000+0x1e2f 09 ffffd001`7166f558 00000000`0000003e 0xffffd001`7166f658 0a ffffd001`7166f560 00000000`00000424 0x3e 0b ffffd001`7166f568 00000000`00000000 0x424 Not a good stack since we're on a small dump. Code: FAILURE_ID_HASH_STRING: km:0xc4_f6_vrf_000+1e2f The hash string for the failure bucket ID shows verifier flagging the PowerDVD driver as the driver that performed the incorrect reference on the handle. Code: 6: kd> lmvm 000 start end module name fffff800`b9b59000 fffff800`b9b67000 000 T (no symbols) Loaded symbol image file: 000.fcl Image path: \??\C:\Program Files (x86)\CyberLink\PowerDVD14\Common\NavFilter\000.fcl Image name: 000.fcl Timestamp: Fri Oct 18 03:16:31 201 Get rid of PowerDVD.
Code: 6: kd> .bugcheck Bugcheck code 000000C4 Arguments 00000000`000000f6 00000000`00000398 ffffe000`d1938480 fffff800`b9b5ae2f Reason for verifier throwing bug check was a user handle being referenced as kernel mode. Code: 6: kd> knL # Child-SP RetAddr Call Site 00 ffffd001`7166efa8 fffff801`6589e6b0 nt!KeBugCheckEx 01 ffffd001`7166efb0 fffff801`658a3fa0 nt!VerifierBugCheckIfAppropriate+0x3c 02 ffffd001`7166eff0 fffff801`6574b2df nt!VfCheckUserHandle+0x1b8 03 ffffd001`7166f0d0 fffff801`655b8915 nt! ?? ::NNGAKEGL::`string'+0x742f 04 ffffd001`7166f170 fffff801`6563d40f nt!ObReferenceObjectByHandle+0x25 05 ffffd001`7166f1c0 fffff801`653754b3 nt!NtQueryInformationFile+0x19f 06 ffffd001`7166f340 fffff801`6536d900 nt!KiSystemServiceCopyEnd+0x13 07 ffffd001`7166f548 fffff800`b9b5ae2f nt!KiServiceLinkage 08 ffffd001`7166f550 ffffd001`7166f658 000+0x1e2f 09 ffffd001`7166f558 00000000`0000003e 0xffffd001`7166f658 0a ffffd001`7166f560 00000000`00000424 0x3e 0b ffffd001`7166f568 00000000`00000000 0x424 Not a good stack since we're on a small dump. Code: FAILURE_ID_HASH_STRING: km:0xc4_f6_vrf_000+1e2f The hash string for the failure bucket ID shows verifier flagging the PowerDVD driver as the driver that performed the incorrect reference on the handle. Code: 6: kd> lmvm 000 start end module name fffff800`b9b59000 fffff800`b9b67000 000 T (no symbols) Loaded symbol image file: 000.fcl Image path: \??\C:\Program Files (x86)\CyberLink\PowerDVD14\Common\NavFilter\000.fcl Image name: 000.fcl Timestamp: Fri Oct 18 03:16:31 201 Get rid of PowerDVD.
D drmokem Member Joined Jul 6, 2015 Posts 7 Jul 7, 2015 #7 Will do, thanks for the quick reply I also added a full kernel dump to my last post, and I will be running the verifier through the night to see if anything else crops up.
Will do, thanks for the quick reply I also added a full kernel dump to my last post, and I will be running the verifier through the night to see if anything else crops up.
P Patrick Sysnative Staff Joined Jun 7, 2012 Posts 4,618 Jul 7, 2015 #8 Code: 6: kd> !handle 300 PROCESS ffffe000d1938480 SessionId: 0 Cid: 0424 Peb: 7ff61f7b3000 ParentCid: 0310 DirBase: 13c271000 ObjectTable: ffffc001d637fd80 HandleCount: <Data Not Accessible> Image: svchost.exe Handle Error reading handle count. 0300: free handle, Entry address ffffc001d6380c00, Next Entry ffffc001d6380900 Code: 6: kd> dt nt!_MODE ffffc001d6380c00 0 ( KernelMode ) Yeah, there's the handle referenced/accessed by kernel mode when it was meant for user mode. Code: 6: kd> !address fffff800b9b5ae2f .. Usage: Module Base Address: fffff800`b9b59000 End Address: fffff800`b9b67000 Region Size: 00000000`0000e000 VA Type: BootLoaded Module name: 000.fcl Module path: [\??\C:\Program Files (x86)\CyberLink\PowerDVD14\Common\NavFilter\000.fcl] And the module responsible is indeed the PowerDVD driver. So yeah, get rid of it.
Code: 6: kd> !handle 300 PROCESS ffffe000d1938480 SessionId: 0 Cid: 0424 Peb: 7ff61f7b3000 ParentCid: 0310 DirBase: 13c271000 ObjectTable: ffffc001d637fd80 HandleCount: <Data Not Accessible> Image: svchost.exe Handle Error reading handle count. 0300: free handle, Entry address ffffc001d6380c00, Next Entry ffffc001d6380900 Code: 6: kd> dt nt!_MODE ffffc001d6380c00 0 ( KernelMode ) Yeah, there's the handle referenced/accessed by kernel mode when it was meant for user mode. Code: 6: kd> !address fffff800b9b5ae2f .. Usage: Module Base Address: fffff800`b9b59000 End Address: fffff800`b9b67000 Region Size: 00000000`0000e000 VA Type: BootLoaded Module name: 000.fcl Module path: [\??\C:\Program Files (x86)\CyberLink\PowerDVD14\Common\NavFilter\000.fcl] And the module responsible is indeed the PowerDVD driver. So yeah, get rid of it.
D drmokem Member Joined Jul 6, 2015 Posts 7 Jul 7, 2015 #9 Sadly I "crashed" again. The screen will go black, i can hear sounds for a couple of seconds, and then sound starts looping for a second, then silence. can't use numlock, so i'm guessing it did indeed freeze/crash. Happened on twitch, but it didn't happen instantly, i have the same video in the background running while typing this. I had verifier running when it crashed, sadly no minidumps were made, nor a kernel.. I even let it sit on the blackscreen for 5-10 minutes, so I'm a loss as to what to do.. any ideas?
Sadly I "crashed" again. The screen will go black, i can hear sounds for a couple of seconds, and then sound starts looping for a second, then silence. can't use numlock, so i'm guessing it did indeed freeze/crash. Happened on twitch, but it didn't happen instantly, i have the same video in the background running while typing this. I had verifier running when it crashed, sadly no minidumps were made, nor a kernel.. I even let it sit on the blackscreen for 5-10 minutes, so I'm a loss as to what to do.. any ideas?
P Patrick Sysnative Staff Joined Jun 7, 2012 Posts 4,618 Jul 7, 2015 #10 Your screen going black and sound looping issue may be entirely unrelated to your blue screen issue. The first thing I'd try is disabling hardware acceleration in your browser, as that often causes a lot of issues. If that doesn't work, uninstall your video card drivers + remove your new graphics card and reinstall the old one, or use integrated. If you don't crash, you most likely have a bad new GPU.
Your screen going black and sound looping issue may be entirely unrelated to your blue screen issue. The first thing I'd try is disabling hardware acceleration in your browser, as that often causes a lot of issues. If that doesn't work, uninstall your video card drivers + remove your new graphics card and reinstall the old one, or use integrated. If you don't crash, you most likely have a bad new GPU.