Random BSOD

[lsuk]

Hello everyone,

I was wondering if you can help me out.
I got a brand new computer on Black Friday and everything was great until January 2nd. That is when my first BSOD happened. I hadn't installed anything recently, but all of a sudden I am getting frequent BSOD. I thought it was my Norton Internet Security, so I uninstalled that, but nope, got one today. If you can look into my minidump log and let me know the culprit, I would really appreciate it. I included all the minidumps I had since the 2nd of January. Thanks in advance.

 

[theog]

As unit is BRAND NEW, take back to retail to check out.

 

[Pauly]

Would prob be easier to return it as above, if you cant heres the breakdown

All dumps are different
0xBE ATTEMPTED_WRITE_TO_READONLY_MEMORY
0x3b SYSTEM_SERVICE_EXCEPTION
0xD1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
0x50 PAGE_FAULT_IN_NON_PAGED_AREA

This is probably a driver error, but to start with

Some things to try:
If your OCing stop until this is sorted
Check your drivers are up to date
Run HDD checks HD Diagnostic
Run RAM checks Memory Diagnostics
Open elevated command prompt(start>search>cmd.exe>right click run as admin)type>sfc /scannow

See how you get on post back your results
Hope this helps let us know if you need further assistannce

Paul

 

[lsuk]

Thanks for your quick response.
I wish I can return it, but the return policy has expired so I can't return it.
I called HP's technical support, but after running some test they said it should be a driver and not a hardware problem. I have tried the sfc / scannow last night, but no error was found. HP has a diagnostic program, which HP tech and I have ran 5 times. It test the memory and harddrive and the result shows that all the hardware is still intact. I also tried the verifier program to see if any drivers were causing the problem, but I haven't had a BSOD yet. Should I just go through each driver in device manager and update the drivers? All help is really appreciated.

 

[Pauly]

Yes i would update all drivers possible, but dont use the update driver feature or windows update actually go to the manufacturers website for each piece of hardware installed and manually get the lastest driver for that piece of equipment.

Not sure what program HP got you to run, might be worth running the diagnostics linked in the post above just to be on the safe side.

Other than that driver verifier is your best option IMO, if the problem remains it will blue screen sooner or later as driver verifier stresses out the driver concerned, if not the problem might be gone if you already updated some.

See how you get on, post back your results and we can help further if needs be
All the best

Paul

 

[lsuk]

Thank you Pauly for your quick response. I did update the Nvidia GE Force 9100 driver this morning and will try to update the audio drivers later tonight. I think it was from the drivers I downloaded from the HP drivers website. Hopefully after the two updates, there will no longer be any BSOD. I will continue to run verifier until the next BSOD. If you do not hear from me again, I want to say Thank You.

 

[Pauly]

