Blue Screens and Random Reboots

[jason786]

Nothing more than what we have discuss so far. The exception code c000005 in those dump still suggest the memory issue

BugCheck 3B, {c0000005, fffff80002a7efa2, fffff8800215afb0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+1c2 )

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

Memory as in RAM?

Just got two blue screens in a row :s

 

[CarlTR6]

Memory means that something is affecting or corrupting memory. It could be RAM, drivers, incompatible software, faulty hardware such as bad RAM slots graphics card, sound card, network adapter, etc. It could be overheating or a faulty PSU affecting memory. This is what Ttran meant by memory.

 

[jason786]

Memory means that something is affecting or corrupting memory. It could be RAM, drivers, incompatible software, faulty hardware such as bad RAM slots graphics card, sound card, network adapter, etc. It could be overheating or a faulty PSU affecting memory. This is what Ttran meant by memory.

I took one RAM stick out but just got a 0xA blue screen :S

 

[Lordbob75]

Memory means that something is affecting or corrupting memory. It could be RAM, drivers, incompatible software, faulty hardware such as bad RAM slots graphics card, sound card, network adapter, etc. It could be overheating or a faulty PSU affecting memory. This is what Ttran meant by memory.

I took one RAM stick out but just got a 0xA blue screen :S

Try the other one.
If it still occurs, try a different slot.

~Lordbob

 

[jason786]

Memory means that something is affecting or corrupting memory. It could be RAM, drivers, incompatible software, faulty hardware such as bad RAM slots graphics card, sound card, network adapter, etc. It could be overheating or a faulty PSU affecting memory. This is what Ttran meant by memory.

I took one RAM stick out but just got a 0xA blue screen :S

Try the other one.
If it still occurs, try a different slot.

~Lordbob

Still occured so I put both of them into the black slots instead, so far I haven't had one restart or bluescreen (after ~4 hours) but they happen randomly so it could come anytime

 

[Lordbob75]

I took one RAM stick out but just got a 0xA blue screen :S

Try the other one.
If it still occurs, try a different slot.

~Lordbob

Still occured so I put both of them into the black slots instead, so far I haven't had one restart or bluescreen (after ~4 hours) but they happen randomly so it could come anytime

That very much sounds like you just had them in the wrong slots.

~Lordbob

 

[jason786]

Try the other one.
If it still occurs, try a different slot.

~Lordbob

Still occured so I put both of them into the black slots instead, so far I haven't had one restart or bluescreen (after ~4 hours) but they happen randomly so it could come anytime

That very much sounds like you just had them in the wrong slots.

~Lordbob

Ah maybe not :S

The PC just crashed and rebooted, I think it was meant to be a blue screen so I disabled automatic restart

Wasn't the usual reboot though, the others ones i've had just reboot instantly

 

[Lordbob75]

Still occured so I put both of them into the black slots instead, so far I haven't had one restart or bluescreen (after ~4 hours) but they happen randomly so it could come anytime

That very much sounds like you just had them in the wrong slots.

~Lordbob

Ah maybe not :S

The PC just crashed and rebooted, I think it was meant to be a blue screen so I disabled automatic restart

Wasn't the usual reboot though, the others ones i've had just reboot instantly

Dang. Well, lets keep at it then.

~Lordbob

 

[jason786]

Got a blue screen, but it's 0xA :/

 

[jason786]

After being away for a week, I just got back and was welcomed by a nice juicy blue screen

 

[ttran]

one stop code is 101, which we have discussed before.

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

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------
PROCESS_NAME:  svchost.exe
BugCheck A, {fffff88003a64d80, 2, 0, fffff80002a8f5db}

Probably caused by : ntkrnlmp.exe ( nt!KiSearchForNewThread+26b )

Followup: MachineOwner
---------
PROCESS_NAME:  javaw.exe

Not sure what to suggest you more, Have you checked this article before?
http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

 

[jason786]

one stop code is 101, which we have discussed before.

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

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------
PROCESS_NAME:  svchost.exe
BugCheck A, {fffff88003a64d80, 2, 0, fffff80002a8f5db}

Probably caused by : ntkrnlmp.exe ( nt!KiSearchForNewThread+26b )

Followup: MachineOwner
---------
PROCESS_NAME:  javaw.exe

Not sure what to suggest you more, Have you checked this article before?
http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

Yep looked at that and prime95 said the cpu was fine

 

[jason786]

Ok, I'm pretty sure the RAM is fine, unless both sticks are faulty

The CPU seems to be fine too

I'm not sure what else I can do, it definately can't be software after all those clean installs and it isn't due to a bad install disk since I had the same problem on Vista too

 

[Tews]

If you had the same problems with Vista, then I am 99.99% sure that somewhere you have a hardware problem/conflict .. were you using the same computer then that you are now??

 

[CarlTR6]

If you had the same problems with Vista, then I am 99.99% sure that somewhere you have a hardware problem/conflict .. were you using the same computer then that you are now??

+1 I concur.

 

[jason786]

If you had the same problems with Vista, then I am 99.99% sure that somewhere you have a hardware problem/conflict .. were you using the same computer then that you are now??

Yep, the reason I changed to Windows 7 was because of this problem

If you had the same problems with Vista, then I am 99.99% sure that somewhere you have a hardware problem/conflict .. were you using the same computer then that you are now??

+1 I concur.

Welcome back to the thread, Carl

 

[Tews]

Lets enable driver verifier and see if we can get some more conclusive .dmp files...follow these instructions...

- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

 

[jason786]

I enabled driver verifier, so far I haven't received any blue screens, but I got a reboot

I'm not sure if this helps, but the PC seems to reboot / blue screen more often when both sticks of RAM are in, compared to when I only have one stick in

 

[Tews]

Have you checked the minidump folder for any new .dmp files??

 

[jason786]

Have you checked the minidump folder for any new .dmp files??

There arn't any new ones, just a few from before with bug check 0xA

I got a blue screen a few minutes ago though, but it didn't collect crash dump data