Lots of BSoD's after new build! Please help!!!

x0160768

Member
Oct 31, 2007
41
0
0
Hiya guys, this is starting to drive me crazy so thought I'd ask here for some help.

Basically I've build a new system (see sig) and have installed a fresh copy of Vista Home Premium but keep being plagued by BSoD's. They flash up too fast for me to read them properly which doesn't help so basically my first question is, does Vista store the blue screen error messages anywhere?

I installed the hardware fine and loaded the motherboard with all the latest drivers from the Gigabyte website so that should be fine right? I'm also using the latest drivers for my 8800GT so that should be fine. Can't really seem to work it out. I ran memtest for about 4-5 hours and that didn't bring back any errors. I'm starting to think that there may be some dodgy hardware somewhere but need to rule out a driver issue first.

Can anyone help please?

Thanks.
 

cozumel

Senior member
Nov 29, 2007
337
0
0
Try relaxing the memory timings to 5-5-5-18 and up the voltage to 2.2v and see if that helps. If that is ok then you can tighten up timings again.
 

bwatson283

Golden Member
Jul 16, 2006
1,062
0
0
right click my computer, advanced tab, startup and recovery, uncheck the auto restart on failure.
Then come back and post what they say.
 

bwatson283

Golden Member
Jul 16, 2006
1,062
0
0
I am still thinking that it is a driver issue, the newest and fresh drivers don't always help. If you had older versions of the drivers, try doing a driver rollback. or find older ones from the web, they are out there somewhere.

And yes look at the specs for the hardware and make sure timings and voltage are at recommended levels.
 

x0160768

Member
Oct 31, 2007
41
0
0
Right, sorry it's taken me a while to get back. Lots of stuff to do.

Had another BSoD today. Basically I've reinstalled Vista and updated all the drivers so everything is fresh and up to date. I had a quick game on Crysis to monitor temps and look for instability but couldn't find any. Didn't really play for long though. I then exited Crysis as I realise I hadn't updated my mouse drivers (Logitech MX700) and whilst doing that I had a PAGE_FAULT_IN_NONPAGED_AREA BSoD. Any ideas?

I'll continue to look for more BSoDs.
 

x0160768

Member
Oct 31, 2007
41
0
0
Just had another one. Was uninstalling my mouseware drivers (so I could update them) and had to reboot. Just as windows was about to restart (heard the startup chimes) a BSoD hit saying MEMORY_MANAGEMENT. Looking to me like its a memory problem. Although this doesn't really make sense as I ran memtest for like 4 hours with no errors!? Could it be the video RAM? Is there anyway to test this?
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
Originally posted by: x0160768
Just had another one. Was uninstalling my mouseware drivers (so I could update them) and had to reboot. Just as windows was about to restart (heard the startup chimes) a BSoD hit saying MEMORY_MANAGEMENT. Looking to me like its a memory problem. Although this doesn't really make sense as I ran memtest for like 4 hours with no errors!? Could it be the video RAM? Is there anyway to test this?

Sure. Read my .sig and go to that web page and that will tell you how to t-shoot this. Let us know the output of !analyze -v in the debugger.
 

x0160768

Member
Oct 31, 2007
41
0
0
Right this is the latest one, when trying to start windows:

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 06fc5bb4
Arg3: 00000000
Arg4: 00000000

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




BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

TRAP_FRAME: 96bf3c5c -- (.trap 0xffffffff96bf3c5c)
ErrCode = 00000000
eax=06fc5b98 ebx=96bf3d14 ecx=00000002 edx=00000000 esi=871fd610 edi=000735c8
eip=81cb1dec esp=96bf3cd0 ebp=96bf3ce0 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!MiCheckVirtualAddress+0xe1:
81cb1dec f7401c00001000 test dword ptr [eax+1Ch],100000h ds:0023:06fc5bb4=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c8fbb4 to 81ca9ef2

STACK_TEXT:
96bf3c44 81c8fbb4 00000000 06fc5bb4 00000000 nt!MmAccessFault+0x106
96bf3c44 81cb1dec 00000000 06fc5bb4 00000000 nt!KiTrap0E+0xdc
96bf3ce0 81cab829 96bf3d14 96bf3d1c 735c8a9a nt!MiCheckVirtualAddress+0xe1
96bf3d4c 81c8fbb4 00000008 735c8a9a 00000001 nt!MmAccessFault+0x1a37
96bf3d4c 735c8a9a 00000008 735c8a9a 00000001 nt!KiTrap0E+0xdc
WARNING: Frame IP not in any known module. Following frames may be wrong.
01abfa9c 00000000 00000000 00000000 00000000 0x735c8a9a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c8fbb4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 470c2f52

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

Followup: MachineOwner
---------
 

x0160768

