Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD on self built system (NEW)

29 Sep 2010   #11
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Quote   Quote: Originally Posted by Lemur View Post
Welcome to SF, tjtoste. Please complete your System Specs.

**EDIT**

Getting an error on Intel.ppm

Carl, what say ye?
I agree. I recommend Memtest and then Prime.


My System SpecsSystem Spec
.
29 Sep 2010   #12
tjtoste

Windows 7 Home Premium 64bit
 
 

I recently tried all of your suggestions and I ended up with a BSOD.

So here's what I've tried so far:

1. Uninstall Asus Utilities
2. Updated storage and marvell drivers
3. memtest86+ up to 7 passes as recommended

Attached is the recent zip file of the BSOD.

Thank you again.
My System SpecsSystem Spec
29 Sep 2010   #13
Lemur

Systems 1 and 2: Windows 7 Enterprise x64, Win 8 Developer
 
 

Don't see anything staring at me in files.

Try booting into safe mode and see if you get a bsod there. Let me know how that goes - bsod or no bsod.

Then boot normal and try this. Sorry, but it's a process of elimination...

Run Selective Startup using System Configuration
My System SpecsSystem Spec
.

29 Sep 2010   #14
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Follow Lemur's suggestion; it is a good one. If that doesn't show us anything. Test your CPU with Prime95.

https://www.sevenforums.com/tutorials...t-prime95.html
My System SpecsSystem Spec
01 Oct 2010   #15
tjtoste

Windows 7 Home Premium 64bit
 
 

Update:

Did Prime95 and ran Memtest86+ for 12 hours and both passed/stable.

I did only get at least 1 BSOD per day instead of the usual 6, but still 1 BSOD is making me wonder. Not sure what else I can do -- I suspect it's still a pesky driver.

Attached is a recent BSOD (10-2-10)

Also noted, I did reinstall win 7 with ACHI for the first time and it started to do this -- not sure if that's what caused it, but would reinstalling windows in sata instead solve it?
My System SpecsSystem Spec
01 Oct 2010   #16
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Good job on running the tests. That tells you that your CPU and RAM are probably OK. If going to ACHI was the change you made when these started to happen, I would have to suspect this change is involved. Try reinstalling SATA and see what happens. At least thing are improving a bit.

This latest dump is error code 1E, KMODE_EXCEPTION_NOT_HANDLED - usually causes are Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS. The dump does not us much.

Code:
Kernel base = 0xfffff800`02c67000 PsLoadedModuleList = 0xfffff800`02ea4e50
Debug session time: Sat Oct  2 04:12:47.805 2010 (GMT-4)
System Uptime: 0 days 3:40:36.757
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+5d3d952f02bcdb5c
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff88002f1ba68 -- (.exr 0xfffff88002f1ba68)
ExceptionAddress: fffff80002ce5025 (nt!PoIdle+0x0000000000000315)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000008
   Parameter[1]: 0000000014e60db1
Attempt to execute non-executable address 0000000014e60db1

