Solved BSOD on fresh morning startup.

theArtizan · Sep 16, 2012

Hi,

my first post and it's a big problem I have. Thank you in advance for any kind of help.
My computer specs are these:

Windows 7 Ultimate 64bit (SP1 updated)
Motherboard: Gigabyte EX58-UD5
Chip: Intel i7 920 2.67GHz
RAM: 12 GB (6sticks of 2Gb each)
Graphics card: nvidia gtx 285
HDD: 5 HDDs

Freezing at fresh morning boot!
During the night I shut down my computer (saving some electricity and I'm not downloading much, lol).
At first boot it shows all RAM and disc at check in the 1st DOS window.
During the end of August 2012 it started to freeze every second day.
I have a Logitech G500 mouse which has lights on it for showing the scroll wheel speed. Those never turn off, except when the PC if off.
When it froze the lights went off (completely dead) and so did the keyboard (no caps lock light). Couldn't do anything except hard rebooting the system.
As I did that it showed only 8GB RAM.
I went into BIOS and upped the voltage of RAM, after investigating on the internet about the Gigabyte EX58-UD5 problems recognizing all RAM.

After that it was good for a week and than it started again. I started to manually up the voltage of the VVT, reading several forums, but never into the PINK area or even in the RED. I was allways carefull.

BSOD at the morning boot!
Now for the past 2 weeks I've experienced BSOD several times, every time in the morning boot.
I thought maybe I set the BIOS voltage too high and revert everything back to AUTO settings except the RAM voltage I left at 1.6.
Now this morning as I boot, it happened again. After 5-10 minutes BSOD.
It rebooted itself (even though it never did before) and
- it failed to move from the first BIOS screen. It checked all RAM, but stopped at the 4th HDD. Didn't move forward. (Here it gives me thinking it's a HDD problem, maybe). I hard booted again, sadly.
- it stopped again just before the Welcome screen. You know the little Windows sign, that forms itself from 4 colors/corners. It FROZE and I hardbooted again.
- I tried a Window restore/repair but it was unable to repair anything.
- After that it rebooted again and I chose 'Start windows normally'.

I'm pretty confident that the PC will work without skipping a beat for the whole day, until I boot it up in the morning, where I'll have to go through this again.

Final note about BSOD:
Today (Sunday 16.9.2012) BSOD after 5-10 minutes (read above description).
Yesterday (Sat.) BSOD after 5-10 minutes, but after the hard reboot it went into Win normally.
Friday I turned it on only around 7PM and no problem untill 11PM when I shut it down for the night.
Thursday it froze in the first 5-10 minutes of morning boot.
Wednesday and Tuesday no problems...
I'm fighting with my PC instead of using it. Searching the internet for a solution instead of working.

If I had this PC for personal use (gaming, surfing the internet,...) I'd probably continue searching for a possible solution, but I have it for work (graphis desing, 3D artist) and I need it, without loosing countless hours checking the internet for possible solutions.

So I turn to you. You have experience I DON'T. You have probably seen these kind of problems before. I politely REQUEST your help to solve this.

Thank you again in advance for any help you will be able to provide.

P.S. I have attached 2 files.
TheArtizan.zip is the file created from the SF Diagnostic tools (Grab all) tutorial here on the site.
091612-21216-01.txt is the minidump file I changed the extension to TXT to attach it here.

P.P.S. Sorry for the long post, but I thought the more info the better.

koolkat77 · Sep 16, 2012

Welcome

All your dumps are corrupted. Could you upload them again following the instructions carefully,
:ar: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

theArtizan · Sep 16, 2012

I re-Grabbed everything again.
I hope it's good this time around.

cheers

koolkat77 · Sep 16, 2012

2 of your dumps still don't load.

Information I got from one:

