- May 30, 2012
- 83
- 0
- 10,640
I've been getting intermittent freezing and buzzing audio on this computer for awhile now especially while running folding@home, but hasn't BSODed until today and looks like a driver issue. I'm not sure if those two issues are even related. Would a soundcard sort out the audio buzzing (happens every minute or so when I am playing music) if it's a motherboard issue?
Computer Specs:
Windows 7
i5-3570k @stock
Nvidia gtx 460
Corsair Xm3 8GB RAM
Antec Earthwatts 650W PSU
I just updated the video card drivers yesterday so those are not the problem... I'll start running memtest right now, but I doubt RAM is the problem since I had the memory replaced last year.
After I restarted the computer, it also gave me a notification that my copy of Windows 7 is not genuine which is perplexing... I guess the issue might be sorted out with a clean install?
Crash details:
Computer Specs:
Windows 7
i5-3570k @stock
Nvidia gtx 460
Corsair Xm3 8GB RAM
Antec Earthwatts 650W PSU
I just updated the video card drivers yesterday so those are not the problem... I'll start running memtest right now, but I doubt RAM is the problem since I had the memory replaced last year.
After I restarted the computer, it also gave me a notification that my copy of Windows 7 is not genuine which is perplexing... I guess the issue might be sorted out with a clean install?
Crash details:
On Thu 11/28/2013 22:26:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112813-35365-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80069B7060, 0xFFFFF80000B9C3D8, 0xFFFFFA80072A0900)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 11/28/2013 22:26:15 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80069B7060, 0xFFFFF80000B9C3D8, 0xFFFFFA80072A0900)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.[ /spoiler]
crash dump file: C:\Windows\Minidump\112813-35365-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80069B7060, 0xFFFFF80000B9C3D8, 0xFFFFFA80072A0900)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 11/28/2013 22:26:15 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80069B7060, 0xFFFFF80000B9C3D8, 0xFFFFFA80072A0900)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.[ /spoiler]
Facebook
Twitter
Instagram