Please help, BSOD on new Windows 7 x64 PC

[samster]

Hi All,

I bought a new PC with Windows 7 x64 and I get BSOD.
It happens less when I disable my onboard soundcard but It still happen.
Im using latest BIOS and drivers. I dont know what do do anymore.
It seems most errors are related to win32k.sys and ntoskrnl.exe.
Hope someone can help, its a brand new PC and I dodnt know what to do anymore.

I have attached some dump files.

Thanks in advance,

Lex

 

[samster]

Dont know if it helps but here is my Software I installed.

- As posted Windows 7 x64 with updates instaled
- Eve Online client
- Steam and Modern Warfare
- Teamspeak RC2
- MCAfee VS 8.7 patch 2

Hope someone can help me out please

 

[usasma]

H/W Diagnostics:
Please start by running these hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
**********************************************************************
This older driver may be affecting your system. Please either update it to a Windows 7 version, or uninstall it: hardlock.sys Thu Nov 30 12:12:07 2006

HARDLOCK.SYS is related to Hardlock Device Driver for Windows NT. Manufacturer: Aladdin Knowledge Systems Ltd. Aladdin - Software security, internet security, content security, dongle and USB solutions.

Beyond that there's no real information in the dump files. See if updating that driver fixes things - if not, post back and we'll see what else we can try.

 

[samster]

Thanks! will do and post back result asap.

 

[samster]

I did what you requested.

I searched my computer for programs responsible for that HARDLOCK.SYS and could find any. I'm not using any Aladdin software.
The only software I did not install myself (see post above) is PC Angel from Softthinks. I think it was pre-installed by the store where I bought the PC, its some sort of recovery software,

I runned Memtest and it showed no errors.

I used HD Tune to scan my drives as the Western Digital test utility (Diag504f) wasnt running (stuck on black dos screen when booting from the CD). It seems Intel doesnt have a test utillity to test the SSD drives. I did noticed there was a firmware upgrade available for the SSD so installed that.
HD Tune didnt show any problems with both of the drives.

Next (couple of minutes ago) I opened IE to go to this forum and there was a BSOD again, this one seems a little different as it is refering to TCP/IP.
I have attached the dump file.

Anything else I can do? Thanks in advance for any support!

 

[usasma]

I don't know about this test, but it purports to be an SSD tester, and it's free: Crystal Dew World
I've had the same issues with the Western Digital diags - and usually just try another diagnostic.

Let's leave the hardlock.sys alone for now (if you mess with PCAngel, it tends to break on you).

The dump file points to TCPIP.SYS - a component of Windows networking.
As such, I'd have to suggest that you do the following:

Driver Removal and Reinstallation
Please do the following:
- download a fresh copy of the latest Win7 version of the drivers for your Realtek network card from the Realtek website (not from Windows Update or from the Update driver function in Device Manager).
- uninstall the current version from your system
- install the freshly downloaded version
- check to see if you have any further BSOD's

I noticed that you have McAfee installed.
After replacing your networking drivers, if you continue to get BSOD's, try this:
Please download a free antivirus for testing purposes: Free AntiVirus
Then uninstall your McAfee software from Control Panel...Programs...Uninstall a program.
Then remove the remnants with this free tool: How to uninstall or reinstall supported McAfee consumer products using the McAfee Consumer Products Removal tool (MCPR.exe)
Then IMMEDIATELY install and update the free antivirus
Then test to see if that cures the BSOD's

Please post back if this doesn't fix things and we'll move on from there.

 

[samster]

Did not have the time to test and do everything but I managed to install the latest drive for my onboard NIC. PC was on yesterday for several hours without a crash.
Will keep you posted.

 

[samster]

I have uninstalled McAfee and used the removal tool. INow Im running MS Security Essentials with latest updates.
It looks like its going a bit better as Im getting less BSDOD but just got another one.

Can anyone take a look please, the fump file is attached.

 

[zigzag3143]

Hi All,

I bought a new PC with Windows 7 x64 and I get BSOD.
It happens less when I disable my onboard soundcard but It still happen.
Im using latest BIOS and drivers. I dont know what do do anymore.
It seems most errors are related to win32k.sys and ntoskrnl.exe.
Hope someone can help, its a brand new PC and I dodnt know what to do anymore.

I have attached some dump files.

Thanks in advance,

Lex

Hi and welcome

these are all similar, yet not identical. they point to a memory problem.

I would
download memtextx86 and run it a long time like hours. it will both test the ram and check to see if there us a heat issue.

run a system file check to verify and repair your system files to do that
type cmd in search>right click and run as admin>sfc /scannow

