Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD


  • Please log in to reply
42 replies to this topic

#1 SourCherry

SourCherry

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:02:27 PM

Posted 05 December 2012 - 07:08 PM

My computer been crashing alot, i scan but no virus. I also upgrade RAM but still happen. Please help

Attached Files



BC AdBot (Login to Remove)

 


#2 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:03:27 PM

Posted 05 December 2012 - 07:38 PM

Hello SourCherry,

Let's see if we can help you with your computer BSOD problem. These problems are often not simple so gathering as much information about your computer will be important.

1. ) Please download the following two files to your Documents folder.
2. ) Navigate to your Documents folder.
  • Right click on BSOD_Windows7_Vista_v2.64_jcgriff2_.exe and select, Run as administrator.
  • This will run autoruns as well and will create a new folder, Windows7_Vista_jcgriff2, within your Documents.
3. ) Run a System Health Report
  • Click START -> type perfmon /report , then click perfmon /report at top of column. .
  • After data collection, click File -> save as perfmon.html in your newly created "Documents\Windows7_Vista_jcgriff2" folder.
4. ) Zip up the Windows7_Vista_jcgriff2 folder.
  • Right click on the folder and select Send to --> Compressed (zipped) folder.
5. ) Please upload the zipped folder to a File Sharing website of your choosing because Bleeping Computer has a 512 K only upload limit and this file will be much larger.

In addition: To help us get a better look at your computer's hardware, please download and install Speccy by Piriform. (mirror site)
  • During installation, uncheck "Install the free Google Toolbar along with Speccy."
  • Run Speccy and from the top menu, select File --> Publish Snapshot. Click "Yes" to proceed.
  • Click, Copy to Clipboard and paste this address into your next post.

Regards,
Brooks



 


#3 SourCherry

SourCherry
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:02:27 PM

Posted 05 December 2012 - 08:40 PM

Windows7_Vista_jcgriff2 link:
http://www.mediafire.com/?a8209d3l6ygy1vg

Piriform Speccy address:
http://speccy.piriform.com/results/BUHsFdk8uweGjOluX28Tq7q

thank you,

#4 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:03:27 PM

Posted 06 December 2012 - 12:11 PM

Hi SourCherry,

All 37 of the bug checks from 10/25/12 to 12/05/12 were:

BugCheck 124
Probably caused by : hardware
WHEA_UNCORRECTABLE_ERROR (124)

To read about this error and perform troubleshooting steps, see Stop 0x124 - what it means and what to try.
  • Steps 1-5 (updating): Make sure to complete. Look for updates on your motherboard manufacturer's website.
  • Step 6 - Testing hardware:
  • Test both hard drives using SeaTools for DOS. Create a bootable CD.
  • Run both Short and Long tests. Both should "Pass."
  • If both hard drives pass SeaTools tests, please perform a Check Disk on each drive.
  • Check both boxes:
  • Automatically fix file system errors.
  • Scan for and attempt recovery of bad sectors
[/list][/list]
  • Use Event Viewer to view Check Disk results:
  • In the search box type "Event" and click on "Event Viewer" in top column.
  • Click on "Windows Logs" -->"Application."
  • Click the "Source" tab ( top, right) to alphabetize that column.
  • Arrow down to "Wininit." It will be an Event ID: 1001.
  • Select the most recent Check Disk report.
  • Double click on it and select the "Copy" button. This will copy the report to the clipboard.
  • Please paste this report into your next post.
[*]Test your computer memory by following this post: Windows 7 - RAM - Test with Memtest86+ to either create a bootable CD (Method 2) or bootable USB flash drive (Method 1) to run the test.
  • Once the computer is booted from the CD or USB flash drive, MemTest86+ with start automatically and continue until you stop it by pressing the ESC key.
  • Test only two memory modules at a time (Slot A1 + B1) then (Slot A2 + B2).
  • My recommendation would be to run each MemTest86+ at least overnight; 12 hours rather than just 7 passes.
  • There should be NO errors reported.
  • The test can be stopped (press ESC key) as soon as an error is reported.
  • See Part 3: If you have errors.
[/list]Let us know the results.

BSOD Bug check Information:
Spoiler

Regards,
Brooks



 


#5 SourCherry

SourCherry
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:02:27 PM

Posted 06 December 2012 - 02:28 PM

i download the Sea Tool DOS and burn into a disc image ( it was a DVD btw because i dont have CD)
I reboot but nothing happen