BSOD Index STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR="Red"]BugCheck 1000007E[/COLOR], {ffffffffc0000005, fffff8800742143a, fffff880053f1618, fffff880053f0e70}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR="red"]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/COLOR]
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800742143a, The address that the exception occurred at
Arg3: fffff880053f1618, Exception Record Address
Arg4: fffff880053f0e70, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::FindResourcesForOneAllocation+31e
fffff880`0742143a 0fba635415      bt      dword ptr [rbx+54h],15h

EXCEPTION_RECORD:  fffff880053f1618 -- (.exr 0xfffff880053f1618)
ExceptionAddress: fffff8800742143a (dxgmms1!VIDMM_GLOBAL::FindResourcesForOneAllocation+0x000000000000031e)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000000000c4
Attempt to read from address 00000000000000c4

CONTEXT:  fffff880053f0e70 -- (.cxr 0xfffff880053f0e70)
rax=0000000000000000 rbx=0000000000000070 rcx=0000000000000001
rdx=fffffa800d172ad0 rsi=0000000000000000 rdi=fffffa800c4e2000
rip=fffff8800742143a rsp=fffff880053f1850 rbp=0000000000000000
 r8=0000000000000101  r9=0000000000000000 r10=0000000000000000
r11=0000000000000006 r12=0000000000000000 r13=0000000000000000
r14=fffffa800d172ad0 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
dxgmms1!VIDMM_GLOBAL::FindResourcesForOneAllocation+0x31e:
fffff880`0742143a 0fba635415      bt      dword ptr [rbx+54h],15h ds:002b:00000000`000000c4=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000000000c4

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ff0e8
 00000000000000c4 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::FindResourcesForOneAllocation+31e
fffff880`0742143a 0fba635415      bt      dword ptr [rbx+54h],15h

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

LAST_CONTROL_TRANSFER:  from fffff8800741e1cc to fffff8800742143a

STACK_TEXT:  
fffff880`053f1850 fffff880`0741e1cc : 00000000`00000000 00000000`00000000 00000000`00000001 fffffa80`00000000 : dxgmms1!VIDMM_GLOBAL::FindResourcesForOneAllocation+0x31e
fffff880`053f1910 fffff880`0743865d : 00000000`00000000 fffff8a0`00a45510 fffffa80`00000000 fffffa80`0db31770 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x738
fffff880`053f1ae0 fffff880`07438398 : fffff800`00b96080 fffff880`07437d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`053f1cd0 fffff880`07437e96 : 00000000`00000000 fffffa80`0db4e4c0 00000000`00000080 fffffa80`0c4bb010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`053f1d00 fffff800`0316bcce : 00000000`0296e64c fffffa80`0c4e1770 fffffa80`0973c040 fffffa80`0c4e1770 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`053f1d40 fffff800`02ebffe6 : fffff800`03040e80 fffffa80`0c4e1770 fffff800`0304ecc0 fffff880`0122b384 : nt!PspSystemThreadStartup+0x5a
fffff880`053f1d80 00000000`00000000 : fffff880`053f2000 fffff880`053ec000 fffff880`053f1400 00000000`00000000 : nt!KxStartSystemThread+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -d !dxgmms1
    fffff88007421148 - dxgmms1!VIDMM_GLOBAL::FindResourcesForOneAllocation+2c
	[ 8b:8a ]
1 error : !dxgmms1 (fffff88007421148)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

STACK_COMMAND:  .cxr 0xfffff880053f0e70 ; kb

FAILURE_BUCKET_ID:  [COLOR="red"]X64_MEMORY_CORRUPTION_ONE_BIT[/COLOR]

BUCKET_ID:  [COLOR="red"]X64_MEMORY_CORRUPTION_ONE_BIT[/COLOR]

Followup: memory_corruption
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR="red"]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/COLOR]
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800742143a, The address that the exception occurred at
Arg3: fffff880053f1618, Exception Record Address
Arg4: fffff880053f0e70, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::FindResourcesForOneAllocation+31e
fffff880`0742143a 0fba635415      bt      dword ptr [rbx+54h],15h

EXCEPTION_RECORD:  fffff880053f1618 -- (.exr 0xfffff880053f1618)
ExceptionAddress: fffff8800742143a (dxgmms1!VIDMM_GLOBAL::FindResourcesForOneAllocation+0x000000000000031e)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000000000c4
Attempt to read from address 00000000000000c4

CONTEXT:  fffff880053f0e70 -- (.cxr 0xfffff880053f0e70)
rax=0000000000000000 rbx=0000000000000070 rcx=0000000000000001
rdx=fffffa800d172ad0 rsi=0000000000000000 rdi=fffffa800c4e2000
rip=fffff8800742143a rsp=fffff880053f1850 rbp=0000000000000000
 r8=0000000000000101  r9=0000000000000000 r10=0000000000000000
r11=0000000000000006 r12=0000000000000000 r13=0000000000000000
r14=fffffa800d172ad0 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
dxgmms1!VIDMM_GLOBAL::FindResourcesForOneAllocation+0x31e:
fffff880`0742143a 0fba635415      bt      dword ptr [rbx+54h],15h ds:002b:00000000`000000c4=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000000000c4

READ_ADDRESS:  00000000000000c4 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::FindResourcesForOneAllocation+31e
fffff880`0742143a 0fba635415      bt      dword ptr [rbx+54h],15h

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

