stop 0x00000101

[Adelin]

Hello
i can't translate my perfmon html log.
i tryed in regedit to edit perflib/009 to 00C key so counter should be in english but it won't work even if i set full right to system admin and users.
I'm sorry about it

Here is the story:

One month ago I applyed mx-4 thermal paste on my cpu .
my plastic grille that hold the cpu in the am2 socket broke one of my athlon 64 6000 89w pin.I had no difficulty to insert the processor that's strange.

from this time i get a bsod error:
Stop 0x00000101
this message happen while playing games surfing working or doing any task with the computer.
i searsh more information about this error.

It could be anything like cpu problem southbridge or integrated graphic chip overheating.

Recently i used bluescreenview to watch at my dmp log if i could find more info.

Ataport.sys and ntoskrnl. was reported.

ataport.sys is maybe related to a data transfer problem.

today i got the idea to swap my sata cable from sata1 to sata4 position.
surely it fixed stop 0x000001 bsod problem but i need a confirmation.




Msi one day told me my motherboard should be replaced cause the nb voltage need to be push up to 1.25v to let me run my comp without crashing.
If i use stock igp core frequency and auto voltage i won't be able to past the bios post message.
it end with a black screen ; display led switch from green to yellow state.

One day i should replace my motherboard soon for an Aod 780GX/128m motherboard from Asrock or cheaper models.

I would like to know if my cpu is broke ?


Ps
If you look at my dump log
ctoss2k.sys will appear in 3 bsod dmp.
It's just a problem with creative patchmix and creative drivers for my emu 0404
that will try to access os kernel a strange way.
Windows verifier will complain a device driver attempt to corrupt the system.
it has been caught resulting with a 0x000000c4 bsod.

I tryed any patchmix version +emu driver from 1.82 to win 7 beta 64bits pci and pcie version .
There is no way to fix currently.
i'm waiting for an answer from creative.

Thank you verymuch.

 

[Adelin]

processor at full load with a stresstest for two hours : 52°C core 1 56°C core2 56°C and mother board 40°C
multimeter same as bios voltage:
1.35v cpu
3.3v:3.424
+5v 4.970
+12v12.056
battery +3.4v

i tryed fussmark for two hours after the satacable position switch:
No crash at 1.25v nb and stock igp speed.

for a89w cpu 57°c is a bit hot at 4000rpm with stock heatsink+fan it reach same temp as 125w 6000+

I think sata 1 is broken it work fine on sata 4.

I'm sure it's almost solved hehe

 

[Adelin]

Hello i have another bsod:
I dunno if my cpu is faulty or motherboard or even soundcard cause i listend to music and one hour later it crashed.

IU don't want to change my components randomly i need to know what is in bad state.

Do you have any idea what could crash my system ?

thank you
Crash List


Created by using BlueScreenView

Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Computer Name Full Path Processors Count Major Version Minor Version Dump File Size 080311-31278-01.dmp03/08/2011 12:26:41 0x0000010100000000`0000006100000000`00000000fffff880`009e918000000000`00000001nsiproxy.sysnsiproxy.sys+1e7309c x64 C:\Windows\Minidump\080311-31278-01.dmp2157601287 409

 

[Adelin]

driver verifier tell me in a bsod that ctoss2k.sys tryed to access the kernel a way that is forbidden.
Is it possible when i reset driver verifier to default setting and hours later i get a stop 0x00000101 error with ntokrnkl it's been related to my emu soundcard ?

i have no errors with memtest86 running it for a day.
I have no error using chkdsk.
I have no error using HDAT2 with my samsung f3 500gb in ide mod.

Lol this is weird

 

[Adelin]

hey again.

I found a way to make my system crashing with stop 0x00000101 bsod.
I listen for streaming music. Eventualy 30 minute later i will get no sound and my mouse will act weird. it's like if my system was hanging two minutes before the bsod happen.
There was no increase at cpu temp.

That's strange cause using prigme 95 during 8 hours and furmark i had no crash.

I'm thinking if ntoskrnl.exe is the thing that appear in all my crash it's cause something is trying to access it a w<rong way .
ok i just realize reading BSOD Kernel Dump Analysis - Discussion - Tech Support Forum
the last driver listed is often colored in red and picked by bsod analyzer.