#6 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:03:27 PM

Posted 06 December 2012 - 03:17 PM

You have to make sure that your CD\DVDROM drive is set in Bios setup to boot first.
  • Restart the computer and press the <Del> key during the Power On Self Test (POST) to enter setup.
  • Arrow over to Boot (top menu) and press <Enter>.
  • Click on Boot device Priority and set the CD\DVDROM to boot first.
  • Press the F10 key to "Save changes and Exit."
  • Try booting from the DVD again.

If it still doesn't boot, it's possible that you didn't burn the SeaToolsDOS223All.iso file to DVD to make it bootable.
  • How to burn an "Iso" image to a disk:
  • Download ImgBurn from here.
  • Install the software then start ImgBurn.
  • Select "Write Image file to disk."
  • Under "Source" click on the "folder icon" Posted Image to the right and select the "iso" file location.
  • Click on this icon Posted Image to start the burning process.

Regards,
Brooks



 


#7 hamluis

hamluis

    Moderator


  • Moderator
  • 43,888 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:27 PM

Posted 06 December 2012 - 03:18 PM

It doesn't matter if you used a CD or DVD :).

Did you burn the SeaTools disk...according to instructions givey by Seagate?

Did you burn it as an .iso image?

http://knowledge.seagate.com/articles/en_US/FAQ/201271en

Burn ISO Using Imgburn - http://www.bleepingcomputer.com/forums/topic444375.html

Did you change the boot order in the BIOS...so that the burner is the first boot device?

Louis

#8 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:03:27 PM

Posted 07 December 2012 - 08:30 AM

Analysis of your System Events Log yields the following additional information:

Below are recent frequently re-occurring errors:

Event[51]:
  Log Name: System
  Source: Service Control Manager
  Date: 2012-12-05T16:03:56.314
  Event ID: 7006
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Cherry-PC
  Description: 
The ScRegSetValueExW call failed for FailureActions with the following error: 
Access is denied.
Googling the error, I found this AVG Forum post that recommends disabling AVG Self-Protection (see photo attached).


Event[187]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2012-12-05T11:13:26.967
  Event ID: 18
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Cherry-PC
  Description: 
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor ID: 5

The details view of this entry contains further information.
"Reported by component: Processor Core." Once the other hardware tests have been completed, we can run a stress test for the processor.


Event[198]:
  Log Name: System
  Source: Service Control Manager
  Date: 2012-12-05T11:13:26.016
  Event ID: 7026
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Cherry-PC
  Description: 
The following boot-start or system-start driver(s) failed to load: 
aiptektp
aiptektp.sys is a kernel mode Tablet driver from WALTOP International Corp. If you use a Tablet, you might try either updating the software or un-installing/re-installing.


Event[1875]:
  Log Name: System
  Source: Disk
  Date: 2012-11-29T22:43:49.653
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Cherry-PC
  Description: 
The driver detected a controller error on \Device\Harddisk2\DR2.
"The driver detected a controller error on \Device\Harddisk2\DR2." Along with running SeaTools for DOS and chkdsk, you should re-seat all hard drive data and power cables. If errors persist and you have an extra motherboard data port, you could move the Western Digital hard drive to a different port as a test.

Regards,
Brooks



 


#9 SourCherry

SourCherry
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:02:27 PM

Posted 07 December 2012 - 10:49 AM

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 12/6/2012 2:34:39 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Cherry-PC
Description:


Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
184576 file records processed.

File verification completed.
214 large file records processed.

0 bad file records processed.

2 EA records processed.

76 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
255258 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
184576 file SDs/SIDs processed.

Cleaning up 3395 unused index entries from index $SII of file 0x9.
Cleaning up 3395 unused index entries from index $SDH of file 0x9.
Cleaning up 3395 unused security descriptors.
Security descriptor verification completed.
35342 data files processed.

CHKDSK is verifying Usn Journal...
36877824 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
184560 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
216873315 free clusters processed.

Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

976657407 KB total disk space.
108750840 KB in 144164 files.
93840 KB in 35343 indexes.
0 KB in bad sectors.
319463 KB in use by the system.
65536 KB occupied by the log file.
867493264 KB available on disk.

4096 bytes in each allocation unit.
244164351 total allocation units on disk.
216873316 allocation units available on disk.