LAST_CONTROL_TRANSFER:  from fffff8800741e1cc to fffff8800742143a

STACK_TEXT:  
fffff880`053f1850 fffff880`0741e1cc : 00000000`00000000 00000000`00000000 00000000`00000001 fffffa80`00000000 : dxgmms1!VIDMM_GLOBAL::FindResourcesForOneAllocation+0x31e
fffff880`053f1910 fffff880`0743865d : 00000000`00000000 fffff8a0`00a45510 fffffa80`00000000 fffffa80`0db31770 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x738
fffff880`053f1ae0 fffff880`07438398 : fffff800`00b96080 fffff880`07437d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`053f1cd0 fffff880`07437e96 : 00000000`00000000 fffffa80`0db4e4c0 00000000`00000080 fffffa80`0c4bb010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`053f1d00 fffff800`0316bcce : 00000000`0296e64c fffffa80`0c4e1770 fffffa80`0973c040 fffffa80`0c4e1770 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`053f1d40 fffff800`02ebffe6 : fffff800`03040e80 fffffa80`0c4e1770 fffff800`0304ecc0 fffff880`0122b384 : nt!PspSystemThreadStartup+0x5a
fffff880`053f1d80 00000000`00000000 : fffff880`053f2000 fffff880`053ec000 fffff880`053f1400 00000000`00000000 : nt!KxStartSystemThread+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -d !dxgmms1
    fffff88007421148 - dxgmms1!VIDMM_GLOBAL::FindResourcesForOneAllocation+2c
	[ 8b:8a ]
1 error : !dxgmms1 (fffff88007421148)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

STACK_COMMAND:  .cxr 0xfffff880053f0e70 ; kb

FAILURE_BUCKET_ID:  [COLOR="red"]X64_MEMORY_CORRUPTION_ONE_BIT[/COLOR]

BUCKET_ID:  [COLOR="Red"]X64_MEMORY_CORRUPTION_ONE_BIT[/COLOR]

Followup: memory_corruption
---------

Suggestions:

Run memtest86+ on each stick for 8 passes preferably overnight:
:ar: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Do post back results.

I've also called a friend to take a look at your problem and suggest something.

theArtizan · Sep 17, 2012

Hi,

I ran memtest over night and it showed 0 errors.

Any other suggestions, perhaps?

I didn't have a BSOD or freezing now, since the Computer was on all night.

cheers

koolkat77 · Sep 17, 2012

To make sure that hard drive is good run disk check following this tutorial:

http://www.sevenforums.com/tutorials/433-disk-check.html

Hard drive scan usings SeaTools:

SeaTools | Seagate both long and short tests.

theArtizan · Sep 18, 2012

Just a minor update.

I've checked 3 of 5 discs yesterday. No errors or bad sectors.

10 minutes ago I have booted my PC (just woke up) and after 3 minutes the BSOD. It was a fast one. A second and then the PC rebooted itself.
I hit start Windows normally and here I am. Probably the PC will work fine untill tomorrow mornings boot.

I'm attaching today's SF diagnostic tools RAR file. I hope it grabbed it OK.

Now, I'm going to check the last 2 discs.

Have a nice day.

P.S. koolkat77, just a THANK YOU for the suggestions and help. I appreciate it.

koolkat77 · Sep 18, 2012

STOP 0x00000024: NTFS_FILE_SYSTEM BSOD Index

Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

If you are overclocking any hardware, please stop.

Problematic software

Code:

