Blue Screens and Random Reboots

[jason786]

Can you upload the dmp to us?

I can't since the restart took place in the middle of windows creating one, so there isn't one in the minidump folder

 

[CarlTR6]

I was afraid of that.

 

[usasma]

Hardware - there's not much else that'll interrupt the process of saving the info AFTER the crash has occurred.

 

[jason786]

Yep, it's been happening a lot now, now leaving a dump and just happened again

Was 0x00000101 again..

I thought it was hardware from the beginning, but is there no way to detect excately what part of my system is causing me problems?

 

[CarlTR6]

Jason, we have probably covered this somewhere in this thread; but what peripherals do you have hooked up when you boot?

To answer your question, I do not know of a way to pinpoint a hardware problem except by swapping out components.

 

[jason786]

Jason, we have probably covered this somewhere in this thread; but what peripherals do you have hooked up when you boot?

To answer your question, I do not know of a way to pinpoint a hardware problem except by swapping out components.

Keyboard, Mouse, Wireless Adapter, Speakers and my Monitor

The keyboard is the only thing that has been swapped once before

On a side note, I just received 3 restarts in under 10 minutes.. not sure why at all :/ I think I better let my PC rest for tonight

I really appreciate all your help

I had a three year return to base warranty on this PC, on which I returned it once before, however when I got it back, I was told it had some stability issues running at high resolution so the PSU had to be changed.. however the problem obviously still persists

It's just a bit annoying having to buy a PC then attempt to figure out the bugs yourself, I think I may send it back again and see what happens (postage costs a bit by itself though which is also why I didn't send it back to the manufacturer a second time)

 

[usasma]

Here's a suggestion on how to troubleshoot by stripping your system down: Hardware Troubleshooting Via System Stripdown

I'd have a nice long talk with a supervisor/manager at the place that you're shipping it to. You shouldn't have to pay for their failure to repair it - especially if you have a warranty.

 

[CarlTR6]

If you have a warranty, that is exactly what I would do.

 

[CarlTR6]

John, thank you for that link; that is a great reference.

 

[jason786]

Here's a suggestion on how to troubleshoot by stripping your system down: Hardware Troubleshooting Via System Stripdown

I'd have a nice long talk with a supervisor/manager at the place that you're shipping it to. You shouldn't have to pay for their failure to repair it - especially if you have a warranty.

Yes, I will phone them up tomorrow and see what they say, it's bad enough that the system wasn't checked before it was first shipped, and then again after I sent it back the first time

I'll have a look through the guide

But I have a quick question, say the blue screens were caused by peripherals, would the dump show this?

 

[Jonathan_King]

Here's a suggestion on how to troubleshoot by stripping your system down: Hardware Troubleshooting Via System Stripdown

I'd have a nice long talk with a supervisor/manager at the place that you're shipping it to. You shouldn't have to pay for their failure to repair it - especially if you have a warranty.

Yes, I will phone them up tomorrow and see what they say, it's bad enough that the system wasn't checked before it was first shipped, and then again after I sent it back the first time

I'll have a look through the guide

But I have a quick question, say the blue screens were caused by peripherals, would the dump show this?

Not necessarily. If they were USB devices malfunctioning, it may show up as blaming the USB hub drivers.

Often peripherals are very hard to pick up on. For that reason, it is advisable to disconnect them when troubleshooting stuff like this.

 

[jason786]

Ok, I'm going to leave my keyboard, mouse, monitor and wireless adapter plugged in

 

[jason786]

Heres another blue screen, first one since the 2nd of July, the rest have been random reboots

 

[Tews]

The analysis for your .dmp file is inconclusive. In light of all of the problems that you are having, I would return the computer for replacement...

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff88002f64180, 2}

Unable to load image \SystemRoot\system32\DRIVERS\Dnetr28ux.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Dnetr28ux.sys
*** ERROR: Module load completed but symbols could not be loaded for Dnetr28ux.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002f64180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

Debugging Details:
------------------


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  d



STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_VRF_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_VRF_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner

 

[jason786]

The analysis for your .dmp file is inconclusive. In light of all of the problems that you are having, I would return the computer for replacement...

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff88002f64180, 2}

Unable to load image \SystemRoot\system32\DRIVERS\Dnetr28ux.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Dnetr28ux.sys
*** ERROR: Module load completed but symbols could not be loaded for Dnetr28ux.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002f64180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

Debugging Details:
------------------


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  d



STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_VRF_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_VRF_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner

Yea, will phone up now

oh yeah, one more thing, on vista, my computer used to freeze regularly, like every 20 seconds it would just freeze and suddenly continue, and it would be this literally every 20 seconds, then when I got windows 7 this problem stopped

However, when I first got the PC, it came with vista and I didn't have this problem

although recently, when my Hard drive crashed, I tried putting vista on, and again it froze every so often.. not sure if this is related to the processor or something?

 

[Tews]

Its entirely possible, but I would still return it for repair/replacement...

 

[jason786]

I have to call tomorrow morning :/

But I just shut down my computer, and came back to a blue screen, this one was prevented by driver verifier

 

[Capt.Jack Sparrow]

Hello Jason,

This time it's pointing to D-link Wi-Fi usb adapter i.e. Dnetr28ux.sys that has caused the crash. You could remove the Drivers and reinstall it. It's also possible it might hardware itself that is the problem.

Good Luck,
Captain

 

[jason786]

Hello Jason,

This time it's pointing to D-link Wi-Fi usb adapter i.e. Dnetr28ux.sys that has caused the crash. You could remove the Drivers and reinstall it. It's also possible it might hardware itself that is the problem.

Good Luck,
Captain

I reinstalled the drivers, and just tried to shut down my PC for the night, and was given a blue screen

I wonder if it's the same one

 

[Capt.Jack Sparrow]

Hello Jason,

This time it's pointing to D-link Wi-Fi usb adapter i.e. Dnetr28ux.sys that has caused the crash. You could remove the Drivers and reinstall it. It's also possible it might hardware itself that is the problem.

Good Luck,
Captain

I reinstalled the drivers, and just tried to shut down my PC for the night, and was given a blue screen

I wonder if it's the same one

Yes Jason it's the same driver !!