• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Not sure where to put this thread

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

kamakasi

Member
Joined
Dec 20, 2013
Location
Erie County
Ok Windows 7 64 bit ULTIMATEEEEEEEE

computer is oc'ed now every once in awhile i get the FATAL BLUE SCREENNN

Says dumping memory or something of that matter. Why would it be doing that?

Any other info let me know.

Rusty
 
two things come to mind, crucial memory and low v core.
will a mod move this to amd cpu's please?
 
Disable Auto Restart so you can see what BSOD says...

Here's How:

Click on the Start button and then on Control Panel.

Tip: In a hurry? Type system in the search box after clicking Start. Choose System under the Control Panel heading in the list of results and then skip to Step 4.

Click on the System and Security link.

Note: If you're viewing the Small icons or Large icons view of Control Panel, you won't see this link. Simply double-click on the System icon and proceed to Step 4.

Click on the System link.

In the task pane on the left, click the Advanced system settings link.

Locate the Startup and Recovery section near the bottom of the window and click on the Settings button.

In the Startup and Recovery window, locate and uncheck the check box next to Automatically restart.

Click OK in the Startup and Recovery window.

Click OK in the System Properties window.

You can now close the System window.

From now on, when a problem causes a BSOD or another major error that halts the system, Windows 7 will not force a reboot. You'll have to reboot manually when an error appears.

You should also have a .dmp file saved in the root of windows.
RGone...ster.
 
Ok Windows 7 64 bit ULTIMATEEEEEEEE

computer is oc'ed now every once in awhile i get the FATAL BLUE SCREENNN

Says dumping memory or something of that matter. Why would it be doing that?

Any other info let me know.

Rusty
How about give us info... system specs... what is the BSOD code... etc? You left nothing. Awfully hard to help without any information. :)
 
Like the ones in my signature or like

Windows 7 64 bit Ultimate

Have to wait for BSOD again

Last time i remember it said dumping memory with a percentage of course
 
OMG... not sure how I missed them, but yeah.

Just leave the code (once you get it, you are welcome to google it on your own and post it here so we are working on it from both sides).
 
CODE TIMEEEE

0x0000000A

0x0000000000000048

0x0000000000000002

0x0000000000000000

0xFFFFF80002EEA8E2
 
What's this?...
CODE TIMEEEE

0x0000000A

0x0000000000000048

0x0000000000000002

0x0000000000000000

0xFFFFF80002EEA8E2
Open Event Viewer and expand Critical, Application, or System logs - under "Windows Logs" (or look under "Summary of Administrative Events--> Event Type--> Critical) double click the specific / latest error so it opens in the Summary Page Events window. Next click on Copy--> Copy Details as Text in the RH pane, and paste the contents of the ClipBoard in this thread.

And upload the latest minidump (*.dmp) file, located in the C:\Windows\Minidump directory via the attachment icon (paperclip) on the Advanced Reply page. Also reset your overclock back to the default clock ("Load optimized defaults" in the BIOS), then change only those options that are absolutely necessary.
 
Log Name: System
Source: Disk
Date: 1/10/2014 1:32:08 PM
Event ID: 11
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Rusty-PC
Description:
The driver detected a controller error on \Device\Harddisk2\DR3.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Disk" />
<EventID Qualifiers="49156">11</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-01-10T18:32:08.279296800Z" />
<EventRecordID>9242</EventRecordID>
<Channel>System</Channel>
<Computer>Rusty-PC</Computer>
<Security />
</System>
<EventData>
<Data>\Device\Harddisk2\DR3</Data>
<Binary>0E04800001000000000000000B0004C003010000000000000000000000082D0000000000000000005FDA000000000000FFFFFFFF060000005800000000000000FF0006120C000010000000003C0000000000000000000000C000E10980FAFFFF0000000000000000100C041280FAFFFF0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>
 
Check the SATA and power cable connection between your SSD and the board. If possible, try another SATA controller port or another SATA cable.
 
No they are hooked up everything is up and running. I got all seperate parts to make the cable. im actually on the computer right now.

oh i get this everytime i restart too. just happpened recentally

error.jpg
 
Yea i got it and im gonna get new Sata cables as well as my new sata power cables and i will let u know the outcome i always thought maybe my ram voltage was too low or cpucore voltage. Thanks a bunch ill keep u updated
 
Back