BSOD on my brand new computer. Pulling my hair out!!!!

#1
Hello there,
I just built myself a brand new computer and I haven't been able to use on any regular basis without Win7 crashing with a BSOD. I decided to start over and had a friend re-install it again a few days ago but I am still crashing. Since the re-install I disabled the auto-restart so I could glimpse at the BSOD but it may as well be in Chinese. I am not very technical so I need some assistance. Here are the minidump files I have accumulated thus far. I don't know what any of this means. Can someone please help me? I spent $2200 on a new system only to have it unstable. From what I can yell I have the latest drivers for the MOBO and VGA card. Here is my build...

CPU: Intel Core i7 920
MB: Asus P6X58D Premium
RAM: Corsair Dominator DDR3 6GB 1600 (3x2GB sticks) (TR3X6G1600C8D)
VGA: XFX ATI 5870
HDD: WD Caviar Black 1 TB 32 MB Cache, 7200 RPM SATA II
Cooling: Corsair H50
Case: Coolermaster HAF 932
PWR: Corsair 1000HX 1000-Watt

Thanks for any help that can be provided
 


Attachments

ickymay

New Member
#2
Here is my build...

CPU: Intel Core i7 920
MB: Asus P6X58D Premium
RAM: Corsair Dominator DDR3 6GB 1600 (3x2GB sticks) (TR3X6G1600C8D)
VGA: XFX ATI 5870
HDD: WD Caviar Black 1 TB 32 MB Cache, 7200 RPM SATA II
Cooling: Corsair H50
Case: Coolermaster HAF 932
PWR: Corsair 1000HX 1000-Watt

Thanks for any help that can be provided
windows debugger came up with this for the first three
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

Unable to load image \SystemRoot\system32\drivers\Lycosa.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Lycosa.sys
*** ERROR: Module load completed but symbols could not be loaded for Lycosa.sys
Probably caused by : Lycosa.sys ( Lycosa+1267 )

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

2: 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:
+0
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: 2

LAST_CONTROL_TRANSFER: from fffff80002e69c2e to fffff80002e71ed0

STACK_TEXT:
fffff880`02f8bc38 fffff800`02e69c2e : 00000000`00000000 fffff880`03f0a3f1 fffff880`02f8c440 fffff800`02e9ee28 : nt!KeBugCheck
fffff880`02f8bc40 fffff800`02e97bed : fffff800`0307ec24 fffff800`02fb7a3c fffff800`02e00000 fffff880`02f8c3a0 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f8bc70 fffff800`02e9f250 : fffff800`02fbfb5c fffff880`02f8bce8 fffff880`02f8c3a0 fffff800`02e00000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f8bca0 fffff800`02ea082e : fffff880`02f8c3a0 fffff880`02f8c440 00000000`00000001 00000000`0000000b : nt!RtlDispatchException+0x410
fffff880`02f8c380 fffff800`02ece7c2 : fffffa80`00000000 fffffa80`07fe4000 fffffa80`07fff4c0 fffff880`03f8a54a : nt!RtlRaiseStatus+0x4e
fffff880`02f8c920 fffff880`039f1267 : fffffa80`087eddc0 00000000`00000000 fffffa80`078568b0 fffffa80`07856a00 : nt! ?? ::FNODOBFM::`string'+0xf63c
fffff880`02f8c9a0 fffffa80`087eddc0 : 00000000`00000000 fffffa80`078568b0 fffffa80`07856a00 00000000`00000000 : Lycosa+0x1267
fffff880`02f8c9a8 00000000`00000000 : fffffa80`078568b0 fffffa80`07856a00 00000000`00000000 fffffa80`087edf10 : 0xfffffa80`087eddc0


STACK_COMMAND: kb