No problem we are here to help
Hope all is ok for you now any probs post back and we`ll do are best to get them sorted for you

 

[lsuk]

Oh well, got the mega BSOD a few minutes ago. It was so bad that my computer didn't start again. Please find enclosed the minidump. Last thing i saw was a win32k.sys. Hope it aint that bad. Thanks for all your help. Much appreciated.

 

[lsuk]

Oh another thing, I didn't know what to do after the BSOD and my verifier. I was told to delete my settings, but I haven't yet. Since I go the BSOD, what do I do now? Do I just delete my settings? Is there some log I should provide? Please advise. Thanks.

 

[Tepid]

I recommend 2 things.

A. Take ti back for warranty work, let them figure it out, it's what you have the warranty for. (i wouldn't, but I'm a tech.)

B. Run the Diags discussed above. If RAM or Hard Driver are bad, it doesn't matter what else you try to do, checking all the dumps in the world ain't going to fix it.

I generally say, let the Memtest run 4 to 6 hours with 4G. I would say for you to let it run 6 hours minimum to 8 to 9 hours max. It does generally (not always) work out to about 1 hour per gig these days.

The reason is the way the Memtests work. I don't fully understand it myself, but just know, it's not testing every bit of ram in a single pass. If you get errors right away, you can be pretty sure you have bad ram. But, there are false positives and false negatives.

So, I generally run both Memtest86+ and Windows Memory Diags to double check against each other. I have found that Windows Memory Diags give far less false positives/negatives than Memtest86+ does.

Which leads me to "

- Windows Memory Diagnostic NO LONGER RECOMMENDED"
​

I would like to see an explanation why.. as I think this is unfounded.

 

[lsuk]

Thanks Tepid for the quick response. I really do not think it is the memory or the hard drive is I have only had this computer for less than 2 months. I haven't even open the case. I want to say it is a driver issue, but it seems like I can't seem to locate it. After reading some post from other users, I guess my small mistake was to update and download the optional items from windows update. However, it was 2 Nvidia files and my modem. I'm sure it isn't my modem, since I don't use it, but I just updated the Nvidia driver today. Although the optional files were some networking controll and system management controller. Isn't memtest to see if it is a memory problem? Thanks in advance.

 

[lsuk]

Like another guy said it is a nightmare. So I went to my device manager and rolled back all my drivers. However, when it restarted, I instantly got BSOD. Here is the latest two minidumps. Thank you.

 

[computersplus]

BSOD

Unplug any unneeded exteranl devices and see if the computer will start in safe mode if so via msconfig uncheck unneeded items on startup tab as well as uneeded items in the services tab then try a restart.

 

[zigzag3143]

Like another guy said it is a nightmare. So I went to my device manager and rolled back all my drivers. However, when it restarted, I instantly got BSOD. Here is the latest two minidumps. Thank you.

Hi and welcome



these were both probably caused by your video driver nvlddmkm.sys. I would at the very least uninstall it and reinstall a fresh copy.

I would also run a system file check. type cmd in search>right click and run as admin>sfc /scannow

Ken

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


Loading Dump File [C:\Users\K\Desktop\010810-24055-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a10000 PsLoadedModuleList = 0xfffff800`02c4de50
Debug session time: Sat Jan  9 00:32:26.522 2010 (GMT-5)
System Uptime: 0 days 0:00:16.598
Loading Kernel Symbols
...............................................................
..........................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff80000000000, 8, fffff80000000000, 0}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Could not read faulting driver name
Probably caused by : nvlddmkm.sys ( nvlddmkm+1e4cb )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff80000000000, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff80000000000, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb80e0
 fffff80000000000 

FAULTING_IP: 
+5d1a952f01cdd970
fffff800`00000000 ??              ???

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880031b5de0 -- (.trap 0xfffff880031b5de0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8008e0b000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80000000000 rsp=fffff880031b5f70 rbp=0000000109109000
 r8=00000000000002b6  r9=fffff80002cb5120 r10=fffff880031b5f70
r11=fffff880031b5f40 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
fffff800`00000000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b011e4 to fffff80002a81f00

STACK_TEXT:  
fffff880`031b5c78 fffff800`02b011e4 : 00000000`00000050 fffff800`00000000 00000000`00000008 fffff880`031b5de0 : nt!KeBugCheckEx
fffff880`031b5c80 fffff800`02a7ffee : 00000000`00000008 00000000`00000008 00000000`00000000 fffff800`02aa7ad2 : nt! ?? ::FNODOBFM::`string'+0x42907
fffff880`031b5de0 fffff800`00000000 : 00000000`00000008 00000001`09109000 fffff880`484c764e fffffa80`091611d0 : nt!KiPageFault+0x16e
fffff880`031b5f70 00000000`00000008 : 00000001`09109000 fffff880`484c764e fffffa80`091611d0 fffff880`0fecf4cb : 0xfffff800`00000000
fffff880`031b5f78 00000001`09109000 : fffff880`484c764e fffffa80`091611d0 fffff880`0fecf4cb 00000000`c000009a : 0x8
fffff880`031b5f80 fffff880`484c764e : fffffa80`091611d0 fffff880`0fecf4cb 00000000`c000009a 00000000`c000009a : 0x1`09109000
fffff880`031b5f88 fffffa80`091611d0 : fffff880`0fecf4cb 00000000`c000009a 00000000`c000009a fffff880`0fecf4cb : 0xfffff880`484c764e
fffff880`031b5f90 fffff880`0fecf4cb : 00000000`c000009a 00000000`c000009a fffff880`0fecf4cb 00000000`00000000 : 0xfffffa80`091611d0
fffff880`031b5f98 00000000`c000009a : 00000000`c000009a fffff880`0fecf4cb 00000000`00000000 00000000`00000000 : nvlddmkm+0x1e4cb
fffff880`031b5fa0 00000000`c000009a : fffff880`0fecf4cb 00000000`00000000 00000000`00000000 fffffa80`09109000 : 0xc000009a
fffff880`031b5fa8 fffff880`0fecf4cb : 00000000`00000000 00000000`00000000 fffffa80`09109000 fffff880`04485ee4 : 0xc000009a
fffff880`031b5fb0 00000000`00000000 : 00000000`00000000 fffffa80`09109000 fffff880`04485ee4 00000000`6a213097 : nvlddmkm+0x1e4cb


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+1e4cb
fffff880`0fecf4cb ??              ???

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  nvlddmkm+1e4cb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b07613e