Member
Oct 31, 2007
41
0
0
And this is the other one I had earlier today:

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: f7a75cac, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 81ce8930, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)

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




WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0
f7a75cac

FAULTING_IP:
nt!ExDeferredFreePool+22c
81ce8930 895f04 mov dword ptr [edi+4],ebx

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: sidebar.exe

CURRENT_IRQL: 0

TRAP_FRAME: b1159afc -- (.trap 0xffffffffb1159afc)
ErrCode = 00000002
eax=fb855d48 ebx=fe2ee4b0 ecx=000001ff edx=00000000 esi=fb855cf0 edi=f7a75ca8
eip=81ce8930 esp=b1159b70 ebp=b1159bac iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ExDeferredFreePool+0x22c:
81ce8930 895f04 mov dword ptr [edi+4],ebx ds:0023:f7a75cac=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c8fbb4 to 81ca9ef2

STACK_TEXT:
b1159ae4 81c8fbb4 00000001 f7a75cac 00000000 nt!MmAccessFault+0x106
b1159ae4 81ce8930 00000001 f7a75cac 00000000 nt!KiTrap0E+0xdc
b1159bac 81ce8322 90200dc0 fef7f7d8 fef7fdd8 nt!ExDeferredFreePool+0x22c
b1159c10 90ae269e fe44e700 00000000 b1159c60 nt!ExFreePoolWithTag+0x7b8
b1159c20 90ae2b99 fe44e700 00000004 90ac5765 win32k!FreeObject+0x2b
b1159c2c 90ac5765 ff045008 90aca3ed ff1cecb8 win32k!REGION::vDeleteREGION+0x14
b1159c34 90aca3ed ff1cecb8 00004000 00000000 win32k!DC::vReleaseVis+0x39
b1159c60 90ad398d 00000001 80040ff7 00000001 win32k!GreSelectVisRgn+0xc3
b1159c78 90aec13e ff1cecb8 b1159d18 01a4f284 win32k!DeleteHrgnClip+0x79
b1159c94 90acc2a2 7601040f 00000001 b1159d18 win32k!ReleaseCacheDC+0x12a
b1159cac 90ad2095 ff213ae8 b1159cd8 b1852610 win32k!xxxEndPaint+0x13
b1159d34 81c8caaa 0001016a 01a4f244 01a4f288 win32k!NtUserEndPaint+0x66
b1159d34 773f0f34 0001016a 01a4f244 01a4f288 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
01a4f288 00000000 00000000 00000000 00000000 0x773f0f34


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExDeferredFreePool+22c
81ce8930 895f04 mov dword ptr [edi+4],ebx

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!ExDeferredFreePool+22c

FOLLOWUP_NAME: Pool_corruption

IMAGE_NAME: Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID: 0x50_W_nt!ExDeferredFreePool+22c

BUCKET_ID: 0x50_W_nt!ExDeferredFreePool+22c

Followup: Pool_corruption
---------
 

x0160768

Member
Oct 31, 2007
41
0
0
I'm going to try and move my RAM into different slots and see if that makes a difference in the meantime.
 

x0160768

Member
Oct 31, 2007
41
0
0
Originally posted by: cozumel
Try relaxing the memory timings to 5-5-5-18 and up the voltage to 2.2v and see if that helps. If that is ok then you can tighten up timings again.

How exactly do I change to timings? I saw that there is something in BIOS about upping the DDR2 voltage (which I tried but it didn't register in CPU-z by the way?) but I can't find anything about timings?
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
Go to Start/run/verifier<enter>/custom/individual settings/check the top 4/click next /restart

If you can't restart successfully after doing this just go into safe mode, go to start/run/verifier and turn everything off. (This verifier option is disabled in safe mode automatically.)

This will make your machine slightly more likely to BSOD (which is good) because once it does, you will have a better idea of what caused the crash. Once you crash, do an !analyze -v again of the latest dump(s), and you should have a better idea of what caused it.
 

x0160768

Member
Oct 31, 2007
41
0
0
Mmm...I did what you suggested and when I tried to boot up again it wouldn't even get as far as trying to boot windows. It would straight BSoD with an error about ROYAL.SYS and trying to write to read only memory? It didn't create any crash dumps. I guess because it was doing it before windows was loaded.
 

x0160768

Member
Oct 31, 2007
41
0
0
On a seperate note, my computer won't detect my SATA HDD whilst the tower is standing up anymore. It'll only find it when its on its side. Very weird.
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
Royal.sys is Paradox's Vista crack so you don't need to buy Vista.

Please buy Vista then get back to us.
 

Comanche

Member
May 8, 2005
148
0
0
Don't know if this will help you or not. I have a new built on a Gigabyte board too. I went through a bunch of BSOD until I found that the Easy Tune Program was causing all the interferance.