Start Menu\Programs\Autodesk	Public:Start Menu\Programs\Autodesk	Public
Start Menu\Programs\COMODO	Public:Start Menu\Programs\COMODO	Public
Start Menu\Programs\COMODO\COMODO Internet Security	Public:Start Menu\Programs\COMODO\COMODO Internet Security	Public
Start Menu\Programs\DAEMON Tools Lite	Public:Start Menu\Programs\DAEMON Tools Lite	Public

Please revert to factory clocks if you're overclocking.
Please uninstall Autodesk and all its components from add/remove programs. (You may install this back afterwards.)

- Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes:
(Most preferable = Microsoft Security Essentials - Free Antivirus for Windows)
- uninstall the Comodo Internet Security from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Comodo Internet Security using this free tool: http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN http://forums.comodo.com/index.php?action=dlattach;topic=17220.0;attach=17692 (Requires registration)
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

Scan the system once you've installed and updated MSE

Run the system file checker for damaged windows files:
:ar: http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
Use Speccy to monitor all hardware temperatures:
:ar: Speccy - System Information - Free Download

Also look for a update on your BIOS version

Code:

BIOS Version/Date	Award Software International, Inc. F12, [COLOR="Red"]11.3.2010[/COLOR]

Let me know if you get more blue screens

theArtizan · Sep 19, 2012

Hi,

yesterday I checked the final 2 discs, no bad sectors no errors.

So, I decided I would put the BIOS in default factory settings and see from there. I think that I only manually set the Voltage of RAM to 1.5 and put everything back to AUTO (as set originally) last week.

Anyways, I booted up the PC, in the first DOC window it checked all 12Gb RAM normally and all 5 HDDs.
I hit DEL to go into BIOS and there I hit F11 to save the settings I changed (I'm paranoid like that).
I hit enter without changing the name of the profile and it gave me a warning that it did not save because I didn't change the name. I hit F11 again and changed the name and hit ENTER.
Nothing happened. The PC froze completely. The keyboard was dead. (I'll mention also that the light on the mouse (scroll wheel speed monitor) was ON. Might not be important, but it's just an additional info.)
- I wait, to see if BIOS wakes up but nothing. I hardboot the PC. It arrives to the Starting Windows screen (black background, Windows LOGO) and the monitor looses signal, even if the PC sounds normal, no rebooting.
- I hardboot again. It arrives again to the Starting Windows screen and freezes there. I leave it to see if it goes into Windows again. Nothing.
- I hard boot again and this time it goes normally into Windows.

As optimistic as I Am I'm slowly starting to get discouraged by all these problems. I have ZERO ideas what is going on here.
The RAM checked out good with MemTest, the DISCS checked out good as well.

The Power Supply is 650W, so it's not a lack of electricity at first boot.

Now, it has passed more than 30 minutes from the time the PC booted in Windows successfully and no freezes or BSOD, which means that are those first 3-5 minutes the problem.
Does my PC needs a fresh cup of coffe to start it's day? LOL

Have a nice day.

EDIT: I reverted the BIOS back to 'Fail-Safe defaults'. Atleast that's what was written in BIOS, heh.
Funny thing. As I came into Windows, it recognized a new hardware, a Floppy Disc (A). I DON'T even have a floppy disc. No use for it. My head is starting to hurt from all of this.

koolkat77 · Sep 19, 2012

Thanks for the feedback.

Were you able uninstall the programs I listed?
Monitor your computer temp with Speccy?

theArtizan · Sep 19, 2012

This is my plan of action for the next few days.

I'll see tomorrow morning what will happen. BSOD? Freeze?

If it freezes in Windows, I'll manually set the RAM voltage to 1.5, instead of leaving it on AUTO. I'll set ONLY this and leave everything else on default (mostly AUTO).

If I get a BSOD I will not uninstall Autodesk (those are the 3D apps I use to work. Basically my bread and butter). But instead I will format the whole system disc on Sunday and freshly install Windows (I already did that at the end of August 2012 when the first troubles started to appear with freezing.).

If after this I still have problems I'll be totally lost. 0 ideas what to do next.

I will definitely post feedbacks in any case. If it freezes or BSOD. I will also post if there are going to be NO problems for a couple of days. So at the least in the next couple of days.

Thanks for the Speccy heads'up. I didn't know that app. Will install it and check my PC temp.

Have a nice day.

EDIT: Speccy: nice app.
CPU: 44-50 C
Motherboard: 38 C
GraphicCard: 58 C
HDDs: system disc (34 C), other discs (42-43 C)

Anthony · Sep 19, 2012

I notice you have 12GB of ram, what are the sizes of each dims and what slots do they occupy? Also can you give me the memory info make, timings & Volts, you can get this info from speccy.

Thanks

Dave76 · Sep 19, 2012

This is known as the Cold Boot issue.
Usually caused by CPU and/or RAM, might be PSU related as well.

Are your CPU temps at idle or under load?

What brand and model of PSU do you have?

Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.
MB Intelligent Tweaker(M.I.T.)
CPU Vcore
DRAM Voltage
QPI/VTT Voltage

You motherboard manual GA-EX58-UD5 (rev. 1.0)

This information will help us to recommend RAM setting adjustments, sometimes with that much RAM you will need to make some adjustments. Not unusual to run for a while, even years, before having issues.

theArtizan · Sep 19, 2012

Hi,

here is the information you requested guys.

1.) I revert BIOS back to FAIL-SAFE defaults (like written in my previous post).

