BSOD clock interrupt not received on secondary processor (0X00000101)

[venkai]

Hi,

I have a Toshiba Qosmio X505-Q870 with an i7-q870 1.73GHz Processor, 8GB ram, 1.5GB NVIDIA GeForce GTX 460M gpu, running win7-64bit home premium.

I have had the laptop since 2010. I recently cloned my HDD to an SSD, put the old HDD in the secondary bay, upgraded the RAM from 4gb to 8gb, and added a PCI USB3 expresscard (in the order mentioned).

However, since my laptop was overheating of late (I tried cleaning the laptop with canned air) and at times simply shut down, I decided to reduce the maximum processor state in power management to 90%, to prevent the CPU from overclocking. After that, the laptop ran pretty well for around a month, and now I am getting this BSOD.

I have the latest BIOS version installed that is available for my machine, and I have no idea why I am suddenly getting this BSOD.

I have attached the dump files from the DM log collector.
Any help will be deeply appreciated !

 

[Thedoctor44]

There are no dump files in the folder.
Small Memory Dumps are of no use for 0x101 bugchecks, to properly analyse them we need Kernel Memory Dumps.

Follow these instructions on how to change to Kernel Memory Dumps.

http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Once changed wait for another BSOD, then upload the new dump file to a file sharing website like OneDrive.
The new dump file will be located in C:/Windows/memory.dmp.

Don't zip it up as it corrupts the dump file by compressing it.

 

[venkai]

Actually, the system was already set to receive kernel memory dumps.
For verification, running

wmic RECOVEROS get DebugInfoType in an elevated command prompt gives

DebugInfoType
2

What actually happened was that the BSOD lasted for a very long time (more than 20 mins), so I forcibly turned the system off (I thought the system froze). Probably it was writing dump information in the meantime. The system then turned back on without any problem. When I get the next BSOD, I guess I will wait till the system turns off by itself. Either way, is it normal for this much time to be taken to write the dump file ?
I have had past experiences with BSOD on different problems, and every time the system used to write the dump file almost immediately and automatically turn off in seconds.

I will re-post on this thread with the dmp file, the next time I get a BSOD.
Thanks for your time.

 

[Thedoctor44]

It shouldn't take that long at all.
We can try it again.

 

[venkai]

Hi,

I didn't receive any bsod since July 14th, but for the past 2 weeks, I have been receiving several of them.
The problem is that the screen freezes even during the bsod. I once waited for 2 hours for the bsod to naturally terminate, but it didn't. Upon forcibly turning off the laptop & restarting, I noticed that no dump files were created, although my system is set to create a "Kernel Memory Dump".

Should I wait longer than 2 hours, the next time I get a bsod ? I hope the cause isn't a hardware issue, since my laptop is beyond its warranty period. As far as "when" the bsod occurs, so far it has always occurred when I am browsing on chrome.

 

[venkai]

BSOD (0X00000101) hangs indefinitely, NO DUMP files produced!

To start with, my apologies for starting a new thread.
However, for reasons I believe are genuine, I do think my problem warrants a new thread.

My previous thread was

http://www.sevenforums.com/bsod-hel...-received-secondary-processor-0x00000101.html

I was advised to share my kernel memory dump file for debugging.
However, my crashes are such that no dump files are ever produced, and the BSOD simply hangs indefinitely until I forcibly turn the power off !
The longest I have waited for the BSOD to produce a dump file is 6 hours, which I believe is more than enough time to assume that something is seriously wrong.

I am running Win7 64 bit home premium.
My system is set to produce "Kernel Memory Dumps".
I have 8 GB ram, and have set the pagefile on the OS drive to ~12GB (just to be on the clear.)

Still, whenever this (0X00000101) clock interrupt bsod occurs, the bsod itself hangs. I haven't heard anyone else experiencing their "Bsod itself freeze."

Another thing I would like to point out is that this bsod has always occured when I am browsing on any internet browser. (I earlier thought this could be a chrome problem, but the bsod occurs even on firefox).
The bsod has never occurred any other time (like when I am doing something computationally intensive on MATLAB, or running a very heavy cuda C++ graphics library). The bsod has so far occured (randomly though) "only" when I am browsing on the internet, sometimes even during a google search ! Also the frequencies of bsod's off late have increased.


At this point, I seem to have exhausted all options, and the last thing I would want is for this to be caused by a hardware issue. I did run chkdsk /R and sfc.exe /scannow, but no problems were reported.

I also read in other forums, that this could be caused by an incorrect vcore voltage.

Any help at this point would be deeply appreciated.
I am having a financial crunch & am sincerely hoping that this is a software/ driver bug.
My first priority is to somehow get the system to produce the damned dump file, so that I could share it, for further debugging.

Thanks in Advance!