BSOD "STOP : 0x00000101" on new system

[kjeehoe]

Hi,

i've recently getting this BSOD error randomly " A clock interrupt was not received on a secondary processor within the allocated time interval "on my new Shuttle XPC SH67H3 system. How it goes is that, at first the system was really stable, without any crashing issues, but recently, when i tried flashing my BIOS, i some how screwed it up and the PC doesnt POST .. so to cut it short, i've manage to changed to a brand new motherboard to replaced it with the faulty one, and that's where BSOD starts to happen ..

i thought at first i needed to do a clean install of windows 7 ultimate x64 again, but after reformatted and reinstalled windows 7, updating all to latest drivers, the problem still occurs, .. im getting random BSOD while playing games, while skyping, or even while watching movies.

i've did all the tests like Prime95, 3dmark11, memtest86 .. and it all show no errors or BSOD .. im really getting frustrated right now .. not too sure what causes it ..

i've also taken out the enitre system and reassemble it just to make sure everything is in place .. but im still getting the BSOD ..

question is that, could it be the motherboard that was replaced is also faulty? or there's something i've not done right?

my computer specification is;

Shuttle XPC SH67H3
Intel i5 2500
2x 4GB Team Elite DDR3 1333
MSI GTX 670
Crucial m4 128GB SSD
Western Digital 160GB HDD
Pioneer 16x DVDR-W

and the error i got from event manager is;

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 5/5/2012 11:23:12 AM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: xxxxx-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2012-05-05T03:23:12.481203500Z" />
<EventRecordID>1933</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>jeehoe-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>


Hope to get a solution to this problem. Cheers

 

[JMH]

How about giving us the latest DMPs...

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.
Please attach the DMP files to your next post not to post one.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[kjeehoe]

i cant seem to locate my "minidump" folder ??

it's not inside Windows folder ..

how do i access it?

Cheers

 

[JMH]

Some reasons for no DMP files include no page file, a page file smaller than your ram, a page file on another HD than the OS, UAC turned off, etc.

Have you searched the whole hard drive for *.DMP?

 

[karlsnooks]

kjeehoe,

[FONT=&quot]MEMORY DUMPS - REQUIREMENTS[/FONT]


Enable automatic management of the Paging file
WIN + PAUSE/BREAK key combo |
Advanced system settings (left-hand side) |
Advanced tab, Performance section, Settings |
Advanced tab, Virtual Memory section, Change |
checkmark Automatically manage paging file size for all drives |
OK | OK | OK



STARTUP AND RECOVERY SETTINGS
WIN + PAUSE/BREAK key combo |
Advanced system settings (left-hand side) |
Advanced tab, Startup and Recovery section, Settings |
System Failure section | checkmark Write an Event to the system log
| uncheck Automatically restart |


Under Write debugging information, select Small memory dump |
in the Small dump directory: box, enter %SystemRoot%\Minidump | OK


If you get a crazy message from Win 7 about your paging file being too small, then just ignore the message since we have already made sure that the paging file is set to be managed by Win 7.

ENABLE THE WINDOWS ERROR REPORTING SERVICE
WIN key | type SERVICES.MSC | ENTER |
Scroll down to Windows Error Reporting Service |
Rt-clk on Windows Error Reporting Service | Properties |
General tab | for Startup type, choose Automatic |
In Service status, Start button (unless grayed out) | OK


ASSURE THAT CCLEANER IS NOT DELETING DUMPS
CCLEANER | Cleaner icon | Windows tab | System category |
Uncheck Memory Dumps
· WINDOWS ERROR REPORTING SERVICE must NOT be disabled!
· WIN | Services.msc | Enter
· Under Name, locate Windows Error Reporting Service
· If Status is not Started, then
Right-click on Windows Error Reporting Service |choose START
· If Startup Type is not Automatic, then
Right-click on Windows Error Reporting Service |
choose Properties | General tab |
set Startup type to Automatic
· Close Services.msc (I like to use ALT + F4)

After a crash, the minidump file will be in C:\Windows\Minidump
===============================================