FOLLOWUP_IP:
Lycosa+1267
fffff880`039f1267 ?? ???

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: Lycosa+1267

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Lycosa

IMAGE_NAME: Lycosa.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ac2e27e

FAILURE_BUCKET_ID: X64_0x1E_Lycosa+1267

BUCKET_ID: X64_0x1E_Lycosa+1267

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

2: kd> lmvm Lycosa
start end module name
fffff880`039f0000 fffff880`039f4f80 Lycosa T (no symbols)
Loaded symbol image file: Lycosa.sys
Image path: \SystemRoot\system32\drivers\Lycosa.sys
Image name: Lycosa.sys
Timestamp: Wed Sep 30 05:45:50 2009 (4AC2E27E)
CheckSum: 00014D02
ImageSize: 00004F80
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
from the first three crashes citing Lycosa+1267, lycosa.sys is I think your Razer Tarantula Keyboard Driver, try an unninstall or reinstall or use another keyboard for debugging purposes, possibly run sfc /scannow to see if theres a corrupted driver ?

the fourth .dmp file was
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88003e20ff0, fffff8800212e698, fffff8800212def0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a0 )

Followup: MachineOwner
---------
and for bucheck 0x1e naming dxgmms1.sys i would advise update or rollback your video drivers or change your video card ?

also for these 0x1e errors Probable Cause "win32k.sys" are normally caused by Invalid Memory or access violations - probably caused by hardware.

Test your memory to get consistent results by burning to CD (using an ISO burner) & running from boot memtest86+ for at least 5 passes and moving the sticks between slots to verify motherboard ram slots work as well as the ram sticks.

Also, check the motherboard bios for correct settings for Vdimm (RAM voltage, check the RAM maker's site for correct settings) and timings as well as all settings in general.

Also check your CPU (L2 Cache) by running prime95 for a cache-parity error on the CPU. This will detect an error in minutes if any.

make sure your BIOS is up to date and also replace or remove these drivers .........
pcouffin.sys fffff880`03ecb000 fffff880`03edf380 0x00014380 0x457584a2 05/12/2006 14:39:30
WUSB54GCv3.sys fffff880`03830000 fffff880`038fb000 0x000cb000 0x48ace7ab 21/08/2008 03:57:31
purendis.sys fffff880`039c4000 fffff880`039d0000 0x0000c000 0x490695a0 28/10/2008 04:31:28
pnarp.sys fffff880`039b8000 fffff880`039c4000 0x0000c000 0x4906a9ac 28/10/2008 05:57:00
as they are old and out of date ?

Patin-Couffin VSO Software is related to CD/DVD burning software
WUSB54GCv3.sys is possibly a linksys Compact Wireless-G USB Network Adapter ?
purendis.sys is possibly by Network Magic\Pure Networks, Inc and is your NDIS Relay Driver ?
pnarp.sys is likely a driver for this component ?

please take your time run and check all these tests if possible and let us know the results ?
 


#3
Ok, first I want to thank you for taking the time to look at my thread and help me! This is super frustrating. I am downloading the latest driver for my video card and installing it. It should be the same as the one I have now but I am gonna do it just cause you recommended it.

As far as the Razer Lycosa keyboard that I had... last night I became so aggravated with the damn thing causing me to crash that I disconnected it, uninstalled the software and packed it up and am sending it back. On one or two of the BSOD I did see the Lycosa mentioned and on a few other sites other had reported a problem. Better safe than sorry so I am just gonna get rid of it. Is there anything else I need to do than uninstall the software for the Lycosa?

Forgive the newbie question here but how do I find these specific drivers and uninstall them?

Patin-Couffin VSO Software is related to CD/DVD burning software
WUSB54GCv3.sys is possibly a linksys Compact Wireless-G USB Network Adapter ?
purendis.sys is possibly by Network Magic\Pure Networks, Inc and is your NDIS Relay Driver ?
pnarp.sys is likely a driver for this component ?

I found the the Patin-Couffin one and uninstalled it. The WUSB54GCv3.sys one is for my usb wireless adapter. If I uninstall it it will not work and I won't have internet... no?

Thanks,
Jim
 


#4
I reinstalled my driver software for the ATI 5870 and everything is and was up to date already.
 


#5
Looks like there was a BIOS update available so I updated to the latest version. I also used the MemOK feature of my motherboard to auto configure the RAM. I have no idea how to adjust timings or what it does so I used to auto feature.
 


#6
Ok, of the 4 drivers you told me to uninstall I uninstalled 3 of them, not the Linksys one though. I did a little research and found out how to locate and uninstall the ones you mentioned.

Over night I will run the memtest86. I ran Prime95 for about 10 minutes and came across no errors. Do you recommend I run the test longer?

I hope I am doing everything correctly, it kinda scares me uninstalling some things.

Thanks,
Jim

*******EDIT*******

Of course now I restart my system and the 2 Pure Network drivers are there again. I see there is a hidden folder in the ProgramData folder but I can't delete it because it says it's open in another program. I don't know what to do... ugh!
 


Last edited:
#7
Well, I tried uninstalling the 2 Pure Network drivers and seems they are gone now as they do not show up on the list. However, I can still not delete the folder for them in ProgramData.

I ran memtest86 for 9 passes overnight with 0 errors which is a good thing. I plan to run Prime95 for more than 20 mins today.
 


ickymay

New Member
#8
Ok, of the 4 drivers you told me to uninstall I uninstalled 3 of them, not the Linksys one though. I did a little research and found out how to locate and uninstall the ones you mentioned.

Over night I will run the memtest86. I ran Prime95 for about 10 minutes and came across no errors. Do you recommend I run the test longer?

I hope I am doing everything correctly, it kinda scares me uninstalling some things.

Thanks,
Jim

*******EDIT*******

Of course now I restart my system and the 2 Pure Network drivers are there again. I see there is a hidden folder in the ProgramData folder but I can't delete it because it says it's open in another program. I don't know what to do... ugh!
well you should only be removing drivers by uninstalling the program rather than simple deletes ?

for those last two drivers do you have >> this program installed ?

prime95 normally gives results in the first 10 mins but an hr or more wouldn't hurt.
memtest 86 overnight as 5 passes can take 7 hrs.

for your linksys Compact Wireless-G USB Network Adapter you need to track down the latest driver for your device.
 


#9
well you should only be removing drivers by uninstalling the program rather than simple deletes ?

for those last two drivers do you have >> this program installed ?

prime95 normally gives results in the first 10 mins but an hr or more wouldn't hurt.
memtest 86 overnight as 5 passes can take 7 hrs.

for your linksys Compact Wireless-G USB Network Adapter you need to track down the latest driver for your device.
I see no program installed for Pure Networks. I did however uninstall the drivers from the 'device manager' list. I have not been able to track down any sort of updated driver for my Linksys Wireless USB Adapter.

I did run memtest86 for 9 passes with no errors. I've had Prime95 running for about a half hour now with no errors as well.
 


#10
I see no program installed for Pure Networks. I did however uninstall the drivers from the 'device manager' list. I have not been able to track down any sort of updated driver for my Linksys Wireless USB Adapter.

I did run memtest86 for 9 passes with no errors. I've had Prime95 running for about a half hour now with no errors as well.
let's wait for the next crash unless of course you have fixed it :p
 


#11
let's wait for the next crash unless of course you have fixed it :p
I just looked under McAfee 'Program Permission' and I came accross this...

Pure Networks Platform Service
C:\Program Files (x86)\Common Files\Pure Networks Shared\Platform\nmsrvc.exe

and

Pure Networks Platform Assistant
C:\Program Files (x86)\Common Files\Pure Networks Shared\Platform\nmctxth.exe

Both of them have 'FULL' access. I do not however find anything to uninstall. Now I'm wondering if I damaged anything by uninstalling the drivers in the device manager.
 


Last edited:
#12
I just looked under McAfee 'Program Permission' and I came accross this...

Pure Networks Platform Service
C:\Program Files (x86)\Common Files\Pure Networks Shared\Platform\nmsrvc.exe

and

Pure Networks Platform Assistant
C:\Program Files (x86)\Common Files\Pure Networks Shared\Platform\nmctxth.exe

Both of them have 'FULL' access. I do not however find anything to uninstall. Now I'm wondering if I damaged anything by uninstalling the drivers in the device manager.
great bit of homework and from a search with google I found "nmctxth.exe is process associated with Pure Networks Platform Assistant. Pure Networks Platform Assistant and Network Magic helps to configure home network and solve network related problems as well as configure network related services."

I cannot see why you would need this program but if the drivers are there and loading then it suggests it's installed ?

is there an unninstaller in that folder or something in control panel\programs and features ?
 


#13
I could not find any uninstall .exe or anything like that in the Pure Netwoks Shared folder inside the 'Common Files' folder. I still cannot delete the Pure Networks Folder in the 'ProgramData' folder either. There is also nothing I can see to uninstall in control panel.

The drivers do not show up any more in the device manager since I uninstalled them.

I still want to thank you for your time in helping me. I am sure there are lots of others worse off than I.

Jim
 


Last edited:
#14
I could not find any uninstall .exe or anything like that in the Pure Netwoks Shared folder inside the 'Common Files' folder. I still cannot delete the Pure Networks Folder in the 'ProgramData' folder either. There is also nothing I can see to uninstall in control panel.

The drivers do not show up any more in the device manager since I uninstalled them.

I still want to thank you for your time in helping me. I am sure there are lots of others worse off than I.

Jim
np and if you find the pure networks software still causes problems you might find it by typing msconfig into your search from the start orb then go ot the start up tab and disable it if it's there, post a screenshot of that tab if your unsure ?

are you crash free at the moment ?
 


#15
Yes, at the moment I am crash free. I did end up deleting one of the Pure Networks folder I found as well as uninstalling the drivers like I said before. I have noticed that now I am no longer able to connect to my laptop to share files through homegroup. Well, that's not entirely true. I can connect from my desktop to my laptop and transfer files that way. But if I am on my laptop it will not recognize my desktop. I think the Pure Netwoks stuff had something to do with this.
 


#16
Ok, well I just had my first BSOD in the past few days. I thought I was just about done with all of them and I go and get another few. Here are the latest... any ideas? Keep in mind I am overclocking to 4.20GHz on a i920. Dunno if that makes a difference or not. Thanks in advance!

Jim
 


Attachments

Last edited:

Captain Jack

Extraordinary Member
#17
Ok, well I just had my first BSOD in the past few days. I thought I was just about done with all of them and I go and get another few. Here are the latest... any ideas? Keep in mind I am overclocking to 4.20GHz on a i920. Dunno if that makes a difference or not. Thanks in advance!

Jim
Hello Jim,

Overclocking often ends up in BSOD. To make sure that's not the case reset it back to Normal and see whether it fixes it. Check for latest BIOS updates. I guess the crash has happen while "uDigital Theat" was running. Whatever that files or Program is make sure it works fine with Windows 7.

Bugcheck Analysis

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800031b31c8, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800b45b5f0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
nt!MiRelocateImageAgain+48
fffff800`031b31c8 f0480fba2e00    lock bts qword ptr [rsi],0

