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: Win 7 64bit BSOD/Freezes/Reboots


13 Oct 2010   #1

Windows 7 Professional 64bit
 
 
Win 7 64bit BSOD/Freezes/Reboots

Hi guys. I'm here with a massive, mind-boggling annoying Win 7 64bit problem that - to be honest - I'm at the end of my tether with.

I purchased a Dell Studio XPS8100 (yeah, I should know better) a few months back and from day one I've been getting BSOD / random reboots almost constantly with it. Sometimes it'll do it as I'm logging on the machine or even during a boot-up, just resetting itself and starting again.

It happens randomly, from working with large files in Photoshop, browsing the net, to the machine idling with no programs open/in use and nobody using it and it will just die/freeze/reboot itself.

Dell, being the nice chaps they are, didn't want to know at first, but after much shouting sent an engineer out and he couldn't find anything wrong with it! They basically ended up replacing 2x HDD's (linked together as 1 HDD), CPU, motherboard, fans, power supply (but not the 8gb of ram strangely). As he put in the new motherboard it became apparent that one of the slots was broken on it (!) so another one would need to be sent out. He said it would work, but with only 6gb in it. So I said fine.

That night & weekend the machine never once fell over. When he came back with the new board and with the full 8gb back in, and was out the door, it froze/rebooted again. How I didn't throw it out of the window I don't know.

Seeing as the ram wasn't replaced, I asked Dell (yeah, I covered myself by getting written permission) If I could take one of the sticks out to see if it would behave on 6gb like it did the previous weekend.

Once I'd done that, it worked fine and left it at that (glad that I could finally get some work done!).

Fast forward to this past week and its returned to its old ways of BSOD/freezing/rebooting almost 5-8 times a day randomly with the 6gb in.

Before I start shouting at Dell again and demanding new ram, I've been reading this forum and thought I'd try and see if anyone can help out.

A few notes from reading other posts here:
  • I'm a noob when it comes to computers and stuff like this (hence I'm in this mess).
  • I run MSE, no other virus scanners etc (the machine originally came with one but the engineer never replaced it during the reinstall of Windows 7).
  • I've checked the Device Manger for yellow triangles (none) and tried updating all the drivers through it, but they all come back as 'Latest driver installed'.
  • I ended turning Windows Update off as during before it was updated by the Dell engineer WinUpdate was set to download/install things by itself, but this only seemed to accelerate the number of times it would fall over. Once the reinstall was done I switched all updates off and it hasn't updated since. I know the patches are useful but it just seem to make the machine worse, not better.
Specs:
System Manufacturer/Model Number Dell Studio XPS 8100
OS Windows 7 Professional 64bit
CPU Intel Core i5 650 @ 3.20GHz
Motherboard Dell Inc. 0T568R (CPU 1)
Memory (8.0GB) 6.0GB Dual-Channel DDR3 @ 665MHz (9-9-9-24)
Graphics Card NVIDIA GeForce GTS 240
Sound Card Realtek High Definition Audio
Monitor(s) Displays DELL E228WFP @ 1680x1050
Screen Resolution 1680x1050
Keyboard Standard Dell unit
Mouse Standard Dell unit
Hard Drives 1954GB Volume0 (SCSI) - 2x 1TB HDD's

Hopefully there is an answer somewhere, that doesn't involve wrestling with Dell for weeks on end to get some new bits, or worse, the machine sent back whilst I twiddle my thumbs unable to do any work / borrow a spare machine.

Sorry for the long post too - thought best to try explaining everything upfront to save time going backwards/forwards on things.

Thanks in advance.
Daz.

My System SpecsSystem Spec
.

13 Oct 2010   #2
Microsoft MVP

 
 

Only one memory dump present in the upload - it's from today (13 Oct).
Please follow the directions here to check and see if the system is set for minidumps:Set MiniDump