CPU Vcore: 1.3250V (set in bios to AUTO)
QPI/VTT: 1.150V (set in bios to AUTO)
DRAM: 1.500V (set in bios to AUTO)
IOH Core: 1.100V (set in bios to AUTO)

PSU: Antec signature 650W

I reverted BIOS back this morning after all the freezing and being unable to get into Windows. I'll see what happens tomorrow morning.

Thanks for any help in advance.

NOTE: One thing I've noticed. My RAM frequency are 540MHz, but I see in BIOS and on boot on the first DOS screen that it's always set on 1066MHz. This might mean nothing, but just writing as much as I notice. I'm not an expert in hardware, I'm a complete newbie. Don't want to or need to OVERCLOCK, just that my computer works.

View attachment 232492

View attachment 232493

View attachment 232494

View attachment 232495

View attachment 232496

theArtizan · Sep 20, 2012

Good morning or not.

Well, after reverting BIOS to factory 'fail-safe' settings this happend.

1.) booted fine into Windows7.

- after 5 minutes it FROZE.
- hardboot
- in the 'recovery window' (Safe mode, normal windows mode) my keyboard didn't work
- waited the 30 seconds and it booted into Windows

2.) Quick BSOD, so I couldn't see what was written.

- it booted with only 8GB of RAM.

3.) Suddenly after 5 minutes another BSOD (NEVER had I 2 sequential BSOD). This one stayed on the screen untill hard boot. I read MEMORY_MANAGEMENT

- I hardbooted again, again waited for the 30 seconds to pass, since my keyboard didn't work.

I don't know what to do. Maybe I'll set BIOS to 'Optimize settings' in the menu and see what tomorrow morning will bring.

Oh, yeah, now, with the third boot there are all 12GB RAM showing.

I'm attaching today's SF Diagnostics tools results/rar. I hope it grabed it OK.

Have a nice day.

Dave76 · Sep 20, 2012

If you get any more crashes, upload the complete set of crash files again.

RAM that is designated DDRx, DDR is Double Data Rate, so you will see it listed at 540 x 2 = 1080. Which is close enough to 1066MHz.

Did you buy all six RAM cards at the same time and place?
Are they the same brand and timings?

In your BIOS, MB Intelligent Tweaker(M.I.T.) > Advanced Voltage Control > DRAM Voltage change to 'Manual' and set to 1.550v.
On the same BIOS page, Advanced Voltage Control > QPI/Vtt Voltage change to 'Manual' and set to 1.200v.
Save and exit your BIOS.

Your last two crashes.

Code:

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
Probably caused by : nvlddmkm.sys ( nvlddmkm+10f61d )
IMAGE_NAME:  nvlddmkm.sys - nVidia Video drivers
FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+10f61d
-------------------------------------------------------------------
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes:  Device driver, memory, kernel
PROCESS_NAME:  uTorrent.exe
IMAGE_NAME:  win32k.sys
FAILURE_BUCKET_ID:  X64_0x1a_41284_win32k!FreeObject+58

