BSOD week after full system recovery.

[steeler7663]

Hey guys, last time i was here i wound up doing a full system recover on my hp, the thread is here :http://www.sevenforums.com/crashes-debugging/236485-bsod-computer-suddenly-slow-2.html#post2014395. Same issues as before. The blue screen popped up after about a two day period of extremely slow wireless internet (its blazing fast when i connect through the wire). I restarted the computer ran the diagnostic tool and it was alright for about an our. I came back from a night out and blue screened again. Last time i was told it was the drivers, i unistalled them reinstalled and it didnt help. Thanks again.

 

[Vir Gnarus]

Do you have any minidumps present in C:/Windows/Minidump directory? I personally don't see in the syslog that it ever made any, but in case it did, providing them would greatly expedite our analysis of this. If there hasn't been any made, then there's some disk I/O issue that's preventing them from being created during a crash, or your environment isn't set properly to make them. Make sure your paging file is located on your Windows partition and that its minimum size is set to at least the same amount as your RAM, and that you have more than 32GB of free space for your Windows partition. That will optimally ensure that the crashdump should be generated. Otherwise, having everything set up default by Windows should suffice as well.

I'm starting to think you may be suffering issues regarding your drive or memory, either of which will prevent successful crashdump generation (and will most likely explain your problems). Two tests you can run:

http://www.seagate.com/support/downloads/seatools/ (run all tests except advanced)

http://www.memtest.org (Run overnight, any red onscreen = bad memory)

Just as a note, if you're using an SSD drive, Seatools probably won't work, or will give false positives.

 

[steeler7663]

Yeah ill try that not sure if i have a SSD drive though. Im just confused im positive it bluescreened and it said it created a minidump. Ill see what the deal is then and run these test. thanks

 

[Vir Gnarus]

Did it say on the bluescreen it was dumping one or that the dump was complete? By default the system should restart after the dump has been completed successfully. If there is an I/O issue, it'll hang up during the dump process and the blue screen will continue to sit there until you manually restart it.

 

[steeler7663]

It was sitting at the blue screen and said windows stopped blah blah blah, due to : power state failure. If this is the first time blah blah then at the bottom it said minidump something then below that was minidump complete, and below that it said restart if this is the first time and such. :If it happens again ill make sure i take a picture of it.

 

[steeler7663]

Nothing came up as a problem with that scan. If im doing something wrong let me know, i am general half decent with computers but still a noob lol. It hasnt bluescreened since, i also restarted again internet back to normal for the most part. The whole wireless still is still a issue and boggles my mind.

 

[Vir Gnarus]

What scan was it, Seatools or Memtest?

Have you went ahead and gone to the HP website and downloaded and installed all latest drivers for your laptop? I know you said you uninstalled and reinstalled the drivers, but I'm not sure if you just reinstalled the old versions that came with the system or new ones available on the website. Also, you may wanna update your BIOS too while you're at it.

The slow wireless may be an incompatibility with your new router, which may or may not be related to your drivers, or the wireless device/router itself. Did you setup a new router in your house so you have two routers running, or did you buy it to replace one that was already running?

Also, this may be odd, but if you've only been getting blue screens after using this new N-router, try switching to the old router temporarily and see if the BSODs go bye-bye. If they do, I can only narrow it down to either an internal failure with your wireless device when dealing with N-traffic, or there some oddball compatibility fluke between your wireless device and the router. I personally point blame on your laptop's hardware (HP is an OEM reputed for having very flaky hardware).

 

[steeler7663]

Hm..Well ive gone to HP made sure they were all up to date. Here a question, is there a way to turn of the N signal of my car? The router i bought brodcasts in all signals so would there be a way to see? Also i wish i would have know, i steered clear of dell because the dells i buy always blow up so i tried hp instead.

 

[Vir Gnarus]

Unfortunately, HP is in the same ballpark as Dell, and in fact some recent huge customer satisfaction surveys showed HPs fizzle out moreso than Dells.

Anyways, I'm not sure what you mean by the router broadcasting in "all signals". N routers are backwards compatible with B and G routers if configured as such (which is by default), yes, but you can also set the channel for the wireless in order to avoid interference with it and other wireless routers/devices. 6 channel spread from the nearest router will suffice, so if you have one router set at channel 6, you'll want to set the other one to channel 12 or 1. Make sure they also are not positioned so close to each other.

Also, what do you mean for your car?

 

[steeler7663]

I meant card. I only have one router, but i know for a fact neighbors have routers too because i pick up a strong signal. Im going to try changing the channel if it doesnt work, I will probably wind up getting someone to look at it. Thanks for your help i really appreciate it.

 

[Vir Gnarus]

Oh, durp. Yeah, to be honest dealing with wireless is something that often has to be trained. I personally deal with wireless all the time and it's a royal pain, but is gratifying once you get it just right.

I'm not sure how to continue approaching the BSODs, though. Without any kind of dump file, we're kinda lost. If you can see the blue screen and tell us what it says, that'd be at least something to start off with. I'll need the code number, the name of the bugcheck (is in all caps), the 4 parameters next to it (4 long hex numbers in parentheses), and a driver name if it shows that up too (as in "probably caused by:" or something like that).

 

[steeler7663]

Yeah ill try and get that. The weird thing is windows is acting like the blue screen never even happened. Usually something pops up where it tells me the error and everything and i can see it but nothing this time its extremely strange.

 

[Vir Gnarus]

If you're having the system reboot instantly from a BSOD, you may need to force it to not do automatic restarting. Type "advanced system settings" in Start Menu, then go to Startup & Recovery settings, and uncheck "Automatically restart".

 

[steeler7663]

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA8007CD3060
BCP3: FFFFF80004938748
BCP4: FFFFFA800D6ECAB0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\082812-22401-01.dmp
C:\Users\Sal\AppData\Local\Temp\WER-547157-0.sysdata.xml



blue screened today i guess. I came home and windows was started with the pop up about a recent crash i made sure to copy this in case the mini dump doesnt work