I suggest starting all troubleshooting with the following diagnostic tests (in this case, to double check the previous work). They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:
Quote:
H/W Diagnostics:
Please start by running these bootable 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)
Here's a link to a brief description of the error message: BSOD Index
As this points at a driver, let's run Driver Verifier according to these instructions:
Quote:
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/Windows 7 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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

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:
Code:
Delete these registry keys (works in XP, Vista, Windows 7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Oct 13 08:17:08.056 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:36.664
BugCheck DE, {2, fffff8a000f0e390, fffff8a000f0e3c1, 14d3588c0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2d2e0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xDE
PROCESS_NAME:  System
Bugcheck code 000000DE
Arguments 00000000`00000002 fffff8a0`00f0e390 fffff8a0`00f0e3c1 00000001`4d3588c0
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
My System SpecsSystem Spec
14 Oct 2010   #3

Windows 7 Professional 64bit
 
 

Thanks usasma - I'm going to work on this today so will report back when I've gone through it all.

Daz.
My System SpecsSystem Spec
.


15 Oct 2010   #4

Windows 7 Professional 64bit
 
 

Hi,

I've run through all the suggestions and this is the outcome:
  • Set Minidumps - OK and working.
  • Memory Diagnostics - OK & no errors - 7 passes over 9.5 hours.
  • HD Diagnostics - OK - No errors
  • Set up Driver Verifier - OK - Reboots okay and was collecting info between crashes.
  • Malware Check - OK - Used saftey.live.com
I've attached the latest dumps & a new health report. I'm not sure how many dumps there are or how many you want so if there isn't enough I can do more.

Thanks in advance.
Daz
My System SpecsSystem Spec
15 Oct 2010   #5
Microsoft MVP

 
 

OK, the latest dumps aren't Driver Verifier Enabled memory dumps.

So, please run Driver Verifier again - this time selecting ONLY the Microsoft drivers (since Driver Verifier didn't fault on the 3rd party drivers we have to check and see if it faults on the Windows drivers).

BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Oct 14 08:26:09.582 2010 (UTC - 4:00)
System Uptime: 0 days 0:20:06.189
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+79 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`05362d45 fffff880`05b896a8 fffff880`05b88f00
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Oct 14 08:02:45.773 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:41.380
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x3B
PROCESS_NAME:  baspin.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02cc0e0e fffff880`08161150 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Oct 14 06:41:29.501 2010 (UTC - 4:00)
System Uptime: 0 days 0:35:13.109
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonWrite+da0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Photoshop.exe
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0a1ff118 fffff880`0a1fe970 fffff800`02cc6105
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
My System SpecsSystem Spec
16 Oct 2010   #6

Windows 7 Professional 64bit
 
 

Hi,
I've tried rerunning the Driver tests with only MS drivers selected and now the machine wont even boot up. It also looked like it wouldn't create any dumps when it BSOD'd but upon creating the latest pull it added 2 from the 16th (today) so I've added them anyway but I don't think they are from when the verifier was running with the MS drivers on.

I had to use the system restore option to get the machine to boot up again.

What do I do now? I cant run windows / create dumps properly with MS drivers selected, and the other drivers throw no errors, even though it crashes.

I'm starting to think of just sending this crapbox back to Dell to get them to figure it out - or give me a new machine.



Thanks,
Daz
My System SpecsSystem Spec
16 Oct 2010   #7

Windows 7 Professional x64
 
 

Looks like Roxio is at fault here. Try removing it and see what happens.

...Summary of the Dumps:
Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Oct 16 07:54:38.703 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:17.327
BugCheck C9, {228, fffff88001062f74, fffff9800b712e10, 0}
*** WARNING: Unable to verify timestamp for iaStorV.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorV.sys
*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
Probably caused by : PxHlpa64.sys ( PxHlpa64+2f74 )
BUGCHECK_STR:  0xc9_228
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
My System SpecsSystem Spec
17 Oct 2010   #8

Windows 7 Professional 64bit
 
 

Hi,

Thanks Jonathan. I've un-installed Roxio now and will keep using the machine this morning to see if it falls over.

Roxio came pre-installed with the PC so, if it is the cause, its caused it to fail from day one and after the rebuilds too.

I'll report back soon. Thanks again.

Daz.
My System SpecsSystem Spec
17 Oct 2010   #9

Windows 7 Professional 64bit
 
 

Jonathan, in little over an hour of use (slightly more than normal) the machine has froze then rebooted. The only thing that was open was Firefox.

Any more ideas?

Daz.
My System SpecsSystem Spec
17 Oct 2010   #10
Microsoft MVP

 
 

Since running Driver Verifier with the Windows files gave problems, let's focus on the Windows installation:

- first run SFC.EXE /SCANNOW
Quote:
SFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.
If that doesn't fix it, then try a repair install of Windows 7: Repair Install

If that doesn't fix it, then backup your stuff and try a clean install of Windows 7: Clean Install Windows 7
Don't install anything extra (except for an antivirus) to see if that fixes things.
Make sure you have all Windows Updates.
Check Device Manager to ensure that all devices are recognized. If not, then post back here for advice.

If that doesn't fix it, then we've gotta assume that there's a hardware problem. I wonder if disconnecting the CD/DVD drives will help (both the power and data cables)? I also wonder about the rest of the storage sub-system due to the presence of iaStorV.sys in the dump file above.
My System SpecsSystem Spec
Reply

 Win 7 64bit BSOD/Freezes/Reboots




Thread Tools



Similar help and support threads for2: Win 7 64bit BSOD/Freezes/Reboots
Thread Forum
Laptop freezes, crashes, BSOD and reboots at random BSOD Help and Support
Win7 Ultimate 64bit BSOD and Freezes BSOD Help and Support
New Win 7 Installation suffering random BSOD, Freezes, Reboots BSOD Help and Support
Help stop the Window 7 64bit BSOD's (0XA, 0X50, 0X3B) and Freezes (Fir BSOD Help and Support
Windows 7 64bit BSOD and freezes BSOD Help and Support
Constant Freezes/Reboots, but no BSoD... 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 09:41 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33