This can still be a result of the RAM settings but does throw suspicion on your graphics card and driver.
What graphics driver are you using now?

First try the BIOS RAM settings adjustments, if you are still getting crashes then follow the suggestions below.

Did you uninstall the programs in post #8?
DAEMON Tools Lite - it's known to cause crashes in Windows 7

- Uninstall the Comodo Internet Security from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- Remove any remnants of Comodo Internet Security using this free tool: http://forums.comodo.com/index.php?a...0;attach=17692
- Download Microsoft Security Essentials - Free Antivirus for Windows for testing purposes.

We have seen many AVs cause issues, it is best to uninstall Comodo Internet Security for testing purposes.
You can re-install these programs if you want to after the source of the crashes is found.

Run the system file checker for damaged windows files:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

From System Event Log
There are a lot of these Comodo errors.

Code:

Event[699]:
  Log Name: System
  Source: Service Control Manager
  Date: 2012-08-23T06:19:25.426
  Event ID: 7030
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Davor-PC
  Description: 
The COMODO Internet Security Helper Service service is marked as an interactive service.  However, the system is configured to not allow interactive services.  This service may not function properly.

Event[1923]:
  Log Name: System
  Source: Service Control Manager
  Date: 2012-08-23T12:00:43.280
  Event ID: 7030
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Davor-PC
  Description: 
The COMODO Internet Security Helper Service service is marked as an interactive service.  However, the system is configured to not allow interactive services.  This service may not function properly.

'Throttle states' indicate your CPU is overheating.
There are several of these.

Code:

Event[4718]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-08-29T11:55:35.580
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Davor-PC
  Description: 
Processor 0 in group 0 exposes the following:

1 idle state(s)
10 performance state(s)
8 throttle state(s)

Event[4719]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-08-29T11:55:35.580
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Davor-PC
  Description: 
Processor 2 in group 0 exposes the following:

1 idle state(s)
10 performance state(s)
8 throttle state(s)

Event[4720]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-08-29T11:55:35.580
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Davor-PC
  Description: 
Processor 4 in group 0 exposes the following:

1 idle state(s)
10 performance state(s)
8 throttle state(s)

Event[4721]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-08-29T11:55:35.580
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Davor-PC
  Description: 
Processor 6 in group 0 exposes the following:

1 idle state(s)
10 performance state(s)
8 throttle state(s)

Event[4722]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-08-29T11:55:35.580
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Davor-PC
  Description: 
Processor 1 in group 0 exposes the following:

1 idle state(s)
10 performance state(s)
8 throttle state(s)

Event[4723]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-08-29T11:55:35.580
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Davor-PC
  Description: 
Processor 3 in group 0 exposes the following:

1 idle state(s)
10 performance state(s)
8 throttle state(s)

Event[4724]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-08-29T11:55:35.580
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Davor-PC
  Description: 
Processor 5 in group 0 exposes the following:

1 idle state(s)
10 performance state(s)
8 throttle state(s)

Event[4725]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-08-29T11:55:35.580
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Davor-PC
  Description: 
Processor 7 in group 0 exposes the following:

1 idle state(s)
10 performance state(s)
8 throttle state(s)

Event[15278]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2012-09-17T16:52:21.707
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Davor-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[15283]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-09-17T16:52:23.516
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Davor-PC
  Description: 
Processor 0 in group 0 exposes the following:

1 idle state(s)
10 performance state(s)
8 throttle state(s)

Event[15284]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-09-17T16:52:23.532
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Davor-PC
  Description: 
Processor 2 in group 0 exposes the following:

1 idle state(s)
10 performance state(s)
8 throttle state(s)

Event[15285]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-09-17T16:52:23.532
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Davor-PC
  Description: 
Processor 4 in group 0 exposes the following:

1 idle state(s)
10 performance state(s)
8 throttle state(s)

Event[15286]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-09-17T16:52:23.532
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Davor-PC
  Description: 
Processor 6 in group 0 exposes the following:

1 idle state(s)
10 performance state(s)
8 throttle state(s)

Event[15287]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-09-17T16:52:23.532
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Davor-PC
  Description: 
Processor 1 in group 0 exposes the following:

1 idle state(s)
10 performance state(s)
8 throttle state(s)

Event[15288]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-09-17T16:52:23.532
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Davor-PC
  Description: 