121809-11653-01.dmp    12/18/2009 7:53:30 PM    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED    0x1000007e    ffffffff`c0000005    fffff800`031d8c9c    fffff880`033e0578    fffff880`033dfdd0    fltmgr.sys    fltmgr.sys+1b52                    
121409-36504-01.dmp    12/14/2009 6:39:40 PM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff800`02ee094b    fffff880`0887dfc0    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    
121709-10296-01.dmp    12/17/2009 10:04:20 PM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff800`033c22fe    fffff880`0a0590e0    00000000`00000000    win32k.sys    win32k.sys+2e785                    
122009-9843-01.dmp    12/20/2009 5:57:00 PM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff800`030930a9    fffff880`09bea620    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    
121609-10374-01.dmp    12/16/2009 4:15:34 PM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    fffff800`0112d9f8    00000000`00000008    fffff800`0112d9f8    00000000`00000000    win32k.sys    win32k.sys+a5632                    
121709-10342-01.dmp    12/17/2009 9:40:22 PM    KMODE_EXCEPTION_NOT_HANDLED    0x0000001e    ffffffff`c0000005    00000000`00000000    00000000`00000008    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\121409-36504-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e62000 PsLoadedModuleList = 0xfffff800`0309fe50
Debug session time: Mon Dec 14 12:37:36.396 2009 (GMT-5)
System Uptime: 0 days 2:39:55.504
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002ee094b, fffff8800887dfc0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+13b )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff80002ee094b, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800887dfc0, 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!KiInsertTimerTable+13b
fffff800`02ee094b 488b42f8        mov     rax,qword ptr [rdx-8]

CONTEXT:  fffff8800887dfc0 -- (.cxr 0xfffff8800887dfc0)
rax=0000000000000002 rbx=fffffa8006df3c20 rcx=0000000000000002
rdx=fffdf88002f66cc8 rsi=0000000000001940 rdi=fffff88002f63180
rip=fffff80002ee094b rsp=fffff8800887e9a0 rbp=fffff88002f66cc8
 r8=ffffffffffffff55  r9=00000000000000ba r10=fffff88002f63180
r11=fffff88002f63100 r12=fffff88002f66cc8 r13=0000000000000001
r14=0000000000000000 r15=00000016576d0dba
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
nt!KiInsertTimerTable+0x13b:
fffff800`02ee094b 488b42f8        mov     rax,qword ptr [rdx-8] ds:002b:fffdf880`02f66cc0=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002ee094b

STACK_TEXT:  
fffff880`0887e9a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInsertTimerTable+0x13b


FOLLOWUP_IP: 
nt!KiInsertTimerTable+13b
fffff800`02ee094b 488b42f8        mov     rax,qword ptr [rdx-8]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiInsertTimerTable+13b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

STACK_COMMAND:  .cxr 0xfffff8800887dfc0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!KiInsertTimerTable+13b

BUCKET_ID:  X64_0x3B_nt!KiInsertTimerTable+13b

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

 

[samster]

Thanks for the advise. I will run memtest over a long period tomorrow. Any idea how to make it run indefinitely, last time I did it finished after about an hour.
Just got another BSOD, again a new one. Weird thing is lately it seems to happen everytime I start internet explorer.

The new BSOD is attached, hope it helps solving this issue.

 

[samster]

How long should I run Memtest? Running it for 4 hours no with no errors.
This is driving me nuts. is there anything else I can do to find out what the problem is?

 

[usasma]

Memtest should be run for a minimum of 3 passes (most agree with this, others suggest up to 7 passes).
All seem to agree that running it overnight is the best thing to do.

 

[samster]

Will it most like be a memory problem? I have been reading the OCZ and MSI forums and other people seem to have the same problem with this mobo and ram combo while memtest shows no problem for them either.

If the dump files are realy pointing towards ram problem I might just buy some other modules.

 

[usasma]

I've seen problems with Gigabyte boards (P45 series) and Asus P5 series boards - haven't dealt with many problems on MSI boards tho'.

If they're having issues with that combo - then I'd suggest following that advice there. I don't delve into memory timings and voltages (my opinion is that if you've gotta change things, the hardware isn't working right and should be replaced).

It's my opinion (from the BSOD's that I've seen) that this could be a software issue (driver) rather than a memory issue. Unfortunately for you - you've gotta decide which one to pursue (the memory settings or the software issue). Trying to do both at once will make it more difficult to figure out what's causing the problem.

 

[samster]

Bit weird, since I set DRAM voltage manually to 1.65v in the BIOS I have no crashes anymore

 

[usasma]

"Nothing succeeds like success"
Glad to hear that it's working for you!