Internal Info:
00 d1 02 00 3e bd 02 00 fe ed 04 00 00 00 00 00 ....>...........
de 87 00 00 4c 00 00 00 00 00 00 00 00 00 00 00 ....L...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-12-06T22:34:39.000000000Z" />
<EventRecordID>7878</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Cherry-PC</Computer>
<Security />
</System>
<EventData>
<Data>

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
184576 file records processed.

File verification completed.
214 large file records processed.

0 bad file records processed.

2 EA records processed.

76 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
255258 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
184576 file SDs/SIDs processed.

Cleaning up 3395 unused index entries from index $SII of file 0x9.
Cleaning up 3395 unused index entries from index $SDH of file 0x9.
Cleaning up 3395 unused security descriptors.
Security descriptor verification completed.
35342 data files processed.

CHKDSK is verifying Usn Journal...
36877824 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
184560 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
216873315 free clusters processed.

Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

976657407 KB total disk space.
108750840 KB in 144164 files.
93840 KB in 35343 indexes.
0 KB in bad sectors.
319463 KB in use by the system.
65536 KB occupied by the log file.
867493264 KB available on disk.

4096 bytes in each allocation unit.
244164351 total allocation units on disk.
216873316 allocation units available on disk.

Internal Info:
00 d1 02 00 3e bd 02 00 fe ed 04 00 00 00 00 00 ....&gt;...........
de 87 00 00 4c 00 00 00 00 00 00 00 00 00 00 00 ....L...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
</EventData>
</Event>

#10 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:03:27 PM

Posted 07 December 2012 - 05:21 PM

Check Disk found and corrected some problems. Were you able to run SeaTools for DOS and if so, did both hard drives pass the long test?

Regards,
Brooks



 


#11 SourCherry

SourCherry
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:02:27 PM

Posted 07 December 2012 - 05:41 PM

Sea Tool DOS already run and yes both long and short passed, with both drive.

Mem test will be running tonight

"
"The driver detected a controller error on \Device\Harddisk2\DR2." Along with running SeaTools for DOS and chkdsk, you should re-seat all hard drive data and power cables. If errors persist and you have an extra motherboard data port, you could move the Western Digital hard drive to a different port as a test. "

I dont understand this and dont know how to move the motherboard.

Edited by SourCherry, 07 December 2012 - 05:47 PM.


#12 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:03:27 PM

Posted 07 December 2012 - 05:45 PM

OK. :thumbup2:

Regards,
Brooks



 


#13 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:03:27 PM

Posted 08 December 2012 - 10:02 AM

"The driver detected a controller error on \Device\Harddisk2\DR2." Along with running SeaTools for DOS and chkdsk, you should re-seat all hard drive data and power cables. If errors persist and you have an extra motherboard data port, you could move the Western Digital hard drive to a different port as a test. "

I dont understand this and dont know how to move the motherboard.

Is your computer still under warranty?

Did you purchase the computer or build it yourself?

Regards,
Brooks



 


#14 SourCherry

SourCherry
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:02:27 PM

Posted 09 December 2012 - 11:05 AM

My friend build this computer for me,

Btw the memtest is very confusing. after reboot then it auto run . There is no option for me to choose to test only 2. So i left it test over night and when i wake up maybe like 9 hours and i see it only at pass 3. and at the bottom screen it said pass complete, no error, press Esc to exit. But i still see it still testing. Then i press C to configure and i forgot wat i did and when i press 0 to continue and the pass column no longer 3, it starts running really fast with numbers. right now it like 150k

#15 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:03:27 PM

Posted 09 December 2012 - 11:49 AM

Hi,

Maybe your friend who built the computer could help you troubleshoot. If you don't feel comfortable opening the tower case, then you should seek professional assistance.

MemTest86+ will autostart and stop only if you press the ESC key. You can not select which memory modules to test from within MemTest86+. You will have to physically remove two memory modules from the motherboard in order to test two at a time. I suggested testing slots A1 + B1 (by removing modules A2 + B2) for overnight, then testing Slots A2 + B2 (by removing modules A1 + B1) the next night. If both sets of tests pass, then we know that the memory modules are good and that the motherboard slots are good. If any errors are recorded, we will have to proceed differently.

If you don't feel comfortable opening the case, then you should run MemTest86+ with all four modules for at least 7 full passes (24 hours +). The longer the test is run without errors, the greater the confidence that the memory is good.

I don't know why it didn't stop when you pressed the ESC key. You may have to reboot the computer and start again.

Regards,
Brooks



 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users