Processor 3 in group 0 exposes the following:

1 idle state(s)
10 performance state(s)
8 throttle state(s)

Event[15289]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-09-17T16:52:23.532
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Davor-PC
  Description: 
Processor 5 in group 0 exposes the following:

1 idle state(s)
10 performance state(s)
8 throttle state(s)

Event[15290]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-09-17T16:52:23.532
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Davor-PC
  Description: 
Processor 7 in group 0 exposes the following:

1 idle state(s)
10 performance state(s)
8 throttle state(s)

Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

theArtizan · Sep 20, 2012

Hi,

I did the System file checker and it passed OK, without any errors found.

Yes, I bought all 6 RAM stick together, all are the same brand (Kingston) and same timings.

I will set the VTT and DRAM manually as you suggested and I will uninstall today Daemon tools and I'll see what happens tomorrow morning.
If I still get BSOD and/or freezes, I will uninstall Comodo as well and again wait till next day. I will report back.

QUESTION for RealTemp. How do I stress (put it under load) the CPU to see the temp?

Thank you.

EDIT: In the DRAM window there was no 1.550 option, only 1.500, 1.540, 1.560,... So I set it on 1.540.

Dave76 · Sep 20, 2012

DRAM at 1.540 is ok.

Good news on SFC and the RAM info.

To get CPU high load temps, open RealTemp and a CPU testing program.
If you want to stress the system you can run OCCT.
OCCT stability checking tool
Run the CPU:OCCT test for at least 30 minutes, be sure to monitor your CPU and GPU temps.
Set the time before you start.
When its done, pass or fail, it will make some graphs. Post these here as they are useful for analyses.

Don't let the CPU core temp go over 73°C, if it does just stop the test.
Intel® Core™ i7-920 Processor

Let us know the results.

theArtizan · Sep 21, 2012

'Morning all.

Sadly problems still persist. I was confident that DAEMON tools might have been the problem, since I didn't have it installed before formating the disc end of August. Anyways, a short recap of my morning boot experience.

- booted fine.
- completely freezes after 3 minutes in Win7. This time I did not surf the internet or anything. I didn't touch it. Suddenly the led light on the mouse vanished and that means frozen.
- hard boot. Keyboard doesn't work in the (Safe mode, start windows normally,...) selection DOS window so I left the 30 seconds run to the end.
- after the 30 seconds it boots, but it does not go into Win, but it boots again and into Windows error recovery window. Since my keyboard doesn't work and Startup repair was highlighted and not Start windows normally after 30 seconds I was thrown into the Startup repair window.
- It gives me the option to set Win to a previous safe version. I decline, to see if it will repair windows. BAM, BSOD a second later (SYSTEM SERVICE EXCEPTION).
- crap. I hard boot again and this time I let windows revert back to a safer version, no repair of data was made.
- now it boot into windows fine, but with only 10MB of RAM usable (of 12 MB I have).

I'm really glad I'm a calm person, otherwise I'd already rip the computer from all the cables and threw it out the window.

Ah, a small joke to cheer me up.

There is no DUMP file today, since the BSOD happened in the Startup repair and not in Windows. If you want I can still grab everything with SF Diagnostic tools, but probably won't be any different than the yesterday one.

Anyways, I'll do the CPU stress test today and monitor the temp.
I'll uninstall COMODO internet security and install Comodo firewall. I had only firewall in the previous Windows install before reinstalling Win7.
If this fails and I get a freeze, BSOD tomorrow, I'll open the case, check if perhaps the RAM is not set properly in the motherboard. It's gonna be a pain, since I'm a big guy (big hands) and the CPU fan is in the way, so I'll have to remove it. (Kind of scared to do it, lol.)

Have a nice day all of you.

Dave76 · Sep 21, 2012

Try using a different keyboard and mouse, I have seen these cause all kinds of problems when they go bad.
Use wired if you can.

Let us know your results.

Solved BSOD on fresh morning startup.

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Member

My Computer

Endeavor to Persevere

My Computer

New member

My Computer

New member

My Computer

Endeavor to Persevere

My Computer

New member

My Computer

Endeavor to Persevere

My Computer

New member

My Computer

Endeavor to Persevere

My Computer