Comp. Immediately Crashes. Safe mode = Ok.

GenRoss · 16 May 2011

Alright...memtest was passing after 5 hours.
These are the last reports I'll upload here before going to the driver verifier thread.

The second most recent BSOD was when I turned my computer off. Only when it was at the end of shutting down did it give me the blue screen. Maybe there's a driver or something associated with this? I don't know.

The most recent one was when I was headed to report back here about when I was shutting down my computer. So maybe the driver isn't just associated with shutting down.

Just trying to speculate while being more or less uninformed at the same time.

GenRoss · 16 May 2011

I was instructed to post here, sorry if I'm digging up an old thread.
So, I'm on my phone right now, looking at my computer in safe mode without networking because sure enough it looks like driver verifier caught something. I'm not given enough time in normal mode to find anything before it crashes.

But nonetheless, where are the verifier reports saved to?

Jonathan_King · 16 May 2011

Driver Verifier's "reports" come in the form of BSODs, which will leave evidence in the form of event logs and memory dumps. The dumps are saved in C:\Windows\Minidump, but you don't need to worry about them as the jcgriff2 file collection app will automatically copy them to the report.

Jonathan_King · 16 May 2011

It looks like your TP-LINK USB wireless adapter is the cause here. I see the drivers are dated May 12, 2011, after the BSODs started. I suspect we're looking at two separate problems, one with RAM and the other with the wireless adapter. Try removing the adapter for now, and use the Realtek ethernet instead.

...Summary of the dumps:

Code:


Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon May 16 18:21:04.452 2011 (UTC - 4:00)
System Uptime: 0 days 0:28:27.951
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+67 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+67
BiosReleaseDate = 06/17/2010
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon May 16 02:40:20.620 2011 (UTC - 4:00)
System Uptime: 0 days 11:29:20.434
*** WARNING: Unable to verify timestamp for athurx.sys
*** ERROR: Module load completed but symbols could not be loaded for athurx.sys
Probably caused by : nwifi.sys ( nwifi!Dot11FlushIntermediateSendQueue+68 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nwifi!Dot11FlushIntermediateSendQueue+68
BiosReleaseDate = 06/17/2010
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

GenRoss · 16 May 2011

I'll start posting my reply's in the driver verifier thread.

GenRoss · 16 May 2011

Oh alright, thanks.
I'm pretty sure the two most recent reports in the report should be the ones verifier generated.

I'm pretty sure i saw RTCore64.sys on the verifiers bsod. A google brought up problems with MSI afterburner. I went ahead and uninstalled that. It shouldn't be the problem since I was receiving problems before I did install it. But I'll run verifier soon again with that uninstalled.

Also, you suggested to stop using the Tp-Link usb wireless adapter and use the realtek one instead.
However my tp-link one is the only one I have.
I'm pretty sure I don't have a built in hardware wifi adapter or anything.

Also when I'm in safe mode w/ networking I haven't had any crashes, unless there are extra drivers not loaded in safe mode.

If I could get a new set of instructions, well... that would help haha...

Jonathan_King · 16 May 2011

Let's stick to the other thread. I've asked the Mods to move this back to the original thread; we can continue to use this thread until then.

You don't have an onboard wireless chip, but you have Realtek ethernet on your motherboard. Try using that for the time being.

...Summary of the dumps:

Code:


Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon May 16 20:35:44.738 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:01.252
*** WARNING: Unable to verify timestamp for RTCore64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTCore64.sys
Probably caused by : RTCore64.sys ( RTCore64+1522 )
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  MSIAfterburner
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_RTCore64+1522
BiosReleaseDate = 06/17/2010
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

GenRoss · 16 May 2011

Ok, if i go ahead and hook up the ethernet I'm gonna end up moving my router and modem, which is fine, but I'll try that tomorrow.
Until then, I found two other wireless adapters. A Netgear pci adapter and a Dell usb adapter.
Would trying to use one of these be a possible fix, or is the problem the fact I'm using wireless?

Jonathan_King · 16 May 2011

The wireless itself wouldn't be the cause, although I'll admit there is a small chance it's a USB issue. You can go ahead and give the other adapters a try though!

GenRoss · 16 May 2011

No luck with the old adapters. Driver aren't compatible or won't work. I'll update the Ethernet situation tomorrow.
Thanks for all the help so far everyone. Hope this works.