i'm still trying to investigate about it.Next step should be remove my emu0404 soundcard+driver and swapping to realtek integrated chip ...
I really need an advice
thanks


here is a report from who crashed:

[FONT=Segoe UI, Arial]Crash Dump Analysis [/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial][FONT=Segoe UI, Arial]Crash dumps are disabled for your computer.
[/FONT][/FONT]

[FONT=Segoe UI, Arial]On Wed 03/08/2011 23:14:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080411-32760-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7FD00)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009E9180, 0x1)
Error: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 02/08/2011 18:45:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080211-17487-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ctoss2k.sys[/FONT] (ctoss2k+0x478E)
Bugcheck code: 0xC4 (0xF6, 0x218, 0xFFFFFA8005337060, 0xFFFFF8800555B78E)
Error: [FONT=Segoe UI, Arial]DRIVER_VERIFIER_DETECTED_VIOLATION[/FONT]
file path: C:\Windows\system32\drivers\ctoss2k.sys
product: [FONT=Segoe UI, Arial]Creative Audio Product[/FONT]
company: [FONT=Segoe UI, Arial]Creative Technology Ltd.[/FONT]
description: Creative OS Services Driver (WDM)
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ctoss2k.sys (Creative OS Services Driver (WDM), Creative Technology Ltd.).
Google query: [FONT=Segoe UI, Arial]ctoss2k.sys Creative Technology Ltd. DRIVER_VERIFIER_DETECTED_VIOLATION[/FONT]


[/FONT]

[FONT=Segoe UI, Arial]On Tue 02/08/2011 18:28:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080211-18595-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ctoss2k.sys[/FONT] (ctoss2k+0x478E)
Bugcheck code: 0xC4 (0xF6, 0x21C, 0xFFFFFA8004FA3910, 0xFFFFF8800485E78E)
Error: [FONT=Segoe UI, Arial]DRIVER_VERIFIER_DETECTED_VIOLATION[/FONT]
file path: C:\Windows\system32\drivers\ctoss2k.sys
product: [FONT=Segoe UI, Arial]Creative Audio Product[/FONT]
company: [FONT=Segoe UI, Arial]Creative Technology Ltd.[/FONT]
description: Creative OS Services Driver (WDM)
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ctoss2k.sys (Creative OS Services Driver (WDM), Creative Technology Ltd.).
Google query: [FONT=Segoe UI, Arial]ctoss2k.sys Creative Technology Ltd. DRIVER_VERIFIER_DETECTED_VIOLATION[/FONT]


[/FONT]

[FONT=Segoe UI, Arial]On Tue 02/08/2011 17:36:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080211-18470-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ctoss2k.sys[/FONT] (ctoss2k+0x478E)
Bugcheck code: 0xC4 (0xF6, 0x208, 0xFFFFFA8004B44B30, 0xFFFFF880048B978E)
Error: [FONT=Segoe UI, Arial]DRIVER_VERIFIER_DETECTED_VIOLATION[/FONT]
file path: C:\Windows\system32\drivers\ctoss2k.sys
product: [FONT=Segoe UI, Arial]Creative Audio Product[/FONT]
company: [FONT=Segoe UI, Arial]Creative Technology Ltd.[/FONT]
description: Creative OS Services Driver (WDM)
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ctoss2k.sys (Creative OS Services Driver (WDM), Creative Technology Ltd.).
Google query: [FONT=Segoe UI, Arial]ctoss2k.sys Creative Technology Ltd. DRIVER_VERIFIER_DETECTED_VIOLATION[/FONT]


[/FONT]

[FONT=Segoe UI, Arial]On Tue 02/08/2011 14:57:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080211-30232-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7FD00)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009E9180, 0x1)
Error: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 02/08/2011 12:38:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080211-30482-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7FD00)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009E9180, 0x1)
Error: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 02/08/2011 01:19:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080211-30295-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7FD00)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009E9180, 0x1)
Error: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 02/08/2011 00:49:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080211-29983-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7FD00)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009E9180, 0x1)
Error: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial] Conclusion [/FONT]
[FONT=Segoe UI, Arial]8 crash dumps have been found and analyzed. 3 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

[FONT=Segoe UI, Arial]ctoss2k.sys (Creative OS Services Driver (WDM), Creative Technology Ltd.)[/FONT]

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.[/FONT]