FAILURE_BUCKET_ID:  X64_0x50_VRF_nvlddmkm+1e4cb

BUCKET_ID:  X64_0x50_VRF_nvlddmkm+1e4cb

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

 

[lsuk]

Great. I already rolled back my video driver and installed a fresh copy of the latest driver. I did the scan and nothing came up. While I am installing a fresh video driver should I stop the verifier? As I stated before I did what another poster said for verifier and waited for the BSOD. Would leaving verifier create more BSOD?

 

[lsuk]

I want to Thank all of you that contributed. Hopefully I won't need to come back. If I do, I will start another thread. Thanks again and hopefully you guys won't need to see me again.

 

[usasma]

Try this for your Driver Verifier settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[Tepid]

Thanks Tepid for the quick response. I really do not think it is the memory or the hard drive is I have only had this computer for less than 2 months. I haven't even open the case. I want to say it is a driver issue, but it seems like I can't seem to locate it. After reading some post from other users, I guess my small mistake was to update and download the optional items from windows update. However, it was 2 Nvidia files and my modem. I'm sure it isn't my modem, since I don't use it, but I just updated the Nvidia driver today. Although the optional files were some networking controll and system management controller. Isn't memtest to see if it is a memory problem? Thanks in advance.

Please understand that I am not saying it is or isn't either.
But, it doesn't matter how new/old parts are, they can break at anytime.

For most BSOD's there are mainly 4 plans of attack at troubleshooting

1. Boot system and hit F8 repeatedly till you get a menu, choose Last Known Good. But, if you successfully reboot after the BSOD into windows, Last Know Good is no longer viable.
............ A. Try a restore point to prior the problem (doesn't always work, not always an option)

2. Start uninstalling things (including updates and drivers) that were recently installed

3. Start Full Hardware Diags (Most times, this should be Number 2 as it is easier to test hardware than software, and if it is hardware related, you aren't wasting time with software which is a pain. So I generally say, it is never a bad idea to run hardware diags on a regular basis anyway and I usually do them before trying software.) Ruling out hardware (as long as the diags are run properly) is Always easier than software.

4. Nuke and Reload or a Repair Install

You can always try other things, such as SFC /scannow or System Repair.
But they don't always work either.

Also,, yes Memtest is for a RAM test. But, bad RAM can cause massive corruption of any files and cause BSOD's. Bad RAM can cause drastic problems on an otherwise perfectly working system.

Bad PSU and Failing HDD can also do these things.

The following is purely from memory and may be missing steps or not exact locations/descriptions....
For the Nvidia drivers......
Go to Guru3d.com and find the Forceware uninstaller, I think.
You will need to Go into Device Manager
Find the Nvidia Video Card
Right Click it and choose Update Driver.
Choose the option taht is not auto searching for a driver
You need install it as a Generic VGA driver
Then reboot
If it tries to install the Nvidia again, you will need to stop it, or re do the Generic VGA driver again and dont reboot
Then go into Add/Remove and try uninstalling them from there
You may also want to use the Unisntaller from Guru3d.
Then Install the latest drivers from nvidia website.

Sorry I can't be more specific, I am not at my system.