CONTEXT:  fffff8800b45b5f0 -- (.cxr 0xfffff8800b45b5f0)
rax=fffffa8009a82bb0 rbx=ffffffffffffffff rcx=fffffa80059e4960
rdx=0000000000000000 rsi=00fff8a007d6f000 rdi=fffffa8009a82b60
rip=fffff800031b31c8 rsp=fffff8800b45bfd0 rbp=0000000001000000
 r8=0000000000000000  r9=fffff8800b45be08 r10=fffffa80062eba80
r11=fffff8800b45bff0 r12=fffffa80059e4960 r13=fffff8a007d68000
r14=fffff8a007d68000 r15=fffffa8009956d30
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210286
nt!MiRelocateImageAgain+0x48:
fffff800`031b31c8 f0480fba2e00    lock bts qword ptr [rsi],0 ds:002b:00fff8a0`07d6f000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  uDigital Theat

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800031b31c8

STACK_TEXT:  
fffff880`0b45bfd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRelocateImageAgain+0x48


FOLLOWUP_IP: 
nt!MiRelocateImageAgain+48
fffff800`031b31c8 f0480fba2e00    lock bts qword ptr [rsi],0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiRelocateImageAgain+48

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

STACK_COMMAND:  .cxr 0xfffff8800b45b5f0 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x3B_nt!MiRelocateImageAgain+48

BUCKET_ID:  X64_0x3B_nt!MiRelocateImageAgain+48
Hope this helps,
Captain
 


#18
I did update my post with 2 or 3 additional BSOD minidump files. Any idea what the concensus is on those? Thanks a lot!
 


#19
Ok here are some more I got today. I'm ready to just give up on computers.
 


Attachments

#20
I don't think your WUSB54GCv3 usb wireless adapter is supported on windows 7 and could be causing problems ?

you need to unninstall the software and drivers and find a replacement or find some drivers that will support it with windows 7 ?

running this driver
WUSB54GCv3.sys fffff880`060b4000 fffff880`0617f000 0x000cb000 0x48ace7ab 21/08/2008 03:57:31
is likely causing problems ?

your bluscreen .dmp files are showing a full variety of errors some memory corruption and another with the networking subsystem and another with the main NT kernel so I would suspect you have an antivirus or third party firewall interfering with driver processes ?

If you are still using Mcafee unninstall it and use a cleaning tool to remove all traces then download and install MSE and use windows firewall ;)
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.
Top