G75, EventID: 41, & abrupt reboots

[MUPiSz]

The computer will just abruptly reboot. i can be playing a sound file and bam, reboot. i thought i had this issue fixed when i got rid of a cheap usb mouse plugged into the power/usb port. then i'd at least get the BSoD out of nowhere. but now, no BSoD, just an abrupt reboot!

last time this happened i had chrome open with a few tabs, one with a youtube video but not playing, Avast Pro running in background, kmplayer 3.2.0.19 playing a sound file, then BAM, abrupt reboot.
i have no idea exactly what is causing this.

Also Get Error ID: 11, whenever i plugin a USB2.0 drive. is this a G75VW/Intel issue or MS?

i purchased two of these machines, one to develop on and one for my music stuff. incidentally, the one for the music stuff is the one crashing periodically.

below is the event log summary for event id:41 and then a summary of hardware profile for the computer.




[Critical Event ID] ------------------------------------------------------
System
- Provider
[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID 41
Version 2
Level 1
Task 63
Opcode 0
Keywords 0x8000000000000002
- TimeCreated
[ SystemTime] 2012-07-05T19:56:30.100409900Z
EventRecordID 8088


---------------------------------------------------------------------------



HWiNFO64 Version 4.00-1680

-------------------------------------------------------------------

[Current Computer]
Computer Name:
Computer Brand Name: ASUS G75VW
[Operating System]
Operating System: Microsoft Windows 7 Ultimate (x64) Build 7601
Service Pack: Service Pack 1


Intel Core i7-3610QM ------------------------------------------------------

BIOS ----------------------------------------------------------------------

BIOS Vendor: American Megatrends Inc.
BIOS Version: G75VW.207
BIOS Release Date: 04/06/2012
BIOS Start Segment: F000
BIOS Size: 6144 KBytes
System BIOS Version: 4.6

System --------------------------------------------------------------------

System Manufacturer: ASUSTeK COMPUTER INC.
Product Name: G75VW
Product Version: 1.0
Family: G

Mainboard -----------------------------------------------------------------

Mainboard Manufacturer: ASUSTeK COMPUTER INC.
Mainboard Name: G75VW
Mainboard Version: 1.0

M4-CT256M4SSD2 ------------------------------------------------------------

[General Information]
Drive Controller: Serial ATA 6Gb/s
Drive Model: M4-CT256M4SSD2
Drive Revision: 000F
Drive Capacity: 244,198 MBytes (256 GB)
Drive Capacity [MB]: 244198
Media Rotation Rate: SSD Drive (Non-rotating)

WDC WD7500BPKT-00PK4T0 ----------------------------------------------------

[General Information]
Drive Controller: Serial ATA 3Gb/s
Drive Model: WDC WD7500BPKT-00PK4T0
Drive Revision: 01.01A01
Drive Capacity: 715,404 MBytes (750 GB)
Drive Capacity [MB]: 715404
Media Rotation Rate: 7200 RPM


Intel Panther Point PCH - High Definition Audio Controller [C1] -----------

Audio Adapter: Intel Panther Point PCH - High Definition Audio Controller [C1]
Audio Controller Hardware ID: PCI\VEN_8086&DEV_1E20&SUBSYS_14871043&REV_04
High Definition Audio Codec: VIA
Audio Codec Hardware ID: HDAUDIO\FUNC_01&VEN_1106&DEV_8446&SUBSYS_00000000
[Driver Information]
Driver Manufacturer: VIA Technologies, Inc.
Driver Description: VIA High Definition Audio
Driver Provider: VIA Technologies, Inc.
Driver Version: 6.0.1.10400
Driver Date: 20-Mar-2012
DeviceInstanceId HDAUDIO\FUNC_01&VEN_1106&DEV_8446&SUBSYS_10431487&REV_1000\4&27159E35&0&0001

nVIDIA GF114 - High Definition Audio Controller ---------------------------

Audio Adapter: nVIDIA GF114 - High Definition Audio Controller
Audio Controller Hardware ID: PCI\VEN_10DE&DEV_0E0C&SUBSYS_0E0C10DE&REV_A1
High Definition Audio Codec: nVidia HDMI
Audio Codec Hardware ID: HDAUDIO\FUNC_02&VEN_10DE&DEV_0016&SUBSYS_10DE0016

[xeromist]

41 kernel power is super generic. Basically you get it whenever Windows has a major crash. 😞

You'll need to basically run a battery of tests to see if you can pin it down. Run Memtest86 for the memory, run temperature monitoring software to see if anything overheats. Try Prime95 or LinX to load up the CPU for a few minutes. Try Furmark for the GPU. If either is the problem then you should get a crash/reset pretty quickly with those.

[Shawnnepc]

Send your minidumps to me and i'll debug it

My email address is: shawn AT neteffectspc DOT cmm

[MUPiSz]

Shawnnepc wrote:
Send your minidumps to me and i'll debug it

My email address is: shawn AT neteffectspc DOT cmm

can do. i'll run the tests from the above suggested apps and include. thx

[MUPiSz]

@shawnnepc, actually, i'll run these tests and take a view of the dump files via some ms debugging tools, etc before i upload them. knowing MS i have no idea what data is actually lurking in there. thanks, more later

[MUPiSz]

xeromist wrote:
41 kernel power is super generic. Basically you get it whenever Windows has a major crash. 😞

You'll need to basically run a battery of tests to see if you can pin it down. Run Memtest86 for the memory, run temperature monitoring software to see if anything overheats. Try Prime95 or LinX to load up the CPU for a few minutes. Try Furmark for the GPU. If either is the problem then you should get a crash/reset pretty quickly with those.

i'll dl the apps suggested and post back results. thx

[Ami_Yuy]

First off, MUPiSz, are you Hibernating your laptop? It's been the cause for at least two of us for random reboots exactly like you are describing.

See: G75VW Random Reboot

[MUPiSz]

Ami Yuy wrote:
First off, MUPiSz, are you Hibernating your laptop? It's been the cause for at least two of us for random reboots exactly like you are describing.

See: G75VW Random Reboot

turned off via `powercfg /hibernate off`

just now downloading the "furmark" app this G75VW did the same reboot as the other. first time for this machine. same event id:41 for this one too. i have an ancient Thinkpad plugged into the same conditioned power strip and it didn't blink.

when i complete the tests i'll post a summary.

[MUPiSz]

note: these results are from one computer. neither computer at the time was setup to NOT reboot on system failure. arrgh! so, these results are not conclusive regarding dmp files. auto reboot on failure has been turned off. when the crash happens again i should get more conclusive data, hopefully. i wouldn't take these results as conclusive but i'll post it here just to add to the troubleshooting arena.




#>------------------------------------------------------------------

memtest86=no errors
furmark=no errors, ran 15min, highest heat val 185.6f, fans ran as expected kept it running ok


[#1 mini-dump short summary]
bug_check_string=DRIVER_POWER_STATE_FAILURE
driver=ntoskrnl.exe
driver=bthpan.sys
SYMBOL_NAME: bthpan!BthpanIfAdapterRegister+158
IMAGE_NAME: bthpan.sys
FAILURE_BUCKET_ID: X64_0x9F_4_bthpan!BthpanIfAdapterRegister+158


[#2 mini-dump short summary]
bug_check_string=DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
driver=ntoskrnl.exe
driver=btath_flt.sys


[Device Manager]
--Bluetooth Radios
----Bluetooth Module
--------Atheros Communications
----------Driver Date: 12.26.2011
----------Driver Version: 7.4.0.115
----Microsoft Bluetooth Enumerator
--------Microsoft
----------Driver Date: 06.21.2006
----------Driver Version: 6.1.7601.17607

#>------------------------------------------------------------------

for the crashes that did write a dmp file the culprit looks like ntoskrnl.sys and bluetooth in those particular instances. but that isn't conclusive to me. i have two machines with same hardware same OS, just different user apps.

hibernation has been turned off both compters.

if this hard crash reboot happens again, hopefully *those* dmp file(s) will provide more data for better comparsions and find the point of failure.

i'll post more when/if this crash scenario reappears...


ps: i did send a msg to ASUS and to Fry's as both these machines are <30 days ownership just to cover bases.

[dstrakele]

It's interesting to see the Atheros Bluetooth drivers listed in the 2 dump files. I would try disabling or uninstalling them for troubleshooting purposes OR try to find more recent versions to install.

NTOSKRNL.EXE, the main Windows 7 process, is a victim in this fault, most likely being passed corrupt data by some other driver, bthpan.sys and btath_flt.sys being suspects.

I would also be tempted to turn off Wireless Network Adapter power management (in Devine Manager Properties for the WiFi Adapter) to troubleshoot this issue. The 1st reported BSOD appears to be related to power management.