TRAP_FRAME:  fffff88002f1bb10 -- (.trap 0xfffff88002f1bb10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000000aa rbx=0000000000000000 rcx=0000000000000001
rdx=fffff80002c67000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ce5025 rsp=fffff88002f1bca0 rbp=0000000000000000
 r8=0000000000000000  r9=0000000bd15ab13c r10=0000000000000f4e
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
nt!PoIdle+0x315:
fffff800`02ce5025 4084ff          test    dil,dil
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ccf46e to fffff80002cd7710

STACK_TEXT:  
fffff880`02f1ab58 fffff800`02ccf46e : 00000000`00000001 fffffa80`00000002 fffff880`02f1b2d0 fffff800`02d04668 : nt!KeBugCheck
fffff880`02f1ab60 fffff800`02cfd40d : fffff800`02ee5eb8 fffff800`02e1edac fffff800`02c67000 fffff880`02f1ba68 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f1ab90 fffff800`02d04a90 : fffff800`02e26b14 fffff880`02f1ac08 fffff880`02f1ba68 fffff800`02c67000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f1abc0 fffff800`02d119ef : fffff880`02f1ba68 fffff880`02f1b2d0 fffff880`00000000 fffff880`009f5001 : nt!RtlDispatchException+0x410
fffff880`02f1b2a0 fffff800`02cd6d82 : fffff880`02f1ba68 00000000`00000000 fffff880`02f1bb10 fffff880`009ea180 : nt!KiDispatchException+0x16f
fffff880`02f1b930 fffff800`02cd58fa : 00000000`00000008 00000000`00000000 ffffd863`33cf5b00 00001f80`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02f1bb10 fffff800`02ce5025 : 00000000`003bbda7 fffffa80`073d9dd8 fffff880`009f50c0 00000000`00000001 : nt!KiPageFault+0x23a
fffff880`02f1bca0 fffff800`02cdfebc : fffff880`009ea180 fffff880`00000000 00000000`00000000 fffff800`02d90230 : nt!PoIdle+0x315
fffff880`02f1bd80 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd40 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`02ccf46e 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

Followup: MachineOwner
---------
I can see that you have updated drivers; but I still find two that are slightly out of date.
Quote:
AsUpIO.sys Sun Jul 05 22:21:38 2009 - Asus PCProbe Utility ASUSTeK Computer Inc.-Support-. If you can't update this driver, try renaming it it. It will break your Probe utility; but you can always rename it back after you get your system stable. Navigate to C:\Windows\System 32\Drivers and rename it from .sys to .bak.

iaStor.sys Thu Jun 04 21:53:40 2009 - Intel Storage drivers http://downloadcenter.intel.com/Default.aspx
See what you can do with this drivers before you reinstall SATA. Post back and let us know.
My System SpecsSystem Spec
02 Oct 2010   #17
tjtoste

Windows 7 Home Premium 64bit
 
 

Quote   Quote: Originally Posted by CarlTR6 View Post
I can see that you have updated drivers; but I still find two that are slightly out of date.
Quote:
AsUpIO.sys Sun Jul 05 22:21:38 2009 - Asus PCProbe Utility ASUSTeK Computer Inc.-Support-. If you can't update this driver, try renaming it it. It will break your Probe utility; but you can always rename it back after you get your system stable. Navigate to C:\Windows\System 32\Drivers and rename it from .sys to .bak.

iaStor.sys Thu Jun 04 21:53:40 2009 - Intel Storage drivers http://downloadcenter.intel.com/Default.aspx
See what you can do with this drivers before you reinstall SATA. Post back and let us know.
Ok, so I updated Asus PCProbe Utility, but it was version II apparently? Not sure if that overwrite the original one, but here's the details:
ASUS PC ProbeII V1.04.86 Install Program for Windows 32/64bit XP & 32/64bit Vista & 32/64bit 7.

Also, I went in and changed AsUpIO.sys to .bak.

Last, I checked that iaStor.sys and apparently that date you gave me is the latest version on the Asus website. Not sure if there's a newer driver on intel, but I couldn't manage to find it.

Thanks again.
My System SpecsSystem Spec
02 Oct 2010   #18
tjtoste

Windows 7 Home Premium 64bit
 
 

Well here's something weird. I went and uninstall the intel storage driver and when I tried to install the new drivers, it said "This computer does not meet the minimum requirements for installing the software."

This was in my motherboard's cd software package, so it's not like i'm installing incompatible software. I believe this may be the cause of my BSOD.
My System SpecsSystem Spec
02 Oct 2010   #19
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Run SFC /SCANNOW. Go to Start and type in cmd.exe.
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator".
Type sfc /scannow at the prompt and press the Enter key. Post your results.

I will also ask one of the installation Guru's to take a look at this thread.

My System SpecsSystem Spec
02 Oct 2010   #20
tjtoste

Windows 7 Home Premium 64bit
 
 

I ran a scannow and it did not find any integrity violations.
My System SpecsSystem Spec
Reply

 BSOD on self built system (NEW)




Thread Tools




Similar help and support threads
Thread Forum
My first BSOD since i built new system - 0x0000001E
I built a new system myself with the following components: i7 2600k @ 4.5ghz asus p8p67 deluxe gskill ripjawsx 16gb 2133mhz @ 2200mhz asus eah4870 1gb crucial m4 64gb wd caviar black 500gb everything has been running smoothly for approximately 6 months, i have been very pleased with how...
BSOD Help and Support
BSOD at random times on new re-built Win 7 x64 system
I just re-built this system in early October 2011 and have had numerous BSOD at random times. I have not been able to identify any primary reason for the crashes. As I am not that skilled at reading dump logs to determine the cause I have come to the Forum for help. I have attached the dump log...
BSOD Help and Support
BSOD on newly built system
hey everyone i just built my new computer, yes it my first one i got it all assembled but im having problems with drivers im pretty sure thats what it is. this is the BSOD i get once in awhile playing Starcraft 2. Problem signature: Problem Event Name: BlueScreen OS Version: ...
BSOD Help and Support
BSOD newly built system
Just built up a 6 core AMD 1075T Asus M4A89GTD PRO 4 gig or ram ddr3 corsair dominator. Using 64 bit 7 and using on board graphics. Any Ideas would really help me out.:cry: Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.768.3 Locale ID: 1033 ...
BSOD Help and Support
New Built System BSOD HELL
I typed in the most common on Google, and it brought me to this forum! Perhaps you guys can help me out. The title of the error is BUGCODE_USB_DRIVER. I send along the dump file with this.
BSOD Help and Support
Newly Built System - Windows 7 BSOD.
Hello everyone, I am new to the forums here, and I am in dire need of some guidance please. I just recently put together a brand new build which hopefully you can see in my system specs. I did a clean install of Windows 7 Professional 64 - bit and have been having it BSOD on me with an...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 18:12.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App