Been BSOD "DRIVER_POWER_STATE_FAILURE". View attachment Dump.zip Any ideas how to stop it?
new Vortex III constantly crashing (win 8)
- Thread starter ArkHazy
- Start date
Updated all the windows 8 ones from here www.clevo.com.tw/en/e-services/download/ftpOut.asp?Lmodel=P1xxEM<ype=9&submit=+GO+
vanthus
Member Resting in Peace
Could be a ram issue,try running memtest.
Using this one http://www.techrepublic.com/article/check-your-ram-with-memtest/1058392 I couldn't allocate more than 2.9 gigs in any one test so I have a bunch running.
Hey, thanks for the info. I was running Avast as well, I've uninstalled and replaced with AVG. Will edit this post later to follow up.
EDIT: Can't be Avast, it just crashed again. Here's the latest dump file. View attachment 112512-16296-01.zip. Can anyone help, the Mem test was pretty inconclusive, didn't find any errors.
Last edited:
According to the last dump diagnostic, the crash was caused by the memtest. Which would indicate you were right about the RAM. What can I do about it? Can identify which chip is causing it and remove it?
Unable to load image \SystemRoot\system32\DRIVERS\btfilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for btfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for btfilter.sys
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: usbhub.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 505ab300
MODULE_NAME: usbhub
FAULTING_MODULE: fffff880048e0000 usbhub
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: memtest.exe
CURRENT_IRQL: 2
TAG_NOT_DEFINED_c000000f: FFFFF88000F01FB0
STACK_TEXT:
fffff880`00f01af8 fffff803`5e3ae61e : 00000000`0000009f 00000000`00000003 fffffa80`131733c0 fffff880`00f01b30 : nt!KeBugCheckEx
fffff880`00f01b00 fffff803`5e3ae651 : fffffa80`130af360 fffffa80`0d936670 fffff880`00f01c89 fffff803`5e2c45c6 : nt!PopIrpWatchdogBugcheck+0xe2
fffff880`00f01b60 fffff803`5e2c5724 : fffffa80`0d936670 fffffa80`14d8fb00 fffff880`00f01e68 fffff880`00ed1180 : nt!PopIrpWatchdog+0x32
fffff880`00f01bb0 fffff803`5e2c5e15 : fffff880`00ed3f00 fffff803`5e2c0038 fffff880`00f01e00 00000000`00000065 : nt!KiProcessExpiredTimerList+0x214
fffff880`00f01cf0 fffff803`5e2c5cc8 : fffff880`00ed1180 fffff803`5e516f80 d88b0001`0000000b 0841f700`00006e4d : nt!KiExpireTimerTable+0xa9
fffff880`00f01d90 fffff803`5e2bf6f6 : fffff880`00ed1180 00000001`b61a3d2b fffffa80`14e6c080 00000000`00000025 : nt!KiTimerExpiration+0xc8
fffff880`00f01e40 fffff803`5e2befc5 : 00fffcba`c003f675 fffff880`00ed1180 fffff880`2121bb80 fffffa80`0cc00580 : nt!KiRetireDpcList+0x1f6
fffff880`00f01fb0 fffff803`5e2bedc9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`2121bac0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0x9F_3_RtkBtfilter_IMAGE_usbhub.sys
BUCKET_ID: 0x9F_3_RtkBtfilter_IMAGE_usbhub.sys
Followup: MachineOwner
---------
Last edited:
what do you think about the bit that mentions usbsys? Is it definitively the RAM?
vanthus
Member Resting in Peace
Sorry,I can't say if it's definitely the ram,but it's always worth testing in these situations.
The USB reference could mean a USB device or driver is causing the issue.
Anything else I can try before pulling out the RAM?
vanthus
Member Resting in Peace
You could give tech support a call (0844 499 4000)
Monday - Friday 9am - 5pm (Saturdays 9am - 1pm).
View waiting times http://www.pcspecialist.co.uk/call-waiting/
Monday - Friday 9am - 5pm (Saturdays 9am - 1pm).
View waiting times http://www.pcspecialist.co.uk/call-waiting/